Team Skill 1 Analyzing the Problem

Slides:



Advertisements
Similar presentations
Inception: Starting a New Project Needs Features Vision.
Advertisements

Systems Analysis and Design 9th Edition
1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.
Analyzing the Problem : Concepts and Techniques 3.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
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.
7M822 Software Requirements A Use Case Approach 14 September 2010.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
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.
Team Skill 1 Analyzing the Problem Business Modeling (6) 1.
Chapter 2: Analyzing Business Case Phase 1: Systems Planning
Chapter 4 Requirements Engineering
Initiating and Planning Systems Development projects
S/W Project Management
RUP Requirements RUP Artifacts and Deliverables
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5.
Typical Software Documents with an emphasis on writing proposals.
Team Skill 1 - Analyzing the Problem Steve Chenoweth & Sriram Mohan Pages 43 – 52 in Requirements Text.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Name Hometown Program Employer/Student Fun Fact 1.
Software Project Management Lecture # 8. Outline Earned Value Analysis (Chapter 24) Topics from Chapter 25.
1 Phases in Software Development Lecture Software Development Lifecycle Let us review the main steps –Problem Definition –Feasibility Study –Analysis.
From Research Prototype to Production
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Software Requirements Engineering: What, Why, Who, When, and How
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
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.
Lecture-3.
1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.
Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5 Leffingwell.
Software Requirements and Design Khalid Ishaq
1 6 C H A P T E R REQUIREMENTS DISCOVERY. 2 Chapter Six Requirements Discovery Define system requirements and differentiate between functional and nonfunctional.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Team Skill 6: Building the Right System Assessing Requirements Quality (29)
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.
Problem Analysis 1. What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Software Project Management Lecture # 9. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Software Requirements Specification Document (SRS)
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.
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
Team Skill 1 Analyzing the Problem Systems Engineering (7) 1.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
Team Skill 2 Understanding User and Stakeholder Needs The features of a Product or System (9)
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Analyzing the Problem.
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
Systems Analysis & Design 7 th Edition Chapter 2.
A Quick Review of the Components THE DMAIC CYCLE.
 System Requirement Specification and System Planning.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
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.
Service Management World Class Operations - Impact Workshop.
Team Skill 1 - Analyzing the Problem
Principles of Information Systems Eighth Edition
OPS/571 Operations Management
Introduction to Projects
DMAIC Roadmap DMAIC methodology is central to Six Sigma process improvement projects. Each phase provides a problem solving process where-by specific tools.
Accounting Information Systems and Business Processes - Part I
Presentation transcript:

Team Skill 1 Analyzing the Problem The 5 Steps in Problem Analysis (5)

Analyzing the Problem What should be the results of analysis? Understand the users’ needs Understand problems Define the users/actors How will we meet these needs? Develop a clear understanding of critical issues that could be road blocks Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem What are problems in reference to analysis A problem is the difference between what’s perceived and what’s desired Perceptions of how things work and what is possible are not always reality Some customer needs may not be realistic Problem Analysis is doing the following for user needs Eliciting Understanding Documenting Validating Proposing a solution?? Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem 5 steps of problem analysis Gain agreement on problem definition Understand root causes Identify users & stakeholders Define solution system boundary Identify constraints on solution Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Gaining agreement First Second Use company accepted format Denote a targeted release date – priority/Urgency Second Document the problem Seek agreement Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Table 5-1 (Problem Statement Format) Element Description The problem of … Describe the problem Affects … Identify stakeholders affected by the problem And results in … Describe the impact of this problem on stakeholders and business activity Benefits of a solution … Indicate the proposed solution and list a few key benefits. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Table 5-2 (Sales order Problem Statement) Element Description The problem of … Inaccuracies in sales orders. Affects … Sales order personnel, customers, manufacturing, shipping, and customer service. And results in … Increased scrap, excessive handling costs, customer dissatisfaction, and decreased profitability. Benefits of a solution … That creates a new system to address the problem include: Increased accuracy of sales orders at point of entry Improved reporting of sales data to management Ultimately, higher profitability Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Understanding root causes Example Problems often have underlying causes that usually take further analysis to discover Use a Tool to help! Example Our product is not profitable Why Poor marketing? Bad pricing? Poor customer retention? Combination? Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem In Total Quality Management (TQM), One way is “root cause” is determined is … Fishbone diagram Start with the problem, on a horizontal line Look for causes of the problem Then look for causes of the causes; repeat Could do this is other formats like distinction analysis, deviation analysis, … Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Figure 5-1 (Fishbone Diagram) Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Root causes’ impacts can vary Determine which ones to fix Pareto (bar) chart -depict relative impact Can also use other formats Rank Risk & Priority Impact & Effort Failure Mode Effect Analysis (FMEA) Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Figure 5-2 (Pareto Chart of Root Causes) Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Figure 5-3 Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Did you get a distinctive answer? You can do another analysis to determine what is causing the issues you have identified Repeat the fishbone process Gives you a better identification of what exactly is causing the problem If you don’t get to the root cause you won’t solve the real problem. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Identifying stakeholders & users Stakeholder Who, if anyone is affected by a system? Users are a subset of stakeholders These are not always obvious Can be internal managers Can be external customers, regulatory agencies, etc. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem How to identify stakeholders 1. Who are the users of the system? 2. Who is the customer? 3. Who else will be affected by outputs? 4. Who will evaluate & approve the system? 5. Are there other external or internal users? 6. Who will maintain the system? 7. Is there anyone who cares? legal/regulatory, etc. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Table 5-3 (Users and Stakeholders) Users Other Stakeholders Sales order entry clerks MIS Director Sales order supervisor Chief Financial Officer Production control Production Manager Billing clerk Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Figure 5-5 (System Boundary) Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Determining the system boundaries can be difficult What pieces are included within our system Interfaces with external systems Can be very difficult to design but can be worth it Interfaces are needed E.g. – credit card processing, shipping manifesting Why are interfaces so important? Allows you to include functionality in your system that might be to difficult, time consuming, lack of expertise to do it yourself. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Some questions to help discover actors Who will supply, or remove information from the system? Who will operate the system? Who will perform any system maintenance? Where will the system be used? Where does the system gets its information? What other external systems will interact with the system? Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Figure 5-6 (System Perspective) Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Identify constraints on system Are a restriction on the degree of freedom we have in providing a solution Non-functional requirements usually impose major restrictions on the system Which can be Human resources Technological Policy/legal/regulatory Performance etc. Copyright Leffingwell, Widrig, & SIS Faculty

Analyzing the Problem Constraints Example (More on page 38) Economics What financial or budgetary constraints apply? Are there costs of goods sold or any product pricing considerations? Technology Are we restricted in our choice of technologies? Are we prohibited from using any new technologies? Are we expected to use any purchased software packages? Systems Is the solution to be built on our existing systems? Must we maintain compatibility with existing solutions? Copyright Leffingwell, Widrig, & SIS Faculty