Creating models and diagrams
You can use models and diagrams to visually represent a
system that you want to build; to build a common understanding of
a system; to develop, verify, and communicate a system's architecture;
and to generate code.
Before you begin
IBM® DevOps Model Architect supports UML 2.2. For detailed information about UML 2.2, see the specification that is available on the Object Management Group (OMG) website.
- Creating UML models
Depending on the complexity of the system or application that you are modeling, you might choose to create a single model or several models. You can create empty models or use an existing model or model template as a starting point. - Creating and populating UML diagrams
You can create UML diagrams to visually represent and develop the elements of a system or application. You can create diagrams and add elements and relationships to them. You can also add supplemental items to the diagram to provide additional information to the diagram. - Sketching simple UML diagrams
Sketches are simple, independent diagrams. Sketches can illustrate any business process or technology-related concept at a high level of abstraction. - Creating use-case diagrams
You can model the required behavior of a complete system, or portions of a system, with use-case diagrams. - Creating activity diagrams
In UML modeling, you can use activity diagrams to model the sequence of actions that must occur in a system or application, or to describe what happens in a business process workflow. - Creating class diagrams
Class diagrams model the static structure of a package or of a complete system. - Creating object diagrams
In UML, object diagrams model instances of the classifiers in a system and the relationships between those instances at a point in time. You can use object diagrams to explore behavior scenarios, illustrate a sample configuration of objects, or test your class diagrams to verify the rules and definitions. - Creating sequence diagrams
In UML models, an interaction is a behavior that represents communication between one or more participants. A sequence diagram is a UML interaction diagram that models the messages that pass between participants, such as objects and roles, as well as the control and conditional structures, such as combined fragments. You can create new sequence diagrams, populate existing sequence diagrams with source elements, add lifelines, messages, and combined fragments to sequence diagrams. - Creating communication diagrams
In UML models, an interaction is a behavior that represents the communication between one or more participants. A communication diagram is a type of UML interaction diagram that illustrates the flow of messages between the objects in an interaction. You can add and modify lifelines, message pathways, and messages in communication diagrams. - Creating composite structure diagrams
In UML models, a composite structure diagram shows the internal structure of classifiers and collaborations by using parts, ports, and connectors. You can use this type of diagram to visually explain the composite parts of the containing classifier and to define the behavior and communication between the parts. - Creating state machine diagrams
You can use state machine diagrams to illustrate the behavior of classes, collaborations, components, nodes, operations, use cases, or entire systems. - Creating component diagrams
You can use component diagrams to model the software architecture of a system. Component diagrams provide a view of the physical software components in the system, their interfaces, and their dependencies. - Creating deployment diagrams
You can use deployment diagrams to model the physical layout or topology of a system. Deployment diagrams describe the configuration of runtime processing nodes and the artifacts that are deployed on them. - Creating and managing timing diagrams
Timing diagrams are similar to sequence diagrams, but focus on the timing of the elements in the model. - Creating and managing interaction overview diagrams
An interaction overview diagram shows the flow of control between different interactions. You can reference interactions and provide the diagram flow between the different interactions.
Feedback