What is and is not included in the UML specification
Define Scope of UML specification.
The UML has a more limited scope than people often assume.
The OMG's Request for Proposal was primarily concerned with the development of a metamodel
for OO modeling.
The metamodel was expected to define an underlying language that could be transmitted between products that support visual modeling without constraining the vendors to a particular
for developing the models.
This metamodel defines the underlying meaning of each element used in visual modeling and the relationships among them. For example, in the UML metamodel,
you will find a detailed description of a class; its component parts, attributes, and operations; and the relationships among them. You will not find a process for finding classes or for evaluating a "good" class specification versus a "bad" class specification. Nor does the metamodel define the visual icons used for each model element .
Nine diagrams are defined in the UML metamodel
Nine diagrams are defined in the UML metamodel. Each is fully described in the metamodel using class diagrams and textual narrative. The net result for most of us is a set of standardized visual models that may be used with many different modeling processes. The process chosen may vary widely among industries, applications, and practitioners.
The key to the UML is understanding that you can use it with any number of different development methods, process controls, and quality measures. The rest of this course is devoted to explaining the purpose and definition of each UML diagram and their relationships to one another. This understanding should prepare you to apply the models in your own unique environment.
In the next lesson, how UML is being refined and extended to provide the most flexibility and applicability will be discussed.