UML 2.0 Full Suite; MetaObjects Standards Complete

Modeling may get easier for developers to implement and support since the OMG completed its work on defining UML 2.0 and MetaObjects 2.0 standards. See how the work aims to expedite use and deployment of model-based application development, especially for object- and XML-based applications in Java, .NET and CORBA-based legacy environments.

Tags: UML, Developers, Modeling, Support, UML Tools, Standards, Upgrade,

Modeling may get easier for developers to implement and support, as the full suite of upgraded standards was adopted last week by the Object Management Group, a collection of more than 50 software vendors focused on object and XML-based modeling.

In specific, OMG members recommended adoption of the final piece to the major UML 2.0 (Unified Modeling Language) upgrade. This last piece, called the Superstructure specification, completes the definition of the UML 2.0, which has been in its final phase since this spring. The UML 2.0 recommendations for the other three (3) main components -- Infrastructure, Object Constraint Language and Diagram Interchange Protocol -- were done in March.

In addition, OMG recommended new MetaObject Facility (MOF 2.0) specifications for the MOF Core and XML Metadata Interchange (XMI) to update the repository foundation upon which UML tools are built. According to an OMG statement, "Alignment of the UML 2.0 metamodel with the MOF metamodel will simplify model interchange via XMI, and cross-tool interoperability." More than 50 companies participated in the UML upgrade.

The upgraded UML standard now has the following features:
  • An extension mechanism allows modelers to add their own metaclasses, making it easier to define new UML Profiles and to extend modeling to new application areas.
  • Built-in support for component-based development eases modeling of applications realized in Enterprise JavaBeans, CORBA components or COM+.
  • Support for runtime architectures allows modeling of object and data flow among different parts of a system.
  • More accurate and precise representation of relationships improves modeling of inheritance, composition and aggregation, and state machines.
  • Better behavioral modeling improves support for encapsulation and scalability, removes restrictions on mapping of activity graphs to state machines and improves sequence diagram structure.
  • Improvements to the language simplify syntax and semantics, and better organize its overall structure.

More UML Developer Resources