Scribd
Upload
2K views4 pages

WATERFALL MODEL For ATM SYSTEM

The document outlines a waterfall model for developing an ATM system with 7 phases: 1) Requirement Gathering which defines user login/logout, password change, profile editing, balance checking, withdrawals, statements, and account details. 2) Requirement Analysis analyzes the requirements. 3) Design designs the system after analysis. 4) Implementation codes the system after design. 5) Testing 1 tests the system after coding. 6) Testing 2 performs final testing. 7) Maintenance maintains the system after testing.

Uploaded by

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

WATERFALL MODEL For ATM SYSTEM

The document outlines a waterfall model for developing an ATM system with 7 phases: 1) Requirement Gathering which defines user login/logout, password change, profile editing, balance checking, withdrawals, statements, and account details. 2) Requirement Analysis analyzes the requirements. 3) Design designs the system after analysis. 4) Implementation codes the system after design. 5) Testing 1 tests the system after coding. 6) Testing 2 performs final testing. 7) Maintenance maintains the system after testing.

Uploaded by

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

WATERFALL MODEL FOR ATM

SYSTEM

Groug01
•Hansi Nipunika
•Kaushalya Sandamali
•Thimal Ranjula
•Kalana Harshana
•Thilanaka Thisara
 SDLC Model For ATM System
WATERFALL MODEL
1. Requirement Gathering
 User Login/ Logout
 User password change
 Edit Profile
 Check Balance
 Balance Withdraw
 Mini Statement
 Account Details

2.Requirement Analysis- analysis the clear requirements


3.Design- after analyzing requirements design the system.
4.implementation- after designing requirements coding the system.
5.Testing 1- after coding test the system.
6.Testing 2- after testing 1 final test
7.maintains- after testing maintain the system
THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy