Problem Analysis 1. What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those.

Slides:



Advertisements
Similar presentations
Workbook 1: Crafting Your Value Proposition Workbook Template
Advertisements

Inception: Starting a New Project Needs Features Vision.
Network Design and Implementation
Project Procurement Management
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.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 Team Skill 1 - Analyzing the Problem Sriram Mohan/ Steve Chenoweth 371 Ch 5 in Requirements Text.
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.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
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.
Initiating and Planning Systems Development projects
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
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 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Aims and Objectives.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
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.
Software Requirements Engineering: What, Why, Who, When, and How
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
Lecture: The Importance of Stakeholders.  Objective of the requirements capture and analysis phases is to understand business processes and develop requirements.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 3 Identification and Selection of Development Projects.
1 BTS330 Introduction to Stakeholders & Business Areas.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
INFO 627Lecture #21 Requirements Engineering and Management INFO 627 Analyzing the Problem Glenn Booker.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
1 SYS366 Week 4, Lecture 2 Requirements Part 4: Constraints, The Problem Statement.
Copyright  2005 McGraw-Hill Australia Pty Ltd PPTs t/a Australian Human Resources Management by Jeremy Seward and Tim Dein Slides prepared by Michelle.
Software Requirements and Design Khalid Ishaq
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
1 SYS366 Lecture Requirements Gathering: Stakeholders.
Chapter 31 Your Prescription for Requirements Management.
Systems Development Life Cycle
By Germaine Cheung Hong Kong Computer Institute
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.
Lecture: The Importance of Stakeholders SYS366. Identifying Requirements Objective of the requirements capture and analysis phases is to understand business.
Team Skill 1 Analyzing the Problem
Modern Systems Analysis and Design Third Edition Chapter 11 Selecting the Best Alternative Design Strategy 11.1.
Rational Requirements Management with Use Cases v 5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Chapter 12 The Network Development Life Cycle
IT2005 System Analysis & Design
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Requirement Engineering
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
Chapter 11 Selecting the Best Alternative Design Strategy Modern Systems Analysis and Design Third Edition 11.1.
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.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
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.
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.
Service Management World Class Operations - Impact Workshop.
Team Skill 1 - Analyzing the Problem
Fundamentals of Information Systems, Sixth Edition
Chapter 4 Systems Planning and Selection
Introduction to Projects
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Problem Analysis 1

What is Problem Analysis?  The process of understanding real-world problems and user needs and proposing solutions to meet those needs  A problem can be defined as the difference between things perceived and things desired 2

Steps in Problem Analysis  Gain agreement on the problem definition  Understand the root causes – the problem behind the problem  Identify the stakeholders and users  Define the solution system boundary  Identify the constraints to be imposed on the solution 3

Gain Agreement on the Problem Definition  Team techniques for understanding the problem that a new software system is intended to solve  One approach is to write it down and see if everyone agrees 4

Problem Statement Format ElementDescription The problem of...Describe the problem Affects...Identify stakeholders affected by the problem And results in...Describe the impact of this problem on the stakeholders Benefits of a solution...Indicate the proposed solution and list a few key benefits 5

Understand the Root Causes – The Problem behind the Problem  The process by which the team gains an understanding of the causes of the problem under consideration  Techniques include fishbone diagrams and pareto charts 6

Identify the Stakeholders and Users  A stakeholder is anyone who could be materially affected by the implementation of a new system or application  Identifying them involves interviewing decision makers, potential users, and other interested parties 7

Helpful Questions to Ask in Identifying Stakeholders Who are the users of the system? Who is the customer (economic buyer) for the system? Who else will be affected by the outputs the system produces? Who will evaluate and approve the system when it is delivered and deployed? Are there any other internal or external users of the system whose needs must be addressed? Who will maintain the new system? Is there anyone else who cares? 8

Define the Solution System Boundary  Determine the boundaries of the solution system  Divide the world in two: Our system Things that interact with our system  Someone or something outside the system that interacts with the system is an “actor” 9

Identifying Actors  Who will supply, use, 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 get its information?  What other external systems will interact with the system? 10

Identify the Constraints to be Imposed on the Solution  A constraint is a restriction on the degree of freedom we have in providing a solution  Some constraints become requirements for the system  Others affect resources, implementation plans, and project plans 11

Potential Sources of System Constraints SourceSample Considerations EconomicWhat financial or budgetary constraints apply? Are there costs of goods sold or any product pricing considerations? Are there any licensing issues? PoliticsDo internal or external political issues affect potential solutions? Are there any interdepartmental problems or issues? TechnologyAre we restricted in our choice of technologies? Are we constrained to work within existing platforms or technologies? Are we prohibited from using any new technologies? Are we expected to use any purchased software packages? SystemsIs the solution to be built on our existing systems? Must we maintain compatibility with existing solutions? What operating systems and environments must be supported? EnvironmentAre there environmental or regulatory constraints? Are there legal constraints? What are the security requirements? What other standards might restrict us? Schedule and resourcesIs the schedule defined? Are we restricted to existing resources? Can we use outside labor? Can we expand resources? Temporarily? Permanently? 12