Experiment-4

AIM: Try simple architecture and design of modules. Represent in activity, sequence,
collaboration
diagrams(UML).

Unified Modeling Language (UML) is a standardized visual modeling language that is a

versatile, flexible, and user-friendly method for visualizing a system’s design. Software
system artifacts can be specified, visualized, built, and documented with the use of UML.
 We use UML diagrams to show the behavior and structure of a system.
 UML helps software engineers, businessmen, and system architects with modeling,
design, and analysis.

Diagrams in UML :

 It can be broadly classified as:

 Structural Diagrams – Capture static aspects or structure of a system.
 Component Diagrams
 Object Diagrams
 Class diagrams
 Deployment Diagrams

Behavioural Diagrams
 Use Case Diagrams
 State Diagrams
 Activity Diagrams
 Interaction Diagrams
Class Diagram

 widely use UML diagram is the class diagram.

 depict the static structure of a system by showing system’s classes,their
methods and attributes

Object Diagram

 referred to as a screenshot of the instances in a system and the relationship that

exists between them

Component Diagram

 represent the how the physical components in a system have been organized.
 depict the structural relationship between software system elements

Deployment Diagram

 represent system hardware and its software.

 what hardware components exist and what software components run on them.

Behavioural Diagrams

 illustrate the flow of control in a system.

 model sequential and concurrent activities using activity diagrams

Use Case Diagrams

 depict the functionality of a system or a part of a system.

 illustrate the functional requirements of the system and its interaction with
external agents(actors).
 high level view of what the system or a part of the system does without
going into implementation details

Sequence Diagram

 A sequence diagram simply depicts interaction between objects in a sequential

order

Collaboration Diagram

 sequenced messages exchanged between objects.

 A communication diagram focuses primarily on objects and their relationships
 Any system can have two aspects, static and dynamic.
 A model is considered as complete when both the aspects are covered fully.
 It basically capture the dynamic aspect of a system.
 Dynamic aspect can be further described as the changing/moving parts of
a system.
UML has the following five types of behavioral diagrams:

 Use case diagram

 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram

USECASE DIAGRAM

Usecase diagrams are a set of usecases, actors and their relationships.

They represent the use case view of a system.

They are Used for describing a set of user scenarios

Mainly used for capturing user requirements

Work like a contract between end user and software developers

ACTORS

A role that a user plays with respect to the system, including human users and other
systems.

USECASE

 A set of scenarios that describing an interaction between a user and a

system, including alternatives.
 It represent the dynamic behavior of a system. It depicts the high-
level functionality of a system
 It gathers the system's needs.
 It represents the interaction between the actors.
 CLASS DIAGRAM

 Depicts a static view of an application.

 It shows the attributes, classes, functions, and relationships to give an overview
of the software system.
 It constitutes class names, attributes, and functions in a separate compartment
 It analyses and designs a static view of an application.
 It describes the major responsibilities of a system.

OBJECT DIAGRAM

 They can be described an instance of class diagram.

 Object diagrams represent an instance of a class diagram
 They are a set of objects and their relationships just like class
diagrams and also represent the static view of the system.
 Object diagrams are derived from class diagrams
 so object diagrams are dependent upon class diagrams
 Object relationships of a system
 Understand object behavior and their relationship from practical perspective
 Object diagrams are consist of objects.
 The link in object diagram is used to connect objects.
 Objects and links are the two elements used to construct an object diagram
 SEQUENCE DIAGRAM

 sequence diagram is the most commonly used interaction diagram.

 Interaction diagram – It is used to show the interactive behavior of a system
 The sequence diagram represents the flow of messages in the system.
 It portrays time-ordered sequence of events.
 It models high-level interaction among active objects within a system.
 lifeline is represented by a vertical bar
 message flow is represented by a vertical dotted line

sequence diagram consists of

 Lifeline
 Actor
 Activation
 Messages
 Call message
 Return message
 Self message
ACTIVITY DIAGRAM

It describes the flow of control in a

system. It consists of activities and links.

The flow can be sequential, concurrent or branched.

Activities are nothing but the functions of a system. Numbers of activity diagrams are
prepared to capture the entire flow in a system.

Activity diagrams are used to visualize the flow of controls in a system.

This is prepared to have an idea of how the system will work when executed.

Swimlane: It is used to cluster all the related activities in one column or one row. It
can be either vertical or horizontal.

Forks: Forks and join nodes generate the concurrent flow inside the

activity. A fork node consists of one inward edge and several outward

edges.

Join nodes are the opposite of fork nodes.

 COLLABORATION DIAGRAM

 The collaboration diagram is used to show the relationship between the objects
in a system.
 Sequence and the collaboration diagrams represent the same information but
differently.
 It depicts the architecture of the object residing in the system.
 It is essential to depict the relationship between the object.
 It is another form of interaction diagram. It represents the structural
organization of a system and the messages sent/received. Structural
organization consists of objects and links.
 The purpose of collaboration diagram is similar to sequence diagram. But
the specific purpose of collaboration diagram is to visualize the organization
of objects and their interaction.
 Objects: The representation of an object is done by an object symbol with its
name and class underlined, separated by a colon.
 Actors: the actor plays the main role as it invokes the interaction. Each actor has
its respective role and name.
 Links: It portrays a relationship between the objects through which the messages
are sent.
 Messages: It is a communication between objects which carries information
and includes a sequence number

Collaboration diagram is represented as:

 STATECHART DIAGRAM

 state machine diagram is also called the Statechart or State Transition diagram
 It captures the software system's behavior
 It models event-based systems to handle the state of an object.
 defines several distinct states of a component within the system
 It records the dynamic view of a system
 It visualize the reaction of a system by internal/external factors.
 It describes the flow of control from one state to another state.
 States are defined as a condition in which an object exists
 It changes when some event is triggered.
 It is used to model life time of an object from creation to termination.

COMPONENT DIAGRAM

 It models the physical view of a system such as executables, files, libraries,

etc. that resides within A component is a single unit of the system, which is
replaceable and executable.
 The implementation details of a component are hidden.
 It depicts the relationships and organization of components.
 They represent a set of components and their relationships.
 These components consist of classes, interfaces or collaborations.
 They represent the implementation view of a system.
 DEPLOYMENT DIAGRAM
 Visualizes the physical hardware on which the software will be deployed.
 It portrays the static deployment view of a system.
 It involves the nodes and their relationships.
 Hardware topology of the system
 It represent the hardware components on which the software components are
installed.
 To describe the processing of nodes at the runtime

Component diagrams and deployment diagrams are closely

related.
CREDIT CARD PROCESSING SYSTEM USECASE DIAGRAM
CREDIT CARD PROCESSING SYSTEM CLASS DIAGRAM
CREDIT CARD PROCESSING SYSTEM OBJECT DIAGRAM
CREDIT CARD PROCESSING SYSTEM SEQUENCE DIAGRAM
CREDIT CARD PROCESSING SYSTEM COLLABORATION DIAGRAM
CREDIT CARD PROCESSING SYSTEM STATE CHART DIAGRAM
CREDIT CARD PROCESSING SYSTEM ACTIVITY DIAGRAM
CREDIT CARD PROCESSING SYSTEM COMPONENT DIAGRAM
CREDIT CARD PROCESSING SYSTEM DEPLPOYMENT DIAGRAM