Daar is geen woord Chinees bij. Follows the push model, messages are not initiated by the software 2.

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

Chapter 4: Requirements Engineering
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 Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
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.
SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.
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.
ATM Case Study A Discussion.
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 – requirements Team B Tom Hastjarjanto Martijn Nijenhof Ales Sturala Paul van der Ende.
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.
Customer Service Module Course Contents Table of Contents Enter A Request Search A Request Create Invoice (Funeral home request) Search Invoice Manage.
ATM : A.T.M Done by Shakila Sattar. What is an A.T.M.? Automated teller machine Or Automatic teller machine.
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML
Events & Messages Paul Ard Ales v2.0. Generic Exceptions  HardwareFail – the device does not respond  HardwareMalfunction – some part of the device.
{ How to Use An ATM A simple tutorial to teach how to use ATM Machines.
INTERACTION DIAGRAMS Example Kingdom of Saudi Arabia Ministry of Higher Education Princess Noura bint Abdulrahman University College of Computer & Information.
Use Cases 2 ENGR ♯10 Peter Andreae
Merijn Benjamin Christina
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
Banking Chapter 7 Money Barter –Trade item for item –May not account for true value Currency –Paper money and coins used for financial transactions –Smaller.
1 Object-Oriented Analysis Use Case Driven. 2 The outline method for OOA 1.Identify object classes within the problem domain 2.Define the behaviour of.
Use Case Diagram: Exercise 5 and 6 Yong Choi BPA CSUB.
Faculty of Computer & Information Software Engineering Third year
UML basics UML distilled, a brief guide to the standard Modeling language, by Martin Fowler, 2000.
Chapter 3, Section 3 ELECTRONIC BANKING.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
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.
Access Online Cardholder Transaction Approval Training 1 Client Logo.
Computer A computer is an electronic machine that takes information, processes it,and stores it. Computers are made up of hardware ( monitor, tower, keyboard,
SFWR ENG 3KO4 Software Development Fall 2009 Instructor: Dr. Kamran Sartipi Software Requirement Specification (SRS) for the Automated Banking Machine.
Sample Problems for Testing
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 LAB What is Collaboration diagram? 4 Collaboration diagrams illustrate the interaction between the objects, using static spatial structure. 4.
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.
Checking & Savings Accounts Economics What is a Checking Account?  Common financial service used by many consumers (a place to keep money)  Funds.
1 Work Orders. 2 Generating a Work Order There are two methods to generating a Work Order in the WYNNE STSTEM. First method: Option 11 – 12 – 13 * Open.
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.
Kiosk Payment Systems, LLC. Payment Options Accepted The kiosk allows users to make full or partial payments of court fines by cash or card. All dollar.
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.
Requirements Document for the Banking System
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
1 Case Study and Use Cases for Case Study Lecture # 28.
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.
Paul Ammann & Jeff Offutt
Dynamic Modeling of Banking System Case Study - I
SECURITY FEATURES OF ATM
Object-Oriented Static Modeling of the Banking System - I
Exercices & Corrections Week 3
Paul Ammann & Jeff Offutt
Real-Time Structured Analysis and Design Technique (RSTAD)
Presentation transcript:

Daar is geen woord Chinees bij

Follows the push model, messages are not initiated by the software 2

Card slot card inserted (card data)—fired upon complete insertion only card ejected card removed Bills slot bills taken Input device (keyboard, touchscreen etc.) keypress (key) Bill scanner valid money inserted (bill value) invalid money inserted Coin scanner valid money inserted (coin value) invalid coin inserted Security sensors intrusion detected (details) 3

Follows the pull model, messages are initiated by the software 4

All devices Request operational status Response: status OK, or hardware malfunction (details) no response at all (in case of complete failure) Screen display text/picture (data) Card slot retrieve card information response: card details eject card response: OK | NOT-OK send card to confiscated card stack response: OK | NOT-OK 5

Confiscated card stack check remaining space response: OK | NOT-OK Withdraw vault retrieve money from withdrawing vault (array of bills) check remaining supply response: stock levels (list of (banknote, amount)) – ‘banknote’ indicates the currency and value of the note, ‘amount’ indicates how many of those there are left. 6

Deposit vault check remaining capacity response: capacity levels (list of (banknote, amount)) – ‘banknote’ indicates the currency and value of the note, ‘amount’ indicates how many there is still room for. Forgotten money vault print information card (data to print) check remaining space response: OK | NOT-OK check stocks response: OK | out of information cards | out of ink 7

Bill scanner enable bill insertion and set currency (currency) disable bill insertion Coin scanner enable coin insertion disable coin insertion set currency (currency) 8

Input drawer return money send money to vault check remaining space response: OK | NOT-OK Receipt printer print (data) check paper status response: OK | NOT-OK check ink status response: OK | NOT-OK Speaker play annoying sound (annoying sound) 9

Follows the pull model, messages are initiated by the software 10

 check card support (card data) – Checks if card is supported by central service ◦ Response: Supported | Unsupported(details)  authenticate (card data, pin) ◦ Response: Accept(Accounts list) | Reject(details) | Confiscate  supported transactions (card data, pin, account) ◦ Response: Balance and/or Withdraw and/or Deposit, or None  retrieve balance on account (card data, pin, account) ◦ Response: Balance(amount, currency) 11

 withdraw amount from account (card data, pin, account, amount, currency) ◦ Response: Accepted(transaction ID) | Rejected(reason)  deposit amount y on account (card data, pin, account, amount, currency) ◦ Response: Accepted | Rejected(reason)  maintenance needed (device, problem) – used when paper runs out etc.  intrusion detected (details) 12

 get withdraw fee (card data, pin, account, amount, currency) ◦ Response: fee  money not taken (card data, pin, account, currency, transaction ID)  card confiscated (card data, reason) – Cards can be confiscated for various reasons  fatal error (error details)  Get new welcome screen ◦ Response: details 13

Follows the push model, messages are not initiated by the software 14

 Disable ATM – sets the atm out of service  Enable ATM - sets the atm in a state so that users can use it 15