Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.

Similar presentations


Presentation on theme: "1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004."— Presentation transcript:

1 1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004

2 2 Outline  5 steps in problem analysis  Try some of the steps

3 3 5 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

4 4 Step 1: Agree on the Problem  Write the problem statement

5 5 Cartoon of the Day

6 6 Step 2: Find Root Causes  Fishbone or Ishikawa (Kaoru Ishikawa) diagrams 1. Place problem in head of fish 2. Draw major bones for different aspects or viewpoints 3. Draw causes as smaller bones (recursively)

7 7 Example Fish Lousy Meals Same old every day Lousy cooks Too far from suppliers Lousy kitchen Poor education Poor attitude Have to get up early Underpaid

8 8 Step 3: Identify Stakeholders  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?

9 9 Step 4: Define Boundaries  Draw a picture: Solution system is a black box in the middle of the picture Users are shown Systems that interact with the solution are shown

10 10 Step 5: Identify Constraints  Economics  Politics  Technology  Existing Systems  Environment  Schedule and resources


Download ppt "1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004."

Similar presentations


Ads by Google