1. Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering Establishing the Product Vision & Project Scope

2. Instructore: Tasneem Darwish2 Outlines  Overview  Defining the Vision Through Business Requirements  The Context Diagram  Keeping the Scope in Focus

3. Instructore: Tasneem Darwish3 Vision and Scope Document  The figure suggests a template for a vision and scope document.  As with any template, adapt this one to meet the specific needs of your own projects.

4. Instructore: Tasneem Darwish4 Business Requirements  The business requirements describe the primary benefits that the new system will provide to its sponsors, buyers, and users Background  Provide a general description of the history or situation that led to the decision to build this product.

5. Instructore: Tasneem Darwish5 Business Requirements Business Opportunity 1.For a commercial product, describe the market opportunity that exists and the market in which the product will be competing. 2.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.

6. Instructore: Tasneem Darwish6 Business Requirements Business Opportunity 3.Include a comparative evaluation of existing products and potential solutions, indicating why the proposed product is attractive and the advantages it provides. 4.Describe the problems that cannot currently be solved without the product.

7. Instructore: Tasneem Darwish7 Business Requirements Business Opportunity 5.Show how it aligns with  market trend,  technology evolution. 6. Include a brief description of any other technologies, processes, or resources required to provide a complete customer solution

8. Instructore: Tasneem Darwish8 Business Requirements Business Objectives and Success Criteria  Summarize the important business benefits the product will provide in a quantitative and measurable way.

9. Instructore: Tasneem Darwish9 Business Requirements Business Objectives and Success Criteria  Summarize the important business benefits the product will provide in a quantitative and measurable way.

10. Instructore: Tasneem Darwish10 Business Requirements Business Objectives and Success Criteria  If such information appears elsewhere refer to the other document rather than duplicate it here.  Determine how the stakeholders will define and measure success on this project.  State the factors that have the greatest impact on achieving that success, including factors both within and outside the organization's control.  Specify measurable criteria to assess whether the business objectives have been met.

11. Instructore: Tasneem Darwish11 Business Requirements Customer or Market Needs  Describe the needs of typical customers or of the target market segment, including needs that current products or information systems do not meet.  Present the problems that customers currently encounter that the new product will address and provide examples of how customers would use the product.  Define at a high level any known important interface or performance requirements, but do not include design or implementation details.

12. Instructore: Tasneem Darwish12 Business Requirements Business Risks  Summarize the major business risks associated with developing—or not developing—this product.  Risk main categories include: 1.marketplace competition, 2.timing issues, 3.user acceptance, 4.implementation issues,

13. Instructore: Tasneem Darwish13 Business Requirements Business Risks  Estimate: 1.the potential loss from each risk, 2.the likelihood of it occurring, 3.your ability to control it.  Identify any potential improvement actions.  If you already prepared this information for a business case analysis or a similar document, refer to that other source rather than duplicating the information here.

14. Instructore: Tasneem Darwish14 Vision of the Solution  This section of the document establishes a strategic vision for the system that will achieve the business objectives.  This vision provides the context for making decisions throughout the course of the product's life.  It should not include detailed functional requirements or project planning information.

15. Instructore: Tasneem Darwish15 Vision of the Solution Vision Statement  Write a brief vision statement that summarizes the long- term purpose and intent of the new product.  The vision statement should reflect a balanced view that will satisfy the needs of diverse stakeholders.  It can be somewhat idealistic but should be grounded in: 1.the realities of existing or anticipated markets, 2.enterprise architectures, 3.corporate strategic directions, 4.resource limitations.

16. Instructore: Tasneem Darwish16 Vision of the Solution Vision Statement  The following keyword template works well for a product 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].

17. Instructore: Tasneem Darwish17 Vision of the Solution Vision Statement  Here's a sample vision statement for the Chemical Tracking System project at Contoso Pharmaceuticals For scientists who need to request containers of chemicals, the Chemical Tracking System is an information system that will provide a single point of access to the chemical stockroom and to vendors…………….. Unlike the current manual ordering processes, our product will generate all reports required to comply with federal and state government regulations that require the reporting of chemical usage, storage, and disposal.

18. Instructore: Tasneem Darwish18 Vision of the Solution Major Features  Name or number each of the new product's major features or user capabilities in a unique.  emphasize those features that distinguish the new product from previous or competing products.  Giving each feature a unique label permits tracing it to individual user requirements, functional requirements, and other system elements.

19. Instructore: Tasneem Darwish19 Vision of the Solution Assumptions and Dependencies  Record any assumptions that the stakeholders made when conceiving the project and writing this vision and scope document.  Often the assumptions that one party holds are not shared by other parties.  If you write them down and review them, you can agree on the project's basic underlying assumptions.  This avoids possible confusion and aggravation in the future.

20. Instructore: Tasneem Darwish20 Vision of the Solution Assumptions and Dependencies  Also record major dependencies the project has on external factors outside its control.  These could include pending industry standards or government regulations, other projects, third-party suppliers, or development partners.