Wednesday, July 11, 2007

UML Diagrams 2.0

Model Management diagrams

Include Packages, which are used to represent Subsystems, Models, and more.
A package is the UML equivalent of a directory or folder.
It is a place to store diagrams.
when packages are combined in a diagram, it is expressly to model the relationships between the packages.

dependency - a specific type of relationships. It means that one element needs help from another element.
The help may be functionality or data provided by another element.


Structural diagrams

Includes the Class diagram, Object diagram, Composite Structural diagram, Component diagram, Deployment diagram, and the Combined Component and Deployment diagram.

Illustrates the static features of a model.

A Class defines the behaviors that type of object can provide.
An association defines the type of relationships that objects can participate in.
A Deployment diagram models pieces of h/w (and people) that can perform work.
Components define pieces of s/w and procedures that need to be deployed to processors.

Class diagram
Is at the heart of the object modeling process.
It models the definitions of resources essential to the proper operation of the system.
Class diagram models the resources used to build and operate the system.
Resources represent people , materials, information, and behaviors.
A class diagram represented by 3 predefined compartments: name, attribute, and operations.

Class diagram models resources and relationships between resources.

Object diagram
models facts or examples.
It is useful for modeling test cases to see whether the Class diagram is correct and complete.

Composite Structure diagram
It visually represent the parts of a class, component, or collaboration, including the interation points(called ports) used to access features of the structure.
Reveals the design of a complex component.
It also model collaborations.

collaboration - describes a behavior, the resources used to perform the behavior, and the roles the participating resources assume during the behavior.

Component diagram
It represents real software in the implementation environment.
They reveal software configuration issues throught the dependency relashionships.

It models the implementation view.

Deployment diagram
Models the hardware of the implementation environment.
Each node on a Deployment diagram typically represents one type of h/w.
A node may also represent a human being or organizational unit, the function that a function can perform. Nodes are classes in that respect.

Combined Component/Deployment diagram
It shows the components installed on nodes.



Behavioral Diagram

It describe how the resources modeled in the Structural diagrams interact and how they each execute their capabilities.
Includes Use Case diagram, Activity diagram, Interaction diagrams, State machine diagram and Protocol State Machine diagram.

Use Case diagram
Models user's expectation for using the system.
The people and systems that interact with the target system are called actors.

Activity diagram
It models logic-any logic-from workflow to use cases to methods.
It represent the logic required to implement system behaviors.


Interaction diagrams

It includes the Sequence, Communication, Interaction Overview, and Timing diagrams.

Sequence diagram
Identifying interactions between objects over time. ie the messages exchanged between objects.
An interface is an operation signature on the class to which the receiving object belongs.

Communication diagram
They identify the objects that participate in an interaction.

Interaction Overview diagram
model the flow of logic in a series of interactions.
Block of interactions called Interaction Occurances

Timing diagram
provides a view of state changed that emphasizes the importance of time and timing.

State Machime diagram
Represents a single object.
The diagram shows how external stimuli cause changes in the object over its lifetime.

Protocol State Machine diagram
show only the transactions that trigger the state changes.
The State Machine defines what is possible while an event causes a change.
The Protocol State Machine defines what is legal.

No comments: