SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples.

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
2.7.1.G1 © Family Economics & Financial Education – December 2005– Get Ready to Take Charge of Your Finances – Electronic Banking Bonanza – Slide 1 Funded.
1.7.2.G2 Electronic Banking Trivia G2 © Family Economics & Financial Education – Revised February 2008 – Financial Institutions Unit – Electronic.
ATM Security Requirements & Specification Decomposition Team B: Martijn Christiaan Vasilis Benjamin.
Lecture 10 Enterprise Systems Development ( CSC447 ) COMSATS Islamabad Muhammad Usman, Assistant Professor.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
1.7.2.G1 © Family Economics & Financial Education – Revised February 2008 – Financial Institutions Unit – Electronic Banking Funded by a grant from Take.
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.
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.
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.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
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.
Part 2: Computers used in Banking
Checking Account & Debit Card Simulation Understanding Checking Accounts and Debit Card Transactions.
{ How to Use An ATM A simple tutorial to teach how to use ATM Machines.
Credit Card vs. Debit Card. Debit Cards Also called “check cards” –Works just like writing a check Deducts money from your checking account.
Chapter © 2010 South-Western, Cengage Learning Checking Accounts and Banking Services Banking Services and Fees 9.
Members Ashley-Gail Wright Jade Mills Sami-Jo Bryant Ruth-Ann Robinson Kimberly Grey.
1.7.2.G1 © Family Economics & Financial Education – Revised May 2009 – Financial Institutions Unit – Electronic Banking Funded by a grant from Take Charge.
Merijn Benjamin Christina
DO NOW:  Take packet:  Review the bank statement on page 3 of the packet.  In your notebook: What items does a bank statement include?
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.
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
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
Unit 3 Functional Requirements. Syllabus Introduction Features and usecases Use case Scenarios Documenting use cases Levels of details SRS Document.
GOALS BUSINESS MATH© Thomson/South-WesternLesson 3.2Slide 1 3.2Electronic Banking Record electronic banking transactions Find account balance when banking.
Business Math 3-2 Electronic Banking. Start up Marc uses his charge card to pay for almost everything he buys. Lenore pays for most of her purchases with.
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.
Checking Account & Debit Card Understanding Checking Accounts and Debit Card Transactions.
Checking & Savings Accounts Economics What is a Checking Account?  Common financial service used by many consumers (a place to keep money)  Funds.
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.
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
Electronic Banking 7.3. EFT  Electronic Funds Transfer Banks ability to move money from one account to another by computer  Advantages to Banks (Cost.
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
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.
Paul Ammann & Jeff Offutt
Use Case Modeling - II Lecture # 27.
Structured Analysis and Design Technique
Take Charge of Your Finances
Dynamic Modeling of Banking System Case Study - I
SECURITY FEATURES OF ATM
Object-Oriented Static Modeling of the Banking System - I
Discover the Boom in Electronic Banking!
Software Modeling Lecture # 11.
How An ATM Work's Prepaid by, kakani Dinesh.
Paul Ammann & Jeff Offutt
Take Charge of Your Finances
Muhammad Ahmad Kahloon
Discover the Boom in Electronic Banking!
Real-Time Structured Analysis and Design Technique (RSTAD)
Take Charge of Your Finances
Piggy Bank vs. Bank Choosing and Maintaining Your Account
Uses of Telecommunications & ICT
Presentation transcript:

SWE 214 (071) Use Case Diagrams Slide 1 Use Case Diagrams Examples

SWE 214 (071) Use Case Diagrams Slide 2 ATM: Problem Description l A bank has several automated teller machines (ATMs), which are geographically distributed and connected via a wide area network to a central server. Each ATM machine has a card reader, a cash dispenser, a keyboard/display, and a receipt printer. By using the ATM machine, a customer can withdraw cash from either a checking or savings account, query the balance of an account, or transfer funds from one account to another. A transaction is initiated when a customer inserts an ATM card into the card reader. Encoded on the magnetic strip on the back of the ATM card are the card number, the start date, and the expiration date. Assuming the card is recognized, the system validates the ATM card to determine that the expiration date has not passed, that the user-entered PIN (personal identification number) matches the PIN maintained by the system, and that the card is not lost or stolen. The customer is allowed three attempts to enter the correct PIN; the card is confiscated if the third attempt fails. Cards that have been reported lost or stolen are also confiscated.

SWE 214 (071) Use Case Diagrams Slide 3 ATM: Problem Description (Cont’d) l If the PIN is validated satisfactorily, the customer is prompted for a withdrawal, query, or transfer transaction. Before a withdrawal transaction can be approved, the system, determines that sufficient funds exist in the requested account, that the maximum daily limit will not be exceeded, and that there are sufficient funds at the local cash dispenser. If the transaction is approved, the requested amount of cash is dispensed, a receipt is printed containing information about the transaction, and the card is ejected. Before a transfer transaction can be approved, the system determines that the customer has at least two accounts and that there are sufficient funds in the account to be debited. For approved query and transfer requests, a receipt is printed and the card is ejected. A customer many cancel a transaction at any time; the transaction is terminated and the card is ejected. Customer records, account records, and debit card records are all maintained at the server.

SWE 214 (071) Use Case Diagrams Slide 4 ATM: Problem Description (Cont’d) l An ATM operator may start up and close down the ATM to replenish the ATM cash dispenser and for routine maintenance. It is assumed that functionally to open and close accounts and to create, update, and delete customer and debit card records is provided by an existing system and is not part of this problem.

SWE 214 (071) Use Case Diagrams Slide 5 l A bank has several automated teller machines (ATMs), which are geographically distributed and connected via a wide area network to a central server. Each ATM machine has a card reader, a cash dispenser, a keyboard/display, and a receipt printer. By using the ATM machine, a customer can withdraw cash from either a checking or savings account, query the balance of an account, or transfer funds from one account to another. A transaction is initiated when a customer inserts an ATM card into the card reader. Encoded on the magnetic strip on the back of the ATM card are the card number, the start date, and the expiration date. Assuming the card is recognized, the system validates the ATM card to determine that the expiration date has not passed, that the user-entered PIN (personal identification number) matches the PIN maintained by the system, and that the card is not lost or stolen. The customer is allowed three attempts to enter the correct PIN; the card is confiscated if the third attempt fails. Cards that have been reported lost or stolen are also confiscated.

SWE 214 (071) Use Case Diagrams Slide 6 l If the PIN is validated satisfactorily, the customer is prompted for a withdrawal, query, or transfer transaction. Before a withdrawal transaction can be approved, the system, determines that sufficient funds exist in the requested account, that the maximum daily limit will not be exceeded, and that there are sufficient funds at the local cash dispenser. If the transaction is approved, the requested amount of cash is dispensed, a receipt is printed containing information about the transaction, and the card is ejected. Before a transfer transaction can be approved, the system determines that the customer has at least two accounts and that there are sufficient funds in the account to be debited. For approved query and transfer requests, a receipt is printed and the card is ejected. A customer many cancel a transaction at any time; the transaction is terminated and the card is ejected. Customer records, account records, and debit card records are all maintained at the server.

SWE 214 (071) Use Case Diagrams Slide 7 l An ATM operator may start up and close down the ATM to replenish the ATM cash dispenser and for routine maintenance. It is assumed that functionally to open and close accounts and to create, update, and delete customer and debit card records is provided by an existing system and is not part of this problem.

SWE 214 (071) Use Case Diagrams Slide 8 ATM System

SWE 214 (071) Use Case Diagrams Slide 9 ATM: Use Case Model

SWE 214 (071) Use Case Diagrams Slide 10 ATM: Use Case Model

SWE 214 (071) Use Case Diagrams Slide 11 Cell Phone System

SWE 214 (071) Use Case Diagrams Slide 12 Cell Phone System: Use Case Model