EXPERMENT 5

AIM: To draw the structural view diagram for the ATM: Class
diagram, Object diagram.
1. Class Diagram

The class diagram depicts a static view of an application. It represents the types of objects
residing in the system and the relationships between them. A class consists of its objects, and
also it may inherit from other classes. A class diagram is used to visualize, describe, document
various different aspects of the system, and also construct executable software code.

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 that helps in software development. Since it is a collection of classes, interfaces,
associations, collaborations, and constraints, it is termed as a structural diagram.

Figure 5.1: Class Diagram of ATM

 EXPERIMENT 4

Aim:- To perform the user’s view analysis for ATM: Use case diagram.
1) Use case
A use case diagram is used to represent the dynamic behavior of a system. It encapsulates the system's
functionality by incorporating use cases, actors, and their relationships. It models the tasks, services,
and functions required by a system/subsystem of an application. It depicts the high-level functionality
of a system and also tells how the user handles a system. They contain the following elements:
a) Actors - It represent users of a system, including human users and other systems.

b) Use cases - It represent functionality or services provided by a system to users.

1.1) Purpose of Use Case Diagrams

The main purpose of a use case diagram is to portray the dynamic aspect of a system. It accumulates
the system's requirement, which includes both internal as well as external influences. It invokes
persons, use cases, and several things that invoke the actors and elements accountable for the
implementation of use case diagrams. It represents how an entity from the external environment can
interact with a part of the system.

Following are the purposes of a use case diagram given below:

a) It gathers the system's needs.

b) It depicts the external view of the system.
c) It recognizes the internal as well as external factors that influence the system.
d) It represents the interaction between the actors.

1.2) How to draw a Use Case diagram?

It is essential to analyse the whole system before starting with drawing a use case diagram, and then
the system's functionalities are found. And once every single functionality is identified, they are then
transformed into the use cases to be used in the use case diagram.After that, we will enlist the actors
that will interact with the system.

The actors are the person or a thing that invokes the functionality of a system. It may be a system or a
private entity, such that it requires an entity to be pertinent to the functionalities of the system to which
it is going to interact. Once both the actors and use cases are enlisted, the relation between the actor
and use case/ system is inspected. It identifies the no of times an actor communicates with the system.
Basically, an actor can interact multiple times with a use case or system at a particular instance of time.
 Figure 3.5: 2-Level DFD of ATM
3) Structure Chart
Structure Chart represent hierarchical structure of modules. It breaks down the entire system into
lowest functional modules, describe functions and sub-functions of each module of a system to a
greater detail. Structure Chart partitions the system into black boxes (functionality of the system is
known to the users but inner details are unknown). Inputs are given to the black boxes and appropriate
outputs are generated. Modules at top level called modules at low level. Components are read from top
to bottom and left to right. When a module calls another, it views the called module as black box,
passing required parameters and receiving results.
Symbols used in construction of structured chart
• Module - It represents the process or task of the system.
• Control Module - A control module branches to more than one sub module.
• Sub Module - Sub Module is a module which is the part (Child) of another module.
• Library Module- Library Module are reusable and invokable from any module.
• Conditional Call- It represents that control module can select any of the sub module on the basis of
some condition.
• Loop (Repetitive call of module) - It represents the repetitive execution of module by the sub
module.
Figure 3.6: Structure Digram of ATM
2.2 Software requirement

In order to perform various different functions, this software needs to interact with various other
softwares. So there are certain software interface requirements that need to be fulfilled which are
listed as follows:- The transaction management software used to manage the transaction and keep
track of resources . The card management software used to verify pin no and login. MongoDB
is an open source. No SQL database management program. NoSQL is used as an alternative to
traditional relational databases. NoSQL databases are quite useful for working with large sets of
distributed data.

The software will preferably run more efficiently and precisely on windows operation system. Thus,
they work accurately on windows operating systems to give a better and accurate results. Else the
software is not constrained for any operating system. It can be accessible for any operating system like
Mac, Linux, ubuntu etc. As the entire software product is based on HTML, JavaScript and CSS.

2.3 Hardware requirement

The hardware components needed for this product is not much. This software can run on any operating
system.Various Laptops, PC, mobile phones etc. can be used to access this software.

transaction and keep track of resources shall be BMS version 2.0.

The card management software used to verify pin no and login
shall be CMS version 3
In order to perform various different functions, this software needs to interact with various other
softwares. So there are certain software interface requirements that need to be fulfilled which are
listed as follows:- The transaction management software used to manage the transaction and keep
track of resources . The card management software used to verify pin no and login .
2.3 Hardware requirement
2.4 Functional requirement

2.4.1 Remote banking and account management

The system is designed to provide the user with the facility of remote banking and perform
various other functions at an interface without any aid of human bank teller. The functioning of the
system shall be as follows:

At the start, the user is provided with a log in screen and he is required to enter his PIN NO.
and Account details which are then verified by the machine. In case of an unsuccessful attempt a
user is asked again for his credentials but the maximum number of attempt given to the user is
limited to 3 only, failing which his card is blocked and need to be unblocked by the bank for any future
use.

After a successful log in, the user is presented with a list of language. The user can select any
one in the list for interaction with the machine for the entire session. After the language selection the
user is also asked whether he wants to fix that language for future use also so that he is never asked
for language in future. In addition there is also a facility for the user to switch to any other language
during that session.It is therefore very important to proceed the requirement of ATM. AMS facilitates
the customer to perform various transactions in his/her account without going to bank. This software
offers benefits such cash withdrawals, balance transfers, deposits, inquiries and other banking related
operations for customers. It also allows the maintainer to fix the issues of ATM and update its
software.

After the language selection, the user is directed towards a main page that displays a set of
options/services along with their brief description, enabling the user to understand function to their