EVOLUTION, NOT REVOLUTION.

Saved in:
Bibliographic Details
Title: EVOLUTION, NOT REVOLUTION.
Authors: Selic, Bran1 bselic@rational.com, Ramackers, Guus2 Guus.Ramackers@oracle.com, Kobryn, Cris3 Cris.Kobryn@telelogic.com
Source: Communications of the ACM. Nov2002, Vol. 45 Issue 11, p70-72. 3p.
Subjects: Unified modeling language, Object Management Group Inc., Object-oriented methods (Computer science), Technical specifications, Computer architecture, Computer science
Abstract: Practitioners and researchers of Object Management Group Inc. (OMG) has adopted Unified Modeling Language (UML) ever since OMG's foundation in 1997. There has been a strong pressure to improve the effectiveness of UML and provide it with a multitude of new features. The original UML specifications, culminating with UML1, were based on input from a relatively large team of experts from different companies and with diverse backgrounds. It was inevitable that such diversity would result in ambiguities and semantic overlaps that have since prompted many questions about the specific meaning of certain UML concepts. A primary requirement for the future UML2 specification is their elimination by providing a precise definition of the semantics of each UML concept, including its dynamic semantics. UML2 must consolidate UML's existing features rather than add a multitude of new and changed ones. This consolidation must yield greater precision and better modularization, both crucial to achieving objectives of OMG's Model Driven Architecture.
Database: Engineering Source
Description
Abstract:Practitioners and researchers of Object Management Group Inc. (OMG) has adopted Unified Modeling Language (UML) ever since OMG's foundation in 1997. There has been a strong pressure to improve the effectiveness of UML and provide it with a multitude of new features. The original UML specifications, culminating with UML1, were based on input from a relatively large team of experts from different companies and with diverse backgrounds. It was inevitable that such diversity would result in ambiguities and semantic overlaps that have since prompted many questions about the specific meaning of certain UML concepts. A primary requirement for the future UML2 specification is their elimination by providing a precise definition of the semantics of each UML concept, including its dynamic semantics. UML2 must consolidate UML's existing features rather than add a multitude of new and changed ones. This consolidation must yield greater precision and better modularization, both crucial to achieving objectives of OMG's Model Driven Architecture.
ISSN:00010782
DOI:10.1145/581571.581595