January 200491.3913 Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, 2004 1.Implement the ProductSpecification and Payment classes in any OO.

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

1.7.2.G1 © Family Economics & Financial Education – Revised February 2008 – Financial Institutions Unit – Electronic Banking Funded by a grant from Take.

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.

Warm-up: April 11 What’s the difference between a checking and savings account?

Requirements for Opening a Checking Account

UML and Systems Analysis MIS3502: Application Integration and Evaluation David Schuff

CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.

Lecture 8 Electronic Commerce Modelling Techniques

ATM – requirements Team B Tom Hastjarjanto Martijn Nijenhof Ales Sturala Paul van der Ende.

Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.

CS3773 Software Engineering Lecture 03 UML Use Cases.

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.

Chapter 12 ATM Case Study, Part 1: Object-Oriented Design with the UML

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.

Interaction Diagrams Activity Diagram State Machine Diagram

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

Use Cases & Requirements Analysis By: Mostafa Elbarbary.

Mr. Stasa – Willoughby-Eastlake City Schools ©. Essential Question #8  In your opinion, how has technology improved and/or damaged the banking industry?

{ 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.

Chapter © 2010 South-Western, Cengage Learning Checking Accounts and Banking Services Banking Services and Fees 9.

Part 4: Debit Cards Dollars & Sense. What Happens If They Don’t Take Checks? Use a Debit Card! Click Visa Debit Commerical 

From Problem Statement to Design

2.7.1.G1 © Family Economics & Financial Education – December 2005 – Get Ready To Take Charge of Your Finances – Electronic Banking Bonanza Funded by a.

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

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 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

Lecture OO05 Object Scenarios Object Interaction Diagrams

1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section

ATM Adv. SW Engineering

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.

Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.

1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde.

UML (Unified Modeling Language)

Topic sentence--2. People need to get a bank card if they want to use an ATM. bank card In order to apply, you must fill out an application. Once you.

Computer Studies Today Chapter 2 1 » Payroll system » Mailing list system » Ticketing system » Point-of-sale system » Electronic funds transfer system.

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.

Electronic Banking 7.3. EFT  Electronic Funds Transfer Banks ability to move money from one account to another by computer  Advantages to Banks (Cost.

© Thomson/South-Western ECONOMIC EDUCATION FOR CONSUMERS Slide 1 Chapter 7 LESSON 7.3 Electronic Banking Objectives: By the end of class, students will.

Unit 9 Finance and Banking. Electronic Banking What is E-Banking Electronic banking or e- banking gives people electronic access to bank accounts and.

Sept Ron McFadyen1 Include Relationship UC1:Process Sale … Main Success Scenario … 7. Customer pays and System handles payment. … Extensions.

Shared Branching Presented by: Sandy Shenk, PaCUSC State Coordinator.

1 Case Study and Use Cases for Case Study Lecture # 28.

ATM OO Design and Implementation Case Study

Dynamic Modeling of Banking System Case Study - I

Object-Oriented Static Modeling of the Banking System - I

Discover the Boom in Electronic Banking!

How An ATM Work's Prepaid by, kakani Dinesh.

Information on Types of Electronic Banking

Discover the Boom in Electronic Banking!

Use Case Modeling - techniques for detailing use cases

Discover the Boom in Electronic Banking!

Real-Time Structured Analysis and Design Technique (RSTAD)

Piggy Bank vs. Bank Choosing and Maintaining Your Account

Uses of Telecommunications & ICT

Presentation transcript:

January Ron McFadyen1 January 2004 Assignment 1 Due: Friday Jan 23, Implement the ProductSpecification and Payment classes in any OO programming language (reference: Figure and section 20.11). Two additional classes you require are ProductSpecificationTest and PaymentTest (reference: Section 20.9). Hand in the source code for each of the above 4 classes and the results from running your tests. Note that the class methods expect valid data. 2.Create a use case model for an ATM. Details follow.

January Ron McFadyen2 January 2004 Assignment 1 Automated Teller Machine (ATM) The ATM system services one customer at a time. A customer is required to insert an ATM card and key in a personal identification number (pin). During one session, a customer may perform any number of transactions on any of their accounts. A customer may also choose to end the session and their card is automatically returned. A customer may make a cash withdrawal transaction from any of his/her accounts. Of course, the customer must have enough funds in the account to cover the withdrawal. A customer may make a deposit to any of his/her accounts. When making a deposit, the customer must place the deposit in an envelope and insert that into the appropriate slot when the systems requests. A customer may transfer money between any of their accounts. When a customer inserts their card into the ATM machine, they have three chances to enter the pin correctly. If they fail to do so, the card is not returned. After a transaction completes, the system prints a receipt and asks the customer if they will do another transaction or quit.

January Ron McFadyen3 January 2004 Assignment 1 Using the brief format in section 6.1, write separate use cases for the following uses cases: Session, Withdrawal, Deposit, Transfer, Inquiry, and Invalid pin. Relate these use cases with a mixture of “include” and “extend”. This is important for the following: Write the Main Success Scenario (reference Section 6.6 on Fully Dressed use cases) and a System Sequence Diagram for the Session use case (this one will have repetition similar to Process Sale use case). Create a use case diagram for your Use Case Model (reference Figure 6.2 and Figures 25.1, 25.2). To review, you must hand in: A Use case diagram (use Rational Rose or other tool) Brief formats for six use cases The main success scenario for the Fully Dressed use case