From UML Models to System Interfaces

The UML models in the registry are platform-independent models. They may be realised on various different technology platforms. For example one UML model could be realised both as a relational database and as XML Schemas. In one case the UML classes and attributes could map to the tables and columns of a database, while in the other case the classes and attributes could map to XML Schema types and elements.

Where a system interface description has been submitted to the registry with details for a specific technology platform, we have included both the platform-independent UML model and a platform-specific mapping document which describes what the UML model elements represent in terms of the specific technology platform.

Usually the mapping from UML to a specific technology should be direct and simple, but in some cases the mapping could introduce more significant refinements to the model. This happens when an abstract model is adapted: to follow style rules for a specific platform, to fit limitations of a platform, or to produce an interface that is optimised for a specific platform.

When viewing registry contents, users should bear in mind that they are viewing platform-independent models that define semantics; for full system interface details these models must be combined with the platform-specific mappings. The platform-specific mappings, where specified, can be found in a "tag", near the bottom of the page for the top-level package of each model.


Current Platform-Specific Mappings

General

System Specific

Externally Defined

Highways Agency