ATM – requirements Team B Tom Hastjarjanto Martijn Nijenhof Ales Sturala Paul van der Ende.

Slides:



Advertisements
Similar presentations
GCSE ICT By the end of this session, you will be able to: Explain main features of ATM machines Identify features of credit cards, debit cards, smart cards.
Advertisements

What Are the Functions of ATM Machines?
Chapter 4: Requirements Engineering
BANKING SYSTEM Software Requirements Document CEN Advanced Software Engineering Fall Term
Use Case Diagrams Damian Gordon.
2.7.1.G1 © Family Economics & Financial Education – December 2005– Get Ready to Take Charge of Your Finances – Electronic Banking Bonanza – Slide 1 Funded.
Use Case & Use Case Diagram
ATM Security Requirements & Specification Decomposition Team B: Martijn Christiaan Vasilis Benjamin.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
USE CASE – ATM EXAMPLE Actors: ATM Customer ATM Operator Use Cases: The customer can withdraw funds from a checking or savings account query the balance.
Sample Problems for Testing For “Program” Level Testing: –Triangle –Next Date –Sales Commission For “System” Level Testing: –ATM system –Currency conversion.
1.2.2.G1 © Take Charge Today – Revised May 2010 – Electronic Banking Bonanza – Slide 1 Funded by a grant from Take Charge America, Inc. to the Norton School.
Warm-up: April 11 What’s the difference between a checking and savings account?
Debit Card Plastic card that looks like a credit card
ATM Case Study A Discussion.
Checking Account & Debit Card Simulation
UML and Systems Analysis MIS3502: Application Integration and Evaluation David Schuff
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
ATM User Interface V3. I/O Devices Input: Keyboardfor input, option select Keyboardfor input, option select Or Touch screen Or Touch screenOutput: Screenfor.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML
ATM User Interface Design. Requirements A bank customer is able to access his or her account using an automatic teller machine. To be able to use an ATM.
Tutorial 2. What is a UML Use Case Diagram? Use case diagrams model the functionality of a system using actors and use cases. Use cases are services or.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Data Flow Diagram Notations
Events & Messages Paul Ard Ales v2.0. Generic Exceptions  HardwareFail – the device does not respond  HardwareMalfunction – some part of the device.
Credit cards and Debit Cards, Credit and Debt
{ How to Use An ATM A simple tutorial to teach how to use ATM Machines.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Banking and Finance Business and Computer Science Mr. Dukes.
Use Cases 2 ENGR ♯10 Peter Andreae
Topic 4 : Know the features of a current account.
Merijn Benjamin Christina
30S Applied Math Mr. Knight – Killarney School Slide 1 Unit: Budgeting Lesson: Cheque Records & Deposit Slips Cheque Records & Deposit Slips Learning Outcome.
ICT and Banks Banks use mainframe computers to maintain customer accounts. They store a record of each customer’s withdrawals and deposits. Each bank mainframe.
SFWR ENG 3KO4 Software Development for Computer/Electrical Engineering Fall 2009 Instructor: Dr. Kamran Sartipi Software Requirement Specification (SRS)
NITWITS NITPICKING Ard Bahlman. Assumptions  “A customer will be required to insert an ATM card and enter a personal identification number (PIN) which.
January Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, Implement the ProductSpecification and Payment classes in any OO.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
ATM Adv. SW Engineering
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
GOALS BUSINESS MATH© Thomson/South-WesternLesson 3.2Slide 1 3.2Electronic Banking Record electronic banking transactions Find account balance when banking.
Learning Intentions Explain what an ATM is and the facilities offered Identify the stages of withdrawing cash from an ATM List the advantages and disadvantages.
1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde.
Events & Messages Merijn Paul Tom. Generic Exceptions  HardwareFail – the device does not respond  HardwareMalfunction – some part of the device is.
ATM environment assumptions Ard Christina Oscar Paul.
Lecture Outline Monday 23 rd February (Week 4) 3 – 3:10pm Review of Requirements Eng. and use cases 3:10 – 3:40pm Exercise on Use Case 3:40-4:40 Class.
Improvements Ales Sturala. Maintenance Money put in the vault Invalid cards taken from stack Forgotten money taken from vault Reading log from ATM software.
More bankingChecks, etc. Check types ServicesMisc. Banking Banking Services Game.
Do Now Why do people have checking accounts?. Unit 4: Lesson 13: Checking Accounts Day 1 Objective: identify vocabulary terms related to checking accounts.
UC Diagram & Scenario RKPL C & D. Using Use Case Diagram Use case diagrams are used to visualize, specify, construct, and document the (intended) behavior.
PD 21 Mrs. Biegel. NPR Podcast Banks are a business, they: Provide a safe place for people to deposit money Lend funds to people & businesses in temporary.
Daar is geen woord Chinees bij. Follows the push model, messages are not initiated by the software 2.
Unit 9 Finance and Banking. Electronic Banking What is E-Banking Electronic banking or e- banking gives people electronic access to bank accounts and.
Introduction What would our society be like now if we did not have ATm’s? Not able to access money when we urgently want it. You will have to go to the.
Teens 2 lesson six using banking services presentation slides 04/09.
Paul Ammann & Jeff Offutt
Dynamic Modeling of Banking System Case Study - I
SECURITY FEATURES OF ATM
Exercices & Corrections Week 3
Banking.
Paul Ammann & Jeff Offutt
Using Use Case Diagrams
using banking services
Teens 2 lesson six using banking services presentation slides 04/09.
using banking services
Discover the Boom in Electronic Banking!
Piggy Bank vs. Bank Choosing and Maintaining Your Account
Uses of Telecommunications & ICT
Presentation transcript:

ATM – requirements Team B Tom Hastjarjanto Martijn Nijenhof Ales Sturala Paul van der Ende

User services Balance inquiry Balance inquiry Withdraw money Withdraw money Deposit money Deposit money

User - Balance inquiry Show account balance Show account balance Print account balance Print account balance

User - Withdraw money User specifies amount of money to withdraw User specifies amount of money to withdraw Optionally specify which banknotes to receive Optionally specify which banknotes to receive Optionally print receipt Optionally print receipt Show transaction fee Show transaction fee

User - Deposit money Puts banknotes in the ATM Puts banknotes in the ATM Choose account where to store the money Choose account where to store the money Optionally print receipt Optionally print receipt

ATM ATM consists of: ATM consists of: vault vault system system user interface user interface Generic service Generic service Intermediate service between ATM and client’s bank Intermediate service between ATM and client’s bank ATM accepts only cards from banks supported by the generic service ATM accepts only cards from banks supported by the generic service

System System communicates with a generic service that handles requests between ATM and bank where client has an account System communicates with a generic service that handles requests between ATM and bank where client has an account User can use credit/debit card from any bank supported by the generic service User can use credit/debit card from any bank supported by the generic service Communicates with the vault Communicates with the vault

System - security Authentication is done using card and pin code Authentication is done using card and pin code User is authenticated through generic service in his bank User is authenticated through generic service in his bank Refuse service if authentication fails Refuse service if authentication fails Take card if client enters invalid pin code for three times in a row Take card if client enters invalid pin code for three times in a row Client gets money  money is subtracted from account Client gets money  money is subtracted from account If physical damage is detected, vault gets locked and remote alarm is triggered If physical damage is detected, vault gets locked and remote alarm is triggered Use secure connection between generic service and ATM system Use secure connection between generic service and ATM system When client doesn’t respond within a proper time frame, card is taken and user is signed off When client doesn’t respond within a proper time frame, card is taken and user is signed off

System - Balance inquiry Client must be authenticated Client must be authenticated Asks generic service for amount of money on client’s account Asks generic service for amount of money on client’s account

System - Withdraw money Client must be authenticated Client must be authenticated User can withdraw money only if a bank allows that User can withdraw money only if a bank allows that Check if vault can emit requested bank notes and amount of money Check if vault can emit requested bank notes and amount of money If money aren’t taken out of the ATM by the client in 1 minute, take the money back and check if the amount didn’t change If money aren’t taken out of the ATM by the client in 1 minute, take the money back and check if the amount didn’t change

System - Deposit money Client must be authenticated Client must be authenticated Allow client to put bank notes in the ATM Allow client to put bank notes in the ATM Money is always put onto client’s account Money is always put onto client’s account System checks whether client’s bank support ATM money deposit System checks whether client’s bank support ATM money deposit System checks if bank notes are valid System checks if bank notes are valid In the list of accepted bank notes provided by the bank In the list of accepted bank notes provided by the bank

User interface Welcome screen when ATM isn’t used Welcome screen when ATM isn’t used Could be customized remotely Could be customized remotely Error screen if the ATM is out of service Error screen if the ATM is out of service