When you model complex systems, you can use modeling diagrams to represent them from several different perspectives. Modeling diagrams contain diagram elements that graphically represent the abstract model elements in your model.
The following table describes the specific modeling diagrams that the Rational modeling products support, and explains to which category they belong.
Diagram | Description |
---|---|
Activity | An activity diagram is a type of a UML behavioral diagram that shows the steps or tasks that constitute a process. An activity diagram is similar to a flowchart and provides a view of the flow between activities in a process. Activity diagrams model the dynamic parts of a system and show how activities interact with each other. |
Browse | A browse diagram is a temporary, non-editable,
non-UML diagram that the product automatically creates from user
input. You can use a browse diagram to navigate through a model
to view the details of its model elements. For example, you can
browse a specific class in your diagram and see the relationships
that it has with other model elements. You can then select one of
these model elements and open a browse diagram to view its relationships. You cannot save a browse diagram, however, you can convert a browse diagram into a modeling diagram using the Save As command. A browse diagram uses auto-layout algorithms and provides user interaction to navigate through the model. Because the product computes the layout automatically, you can collapse or expand parts of the browse diagram. |
Class | A class diagram is a UML structural diagram.
Depending on the complexity of a system, you can use a single class
diagram to model the entire system, or you can use several class diagrams
to model the components of the system. Class diagrams are the blueprints of your system. Use class diagrams to model the building blocks (or objects) that make up the system, to display the relationships between the objects, and to describe what those objects can do. |
Communication | A communication diagram is a new UML 2.0 behavioral diagram. In UML 1.4, it was named a collaboration diagram and had a different notation. A communication diagram shows the interaction between the instances (objects or roles) associated with a lifeline and the passing of messages. |
Component | A component diagram is a UML structural diagram that provides a view of the physical software components in a software system, their interfaces, and their dependencies. Components are physical, replaceable parts of a system, such as executables, libraries, software components (for example, ActiveX or JavaBean components), documents, databases, and files. A component diagram can depict all or some of the components in a system. |
Composite structure | A composite structure diagram is a UML structural diagram that defines the parts of a system and the communication relationships between them. |
Deployment | A deployment diagram is a UML structural diagram that models the physical nodes where your system executes (or that support execution), and the physical connections and relationships of the nodes. Physical nodes can include common devices (such as servers and workstations), as well as other devices that support the runtime environment of a system. Deployment diagrams document the physical relationships between the software and hardware components in the system, and the physical distribution of the processing. |
Freeform | A freeform diagram is a non-UML diagram that
can contain a combination of UML and non-UML shapes such as classes,
components, and geometric shapes. You can use freeform diagrams
to show any part of your software system early in the software development process.
For example, in a freeform diagram, you can use the geometric shapes
(such as ovals, rectangles, and triangles) to create an organizational
chart for your software development team. You can create some parts
of your model or diagram with UML shapes and create other parts
with shapes that address your specific needs. You can later evolve
the diagrams to be compliant with UML. Note: You cannot
add model elements that belong to UML state machines, activity graphs,
and interactions to freeform diagrams.
|
Interaction overview | An interaction overview diagram is a new UML 2.0 behavioral diagram. An interaction diagram defines interactions and is a variant of the activity diagram that emphasizes the high-level control flow. Interaction overview diagrams focus on the overview of the flow of control where each node can be an interaction diagram. |
Object | An object diagram is a UML structural diagram that is similar to a class diagram except that instead of dealing with classes, it shows objects that are instances of classes. |
Package | A package diagram is a UML structural diagram that shows how model elements are organized into packages and the dependencies between them including package imports and package merges. |
Sequence | A sequence diagram is a UML structural diagram that provides a view of the chronological sequence of messages between instances (objects or classifier roles) that work together in an interaction or interaction instance. A sequence diagram consists of a group of instances (represented by lifelines) and the messages that they exchange during the interaction. |
State machine | A state machine diagram, which was named a state chart diagram in UML 1.4, is a UML behavioral diagram. State machine diagrams model the dynamic behavior of individual class objects, use cases, and entire systems, and are one of the diagrams used to realize use cases. There are two types of state machines in UML 2.0: behavioral and protocol state machines. The keyword {protocol} is placed beside the name of the state machine to indicate that it is a protocol state machine. |
Timing | A timing diagram is a new UML 2.0 behavioral diagram that shows the change in state or other condition of a lifeline (representing a classifier instance or classifier role) over time. |
Topic | A topic diagram is a non-editable, non-UML
diagram that provides a quick way to show existing relationships
between elements. You can use a topic diagram to define a query
and to display and persist the results from that query. For example,
you can create a hierarchy topic diagram that you can then update
to always show the hierarchy for a specific class. You can also
use this diagram to show traceability information. A topic diagram is similar to a browse diagram except that you can save the topic diagram in the model and you can reopen it. The topic diagram editor shows a topic diagram view that you can refresh to reflect the latest elements in a project. |
Use case | A use case diagram is a UML behavioral diagram that focuses on the requirements of a system and describes the high-level functions and scope of a system. These diagrams identify the users and show interactions between the system and the user. Use case diagrams can depict an entire system or only significant portions of the system. The use cases and actors in use case diagrams describe how a user uses a system, not how the system operates internally. |