Scenarios: The missing link or – “ Some Stuff About Use Cases and Testing”

Slides:



Advertisements
Similar presentations
Writing Good Use Cases - Instructor Notes
Advertisements

Use-Cases.
CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
1 Lecture 2: Processes, Requirements, and Use Cases.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Information System Engineering
1 Project Management Office Lunch & Learn Use Case.
Systems Analysis and Design in a Changing World, Fourth Edition
Fall 2009ACS-3913 Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,
WEEK 4 Material Lecture 4a (Wed.). Use Cases/Actors o What is a use case ? l A sequence of actions performed by a system that yields an observable result.
Use Case Analysis Chapter 6.
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
InceptionPhase Mesekach Kaleem Ullah, Melody Parsa, Charmie Dela Cruz, Setareh Vali S C K M MeSeKaCh.
Use Cases.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
Use Case Diagram.
CMPT 275 Software Engineering
Chapter 7: The Object-Oriented Approach to Requirements
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
® 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.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
State of Kansas Travel Authorizations Statewide Management, Accounting and Reporting Tool Entering a Travel Authorization Navigation: Employee Self Service.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant.
Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
1 Use Case Modeling Reference: RUP Doc. Use Case Example 2.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
Functional Requirements – Use Cases (Chapters 14, 21) Sriram Mohan 1.
 Relate Use Cases to  MVC and Application Architecture  CRC  Recap distinctions : Language, Process, Tool  Detail a Use Case  Elements of a Use Case.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 5 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH CHAPTER.
Week IV in SOS  Tuesday Project Time -- 4:15pm-5pm URL for project(s) due to Judy by Friday 5pm  Friday Paper  OOAD Handouts thru last Thursday (see.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Analysis and Design Use cases Finding classes Collaboration and Sequence diagrams Associations between classes.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Jan Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Use Case Analysis Chapter 6.
Chapter 4: Business Process and Functional Modeling, continued
Systems Analysis and Design in a Changing World, 6th Edition
Use Cases Discuss the what and how of use cases: Basics Benefits
Recall The Team Skills Analyzing the Problem (with 5 steps)
Storyboarding and Game Design SBG, MBG620 Full Sail University
Use Case Model.
Use Case Analysis Chapter 5.
Week 10: Object Modeling (1)Use Case Model
Use Case Model Use case description.
Systems Analysis and Design in a Changing World, 6th Edition
Object Oriented Analysis and Design
Use Cases 1.
Project Management Scenario Overview
Use Case Document Example
Requirements Very High level specification of what system should do
CS 420/620 HCI Use Case Modeling Project Preparation
Use Case Modeling Part of the unified modeling language (U M L)
CS 425 Software Engineering
CS 425/625 Software Engineering
Presentation transcript:

Scenarios: The missing link or – “ Some Stuff About Use Cases and Testing”

Page 2 of 12 ©equinox limited 2006 What’s in a Use Case Model? Use Case Diagram Actor Use Case Actor Someone or something outside the system acting in a role that interacts with the system. Could be a human or another system. Use Case Defines a sequence of actions performed by a system that yields an observable result of value to the actor

Page 3 of 12 ©equinox limited 2006 IdentifyOutline Project Inception Phase Elaboration and Construction Iterations (development cycles) A Use Case Model Evolves Fully Detail

Page 4 of 12 ©equinox limited 2006 Project Accounting Consultant System Project Manager Submit Timesheet Complete Timesheets Use Case Model: Identify Use Case Name The name should be: Brief Unique Written as an active verb Meaningful You should be able to tell what the actor wants to achieve in the use case from its name. Each Actor and Use Case needs a brief description. Actor Briefly state its role, goals and responsibilities in relation to the system. Use Case Briefly summarise what takes place in the use case, giving an indication of its scope. Example actor: Name: Consultant Brief Description: The consultant updates their daily timesheet and expense information and gets status reports. Example use case: Name: Submit Timesheet Brief Description: The consultant enters details of the number of hours worked and the activities worked on, then confirms and submits the timesheet.

Page 5 of 12 ©equinox limited 2006 Project Accounting Consultant System Project Manager Submit Timesheet Complete Timesheets Use Case Model: Outline Use Case Outline: Submit Timesheet Brief Description: The consultant enters details of the number of hours worked and the activities worked on, then confirms and submits the timesheet. User Goal: To quickly provide accurate weekly timesheet information from any location, at any time. Basic Flow 1.Log in and select timesheet to update 2.Enter details 3.Confirm 4.Submit Alternate Flows Can’t log in Details invalid…. Scenarios

Page 6 of 12 ©equinox limited 2006 Project Accounting Consultant System Project Manager Submit Timesheet Complete Timesheets Use Case Model: Detail Use Case Report… What Needs to be Tested? Pre and post conditions Special Requirements Business Rules (UI / Data Elements) Basic Flow Alternate Flows

Page 7 of 12 ©equinox limited 2006 Testable Flows Basic FlowAlternate and Exception Flows Use Case No branches No loops No conditions Self Contained Consistent format Alternate Flow 1 Alternate Flow 2 Alternate Flow 3 Alternate Flow 4 Exception Flow 1 Exception Flow 3 Exception Flow 2

Page 8 of 12 ©equinox limited 2006 Use Case Scenarios Scenario 1 = basic flow Scenario 2 = basic flow + Alternate flow 1 + Alternate flow 3 Scenario 3 = basic flow + Alternate flow 3 + Exception flow 3 Scenarios

Page 9 of 12 ©equinox limited 2006 Test Scenarios Scenario 1 = basic flow Scenario 2 = basic flow + Alternate flow 1 + Alternate flow 3 Scenario 3 = basic flow + Alternate flow 3 + Exception flow 3 Action: Verification: User… System… Test Case Template

Page 10 of 12 ©equinox limited 2006 Summary and Scenario Support Test Scenario Requisite Pro CaliberRM

Page 11 of 12 ©equinox limited 2006 In Summary Disciplined documentation of use case flows makes testing easier Use case flows combine as use case scenarios Use Case scenarios become test scenarios Test scenarios + data = test cases

Thank you