ATM Security Requirements & Specification Decomposition Team B: Martijn Christiaan Vasilis Benjamin.

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
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.
Warm-up: April 11 What’s the difference between a checking and savings account?
Debit Card Plastic card that looks like a credit card
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.
1 Classes. 2 Finding classes w Choosing classes is first step in defining essence of problem w If you can recognize an abstraction, you’ve found a candidate.
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.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
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
Bank-affiliated Business Process Description Bank-affiliated Business Process 1.1 Precondition - Securities firm makes an agreement with more than.
Merijn Benjamin Christina
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Faculty of Computer & Information Software Engineering Third year
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.
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)
NITWITS NITPICKING Ard Bahlman. Assumptions  “A customer will be required to insert an ATM card and enter a personal identification number (PIN) which.
What are Sequence Diagrams? Collaboration Diagrams allow designer to specify message flow between collaborating objects –Focus on relationship between.
Information Systems Engineering Interaction Diagrams: Sequence Diagram Collbortion Diagram.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
ATM Adv. SW Engineering
Introduction to Business Analytics & Business Intelligence Information Systems Functions i-Clicker Demo IS vs IT IPO Model Note Taking.
IdentiTrip Key Features & Benefits All data imported from MIS system Quick MIS upload annually for new intake and class changes No manual input of pupil.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Building: Knowledge, Security, Confidence Check It Out FDIC Money Smart for Young Adults.
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.
1.7.2.G1 © Family Economics & Financial Education – Revised May 2005 – Financial Institutions Unit – Electronic Banking Funded by a grant from Take Charge.
Improvements Ales Sturala. Maintenance Money put in the vault Invalid cards taken from stack Forgotten money taken from vault Reading log from ATM software.
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.
1 Object-Oriented Static Modeling of the Banking System - II Lecture # 32.
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.
Kiosk Payment Systems, LLC
Using Use Case Diagrams
Paul Ammann & Jeff Offutt
Structured Analysis and Design Technique
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
Discover the Boom in Electronic Banking!
Easy Steps to Send Money in Quick Pay
How An ATM Work's Prepaid by, kakani Dinesh.
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Paul Ammann & Jeff Offutt
Using Use Case Diagrams
Real-Time Structured Analysis and Design Technique (RSTAD)
Presentation transcript:

ATM Security Requirements & Specification Decomposition Team B: Martijn Christiaan Vasilis Benjamin

System-wide functionality Logging – Every event must be chronologically logged Time and date Event type and details Account number if present – A video camera may be present and recording Timeouts – Upon timeouts current process must be aborted and possibly rolled back. – All functionality that awaits user input may provoke a timeout that will eject the card. – If the user does not take his/her card after ejection, it will be confiscated. – Upon communication with central service a timeout should be handled. Upon timeout eject card and enter out-of-order mode.

Card slot Assumed functionality: – Insert Card Read contents of magnetic strip Verify chip – Eject Card Timeout – Confiscate Card Can be signaled from card verification

Verification - ATM Assumption: Central service ATM Verification – ATM machine will authorize itself to the central service with some unique id. – All communication with central service must be secure. No outsiders can listen in. – Verifications must precede all transactions Central service must also be authorized

Verification - Card Card verification – Card must be verified at central service – PIN code must be verified at central service. – A user’s PIN code can NEVER be mentioned on screen, receipt or in logs. – Upon failed entry the card may be confiscated if signaled by the central service. – Card verification must precede all actions: Withdrawal, deposit, balance etc.

Withdrawal Try to commit withdrawal using central service. – On failure: 1.Receive error message from central service (like Daily Limit Exceeded etc.) 2.Eject card – On success: 1.Eject card 2.Wait for some specified period 3.If card was ejected cash out. Otherwise rollback transaction. (2 and 3 are an example of the requirement mentioned at Timeouts)

Deposit Notes are assumed to be identified, verified and counted by note slot. After user is finished, total amount is added to account through the Central Service. On succes – Eject card On failure – Eject card – Eject money

Alarms Alarm messages send to the maintenance service Physical damage sensors – Card slot – Vault – Screen – Buttons and keyboard – Video camera Maintenance – Outgoing vault (almost) empty – Incoming vault (almost) full Network communication failure

Specification Decomposition Hardware – Card slot – Cash dispenser and outgoing vault – Cash insertion and incoming vault – Screen, keyboard, button panel etc Hardware – Card slot – Cash dispenser and outgoing vault – Cash insertion and incoming vault – Screen, keyboard, button panel etc Core System Logging Maintenance Communication – ATM Central Service Verification Withdrawal Deposit Printing UI Central Sevice

Questions