1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan

2 Outline  The five steps in problem analysis  Business modeling  System engineering issues

3

4 Problem Analysis “ the process of understanding real world problems, user needs and proposing solutions to meet those needs” “ problem is defined as the difference between things perceived and things desired” Not every problem needs a new solution

5 The Five Steps in Problem Analysis 1.Gain agreement on the problem 2.Understand the root causes 3.Identify the stakeholders 4.Define the solution system boundary 5.Identify the constraints imposed on the solution

6 Step 1: Identify Stakeholders “ anyone who can be marginally affected by the implementation of a new system or application”  Who are the users?  Who is the customer?  Who else will be affected?  Who will approve the system?  Who will maintain the system? Who else cares?

Team Work  As a team try to identify stakeholders for our sample project. I will be the client as far as the sample project is concerned, you can question me for 5 minutes and at the end of 10 minutes, type in your answers in a word document and turn it in using Angel (Lessons – Week 01 – Day 02 – Stakeholder Drop Box) 7 05

8 Step 2: Agree on the Problem  Write the problem statement A problem statement is the problem to be solved, written in a standardized format It helps to know the benefits the proposed system will offer from a customers perspective. There may be more than one statement.

9 One Format for Problem Statements  The problem of: A description of the problem solved by the system  Affects: The people affected by this new system  And results in: The impact of the problem on stake-holders  Solution Benefits: Indicate the solution and list a few benefits

Elevator Statement  According to Wikipedia In business jargon an elevator statement (or elevator pitch) is a short concise and compelling statement about a business or a business situation that can be delivered in the time it takes for an imaginary elevator ride. 10

Team Work  Download the template from Angel. (Lesson – Week 2 – Day 2). Once you are done drafting the problem statement and the elevator statement, turn it back in using Angel (Lesson – Week 01 – Day 02 – Problem Statement Drop Box). You have 10 minutes. 11

12 Step 3: Find Root Causes  How do you find problems and their causes? Don’t Assume “ ask and ask again ”

Fishbone or Ishikawa (Kaoru Ishikawa) diagrams Problem in head of fish Draw major bones for different aspects or viewpoints Draw causes as smaller bones (recursively) 13

14 An Example Fishbone Diagram Lousy Meals Same old every day Lousy cooks Too far from suppliers Lousy kitchen Poor education Poor attitude Have to get up early Underpaid

Tool for Drawing Fish Bone Diagrams  15

16 Step 4: Define Boundaries “define the boundary between the solution and the real world”  Draw a picture: Solution system is a black box in the middle of the picture Users of the software are shown Systems that interact with the solution are also shown Users and interacting systems are collectively known as “Actors”

17 Here Are Some Actors Source: Rose-Hulman Drama Club website

Actors Can Also Be Something Rather Than Someone

19 Some Questions to ask  Who will supply, use or remove information from the system?  Who will operate the system?  Who will perform system maintenance?  Where will the system be used?  Where does the system get its information?  What other external systems will interact with this system?

20 Step 5: Identify Constraints “ A restriction on the degree of freedom we have in providing a solution” Frequently-Used Constraint Classifications Economics Politics Technology Existing Systems Environment Schedule and Resources

21 Two Domain-Specific Problem Analysis Techniques  Business Modeling Information Systems/IT domain  Systems Engineering Embedded systems domain