Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

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.
Use Case Model. C-S 5462 Use case model describes what the user expects the system to do –functional requirements may describe only the functionalities.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
What are the questions really asking?
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
Requirements and Design
Lecture 8 Electronic Commerce Modelling Techniques
Information System Design IT60105 Lecture 3 System Requirement Specification.
ATM – requirements Team B Tom Hastjarjanto Martijn Nijenhof Ales Sturala Paul van der Ende.
Paul Deitel, CEO Deitel & Associates, Inc.. Contact Information  Paul Deitel, CEO  Deitel & Associates, Inc.  Twitter:  Facebook:
Information System Design IT60105
Bank On It.
Lecture 9 Object-Oriented Analysis
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.
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Introduction to Software Engineering
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Object Oriented Analysis Process
Inception What needs to be done? Describe the vision and business case for this project. Determine if the project is feasible. Determine if the enterprise.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements 2.
Check It Out 1. 2 Introductions Instructor and student introductions Module overview.
Chapter 13: Designing the User Interface
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
3. 18 Methods of making and receiving payments Methods of making and receiving payments Banks and bank accounts  All businesses have bank accounts.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Rational Unified Process (Part 1) CS3300 Fall 2015.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
Check It Out. 2 You Will Know  The benefits of using a credit union or bank vs. using a check cashing service  Types of fees  Types of checking accounts.
Lecture 3: Information Engineering Dr. Taysir Hassan Abdel Hamid November 3, 2014.
CS212: Object Oriented Analysis and Design Lecture 4: Objects and Classes - I.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
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.
Faculty of Computer & Information Software Engineering Third year
Chapter 6 A Use-Case-Driven Process. 2 Definitions The choice of models and the choice of techniques used to express them have a significant impact on.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
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.
Chapter 7 Applying UML and Patterns Craig Larman
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)
Faculty of Computer & Information
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Lecture OO05 Object Scenarios Object Interaction Diagrams
January Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, Implement the ProductSpecification and Payment classes in any OO.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Lecture 3: Methods for Architecture Development Information Engineering Dr. Taysir Hassan October 19, 2015.
Check It Out 1. 2 Introductions Instructor and student introductions Module overview.
GOALS BUSINESS MATH© Thomson/South-WesternLesson 3.2Slide 1 3.2Electronic Banking Record electronic banking transactions Find account balance when banking.
Session 5 Object Model Development. OOAD with UML / Session 5 / 2 of 19 Review A class icon is a rectangle with three sections within it An object is.
Identification of Classes. Object Oriented Analysis (OOA) OOA is process by which we identify classes that play role in achieving system goals & requirements.
Requirements Document for the Banking System
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
Software Engineering USE CASE DIAGRAM.
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.
IT’S ALL ABOUT THE INTERFACES Jeffrey Eyster Indianapolis, IN.
CMPE 280 Web UI Design and Development August 29 Class Meeting
Structured Analysis and Design Technique
Dynamic Modeling of Banking System Case Study - I
Use Case Model.
Object-Oriented Static Modeling of the Banking System - I
Introduction to Unified Modeling Language (UML)
17 Banking and Financial Services
Software Requirements
using banking services
Real-Time Structured Analysis and Design Technique (RSTAD)
Uses of Telecommunications & ICT
Presentation transcript:

Case Study :

Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must be able to handle a growth in ATM terminals and an expanding geographical area. It will have to be able to readily form an interface with other ATM networks in other parts of the world. The ATM network will provide services to users and collaborate with other banking networks as indicated in the diagram on the next slide.

We envision a banking system that provides automatic teller machines (ATMs) at which customers holding a bank card can make deposits and withdrawls to and from their accounts. The ATM machines will belong to a consortium of banks participating in this project. ATM machines will be attractive to banking customers because they allow access to their accounts outside of regular business hours. They allow the bank to expand customer services and geographical reach without the cost of building additional branches or hiring additional tellers. Business Opportunity Vision Vision and Business Case

Customer ATM Network Member Bank Customer Accounts Use services Actors Consortium Computer System Use Case Model User Goals Customer – Make withdrawals, deposits, and balance checks to his/her account. Consortium server must be able to identify the home bank of the customer card. Banks owning an ATM must be able to determine the cash on hand in the ATM Use Case Model: functional requirements

Human Factors Reliability Performance Configurability Implementation Constraints Interfaces Business Rules Secure transaction Real-time transactions Legal Issues Each transaction should require less than 1 minute of customer’s time The consortium computer must keep a transaction record for member banks to use for comparison Projected growth rate of the ATM base and member banks. Recommend a Linux based consortium server and java as the programming language for ATM client code. Text visible from at least 1 meter. Clear, step-by-step instructions for use. Card reader in ATM. Touch screen monitor. Receipt printer. Fee structure charged by member banks. Supplementary specifications

Glossary In the example shown here, The term ATM refers to both the physical terminal and the supporting software that it contains. Glossary is refined (during elaboration) to include : Format (type, length, unit) Range of values Validation rules Term Definition and InformationAliases ATM A banking terminal and required software for processing customer transactions Automatic teller machine

Prototypes : to clarify purpose Sample Model Drawing Program Screen sketches User interface prototype

Time frame for the iteration: Start date: Jan. 15, 2008 End Date: Feb. 6, 2008 Deliverable Artifacts Use cases: Access Account Deposit Withdraw Balance Statement Domain Model (Concept Model Diagram) Software prototype A simulation demonstrating the user interaction with an ATM terminal Test Plan Use Case Diagrams Sequence Diagram Iteration Plan

Preliminary User Manual Developed Describe the appearance of the screen and the sequence of actions that the user must perform Iteration Plan(cont.)

Discipline – Requirements - Artifacts Browse glossary vision Supplementary specifications Use case Use case model