Events & Messages Merijn Paul Tom. Generic Exceptions  HardwareFail – the device does not respond  HardwareMalfunction – some part of the device is.

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.
Use Case & Use Case Diagram
ELECTION DAY ACTIVITIES. Checklist of contents of the box PCOS machine and its power adaptor Thirteen (13) rolls of official thermal paper Three (3)
ATM Security Requirements & Specification Decomposition Team B: Martijn Christiaan Vasilis Benjamin.
1 Object-oriented design Part 2: OO tools & UML. 2 CRC cards Design tool & method for discovering classes, responsibilities, & relationships Record on.
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.
Requirements for Opening a Checking Account
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.
Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
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.
Navy Cash Cardholder Procedures SYSTEMS C ORPORATION ELDYNE Division.
INTERACTION DIAGRAMS Example Kingdom of Saudi Arabia Ministry of Higher Education Princess Noura bint Abdulrahman University College of Computer & Information.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Use Cases 2 ENGR ♯10 Peter Andreae
Merijn Benjamin Christina
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
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
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.
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.
SFWR ENG 3KO4 Software Development for Computer/Electrical Engineering Fall 2009 Instructor: Dr. Kamran Sartipi Software Requirement Specification (SRS)
Chapter 9 Checking Accounts.
NITWITS NITPICKING Ard Bahlman. Assumptions  “A customer will be required to insert an ATM card and enter a personal identification number (PIN) which.
Module 1.5 Problems with I/O devices and storage Theme: Finding solutions.
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.
ATM environment assumptions Ard Christina Oscar Paul.
RTM (Robotic Teller Machine) By Jonathan Daudelin Construction Time : February – June 2006 Parts used : 2 RCX’s, 4 Motors, 4 Sensors, Hundreds of Legos.
The following shows the steps of adding value in Octopus card. Can you put them in correct order? Motivation A Insert the Octopus card into the card slot.
DS200 PROCEDURES SPEAKER TOUCH SCREEN DISPLAY
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.
Chapter 3: Software Design –Use case Diagram Nouf Alghanmi.
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.
Daar is geen woord Chinees bij. Follows the push model, messages are not initiated by the software 2.
Vending Machine Through Mobile (A BLUE TOOTH BASED APPLICATION)
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.
ATM OO Design and Implementation Case Study
Event-driven programming
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
How An ATM Work's Prepaid by, kakani Dinesh.
Real-Time Structured Analysis and Design Technique (RSTAD)
Presentation transcript:

Events & Messages Merijn Paul Tom

Generic Exceptions  HardwareFail – the device does not respond  HardwareMalfunction – some part of the device is not working correctly Device still responds and knows what is wrong Example are: Device is jammed, a part is not functioning.

Card slot events/messages  Events: Card slot  ATMSoftware Card inserted Card removed  Messages: ATMSoftware  Card slot Retrieve card information Send card to invalid card stack Eject card  Exceptions InvalidCard - card is unreadable/invalid CardStackFull - invalid card stack full EjectCardFail - unable to eject card

Bill slot events/messages Slot for withdrawing bills  Bill slot  ATMSoftware Bills taken  ATMSoftware  Bill slot Eject bills Retrieve bills

Bill verifier & counter events/messages  Bill counter  ATMSoftware Valid bill counted Invalid bill detected

Vault events/messages  Vault  ATMSoftware Vault empty Vault refilled Deposit vault full  ATMSoftware  Vault Retrieve x amount of y bills

Deposit events/messages  Coin slot  ATMSoftware Coin of value x inserted Invalid coin inserted  ATMSoftware  Coin slot Return coins  Bill slot + counter handles deposited bills

Printer events/messages  Printer  ATMSoftware Out of paper Out of toner  ATMSoftware  Printer Print data x Check paper status Check toner status

UI events  Keyboard  ATMSoftware Key x pressed  ATMSoftware  Screen Display bitmap  ATMSoftware  Speaker Play sound x

Security events  Security sensors  ATMSoftware Intrusion detected  ATMSoftware  Security sensors Request status

Bank server events/messages  Bank server  ATMSoftware Welcome screen Software update  ATMSoftware  Bank server Authenticate PIN + card number for account x  Response Retrieve balance on account x  Response Withdraw amount x from account y Deposit amount x on account y Request maintenance Intrusion detected

Maintenance  Device failure Mechanic needs to bring a new device  Device malfunction Mechanic needs to bring tools  Toner empty Mechanic needs to bring new toner  Paper empty Mechanic needs to bring paper  Low on banknotes Bank needs to transfer money to the ATM  Card stack full Bank needs to empty invalid card slot  Deposit box full Bank needs to transfer money to the bank

Questions?