1 / 13

Analyzing the Problem

Waniwatining Astuti, M.T.I. Analyzing the Problem. The five steps in Problem Analysis Business Modeling System engineering of software – intensive systems Development teams tend to forge ahead, proiding solutions based on an inadequate understanding of the problem to be solved.

season
Télécharger la présentation

Analyzing the Problem

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Waniwatining Astuti, M.T.I Analyzing the Problem

  2. The five steps in Problem Analysis • Business Modeling • System engineering of software – intensive systems Development teams tend to forge ahead, proiding solutions based on an inadequate understanding of the problem to be solved.

  3. A. The five steps in problem analysis Key points : • Problem analysis is the process of understanding real – world problems and user’s needs and proposing solution to meet those needs. • The goal of problem analysis is to gain a better understanding of the problem being solved, before development begins • To identify the root cause, or the problem behind the problem, ask the people directly involved. • Identifying the actors on the system is a key step in problem analysis.

  4. The specific steps that must be taken in order to achieve the goal are listed below • Gain agreement on the problem definition. • Understand the root causes – the problem behind the problem. • Identify the stakeholders and the users. • Define the solution sysem boundary. • Identify the constraints to be imposed on the solution.

  5. Step 1. Gain agreement on the problem definition • The problem statement Example : problem statement format

  6. Step 2. Understand the root causes – the problem behind the problem. • Quality data demonstrates that many root causes are simply not worth fixing • Fishbone diagram • Pareto chart

  7. Problem to solve & technique applied Problem to solve technique applied Lack of profitability total quality management Cost of nonconformance fishbone diagram Too much scrap pareto chart Inaccurate sales order new software solution

  8. Step 3. Identify the stakeholders and the users The following questions can be helpfull in this process • 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 produce? • Who will evaluate and approve the system when it is delivered and deployed? • Are they 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?

  9. Understanding the needs of the users and other stakeholders is a key factor in developing an effective solution.

  10. Step 4. Define the solution sysem boundary. • We defide the world into two interesting classes of things : • Our system • things that interact with our system Input system output

  11. How do we find these actors? Here are some helpful questions to ask • 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 over external system will interact with the system?

  12. Step 5.Identifying the actors on the system is a key step in problem analysis • Potential sources of system constraints • Economics • Politics • Technology • Systems • Environment • Schedule and resources

More Related