Standards: Diagram
Overview
| Diagram |
The graphical representation of a set of elements, most often rendered as
a connected graph of vertices (things) and arcs (relationships). |
| Related Information: |
|
Topics
Background 
When you view a software system from any perspective using the UML you use diagrams to
organize the elements of interest. In a UML model, and in Rose, you can have as many
diagrams as you like each presenting some aspect of the model.
UML diagrams are used in two basic ways:
- to specify and create models and their elements
- to provide views from a particular perspective of the models and their elements
The main our purpose of the diagrams is to communicate the intent and design of the
model. To this end each diagram should serve some narrative purpose, not be overly
complex and be presented in an accessible manner. The purpose of these standards is
to facilitate these objectives. To this end many standard diagrams have been
introduced as part of these standards (See Standard Diagrams below for details)
Diagramming Standards
Standards are provided for the following diagram types (those that are used during
Analysis and Design):
Class Diagram
Interaction Diagrams
Sequence Diagram
Collaboration Diagram
State Diagram
Standard Diagrams
A set of standard diagrams have been defined for use when documenting packages and
collaborations. See Standards: Standard Diagrams
for more details.
Stereotypes
N/A
Examples
None |
