Lesson 11

The UML is a major step toward the standardization of software development. The standard has received widespread support from tool vendors and customers alike.
The UML includes specifications for nine different diagrams used to document different views of a software solution from project inception to installation and maintenance. The specifications define the elements of each model, how the models are assembled, and how they can be extended.

The UML standard does not prescribe a process for applying the diagramming notation. Various processes or methods are being proposed, including a "unified modeling process" being published by Rational Software.
Although this process bears the same name, it is not part of the UML standard approved by the OMG. Each user should select and apply the method or methods most appropriate for their particular application domain.

The views supported by the standard include the

1. use case view,
2. the logical view,
3. the component view, and
4. the deployment view.

1. The use case view employs the use case model to capture user requirements.
2. The logical view uses class and object diagrams, sequence and collaboration diagrams, activity diagrams, and statechart diagrams to capture the conceptual design of the software solution.
3. The component and deployment views each use a corresponding diagram to model the physical implementation of the solution.

In the following modules, you will have opportunities to use each of the diagrams in the UML. With each diagram description, we will identify the relationships among the models.

This module introduced you to the following terms:

1. Component view:A view dedicated to the description of software implementation units; may be used in combination with the deployment view.
2. Deployment view:A view dedicated to the description of hardware architectures; may be used in combination with the component view.
3. Logical view:A view dedicated to the description of design options for a software solution.
4. Metamodel:1. The specification of a language for describing object-oriented models. 2. A model that describes the elements, and the relationships between those elements, that make up a specified domain.
5. Model element:The smallest unit of semantic definition in a model. The same model element may appear in multiple diagrams. For example, an event appears in sequence diagrams, collaboration diagrams and statechart diagrams. In all three contexts it provides the same semantic information.
6. Object-Oriented Analysis and Design Task Force: The group assigned by the OMG to generate and oversee the RFP for a metamodel for object design.
7. Object Management Group:The standards group currently overseeing the development and acceptance standards related to object-oriented software development.
8. Package:A general-purpose mechanism for grouping models and model elements, typically by similar functions or uses within the context of a system. See also: Component
9. Stereotype:A UML extension that provides a means of further describing or qualifying a model element without defining its implementation.
10. Use case view:A view dedicated to the description of user requirements.
11. View:A grouping of diagrams for a particular function in the overall process for developing software.

In the next module, the use case view will be explored.

Click the Quiz link below to check your knowledge with a short, multiple-choice quiz.
UML Software - Quiz