Kiến trúc máy tính và hợp ngữ - Chapter 2: Establishing the product vision anh project scope

Problem Analysis Business Requirement Project vision Project scope Goal: gain a better understanding of the problem being solved before development begins Identify root cause Identify stakeholders and their needs (or problems) Identify solution boundary Uses business requirements obtained from stakeholders Results in Product Vision and Project Scope 4 Five steps for problem analysis: Gain agreement on the problem definition Understand the root causes – the problem behind the problem Identify the stakeholders Define the solution system vision and boundary Identify the constraints to be imposed on the solution 5 Document the problem and seek agreement Ask stakeholders to write a problem statement in an agreed format Statement should include What the problem is Who is affected by it? What is the impact? Is there a proposed solution? What are key benefits? 6 There is often a problem behind the problem Root cause analysis consists of finding underlying causes that may not be immediately apparent Example: Our e-commerce site is not profitable Why is it not profitable? Poor site design? Bad pricing? Poor customer management after the sale? Some or all of the above? Root cause analysis can be used to understand root causes Determine what factors contribute to the problem (subproblems) Recursively determine what factors contribute to these problems Decompose until causes are understood (possible solution clear) 8 9 Stakeholders: persons or organizations (ex: customers, sponsors,.. ) who are actively involved in the project or whose interests may be affected by the performance or completion of the project. How to identify Stakeholders? The vision: describes what the product is about and what it eventually could become Project scope: identifies what portion of the ultimate long-term product vision the current project will address. 11 Restrictions on the solution space Put limitations on the ability to deliver a solution as envisioned Usually non-functional requirements that impose major restrictions on the system 12 Sources of constraints include: Economics (e.g., costs, licensing issues) Politics (e.g., internal or external, interdepartmental issues) Technology (e.g., choice of technology/platform) Systems (e.g., existing system, compatibility issues) Environment (e.g., legal/environmental/security/standards) Schedule and resources (e.g., fixed schedule, team) Describe the primary benefits that the new system will provide to its sponsors, buyers, and users. Include: Background Business Opportunity Business Objective Customer Need Business Risk Background: Provide a general description of the history or situation that led to the decision to build this product. Business Opportunity: For a commercial product, describe the market opportunity For a corporate information system, describe the business problem that is being solved or the business process being improved, as well as the environment in which the system will be used Business Objective:the important business benefits the product will provide in a quantitative and measurable way, how success will be measured, factors that have great impact on success... Customer Need: the needs of typical customers or of the target market segment Business Risk: the major business risks associated with developing—or not developing— this product Vision for the system that will achieve the business objectives. Include: Vision statement Major feature Assumption and Dependencies Vision statement For [target customer] Who statement of the need or opportunity] The [product name] Is [a product category] That [key benefit, compelling reason to buy or use] Unlike [primary competitive alternative, current system, or current business process], Our product [statement of primary differentiation and advantages of new product]. Vision statement sample  For employees who wish to order meals from the company cafeteria or from local restaurants on-line, the Cafeteria Ordering System is an Internet-based application that will accept individual or group meal orders, process payments, and trigger delivery of the prepared meals to a designated location on the Process Impact campus. Unlike the current telephone and manual ordering processes, employees who use the Cafeteria Ordering System will not have to go to the cafeteria to get their meals, which will save them time and will increase the food choices available to them. Major feature: the new product's major features or user capabilities in a unique, persistent way, emphasizing those features that distinguish it from previous or competing products. Assumptions and Dependencies: The project scope defines the concept and range of the proposed solution. The limitations itemize certain capabilities that the product will not include. The scope and limitations help to establish realistic stakeholder expectations. Include 3 parts: Scope of Initial Release: Summarize the major features that are planned for inclusion in the initial release of the product Scope of subsequent Release: Limitations and Exclusion Summarize some of the project's business issues, including profiles of major stakeholder categories and management's priorities for the project Include: Stakeholder Profiles Project Priorities Operating Environment 23 Profile should include: Major value or benefit that stakeholder will receive from product (e.g., improved productivity, reduced rework, cost saving, ability to perform new tasks...) Likely attitude toward the product Major features and characteristics of interest Any known constraints that must be accommodated