{"title":"Business object design and implementation workshop","authors":"J. Sutherland","doi":"10.1145/260094.260274","DOIUrl":null,"url":null,"abstract":"2. Abstract The OOPSLA Workshop on Business Object Design and Implementation was jointly sponsored by the Accredited Standards Committee X3H7 (Object Information Management) and the Object Management Group (OMG) Business Object Management Special Interest Group (BOMSIG). A variety of papers were presented on business object architectures, reusable component requirements, specification of distributed systems, and patterns which should be used in design of business systems. The Workshop concluded that reengineering and rapid delivery of new business functionality would require significant changes in current development tools and methodologies. Software development has traditionally supported tightly coupled components built with loosely coupled analysis, design, and implementation methods. New systems will require that loosely coupled, reusable, plug compatible components be constructed using a tightly coupled development method that combines business process reengineering, analysis, design, implementation, and reusable component market delivery systems similar to today’s custom IC chip industry. 2.1 X3H7 Object Information Management In 1994, the X3H7 Object Information Management Technical Committee projected that over the next decade, more than 80% of new object-oriented software systems would be built in three objectoriented languages (Smalltalk, C++, and 00 COBOL) and communicate through a Object Request Broker to four primary external environments (SQL databases, Object Databases, Microsoft OLE/COM, and CORBA objects). Interoperability of large grained objects existing in these environments was identified as a core activity in the standards process.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"4 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"33","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/260094.260274","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 33
Abstract
2. Abstract The OOPSLA Workshop on Business Object Design and Implementation was jointly sponsored by the Accredited Standards Committee X3H7 (Object Information Management) and the Object Management Group (OMG) Business Object Management Special Interest Group (BOMSIG). A variety of papers were presented on business object architectures, reusable component requirements, specification of distributed systems, and patterns which should be used in design of business systems. The Workshop concluded that reengineering and rapid delivery of new business functionality would require significant changes in current development tools and methodologies. Software development has traditionally supported tightly coupled components built with loosely coupled analysis, design, and implementation methods. New systems will require that loosely coupled, reusable, plug compatible components be constructed using a tightly coupled development method that combines business process reengineering, analysis, design, implementation, and reusable component market delivery systems similar to today’s custom IC chip industry. 2.1 X3H7 Object Information Management In 1994, the X3H7 Object Information Management Technical Committee projected that over the next decade, more than 80% of new object-oriented software systems would be built in three objectoriented languages (Smalltalk, C++, and 00 COBOL) and communicate through a Object Request Broker to four primary external environments (SQL databases, Object Databases, Microsoft OLE/COM, and CORBA objects). Interoperability of large grained objects existing in these environments was identified as a core activity in the standards process.