1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text.

Slides:



Advertisements
Similar presentations
S D S A.
Advertisements

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Hogeschool van Amsterdam Interactieve Media The art of pitching Hoorcollege marketing blok 2 week 6.
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini September 28, 2011 PDCA Training Series 2 PLAN, Part 2.
Workbook 1: Crafting Your Value Proposition Workbook Template
Inception: Starting a New Project Needs Features Vision.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.
BA 301 Week 4. Homework Assignment – Read pages 40 – 56 (Yuthas) List all your activities for the last week and time spent to the closest hour e.g. Study,
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
Functional Requirements – Use Cases Sriram Mohan/Steve Chenoweth (Chapters 14, 21 – Requirements Text) 1.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
7M822 Software Requirements Introduction 7 September 2010.
Waniwatining Astuti, M.T.I
Problem Analysis The goal of problem analysis is to gain a better understanding of the problem being solved before development begins Gain agreement on.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
Organizing Requirements & Managing Scope (Chapters of the requirements text ) Steve Chenoweth & Chandan Rupakheti RHIT Which brings up Question 1,
12/28/08 - L6 ProcessesCopyright Joanne DeGroat, ECE, OSU1 The Request for Information (RFI)
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5.
Team Skill 1 - Analyzing the Problem Steve Chenoweth & Sriram Mohan Pages 43 – 52 in Requirements Text.
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Consulting Guidelines Dr. Robert Lahm (With Thanks to Dr. Louis Buck for his Valuable Contributions)
Class #2-4: Entry, Contracting and Proposal Writing.
Traceability, Change and Quality – Chapters Requirements Text Steve Chenoweth & Chandan Rupakheti RHIT Question 1.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
STAKEHOLDER MEETING Selecting Interventions to Improve Utilization of the IUD City, Country Date Insert MOH logoInsert Project logoInsert USAID logo (Note:
Software Requirements and Design Khalid Ishaq
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
Chapter 31 Your Prescription for Requirements Management.
Team Skill 2 Understanding User and Stakeholder Needs Interviewing (10)
1 Team Skill 1 - Analyzing the Problem Continued and Product Features and Challenges Sriram Mohan.
Requirements Management with Use Cases Module 3: Analyze the Problem Requirements Management with Use Cases Module 3: Analyze the Problem.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
Team Skill 1 Analyzing the Problem
FishboneFishbone Six Sigma Foundations Continuous Improvement Training Six Sigma Foundations Continuous Improvement Training Six Sigma Simplicity.
1 Class #1 Assignments Mark E. Sampson UPDATED 8/02/04 EMIS 8390 Systems Engineering Tool—applying tools to engineering systems.
Problem Analysis 1. What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those.
Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
The Vision Document & Product Management CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 27, 2004 In.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Consulting Guidelines.  This is not your business!  You can only make recommendations based on the consulting agreements objectives  You may recommend.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
SYS366 Problems and Problem Statement. What is a problem? Gause and Weinberg (1989): A problem can be defined as the difference between things as perceived.
Traceability, Change and Quality – Chapters Requirements Text Sriram Mohan/Steve Chenoweth.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
Cause effect identification using Fishbone Diagram Powered by: Jazz PresentationJazz Presentation.
Crafting Your Offer & Market Value Proposition By Ed Downes.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
1 Team Skill 1 Analyzing the Problem … Part 1: 5 steps in Problem Analysis Based on “Software Requirements Management, A use case approach”, by Leffingwell.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Team Skill 1 - Analyzing the Problem
Strategies to Promote Collaboration
INF 342 Enthusiastic Study/snaptutorial.com
© 2013 American College of Cardiology
GHSP Problem Solving Team Champion: Team Members: Team Mentor:
Strategies to Promote Collaboration
Fishbone Diagram/ Cause & Effect Diagram
Interviewing Sriram Mohan.
CAUSE AND EFFECT DIAGRAM
WORKSHOP Establish a Communication and Training Plan
APMP Professional Certification
Presentation transcript:

1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text

2

3 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

4 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

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

Class Project  This project you just work on in class – don’t take it outside the class at all.  “System that integrates micro-blogging services likes twitter to run in-class assessments and gather feedback during class. This could be generalized into a system that integrates with powerpoint and helps gather student feedback in classes. Faculty can conduct quizzes, gather data via polls, conduct plus delta etc.”

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 us for 10 minutes and at the end of 10 minutes, type in your answers in a word document and turn it in using Angel (Lessons -In Class Activity – Week 1– Stakeholder Drop Box) 7 05

8 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

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

10 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. 11

Team Work  Download the template from Angel. (Lesson – Template). Once you are done drafting the problem statement and the elevator statement, turn it back in using Angel (Lesson – In Class Activity- Week 1– Problem Statement Drop Box). You have 10 minutes. 12

13 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

14 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 sources of the problem Expand recursively. 15

16 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  Template on Angel [Lessons – Templates]  Visio has a nice template  Powerpoint  17

Extra Credit  Draw a fish bone diagram for the class sample project and turn it in by class time on Thursday via Angel ( Lessons – Extra Credit – Week 1 - Fish Bone Drop Box) 18