© 2007 First Data Corporation. All Rights Reserved. RFP 101 – Requirements Management Dave Halbig December 6, 2007.

Slides:



Advertisements
Similar presentations
Use-Cases.
Advertisements

Process Redesign Stages Developing Business Vision Understanding the Existing Business Designing the New Business Installing the New Business.
MAY 11, 2011 WRITING USE CASES IN AN AGILE WORLD KARL O’BRIEN SENIOR SOLUTIONS ENGINEER BLUEPRINT SYSTEMS.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Information System Engineering
SWENET.org1 Applying Use Case Templates Paul Grabow - Baylor University Stephen Frezza – Gannon University.
Conversation Form l One path through a use case that emphasizes interactions between an actor and the system l Can show optional and repeated actions l.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
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,
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Bina Nusantara 7 C H A P T E R MODELING SYSTEM REQUIREMENTS WITH USE CASES.
Copyright ©2004 Cezary Z Janikow 1 Use Cases n Within Requirements discipline/workflow n Verbal descriptions of important functional (behavioral, transactional,
Requirements Analysis 4. 1 Use Case I b504.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Use-Cases.
Modeling System Requirements with Use Cases
Use Cases.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Project Plan Development
The first step in getting what you want is to decide what you want.
CMSC 345 The Requirements Specification. Why do we need requirements Without the correct requirements, you cannot design or build the correct product,
RUP Requirements RUP Artifacts and Deliverables
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Use Cases Descriptions and Use Case Models.
CS499 Use Cases References From Alistair Cockburn Writing Effective Use Cases (Book) - Use Case.
Object-Oriented Analysis - Instructor Notes
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.
Rational Unified Process (Part 1) CS3300 Fall 2015.
1 © 2005 course technology University Of Palestine Chapter 6 Storyboarding the User’s Experience.
Introduction to Sequence Diagrams
Use Cases Ivar Jacobson - guru at Rational Corp., defined UML.
7 MODELING SYSTEM REQUIREMENTS WITH USE CASES C H A P T E R
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.
Use-Cases Elicitation and FAST Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
Software Requirements (Advanced Topics) “Walking on water and developing software from a specification are easy if both are frozen.” --Edward V Berard.
IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Writing Use Cases: Requirements in Context.
Use Cases 7/09. lnot part of the system lrepresents roles a user can play lrepresents a human, a machine or another system lactively exchanges information.
1 CMPT 275 Software Engineering Requirements Gathering Activity Janice Regan,
 Development is organized in a series of short, fixed-length mini-projects called iterations  Iterations are also incremental  Successive enlargement.
Requirements Reference: Chapters 5, 6, & 8. CMSC 345, Fall Objectives To introduce the concepts of user and system requirements To explain functional.
Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore USE CASES BY.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 8 (Chapter 7) MODELING SYSTEM REQUIREMENTS WITH USE.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
Behavior Modeling (based on Alistair Cockburn book) PA116 – L11 (c) Zdenko Staníček, Sept 2010.
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.
Phase 6 Start: Saturday14 April End: Saturday 21 April
CMSC 345 Use Cases. u Describes the system’s behavior under various conditions as the system responds to a request from one of the stakeholders, called.
PRESENTATION ON USE CASE. Use Case Modeling Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is.
IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Writing Use Cases: Requirements in Context.
Data Flow Diagrams. A diagram which shows the movement of data in a system.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
Jan Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Contents What is “RUP?” What are Requirement Types
Storyboarding and Game Design SBG, MBG620 Full Sail University
SafeHome Product.
UML Use Case Diagrams.
Concepts, Specifications, and Diagrams
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Use Cases 1.
Using Use Case Diagrams
Object-Oriented Software Engineering
Use Case Modeling Part of the unified modeling language (U M L)
How to Write Effective Use Cases
Use cases Dr. X.
Presentation transcript:

© 2007 First Data Corporation. All Rights Reserved. RFP 101 – Requirements Management Dave Halbig December 6, 2007

© FDC 2 RFP 101 – Requirements Management - Agenda ► Why Requirements? ► What’s a Use Case? ► Why Use Cases? ► Use Case Terminology ► Use Case Simple Example ► Use Case Extensions ► Use Case Collections/Linkages ► Use Case Do’s and Don’ts ► Use Cases and RFPs ► Resources ► Q&A

© FDC 3 RFP 101 – Requirements Management – Why Requirements? ► Settle disconnects on expected behavior ► AVOID SCOPE CREEP ► Define boundaries ► Allow project managers to do estimation and assess risks ► Allow vendors to do estimation & assess risks ► Permit creation of accurate test cases

© FDC 4 RFP 101 – Requirements Management – What’s a Use Case? ► A structured way of telling a story of behavior. ► They really ARE requirements (behavior). ► They are not ALL the requirements (missing: external interfaces, data formats, complex formulae, business rules, non-functional requirements). ► And they look like this:

© FDC 5 RFP 101 – Requirements Management – Sample Use Case Use Case: 1 – Retrieve Document __________________________ CHARACTERISTIC INFORMATION Goal in Context: Obtain a legal copy of an original document Scope: Organization Level: Primary Task Preconditions: (none) Success End Condition: Customer has legal copy; we have copy fee. Failed End Condition: Customer does not have a legal copy; we do not have the copy fee. Primary Actor: Customer/citizen Trigger: Customer requests a document __________________________ MAIN SUCCESS SCENARIO 1. Customer enters search for document. 2. A list of potential documents is returned 3. Customer selects a document 4. Customer pays a fee for the document 5. Customer receives a legal copy of the document 6. Log information about the transaction __________________________ EXTENSIONS 3a. Requested document not found. 3a1. Revise and re-enter search 3a2. Abandon search 4a. Customer does not have sufficient funds. 4a1. Access denied. Session ended. 4a2. Customer is asked for alternate source of funds (credit card, debit card) 5a. Copy process fails. 5a1. Customer is re-directed to a new session 5a2. Document specialist completes the copy operation elsewhere. (use case 1B) SUB-VARIATIONS (none) __________________________ RELATED INFORMATION Priority: top Performance Target: 3 minutes Frequency: 200/day Superordinate Use Case: Manage Documents (Use Case 0) Subordinate Use Cases: Complete copy operation by human intervention (Use Case 1B) Channel to primary actor: may be phone or interactive Secondary Actors: credit card company, bank (debit card) Channels to Secondary Actors: (none) __________________________ OPEN ISSUES What happens if the original document is not readable or is missing? What happens if credit card is stolen? __________________________ SCHEDULE Due Date: release 1.0

© FDC 6 RFP 101 – Requirements Management – Use Cases and Overall Req’ts Alistair Cockburn, “Writing Effective Use Cases”, p 15

© FDC 7 RFP 101 – Requirements Management – Why Use Cases? ► Enables collaboration ► Allows for change / Iterative development ► Can be done in parallel

© FDC 8 RFP 101 – Requirements Management – Managing Scope TopicInOut Retrieve a documentIn Amend a documentIn Create validated backup of document In Change legislation dealing with documents Out Bill for document retrievalIn Table 1: In-Out List

© FDC 9 RFP 101 – Requirements Management – Another Negotiating Document ActorTask-level GoalPriority/Phase Customer/CitizenRetrieve document1 Document SpecialistAmend document2 Computer OperatorCreate Validated Document Backup 1 Table 2: Actor/Goal List

© FDC 10 RFP 101 – Requirements Management – Manage Your Energy Work in iterations from less precision to more precision 1. Brainstorm / list all the PRIMARY actors 2. Brainstorm / list all the GOALS 3. Work on the Main Success Scenarios 4. Work on the Failure/Extension Conditions 5. Work on the Recovery Steps 6. Brainstorm / list the data fields * 7. Brainstorm / list the data field details and checks * * outside the Use Cases

© FDC 11 RFP 101 – Requirements Management – Use Case Simple Example

© FDC 12 RFP 101 – Requirements Management – Use Case Extensions

© FDC 13 RFP 101 – Requirements Management – Use Case Collections

© FDC 14 RFP 101 – Requirements Management – Use Case Do’s and Don’ts

© FDC 15 RFP 101 – Requirements Management – Use Cases and RFPs

© FDC 16 RFP 101 – Requirements Management – Resources ► Coburn, Alistair, “Writing Effective Use Cases”, Addison-Wesley, 2001 ► _writing_use_cases _writing_use_cases ► Robertson, Suzanne and James, “Mastering the Requirements Process”, Addison-Wesley, 2006 ►

© FDC 17 RFP 101 – Requirements Management – Q&A ?