1. 1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem

2. 2 Objectives  Define “problem analysis” and its goal.  Describe activities for problem analysis.  Identify the stakeholders.  Gain agreement on the problem.  Find actors and define system boundaries.  Start development of the project Vision.  Define a problem statement.  Identify constraints on the project.  Establish common vocabulary.

3. 3 Where Are We in the Requirements Discipline?

4. 4 Analyze the Problem: Activities and Artifacts

5. 5 Problem Analysis  Is the process of understanding real-world problems, how they relate to stakeholder needs, and proposing solutions to meet those needs.  What is the goal of problem analysis?  Gain a better understanding before development begins.  Identify root causes.  Help find the right solution. Avoid the “Yes, but…”  Minimize extra work. What is the real problem?

6. 6 Gause & Weinberg, 1989 Definition of a Problem A problem can be defined as the difference between things as perceived and things as desired. (Problem) perceived desired

7. 7 Problem Analysis Steps  Identify stakeholders.  Understand the root causes.  Gain agreement on the problem definition.  Identify constraints on the system or project.  Identify and validate the solution against the root causes.  Define the solution system boundary.

8. 8 Elicit Requirements Expand stakeholder list for solution. Problem Analysis Roadmap Choose the best solution(s) to meet the goals. Best solution identified Problem validated/adjusted Business problem definedActual problem identified and defined Identify stakeholders for problem. Root cause analysis. Reassess that the solution idea is the best solution. Understand the problem in the context of the business goals. Business Problem Solution idea or Opportunity

9. 9 Stakeholders: Definitions  Stakeholder  An individual who is materially affected by the outcome of the system or the project(s) producing the system.  Stakeholder Representative  A stakeholder representative represents one or more stakeholders. They are directly involved in the steering, shaping, and scoping of the project.

10. 10 Identify the Stakeholders  Each group of stakeholders needs a representative.  Not all stakeholder groups need to be consulted.  Some will provide requirements. Customers, users, system administrators  Some may not provide requirements. Shareholders Who are some of the stakeholders for your projects?

11. 11 Describe Stakeholders in the Vision Document StakeholderRegistrar RepresentativeKelly Hansen DescriptionUser TypeThe Registrar is typically a college-educated professional with full computer skills. The Registrar is trained and experienced with the use of the current batch-oriented registration. ResponsibilitiesThe Registrar is responsible for administering course registration for each school term. This includes supervising administrative and data entry personnel. Success CriteriaThe registrar’s primary responsibility will be maintaining student and professor databases, and opening/closing courses to registration. The registrar’s office will also be required to perform …. InvolvementThe registrar’s primary responsibility will be maintaining student and professor databases, and opening/closing courses to registration. The registrar’s office will also be required to perform….. DeliverablesManagement reviewer – especially related to functionality and usability of features required by the Registrar staff. Comments/ Concerns None

12. 12 What Is the Problem Behind the Problem? Fishbone Diagram Techniques List contributing causes to the identified problem. Keep asking “Why?” (expand each rib). The perceived business problem. No Banking at night Too much waiting Want Privacy when banking Customers are dissatisfied with our service. Banking in airports Want more banking locations Queues in the branches are too long

13. 13 Problem Analysis – Validating a Solution List the reasons why the solution is the right solution. Keep asking “Why?” (expand each rib). No Banking at night Too much waiting Customers are dissatisfied with our service We need ATMs. Banking in airports Want more banking locations Queues in the branches are too long The perceived solution to some ill-defined problem.

14. 14 Benefit Effort 20% 80% Focus on Largest Contributors - Pareto’s Law Rank in order. Use the 80-20 Rule to focus on the top contributing causes to address the greatest portion of the problem. 20% of the effort yields 80% of the benefit.

15. 15 Understand the Broader Context of the Problem  A lack of understanding the business and its goals increases risk.  Does the problem have an organization/process component?  Does the team understand the domain in which the problem exists?  Does solving the problem present the opportunity to make process improvements?

16. 16 Business Modeling and Requirements Disciplines The connection between disciplines. Business ModelingRequirements

17. 17 Business Models  Model organization structure and dynamics.  Business processes  Organizational structure  Roles and responsibilities  Visualize the organization and its processes.  Help understand current problems.  Identify potential improvements.  Derive and validate system requirements needed to support the organization.  Products  Deliveries  Events

18. 18 Exercise 4.1: Identify the Problem  Discuss the class project.  Identify and rank root causes.  Fishbone diagram

19. 19 Describe the Problem in the Vision Document User Documentation Specifications Design Specifications Stakeholder Requests Vision Document Supplementary Specification Use-Case Model Problem Definition

20. 20 Vision Document  Communicates information between management, marketing, and the project team.  Provides initial customer feedback.  Fosters general understanding of the product.  Establishes scope and priority of high-level stakeholder requests and features.  A system-level document that describes the “what” and “why” of the product. A document that gets “all parties working from the same book.” Vision

21. 21 Vision Document Outline 1.Introduction 2.Positioning 3.Stakeholder and User Descriptions 4.Product Overview 5.Product Features 6.Constraints 7.Quality Ranges 8.Precedence and Priority 9.Other Product Requirements 10.Documentation Requirements 11.Appendix 1 - Feature Attributes

22. 22 Gain Agreement on the Problem Definition Problem Statement Vision 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 business benefits of a successful solution)

23. 23 Identify Constraints Economic Technical Environmental System Political Feasibility

24. 24 Identify the Best Business Solution  Identify a number of solutions for the main contributing problems.  Technical, non-technical, or both.  Choose the ones that:  Best solve the root causes.  Support the business’ goals.  Gather the requirements to implement the solution.

25. 25 Define the Solution System Boundary Maintenance Communications Reports New System Other Systems Users Legacy System

26. 26 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 User PC

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

28. 28 Visualize the Glossary With a Domain Model Trade Customer Trading Acct. Transaction 1..2 11..** Market transactionTransferLimit Transaction

29. 29 Exercise 4.2: Describe the Problem  Start the Vision document.  Identify project stakeholders.  Find actors and system boundaries.  Identify constraints on the project.  Formulate a problem statement. Vision

30. 30 Review: Analyze the Problem 1.What are the activities in problem analysis? 2.How do you gain agreement on the problem? 3.Who are the stakeholders in your project? 4.How can actors be used to help determine the boundaries of a system? 5.Why is it important to establish a glossary? 6.What should be included in a problem statement?