Scribd
Upload
4K views7 pages

Component Diagram and Deployment Diagram

The document provides information about a student named Ameya A. Joshi enrolled in batch Div 02/B1 for the course MCP543. It then provides details about the component diagram of a bank management system including the key components, their interfaces, dependencies and how they work together. It also includes annotations to explain the symbols and elements used in a component diagram.

Uploaded by

Anjali Thakur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4K views7 pages

Component Diagram and Deployment Diagram

The document provides information about a student named Ameya A. Joshi enrolled in batch Div 02/B1 for the course MCP543. It then provides details about the component diagram of a bank management system including the key components, their interfaces, dependencies and how they work together. It also includes annotations to explain the symbols and elements used in a component diagram.

Uploaded by

Anjali Thakur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Name :- Ameya A. Joshi (Roll no.

06)

Batch :- Div 02/B1

Course code :- MCP543 (Concepts In Software Engineering Lab)

Bank Management System Component Diagram

The Component Diagram of bank management system is used to show how the parts work
together to make the bank system operate successfully. A component diagram shows how
the software’s parts are organized and how they are depend on each other .This diagram
gives a High-Level look at the parts of the system.
Components of a bank management component diagram can be part of
software or hardware. They could be a database, a user interface, or something else that
helps the bank management system work properly.
A component diagram in the (UML) Unified Modeling Language shows how parts are wired
together to explain the parts of bank systems. They are used to show the structure of any
kind of system.

The UML component diagram shows how a bank management system will be made up of a
set of deployable components, such as dynamic-link library (DLL) files, executable files, or
web services. Using well-defined interfaces, these parts communicate with each other and
keep their internal details hidden from each other and the outside world.

The Component Diagram for bank Management System


This component diagram of bank management system is the illustration of the components
of every hardware and software node. The component diagram below is a detailed
illustration of the Deployment Diagram Of The Bank Management System.
This component diagram shows the structure of the bank system, which consists of the
software components and their interfaces, accounts database, transaction information, and
financial information. Their dependencies explain how they work together. You can use
component diagrams to show how software systems work at a high level, or you can use
them to show how each component works at a lower level, like in a package.

Bank Management System Component Diagram


(Explanation)

The Bank Management System UML component diagram explains the sketch of the
required software and hardware components and the dependencies between them. These
components are labeled to clarify their part in the system's operation. They were
represented by symbols that explain their function and role in the overall bank management
system operation. The dependencies on each component are explained through the lines
and arrows drawn in the diagram.

The component diagram of bank management system has 4 components and a package
which are user interface, room management, reservation management, monitoring and
updates, web interface, and the list of services. This diagram shows several interfaces that
are provided and required. The client's side package contains the required interfaces and the
crew's side contains the provided interfaces. The admin's side package also holds and
manipulates the crew's components.
Annotations For Component Diagram
1.) Component symbol:- An entity required to execute a stereotype function. A
component provides and consumes behavior through interfaces, as well as through
other components. Think of components as a type of class. In UML 1.0, a component
is modeled as a rectangular block with two smaller rectangles protruding from the
side. In UML 2.0, a component is modeled as a rectangular block with a small image
of the old component diagram shape.

2.) Node symbol:- It represents hardware or software objects, which are of a higher
level than components. The diagram is given below.

3.) Package symbol:- Groups together multiple elements of the system and is
represented by file folders in Lucidchart. Just as file folders group together multiple
sheets, packages can be drawn around several components.
4.) Dependency symbol:- Shows that one part of your system depends on
another. Dependencies are represented by dashed lines linking one component (or
element) to another.

5.) Provided interfaces:- A straight line from the component box with an
attached circle. These symbols represent the interfaces where a component
produces information used by the required interface of another component .

6.) Required interfaces:- A straight line from the component box with an
attached half circle (also represented as a dashed arrow with an open arrow). These
symbols represent the interfaces where a component requires information in order
to perform its proper function.
Banking System Deployment Diagram

Banking System Deployment Diagram Description


Deployment diagrams demonstrate how software and hardware communicate to ensure
appropriate banking system operation. It properly explains how software interacts with
hardware. They also help figure out which certain type of hardware uses software parts .

The main aim of deployment diagrams is to describe how software is delivered into
the hardware system. It depicts how software interacts with hardware to perform all
of the functions. It's a term that describes how software interacts with hardware and
vice versa.

UML Deployment Diagram for Banking System


UML deployment diagram for banking management system is used to illustrate its' physical
architecture. In UML, deployment diagrams can show you how the software and hardware
of the system work together and where the processing takes place.
The banking system uses a UML deployment diagram to show how should the developed
software be deployed. It clarifies the communications between links(nodes) which helps the
project to work according to the design given to it. Deployment diagrams depict the setup of
run-time processing nodes and the components that reside on them.

Benefits of UML Deployment Diagram


They visualize a system's hardware processors/nodes/devices, communication linkages
between them, and software file layout on that hardware.
It aids in the visualization of the various aspects involved.
• • Aids in a more accurate description of all the hardware elements used by software
components.
• • It clarifies the description of the runtime involved in processing nodes.
• • Provides hardware specified details for a distributed application.
• • Helps in modeling the system's hardware topology.
• • It aids in the modeling of inserted or included software.
• • Provides more information on the hardware system.
• • Reverse engineering is made easier using the UML deployment diagram
Here's the Deployment Diagram for Banking System showing the detailed illustration of the
system's software and hardware specification. Additionally, it gives the complete physical
structure of the banking system that is needed in its deployment for its users.
It is important to create the deployment diagram to clarify the needs of the project before it
will put into operation. This will help you avoid unnecessary difficulties that may encounter
because of specification deficiency. The banking system UML deployment diagram explains
the sketch of the relationship between software and hardware. These hardware and
software are labeled to clarify their part in the system's operation. They were represented
by nodes and the connections were represented by labeled arrows.

The deployment diagram shows the scenario when the system is deployed. It has 4 nodes
represented with boxes and relationship connections. The nodes are the banking system,
the client's PC, the bank application, and the bank database. The system node contains
developed software that will hold the banking materials needed online.
For the connection, the system is connected to the application and database using a private
network which enables it to pass a connection to the devices and enable clients to access
the system. The database and the application then can communicate using a TCP/IP
connection.
Annotation For Deployment Diagram
1.) Nodes:- A node, represented as a cube, is a physical entity that
executes one or more components, subsystems or executables. A node
could be a hardware or software element.

2.) Artifacts:- Artifacts are concrete elements that are caused by a


development process. Examples of artifacts are libraries, archives,
configuration files, executable files etc.

You might also like