1. Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem

2. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 2 Objectives: Analyze the Problem  Describe the steps in problem analysis  Explain how to gain agreement on the problem  Identify the stakeholders  Find actors and define system boundaries  Formulate a problem statement  Identify constraints on the project  Establish common vocabulary  Draft a Requirements Management Plan outline

3. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 3 Where Are We in the Requirements Discipline?

4. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 4 Analyze the Problem: Activities and Artifacts

5. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 5 Why Is Analyzing the Problem Important?  To avoid the “Yes...but...”  To avoid extra work  To understand requirements What is the problem really?

6. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 6 Gause & Weinberg, 1989 Definition of a Problem “A problem can be defined as the difference between {Problem} things as perceived things as desired” and

7. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 7 What Is Problem Analysis?  Gain agreement on the problem definition  Identify stakeholders  Find actors and system boundaries  Identify constraints on the system  Capture a common vocabulary  Develop Requirements Management Plan

8. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 8 Gain Agreement  What is the problem?  Understand customer’s perspective  Write it down  Gain agreement on it  What is the problem, really?  Search for root causes  Address the root cause

9. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 9 What Is the Problem Being Solved? Fishbone Diagram: One method for Root-Cause Analysis in Solving the Problem List contributing causes to the identified problem. Keep asking “Why?” (expand each rib). How much does each contribute? What the customer believes to be the problem Customers dissatisfied with our service Banking at night Want something fast Privacy when banking Banking in airports More banking locations Queues are too long

10. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 10 Focus on the Largest Contributors Rank in order and use the 80-20 Rule to focus on the top contributing causes to address the greatest portion of the problem. 0 5 10 15 20 25 30 35 40 45 50 Contributing Causes Banking at Night More banking locations Banking at airport Tellers too costly Privacy while banking Other Reasons Pareto Diagram % Contribution

11. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 11 Identify the Stakeholders  A stakeholder is anyone who is materially affected by the outcome of the system. Who are some of the stakeholders for your projects?

12. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 12 Define the System Boundaries Maintenance Communications Reports New System Other Systems Users Legacy System

13. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 13 Actors Help Define System Boundaries PC System boundary? Server PC Is the client software part of the system or is the client an actor? Server End User PC

14. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 14 Identify Constraints Economic Technical Environmental System Political Feasibility

15. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 15 Capture a Common Vocabulary  Define terms used in the project  Help prevent misunderstandings Glossary Capture common vocabulary Start as soon as possible Continue throughout the project RUCS2: Glossary TP1: Glossary Template

16. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 16 Formulating the Problem Statement The problem of(describe the problem) affects(the stakeholders affected by the problem) The impact of which is (what is the impact of the problem) A successful solution would (list some key benefits of a successful solution)

17. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 17 Case Study: RU e-st RM Plan Supplement. Spec Vision Use-Case Model RM Plan UC Report Requirements Database (RequisitePro) Glossary RUCS2: Glossary

18. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 18 Exercise 4.1: Analyze the Problem  Identify root causes  Identify stakeholders  Find actors and system boundaries  Identify constraints on the project  Formulate a problem statement

19. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 19 Develop Requirements Management Plan  Up-front planning helps  What is in a Requirements Management Plan?  Types of requirements to collect  Types of attributes to collect  Types of requirements to trace  Types of documents to produce  Management guidelines TP2: RM Plan Template

20. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 20 RU e-st Requirements Management Structure

21. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 21 RU e-st Requirements Management Plan Stakeholder Requests Features Supplementary Specifications Actors Use Cases Traceability Criteria RUCS10: RM Plan Test

22. Requirements Management with Use Cases Copyright © 1998-2001 Rational Software, all rights reserved 22 Review: Analyze the Problem 1.What are the steps in problem analysis? 2.How do you gain agreement on the problem? 3.Who are the stakeholders in your project? 4.What determines the boundaries of a system? 5.How can actors be used to help determine the boundaries of a system? 6.What should be included in a problem statement? 7.Why is it important to establish a glossary? 8.What is in a Requirements Management Plan?