vpadmin, Author at Visual Paradigm Community Circle

State Diagram Example – Phone Call

A state diagram is a graph whose node are state and whose directed arcs are transition between states which describes sequence caused by event sequences. A state diagram typically models the common behavior of a class

In this state diagram example, the phone line is idle at the start of a call. When the phone is removed from the hook, it emits a dial tone and can accept the dialling of digits. Upon entry a valid number, the phone system tries to connect the call and route to the proper destination. The connection can fail if the number or trunk are busy. If the connection is successful the called phone begins ringing. When put on hook again, the phone line will go back to idle.

Import into your Project

State Diagram – A Toaster (Initial and Extended State Diagram)

Here is a state machine diagram example.

Suppose you're designing a toaster. You would build a plenty of UML diagrams, but here only state diagrams will be of our interest. What are the steps of making a toast? First of all we must turn on the toaster, put in the bread and wait for several minutes to bake it. The initial state diagram is shown here.

But this is not the final state diagram. To prevent burning out the bread, heater of the toaster must produce heat in temperature interval (upper and lower temperature limits). For this purpose thermometer measures the temperature of heater, and when the upper limit of temperature is reached then heater must go into idle state. This state resists until heater's temperature decreases to lower limit, and then working state is again aimed.

Import into your Project

Order Processing

Import into your Project

Web Store

Here is a component diagram example. Component diagram shows components, provided and required interfaces, ports, and relationships between them. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA).

The following nodes and edges are typically drawn in a component diagram: component, interface, provided interface, required interface, class, port, connector, artifact, component realization, dependency, usage. These major elements are shown on the picture here.

Import into your Project

Deployment Diagram with Components

Import into your Project

Swimlane

Here is an activity diagram example for ATM.

Withdraw money from an ATM Account - The three involved classes (people, etc.) of the activity are Customer, ATM, and Bank. represented swimlanes that determine which object is responsible for which activity. The process begins at the black start circle at the top and ends at the concentric white/black stop circles at the bottom. The activities are rounded rectangles.

A single transition comes out of each activity, connecting it to the next activity, which may branch into two or more mutually exclusive transitions. Guard expressions (inside [ ]) label the transitions coming out of a branch. A branch and its subsequent merge marking the end of the branch appear in the diagram as hollow diamonds. A transition may fork into two or more parallel activities. The fork and the subsequent join of the threads coming out of the fork appear in the diagram as solid bars.

Import into your Project

Hotel Reservation

Here is a communication diagram example.

Communication diagrams are also interaction diagrams. They convey the same information as sequence diagrams, but they focus on object roles instead of the times that messages are sent. In a sequence diagram, object roles are the vertices and messages are the connecting links.

The object-role rectangles are labelled with either class or object names (or both). Class names are preceded by colons ( : ). Each message in a collaboration diagram has a sequence number. The top-level message is numbered 1. Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1, 2, etc. according to when they occur.

Import into your Project

Sequence Diagram Example

Sequence Diagram is an interaction diagram that details how operations are carried out -- what messages are sent and when. Sequence diagrams are organized according to time. The time progresses as you go down the page. The objects involved in the operation are listed from left to right according to when they take part in the message sequence.

Note That: Class and object diagrams are static model views. Interaction diagrams are dynamic. They describe how objects collaborate.

Here is a sequence diagram example for making a hotel reservation. The object initiating the sequence of messages is a Reservation window.

Import into your Project

MVC Framework

Here is a sequence diagram example.

Entities are objects representing system data: Customer, Product, Transaction, Cart, etc.
Boundaries are objects that interface with system actors: UserInterface, DataBaseGateway, ServerProxy, etc.
Controls are objects that mediate between boundaries and entities.

They orchestrate the execution of commands coming from the boundary by interacting with entity and boundary objects. Controls often correspond to use cases scenario and often represented by a sequence diagram.

Import into your Project

Analysis Stereotypes

Import into your Project

1 2 3 … 43 44 45 46 47

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Open diagram in Visual Paradigm [?]

Posts navigation