Exercices & Corrections Week 3

Slides:



Advertisements
Similar presentations
Context Diagram Yong Choi BPA CSUB.
Advertisements

What Are the Functions of ATM Machines?
Chapter 4: Requirements Engineering
Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer.
Use Case Diagrams Damian Gordon.
Use Case & Use Case Diagram
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 7 – More on use cases and activity diagrams.
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.
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.
Introduction to Software Testing Chapter 2.6 Graph Coverage for Use Cases Paul Ammann & Jeff Offutt
Lecture 8 Electronic Commerce Modelling Techniques
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.
CS3773 Software Engineering Lecture 03 UML Use Cases.
{ 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.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
From Problem Statement to Design
Use Cases 2 ENGR ♯10 Peter Andreae
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Merijn Benjamin Christina
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Developing Use Cases in a Group Carolyn L. Cukierman Face-to-Face Technology Conference March 27, 2000.
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
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
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.
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
Requirements specification Why is this the first major stage of software development? –Need to understand what customer wants first Goal of requirements.
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Scenario A scenario is a sequence of steps describing an interaction between a user and a system. Use case is a set of scenarios tied together by a common.
1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde.
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.
Chapter 3: Software Design –Use case Diagram Nouf Alghanmi.
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 Case Study and Use Cases for Case Study Lecture # 28.
Using Use Case Diagrams
Paul Ammann & Jeff Offutt
Output “Funds not available”
CMPE 280 Web UI Design and Development August 29 Class Meeting
Use Case Modeling - II Lecture # 27.
Structured Analysis and Design Technique
Storyboarding and Game Design SBG, MBG620 Full Sail University
Dynamic Modeling of Banking System Case Study - I
Requirements Analysis
SECURITY FEATURES OF ATM
Object-Oriented Static Modeling of the Banking System - I
UML Use Case Diagrams.
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Functional Testing Testing against the Requirements
Use Case Modeling - techniques for detailing use cases
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Paul Ammann & Jeff Offutt
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Using Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Real-Time Structured Analysis and Design Technique (RSTAD)
Test Design Techniques Software Testing: IN3240 / IN4240
Presentation transcript:

Exercices & Corrections Week 3

Exercise (2) Abstract from the example scenarios (p10&19) and put the Regnell’s approach in the Reference Framework

Regnell’s UCM (Use Case Model) 1. Withdraw Cash, normal case Actor: ‘ATM customer’ 1.IC Invocation Conditions: 1.IC.1 The system is ready for transactions. 1.FC Flow Conditions: 1.FC.1 The user’s card is valid. 1.FC.2 The user enters a valid code. 1.FC.3 The user enters a valid amount. 1.FC.4 The machine has the required amount of cash. 1.FE Flow of Events: 1.FE.1 The user inserts the card. 1.FE.2 The system checks if the card is valid. 1.FE.3 A prompt for the code is given 1.FE.4 The user enters the code. 1.FE.5 the system checks if the code is valid 1.FE.6 A prompt ‘enter amount or select balance’ is given. 1.FE.7 The user enters the amount. 1.FE.8 The system checks if the amount is valid 1.FE.9 The system collects the cash. 1.FE.10 The cash us ejected. 1.FE.11 A prompt ‘take cash’ is given. 1.FE.12 The user takes the cash. 1.FE.13 The card is ejected. 1.FE.14 A prompt ‘ take card’ is given. 1.FE.15 The user takes the card; 1.FE.16 The system collects receipt information. 1.FE.17 The receipt is printed. 1.FE.18 A prompt ‘take receipt’ is given. 1.FE.19 The user takes the receipt. 1.TC Termination condition: 1.TC.1 The system is ready for transactions. UCM is built during the analysis phase of UORE

Regnell’s SUM (Synthetized Usage Model) code fail ready The SUM is constructed during the synthesis phase aborted insert card re-enter code abort code invalid account number code card validation retry validation card invalid card ok code ok too many errors aborted The synthetized usage view for the ‘ATM Customer’ integrates different use case descriptions abort enter code disclaim card code code validation ready aborted code ok enter amount or select balance User action amount amount invalid ... amount validation abort System action amount ok ... take card message ready

Exercise (2) Regnell’s UORE (Usage Oriented Requirements Engineering) Form.Desc.Medium: Graphics(SUM), Text (UCM) Form.Desc.Notation: Semi-formal Form.Present.Anim: False Form.Present.Interac: None Content.Abstraction: Type Content.Context : Syst. Interaction, Syst. Internal Coverage.Func.: S, F, B Coverage.Intent.: Goal Coverage .Non Func.: False Content.Argumentation: False Purpose: Descriptive Life cycle. Duration: Persistent Life cycle.Op.: Capture, Integration

Exercise (3) You have been hired to create the requirements document for a new ATM. Decide whether each item in the following list is a stakeholder, a primary actor, a secondary actor, the SuD, or not an actor at all: The ATM The customer The ATM card The bank The front panel The bank owner The serviceman The printer The bank clerk The main bank computer system The bank robber List the primary actors

Exercise (3) Decide whether each item in the following list is a stakeholder, a primary actor, a secondary actor, the SuD, or not an actor at all: The ATM : the SuD The customer : a primary actor The ATM card : not an actor, a resource The bank : not an actor, The front panel : not an actor ; a component of the SuD The bank owner : a stakeholder (probably!) The serviceman : a primary actor The printer : not an actor; a component of the SuD The bank clerk : a primary actor (who refills the cash?) The main bank computer system : a secondary actor The bank robber : use your imagination!!!!! List the primary actors The customer, the serviceman, the bank clerk

List goals that the various ATM primary actors will have Exercise (4) List goals that the various ATM primary actors will have with respect to the ATM

Exercise (4) Serviceman Put ATM in working order Run ATM self test Bank clerk Restock money Refill supplies Customer Withdraw cash Deposit money Transfer money Check balance

Write the base scenario for the use case Withdraw Money Exercise (5) Write the base scenario for the use case Withdraw Money Using Fast Cash Option

Withdraw Money Using Fast Cash Option Exercise (5) Withdraw Money Using Fast Cash Option The customer runs card through the card reader; the ATM checks the validity of the card and if the card is valid, the ATM sends a prompt for PIN to the customer. The customer enters the PIN. If the PIN is valid, the ATM displays a table of possible amounts. The customer selects a withdrawal amount. If the system authorizes the amount, it delivers the card and the cash.

Exercise (6) 1- Brainstorm about possible conditions for failure in the use case Withdraw Money 2- List failure scenarios and Name them 3- Identify circumstances and outcome for each of them 4- Write the failure scenario comprising three wrong captures of the customer’s PIN

Exercise (6) Possible failure conditions - an expired card - not an ATM card - incorrect PIN - no credit 2- List failure scenarios - Withdraw Money with expired card - Withdraw Money with invalid card - Withdraw Money with incorrect PIN - Withdraw Money with no credit

Exercise (6) 3. Circumstances & outcome - Withdraw Money with expired card circumstances : the customer has an expired card outcome : card - Withdraw Money with incorrect PIN circumstances : the customer has a valid card but not the PIN outcome : “your card has been swallowed : please, contact your bank agency”

Withdraw Money with incorrect PIN Exercise (6) Withdraw Money with incorrect PIN The customer runs card through the card reader; the ATM checks the validity of the card and if the card is valid, the ATM sends a prompt for PIN to the customer. The customer enters the PIN. If the PIN is not valid, the ATM sends again a prompt for PIN to the customer. The customer enters the PIN. If the PIN is not valid, the ATM sends a third time a prompt for PIN to the customer. The customer enters the PIN. If the PIN is not valid, the ATM swallows the card and displays a message “your card has been swallowed, please contact your bank agency”

Exercise (7) 1- Brainstorm about possible variations of the course of actions in the base success scenario of the use case Withdraw Money 2- List variant scenarios and Name them 3- Identify circumstances and outcome for each of them 4- Write the variant scenario comprising two wrong captures of the customer’s PIN

Exercise (7) Possible variations of the normal course of actions - two captures of incorrect PIN - customer asks for a receipt 2- Name variant scenarios - Withdraw Money with a receipt - Withdraw Money with two captures of incorrect PIN 3- Outcome & circumstances Withdraw Money with a receipt circumstances : the customer has a valid card and credit on her account outcome : cash, receipt and card

Withdraw Money with two captures of incorrect PIN Exercise (7) Withdraw Money with two captures of incorrect PIN The customer runs card through the card reader; the ATM checks the validity of the card and if the card is valid, the ATM repeats at maximum twice and till the PIN is valid, a prompt for PIN is sent to the customer. the customer enters the PIN. If the PIN is valid, the ATM displays a table of possible amounts. The customer selects a withdrawal amount. If the system accepts the amount, it delivers the card and the cash.