Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications最新文献

{"title":"The Navigation Toolkit project revisited","authors":"Stephen W. Strom, William F. Rich, Matthew T. Verona","doi":"10.1145/260094.260234","DOIUrl":"https://doi.org/10.1145/260094.260234","url":null,"abstract":"report is a follow-on to “The Navigation Toolkit,” which was presented at OOPSLA ‘94. The Navigation Toolkit was the first fully objectoriented project within our company. and was “completed” in May 1994. But its impact since then has been enormous. Its success was used as the primary hard data point for selling a much larger follow-on project to NASA. The basic Toolkit architecture has been selected as the architecture for all future systems, but changes will clearly be needed to expand into new domains. The Navigation Toolkit itself continued on in a somewhat independent M&M mode. Users gained some capability over existing tools (such as the ability to model any number of space vehicles) and lost others (such as the ability to model tethered satellites and other, similar forces). The lost capabilities have resulted in user frustration, and the new capabilities have not yet been exploited. Another influence on the evolution of the Toolkit is the continued slow-down in the aerospace business. This is leading our company to seek new business opportunities, and improved flexibility in software could be a key to success in this area. 1. Scaling up is hard to do The Toolkit was built with a 7person. mostly highly experienced team. As reported in our original experience report, despite the introduction of new technology, etc., the team performed nearly as promised, achieving an overall productivity rate of 300 SLOG/Person Month and low defect density rates. The success of the Toolkit (and an object-based C predecessor, built by the same team) was the primary hard data point used to sell the Reusable Object Software Environment, or ROSE, to NASA. ROSE is a proposed major rewrite of most of the design and analysis software used for space shuttle trajectory operations. Rockwell management was concerned that the kind of software development organization which proved successful for Toolkit development would not scale up to the full ROSE project. In particular, management felt it could not count on the availability of highly skilled developers and chose instead to rely on minimally-skilled developers (90 days of training). It also needed to work under an accelerated development schedule, meaning it needed a larger development team. ‘Current address: TRW Systems Integration Group, Rosslyn, Virginia 2Current address: McDonnell Douglas Aerospace Houston Division Addendum to the Proceedings OOPSLA ‘95 61 A raw size comparison of the two projects is contained in the following table: Code produced (KSLOC) Nav Toolkit ROSE actual s proposals","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129593502","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Performance of an OODB in an online 7×24×365 manufacturing operation","authors":"C. Gardner","doi":"10.1145/260094.260229","DOIUrl":"https://doi.org/10.1145/260094.260229","url":null,"abstract":"A online reporting application which is used to report and schedule material on factory floors is described in terms of the realtime updates and scheduled maintenance. Performance issues for these parts of the system are described by the various parts. The online feeds are described in terms of tuning each part according to function. DBA type functions such as clustering of data and backups are described. The best tuning came from breaking the functions into definable parts which could then be tuned according to need. Factors which affected each part of the system are described.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"120 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122590444","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Patterns for decision making in architectural design: workshop summary","authors":"G. Meszaros","doi":"10.1145/260094.260267","DOIUrl":"https://doi.org/10.1145/260094.260267","url":null,"abstract":"This contribution describes the OOPSLA-95 workshop entitled “Patterns in Architectural Decision Making.” In Part 1, we describe the process we followed during the workshop. In Part 2, we describe some of the key work-products of the workshop including an overview of the common process the workshop participants follow, as well as a number of common Architecture Patterns discovered in the participants’ submissions.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127553438","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Subjectivity in object-oriented systems: workshop summary","authors":"W. Harrison, H. Ossher, H. Mili","doi":"10.1145/260094.260261","DOIUrl":"https://doi.org/10.1145/260094.260261","url":null,"abstract":"Subjectivity in object-oriented systems is a new research area. At this, the first workshop in this area, there was much discussion of fundamental concepts and issues, as well as of perceived needs for subjectivity and models for realizing it. The discussion is summarized here, and a list of issues that were identified during the workshop is presented.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132757436","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Object-oriented real-time systems: report on the workshop","authors":"Bob Wilhelm, John Gilbert, M. Fayad","doi":"10.1145/260094.260282","DOIUrl":"https://doi.org/10.1145/260094.260282","url":null,"abstract":"Issue 2: The Workshop on Object-Oriented Real-Time Systems has been conduced each year at OOPSLA since 1988 with a variety of formats. In this year’s workshop, participants submitted position papers on a broad range of subjects, but were all asked to show the relevance of their work to three critical issues in 00 real-time systems: dealing with time constraints; the roles of reactive versus scheduled behavior; and appropriate models of concurrent behavior. All position papers were presented and discussed during the workshop, followed by a round-table discussion of the state of the art regarding the three focus issues.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"56 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131800410","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Business object design and implementation workshop","authors":"J. Sutherland","doi":"10.1145/260094.260274","DOIUrl":"https://doi.org/10.1145/260094.260274","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.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131899755","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Metamodeling in OO: OOPSLA'95 workshop summary","authors":"H. Mili, F. Pachet, I. Benyahia, F. Eddy","doi":"10.1145/260094.260257","DOIUrl":"https://doi.org/10.1145/260094.260257","url":null,"abstract":"The purpose of this workshop was to explore metamodeling concepts in the context of object-oriented software development, from a methodolog-ical perspective, namely: 1) Exploring the additional modeling constructs that are needed to model information at several levels of abstraction, 2) Exploring changes to modeling procedures/heuristics that are needed to build object meta-models and integrating them with object models, 3) Exploring the effects of such changes on design and implementation (e.g. reflective languages, metaprogramming, etc). As is usual (and healthy) in such events, the papers we received did not fit in exactly with the advertised agenda, with its heavy emphasis on methodological (analysis and design) aspects, and the proposed agenda was as much the result of what the organizers wanted discussed as it was a result of what \"par-ticipants\" were willing to discuss! That result is shown next. We first attempt to define metamodel-ing in the context of object-oriented software engineering, identifying major issues. Next, we discuss each one of those issues in some detail. Object-oriented structural modeling uses classes to represent the structure of similar application objects, and associations to represent patterns of connections between application objects. Applications where the representation of objects needs to be queried or otherwise manipulated need to explicitly represent the representation of objects [Diaz,1994]; we call the representation of the representation of application objects metamodeling. The need for metamodels is more frequent than one might first think. In relational database modeling, meta-data consists of table descriptors, which are system tables (system dictionary) describing the data tables (their columns, domains for the columns, etc) and integrity constraints, which, by and large, are semi-declarative constructs to be executed during database updates. [1] A typical computer-assisted manufacturing application needs two levels of abstraction: 1) one level to represent bills of material, e.g., describing the compositions of different manufactured products, 2) a second level to describe actual manufactured products in stock. Bills of material are representations of manufactured products. However, to the extent that they can be created, consulted, and modified, they too need to be represented by a construct that describes their structure; these are called metaclasses. When not a part of the problem (e.g. a bill of materials and inventory application), metamodeling is part of the solution: metamodeling is an abstraction mechanism in the sense that, much like classification, it enables us to differentiate identity-dependent behavior from state-dependent behavior, hence making some sense of the variations in …","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"89 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122202354","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"OO process and metrics for effort estimation","authors":"D. Champeaux, S. Horner, G. Miller","doi":"10.1145/260094.260268","DOIUrl":"https://doi.org/10.1145/260094.260268","url":null,"abstract":"Software development remains difficult to plan. Object-orientation has thus far not changed the picture. However due to the greater continuity in 00 across the life-cycle (objects everywhere), there is hope that 00 technology may improve the predictability of 00 projects. Last year’s Pragmatic and Theoretical Directions in Object-Oriented Software Metrics workshop found a division between the two camps: theoretic and pragmatic. Out of the pragmatic camp came an interesting revelation: software development remains difficult to plan.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129465793","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Design and construction of large-scale components: main insights of OOPSLA'95 workshop 10","authors":"George Brown, Brad Kain","doi":"10.1145/260094.260281","DOIUrl":"https://doi.org/10.1145/260094.260281","url":null,"abstract":"The main insights from this workshop centered on the expectations for realizing large-scale systems built of software components. A secondary consideration was that the implementations were compliant with the OMG Architecture. It was generally accepted that a pre-requisite for large-scale components is a common infrastructure for sharing components in a distributed environment. Within this context, a distinction should be made between small and large components. The component model definition was assumed to be distinct from an object model. There was recognition of the need for heterogeneous component interaction and integration. Current IDL was considered insufficient to express both the semantics of components and the configuration syntax associated with components within components as part of a good model. There was general agreement that new cost models are needed. If efforts to promote software component technology are successful, we will be faced with how to do pricing. It was emphasized that bits and atoms are different and our models for selling products may not apply. For example, one possibility is that software components are given away free, and payback of components occurs through integration services. There needs to be better understanding of break-even cost factors of component reuse. Clearly, if you only share a component with one other, then building the component may not be cost justified due to maintenance cost, etc. Because of the uncertainty in cost factors, it was asserted that development organizations should at least consider the cost and risk of not enabling “software components”.","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132463021","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Workshop on design patterns for concurrent, parallel, and distributed object-oriented systems","authors":"D. Kafura, R. G. Lavender, D. Schmidt","doi":"10.1145/260094.260266","DOIUrl":"https://doi.org/10.1145/260094.260266","url":null,"abstract":"The workshop was organized to stimulate and focus research on design patterns for concurrent, parallel, and distributed (CPD) object-oriented systems. Workshop participants spent a day examining design patterns that capture the static and dynamic structures of successful solutions to problems known to arise when building CPD systems. The goal of the workshop was to document and collect common design patterns to facilitate the practical construction of CPD systems. The suggested topics for papers included:","PeriodicalId":286350,"journal":{"name":"Addendum to the proceedings of the 10th annual conference on Object-oriented programming systems, languages, and applications","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1995-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130663068","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}