UML22 — UML 2.2 scope statement

Current Scope section in UML 2.1.1 Infrastructure
=================================================

This UML 2.1.1: Infrastructure is the first of two complementary
specifications that represent a major revision to the Object Management
Group's Unified Modeling Language (UML), for which the previous current
version was UML v1.5. The second specification, which uses the
architectural foundation provided by this specification, is the UML 2.1.1:
Superstructure. The UML 2.1.1: Infrastructure defines the foundational
language constructs required for UML 2.1.1. It is complemented by UML
2.1.1: Superstructure, which defines the user level constructs required for
UML 2.1.1.

Current Scope section in UML 2.1.1 Superstructure
=================================================

This Unified Modeling Language: Superstructure is the second of two
complementary specifications that represent a major revision to the Object
Management Group's Unified Modeling Language (UML), for which the most
current version is UML v2.0. The first specification, which serves as the
architectural foundation for this specification, is the Unified Modeling
Language: Infrastructure.

This Unified Modeling Language: Superstructure defines the user level
constructs required for UML 2. It is complemented by Unified Modeling
Language: Infrastructure which defines the foundational language constructs
required for UML 2. The two complementary specifications constitute a
complete specification for the UML 2 modeling language.

Proposed Scope section
======================

This specification defines the Unified Modeling Language (UML), revision 2.
The objective of UML is to provide system architects, software engineers,
and software developers with tools for analysis, design, and implementation
of software-based systems as well as for modelling business and similar
processes.

The initial versions of UML (UML 1) originated with three leading
object-oriented methods (Booch, OMT, and OOSE), and incorporated a number
of best practices from modelling language design, object-oriented
programming and architectural description languages. Relative to UML 1,
this revision of UML has been enhanced with significantly more precise
definitions of its abstract syntax rules and semantics, a more modular
language structure, and a greatly improved capability for modelling
large-scale systems.

One of the primary goals of UML is to advance the state of the industry by
enabling object visual modeling tool interoperability. However, to enable
meaningful exchange of model information between tools, agreement on
semantics and notation is required. UML meets the following requirements:

• A formal definition of a common MOF-based metamodel that specifies the
  abstract syntax of the UML. The abstract syntax defines the set of UML
  modelling concepts, their attributes and their relationships, as well as
  the rules for combining these concepts to construct partial or complete UML
  models.

• A detailed explanation of the semantics of each UML modelling concept.
  The semantics define, in a technology-independent manner, how the UML
  concepts are to be realised by computers.

• A specification of the human-readable notation elements for representing
  the individual UML modelling concepts as well as rules for combining them
  into a variety of different diagram types corresponding to different
  aspects of modelled systems.

• A detailed definition of ways in which UML tools can be made compliant
  with this specification. This is supported (in a separate specification)
  with an XML-based specification of corresponding model interchange formats
  (XMI) that must be realised by compliant tools.

No Data Available