UML Weekend Crash Course™ - To Parent Directory

APPENDIX
A
Answers to Part Reviews
Friday Evening Review Answers
1. The UML is a diagramming notation standard. The UML does not include anything
about how to build software. The UML does not include anything about how to perform
analysis and design. It only specifies the diagramming models used to capture
the results of these tasks. Finally, the UML is not proprietary.
2. The UML was the merger of most of the current object-oriented methods. Elements
from nearly all the leading methods have been included in the UML. Although
Booch, Rumbaugh, and Jacobson took an aggressive stance to push the development
of the UML and even now play the part of stewards of the documentation, many
others joined them. The OMG is the coordinating standards representative only.
3. The Object-Oriented Analysis and Design Task Force RFP asked for a metamodel for
specifying software solutions. The RFP specifically avoided methodologies. The
visual notation is actually left up to the vendors, whereas the underlying element
definitions (the metamodel) are required to be consistent among vendors.
4. The UML may be extended by using stereotypes to qualify element descriptions.
Stereotypes are defined in the UML and have a suggested notation for their use.
You are not allowed to alter the standard; otherwise, it would not be a standard.
The set of diagrams is part of the specification. To create a new one would be outside
of the UML standard. Although you’re allowed to choose your own icons for
existing elements, you may not arbitrarily add your own.
5. The metamodel includes definitions of the modeling elements. The UML does not
specify usage at all. The specification defines function and relationships among
elements only. The UML only suggests a visual icon for each element, leaving the
final choice to the vendor. The UML is explicitly independent of any programming
language used to implement the models.
6. The three elements are the process, the notation, and the guidelines and rules. The
process describes how to go about the development effort. The notation defines
the appearance and meaning of the work products. The guidelines and rules define
how you will assess the quality of the work products and the process.