EXPERIMENT No:-02

Aim: - Develop a Data Flow Diagram for Bank Management System.

Theory:Data Flow Diagram: A data flow diagram (DFD) maps out the flow of information for any
process or system. It uses defined symbols like rectangles, circles and
arrows, plus short text labels, to show data inputs, outputs, storage points
and the routes between each destination.
Data flowcharts can range from simple, even hand-drawn process
overviews, to in-depth, multi-level DFDs that dig progressively deeper into
how the data is handled.
They can be used to analyze an existing system or model a new one. Like
all the best diagrams and charts, a DFD can often visually say things that
would be hard to explain in words, and they work for both technical and
nontechnical audiences, from developer to CEO.
Thats why DFDs remain so popular after all these years. While they work
well for data flow software and systems, they are less applicable
nowadays to visualizing interactive, real-time or database-oriented
software or systems.
Components of Data Flow Diagram: External entity: an outside system that sends or receives data,
communicating with the system being diagrammed. They are the sources
and destinations of information entering or leaving the system. They
might be an outside organization or person, a computer system or a
business system. They are also known as terminators, sources and sinks
or actors. They are typically drawn on the edges of the diagram.
Process: any process that changes the data, producing an output. It might
perform computations, or sort data based on logic, or direct the data flow
based on business rules. A short label is used to describe the process, such
as Submit payment.
Data store: files or repositories that hold information for later use, such
as a database table or a membership form. Each data store receives a
simple label, such as Orders.

 Data flow: the route that data takes between the external entities,
processes and data stores. It portrays the interface between the other
components and is shown with arrows.
Context Diagram: Its a basic overview of the whole system or process being analyzed or
modeled. Its designed to be an at-a-glance view, showing the system as
a single high-level process, with its relationship to external entities.

Level 0: DFD Level 0 provides a more detailed breakout of pieces of the Context
Level Diagram. The main functions carried out by the system, as you break
down the high-level process of the Context Diagram into its sub
processes.

Conclusion:Hence we have studied Data Flow Diagram for Bank management system.

EXPERIMENT No:-03
Aim: - Develop a Use Case Diagram for Bank Management System.
Theory:Use Case Diagram: The use case diagram is dynamic in nature there should be some internal
or external factors for making the interaction.
These internal and external agents are known as actors. So use case
diagrams are consists of actors, use cases and their relationships.
The diagram is used to model the system/subsystem of an application. A
single use case diagram captures a particular functionality of a system.
Purpose:

Used to gather requirements of a system.

Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.

Components of Use Case Diagram: Use cases: - Use cases are the horizontally shaped ovals. This represents
the different uses that a user might need.
Actors :- represented by stick figure people and are the people actually
employing the use cases
Associations: - represented by a line between actors and use cases. In a
more complex diagram, it is important to know which actors are
associated with which use cases.
System boundary boxes: - a box that sets a system scope to use cases. All
use cases outside the box would be considered outside the scope of that
system.
Packages: - A UML shape that allows you to put different elements into
groups. Just as with component diagrams, these groupings are
represented as file folders.

Use Case Diagram:-

Conclusion:Hence we have studied Use Case Diagram for Bank management system.

EXPERIMENT No:-08
Aim: - Develop a sequence diagram for Bank Management System.
Theory:Sequence Diagram: A sequence diagram is a UML diagram that models the logic use of a use
case by depicting the interaction of message between objects in time
sequence. A full sequence diagram depicts the interaction between all
the object classes involved in the scenario.
A sequence diagram models the logic of a use case by depicting the
interaction between objects in the time sequence. The messages are
arranged in time sequence from top to bottom.
A sequence diagram can be seen as a way to integrate the steps of a use
case with the objects of a class diagram. A sequence diagram graphically
documents the use case by showing the classes the messages, and the
timing of the messages.
Purpose: The sequence diagram is used primarily to show the interactions between
objects in the sequential order that those interactions occur.
Much like the class diagram, developers typically think sequence diagrams
were meant exclusively for them
An organization's technical staff can find sequence diagrams useful in
documenting how a future system should behave.
One of the primary uses of sequence diagrams is in the transition from
requirements expressed as use cases to the next and more formal level of
refinement.
In addition to their use in designing new systems, sequence diagrams can
be used to document how objects in an existing (call it "legacy") system
currently interact.
Sequence diagram include symbols that represent classes, lifelines, messages
and focuses.
Classes a class is identified by a rectangle with the name inside. Classes
that send or receive messages are shown at the top of the sequence
diagram
Lifelines A lifeline is identified by a dashed line. The lifeline represent
the time during which the object above it is able to interact with the other
objects in the use case. An X marks the end of the lifeline

 Messages a message is identified by a line showing direction that runs

between two objects. The label shows the name of the message and can
include additional information about the contents
Focuses a focus is identified by a narrow vertical shape that covers the
lifeline. The focus indicates when an object sends or receives a message.

Conclusion: - Hence we have studied Sequence Diagram for Bank management

system.

EXPERIMENT No:-09
Aim: - Develop a collaboration diagram for Bank Management System.
Theory:- Collaboration Diagram
The interactive behaviour is represented in UML by two diagrams known as
sequence diagram and Collaboration diagram.
Sequence diagram emphasizes on time sequence of messages
and collaboration diagram emphasizes on the structural organization of
the objects that send and receive messages.
Here in collaboration diagram the method call sequence is indicated by
some numbering technique .The number indicates how the methods are
called one after another.
The method calls are similar to that of a sequence diagram. But the
difference is that the sequence diagram does not describe the object
organization whereas the collaboration diagram shows the object
organization.
Purpose: Collaboration diagrams are used to describe the structural organizations
of the objects taking part in the interaction.
Collaboration diagram emphasizes on the structural organization of the
objects that send and receive messages.
Elements Of collaboration Diagram: Object: The objects interacting with each other in the system. Depicted
by a rectangle with the name of the object in it, preceded by a colon and
underlined.

Relation/Association: A link connecting the associated objects. Qualifiers

can be placed on either end of the association to depict cardinality.

Messages: An arrow pointing from the commencing object to the

destination object shows the interaction between the objects. The
number represents the order/sequence of this interaction.

Collaboration Diagram:-

Conclusion: - Hence we have studied Collaboration Diagram for Bank

management system.

EXPERIMENT No:-04
Aim: - Develop a class diagram for Bank Management System.
Theory: - Class Diagram
The class diagram is a static diagram. It represents the static view of an
application. Class diagram is not only used for visualizing, describing and
documenting different aspects of a system but also for constructing
executable code of the software application.
The class diagram describes the attributes and operations of a class and
also the constraints imposed on the system. The class diagrams are widely
used in the modelling of object oriented systems because they are the
only UML diagrams which can be mapped directly with object oriented
languages.
The class diagram shows a collection of classes, interfaces, associations,
collaborations and constraints. It is also known as a structural diagram.
Purpose: The purpose of the class diagram is to model the static view of an
application.
The purpose of the class diagram can be summarized as:
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering.
Now the following diagram is an example of a Bank management system.
So it describes a particular aspect of the entire application.
Bank management systems need to reflect the relationships between a
varieties of Bank-related objects.
These objects can be sorted into classes via a class diagram, which shows
the relationships between each object in the system or application.
Developing class diagram consist of following steps: Identifying classes
Identifying association
Identifying attributes
Identifying Inheritance
Identifying operation
Iterate and refine model

CLASS DIAGRAM:

Conclusion: - Hence we have studied Class Diagram for Bank management

system.

EXPERIMENT No:-05
Aim: - Develop an Object diagram for Bank Management System.
Theory:Object Diagram: Object diagrams are derived from class diagrams so object diagrams are
dependent upon class diagrams.
Object diagrams represent an instance of a class diagram. The basic
concepts are similar for class diagrams and object diagrams. Object
diagrams also represent the static view of a system but this static view is
a snapshot of the system at a particular moment.
Object diagrams are used to render a set of objects and their relationships
as an instance.
Purpose: The purposes of object diagrams are similar to class diagrams.
The difference is that a class diagram represents an abstract model
consisting of classes and their relationships. But an object diagram
represents an instance at a particular moment which is concrete in
nature.
It means the object diagram is more close to the actual system behaviour.
The purpose is to capture the static view of a system at a particular
moment.
The purpose of the object diagram can be summarized as:
Forward and reverse engineering.
Object relationships of a system
Static view of an interaction.
Understand object behaviour and their relationship from practical
perspective

Object Diagram:-

Conclusion:Hence we have studied Object Diagram for Bank management system.

EXPERIMENT No:-06
Aim: - Develop an Activity diagram for Bank Management System.
Theory:- Activity Diagram
Activity diagram is another important diagram in UML to describe
dynamic aspects of the system.
Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an operation
of the system.
So the control flow is drawn from one operation to another. This flow can
be sequential, branched or concurrent.
Activity diagrams are mainly used for describing the activities within an
object in order to capture their operation and state between objects.
Purpose: It captures the dynamic behaviour of the system. Other four diagrams are
used to show the message flow from one object to another but activity
diagram is used to show message flow from one activity to another.
Activity is a particular operation of the system. Activity diagrams are not
only used for visualizing dynamic nature of a system but they are also used
to construct the executable system by using forward and reverse
engineering techniques. The only missing thing in activity diagram is the
message part.
It does not show any message flow from one activity to another. Activity
diagram is some time considered as the flow chart. Although the diagrams
looks like a flow chart but it is not. It shows different flow like parallel,
branched, concurrent and single.
The purposes can be described as:
Draw the activity flow of a system.
Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the system.
Component of activity diagram: Solid circle:The start symbol represents the beginning of a process or workflow in
an activity diagram. It can be used by itself or with a note symbol that
explains the starting point.

 Rounded rectangle:The activity symbol is the main component of an activity diagram.

These shapes indicate the activities that make up a modelled process.
Arrows:The connector symbol is represented by arrowed lines that show the
directional flow, or control flow, of the activity. An incoming arrow
starts a step of an activity; once the step is completed, the flow continues with
the outgoing arrow.
Join symbol:The join symbol, or synchronization bar, is a thick vertical or horizontal
line. It
combines two concurrent activities and re-introduces them
to a flow where only one activity occurs at a time.
Fork symbol:A fork is symbolized with multiple arrowed lines from a join. It splits
a single activity flow into two concurrent activities.
Diamond:The decision symbol is a diamond shape; it represents the branching or
merging of various flows with the symbol acting as a frame or container.
Bulls eye symbol:The end symbol represents the completion of a process or workflow.
Now the following diagram is an example of a Bank management system.
So it describes a particular aspect of the entire application.

Activity diagram:-

Conclusion:Hence we have studied Activity Diagram for Bank management system.

EXPERIMENT No:-07
Aim:- Develop a State Machine diagram for Bank Management System.
Theory:State Machine Diagram: The name of the diagram itself clarifies the purpose of the diagram and
other details. It describes different states of a component in a system. The
states are specific to a component/object of a system.
A State chart diagram describes a state machine. Now to clarify it state
machine can be defined as a machine which defines different states of an
object and these states are controlled by external or internal events.
Purpose: They define different states of an object during its lifetime. And these
states are changed by events. So State chart diagrams are useful to model
reactive systems. Reactive systems can be defined as a system that
responds to external or internal events.
State chart diagram describes the flow of control from one state to
another state. States are defined as a condition in which an object exists
and it changes when some event is triggered.
State chart diagrams are also used for forward and reverse engineering of
a system.
The purpose of the object diagram can be summarized as:
To model dynamic aspect of a system.
To model life time of a reactive system.
To describe different states of an object during its life time.
Define a state machine to model states of an object.

State Machine Diagram:-

Conclusion: - Hence we have studied State Machine Diagram for Bank

management system.

EXPERIMENT No:-10
Aim: - Develop a Component diagram, Deployment diagram, Package diagram,
architecture diagram for Bank Management System.
1. COMPONENT DIAGRAM

2. DEPLOYEMENT DIAGRAM

3. PACKAGE DIAGRAM

4. Architecture Diagram: