Institute of Engineering and Technology , MLSU

Project
on
Automated Teller Machine (ATM)

Name: Dakshit Singh Adhikari

Section: A
Subject: Software Engineering
Year: 2nd

Signature
 Introduction to Project

Purpose

The overall purpose of this project is to evaluate and analyses the requirement of
the customer, design and implement the system, testing the functionality and
maintain the software of an ATM component of a larger ATM network project,
consistent with the requirement specification.

Scope

The scope of the ATM is to support a computerized banking network. All activities
directly related to the purpose are considered to be in scope. The other activities
not directly related to the purposes are considered to be out of scope, such ATM
hardware and concern issues.

Need for the Software: Now a days every one very busy in their work. So they
feel that the job must be easier sothe system is used to reduce their work which is
done in the ATM system. Instead of keeping lots of paper into a record or file and
it may be missed somewhere so, thissystem help to keep the record of the customer
it also keeps the details of he customer.It is also easy to access.

Problem description : The system mainly used by the bank clients. When a client
comes to ATM centre toupdate and delete their account. It reduces the time
consumption and lot of paperwork.For any single operation it involves numerous
references and updating also takessubsequent changes in other places.
 Practical 1

Practical name : Software Development Life Cycle and User Model

Software Development Life Cycle (SDLC)

SDLC stands for Software Development Life Cycle. It's a process used by
software development teams to design, develop, test, and deploy high-quality
software efficiently. The SDLC typically consists of several stages, including:

1. Planning: Defining the project goals, scope, requirements, and resources

needed.
2. Analysis: Gathering and analyzing requirements from stakeholders to
understand the project's objectives and constraints.
3. Design: Creating a detailed blueprint of the software system, including
architecture, database design, user interface design, and other technical
specifications.
4. Implementation: The actual coding and development phase where
developers write and integrate code based on the design specifications.
5. Testing: Systematically evaluating the software to identify and fix bugs,
ensure functionality, and validate that it meets the specified requirements.
6. Deployment: Releasing the software to users or clients, which may
involve installation, configuration, and migration of data.
7. Maintenance: Providing ongoing support, updates, and improvements to
the software to address issues, add new features, and adapt to changing
requirements

Importance of SDLC

The SDLC is important because it helps ensure that the right people are involved
in the right activities at the right times. Using a structured approach to developing
software helps ensure that your project will be successful. Some of the SDLC's
benefits are:
• Understanding your requirements and the goal of the software
• Identify risks at an early stage
• Plan how you will deliver your solution in stages, such as building
prototypes or writing functional specifications
• Measure your progress relative to your goals and ensure everything is on
track
• The development team must determine a suitable life cycle model for a
particular plan and then observe to it.
User Model: A user model refers to a conceptual representation of the
characteristics, preferences, behaviors, and needs of the users who will interact
with a software system. It helps developers and designers understand how users
will use the system and what features or functionalities are important to them.

The waterfall model is a software development model used in the context of

large, complex projects, typically in the field of information technology. It is
characterized by a structured, sequential approach to project
management and software development.
 Practical 2
Practical name: Project Breakdown , PERT Chart, GANT Chat

Project Breakdown
Project breakdown, also known as work breakdown structure (WBS), is a method
used in project management to divide a project into smaller, more manageable
components or tasks. These smaller components are easier to understand,
estimate, and track throughout the project lifecycle. The breakdown typically
starts with the project's main deliverables and is further decomposed into smaller
tasks until each task is well-defined and actionable.

The main objectives of project breakdown are:

1.Clarity: Breaking down the project into smaller tasks provides clarity on what
needs to be accomplished to achieve the project's goals.

2.Estimation: It facilitates more accurate estimation of resources, time, and costs

required for each task, enabling better planning and budgeting.

3.Assignment: Clearly defined tasks make it easier to assign responsibilities to

team members or teams, ensuring accountability and efficient resource allocation.

4.Tracking: Smaller tasks are easier to track and monitor, allowing project
managers to identify progress, delays, and potential issues more effectively.

5.Risk Management: Identifying and breaking down tasks helps in identifying

potential risks and dependencies, allowing for better risk management and
mitigation strategies.
Project Breakdown Diagram:

ATM

REQUIRMENTS ANALYSIS DESIGN CODING TESTING MAINTENANCE

TEAM GUI PYTHON

HARDWARE AND
DATABASE
SOFTWARE

PERT Chart
A PERT (Program Evaluation and Review Technique) chart is a project
management tool used in software engineering (as well as other industries) to
visually represent and schedule tasks within a project. PERT charts help project
managers and teams understand the dependencies between tasks and estimate the
time required to complete a project.
GANT Chart
A Gantt chart is another widely used project management tool in software
engineering. It provides a visual representation of the project schedule by
displaying tasks, their durations, start and end dates, and dependencies between
tasks.
Gantt charts are useful for visualizing the project schedule, identifying critical
tasks, managing dependencies, and communicating project plans to stakeholders.
They provide a clear overview of the project timeline and help project teams stay
organized and focused on meeting deadlines throughout the software
development process.
 Practical 3
Practical name: Theory of DFD
Data Flow Diagram (DFD)
A Data Flow Diagram (DFD) is a visual representation of how data flows through
a system. It's a structured approach used in software engineering to model the
flow of data within a system, from external sources or destinations through
processes and data stores.
Here's a breakdown of the components typically found in a DFD:
1.External Entities: These are sources or destinations of data outside the system
being modeled. They interact with the system but are not part of it.
2.Processes: Processes represent the transformations or actions that occur within
the system. They take input data, perform some processing, and produce output
data.
3.Data Flows: Data flows represent the movement of data between external
entities, processes, and data stores. They show the direction in which data moves
through the system and what data is being exchanged.
4.Data Stores: Data stores represent repositories where data is stored within the
system. These can be databases, files, or other storage mechanisms.

DFD Level 0: It is also known as a context diagram. It’s designed to be an

abstraction view, showing the system as a single process with its relationship to
external entities. It represents the entire system as a single bubble with input and
output data indicated by incoming/outgoing arrows.
DFD Level 1: A Level 1 DFD provides a more detailed view of the processes
and data flows identified in a Level 0 DFD. It breaks down the processes into
sub-processes and provides more information about the data stores, external
entities, and data flows.
Level 2 DFD: This level provides an even more detailed view of the system
by breaking down the sub-processes identified in the level 1 DFD into further
sub-processes. Each sub-process is depicted as a separate process on the level 2
DFD. The data flows and data stores associated with each sub-process are also
shown.
 Practical 4
Practical name: ER Diagram (Theory+Practical)
Entity-Relationship Diagram
The Entity Relationship Diagram explains the relationship among the entities
present in the database. ER models are used to model real-world objects like a
person, a car, or a company and the relation between these real-world objects.
In short, the ER Diagram is the structural format of the database.
Why Use ER Diagrams In DBMS?

1 ER diagrams are used to represent the E-R model in a database, which makes
them easy to convert into relations (tables).
2 ER diagrams provide the purpose of real-world modeling of objects which
makes them intently useful.
3 ER diagrams require no technical knowledge and no hardware support.
4 These diagrams are very easy to understand and easy to create even for a naive
user.
5 It gives a standard solution for visualizing the data logically.
COMPONENTS OF ER-DIAGRAM:
ER Diagram
 Practical 5
Practical name: Use Case Diagram
User case Diagram:
A Use Case Diagram is a vital tool in system design, it provides a visual
representation of how users interact with a system. It serves as a blueprint for
understanding the functional requirements of a system from a user’s perspective,
aiding in the communication between stakeholders and guiding the development
process.

USE CASE DIAGRAM

 Practical 6
Practical name: Sequence Diagram
Sequence Diagram:
Sequence Diagram: Sequence diagrams typically show the flow of functionality
through a use case, and consist of the following components: 1. Actors , involved
in the functionality 2. Objects , that a system needs to provide the functionality 3.
Messages , which represent communication between objects
Here, is an example of Sequence diagram for withdrawing amount from ATM
 Practical 7
Practical name: Class Diagram
Class Diagram: Class Diagram:- Class diagrams describe the static structure of
a system, or how it is structured rather than how it behaves. These diagrams
contain the following elements:
1. Classes , which represent entities with common characteristics or features.
These features include attributes, operations, and associations.
2. Associations , which represent relationships that relate two or more other
classes where the relationships have common characteristics or features. These
features include attributes and operations.
 Practical 8
Practical Name: Activity Diagram
An activity diagram is a type of UML (Unified Modeling Language) diagram that
represents the dynamic aspects of a system or process. It is commonly used to
model the workflow of a business process, a use case, or the flow of activities in
a system. Activity diagrams are especially useful for visualizing the sequential
and parallel activities within a process.
Key elements of an activity diagram include:
1. Activity: Represents a specific action or operation within the system or process.
Typically shown as rounded rectangles.
2. Transition/Arrow: Represents the flow of control from one activity to another.
Arrows indicate the direction of flow.
3. Decision Node (Diamond Shape): Represents a decision point where the flow
of control can take different paths based on conditions.
Usually labeled with a condition or constraint.
4. Merge Node (Diamond Shape with "+"): Indicates the merging of multiple
flows into a single flow after parallel activities.
Typically used after decision nodes.
5. Initial Node (Solid Circle): Represents the starting point of the activity
diagram.
6. Final Node (Encircled X or Circle with a Dot inside): Represents the end or
completion of the process.