Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.

Slides:



Advertisements
Similar presentations
THE BUSINESS PLAN The Business Plan Chp. 5 ITB.
Advertisements

Chapter 5 – Enterprise Analysis
Title Slide – Technology or Company Name
Information Technologies Page 1 Information Technologies Page 1 Information Technologies Page 1 Information Technologies Page 1Information Technologies.
Prompts Consider the following questions as you build this slide:
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
Chapter 3 Project Initiation
Conducting a Feasibility Study and Crafting a Business Plan
Chapter 2.
Preparing Your Business Plan
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 6 Initiating and Planning Systems Development Projects 6.1.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Modern Systems Analysis and Design Third Edition
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Submission Writing Fundamentals – Part Webinar Series Leonie Bryen.
Essentials of Management Chapter 4
Concept Analysis Document Executive Summary Template, (To view template instructions – Save this template to project files, reopen and then select View,
Slide 2-1.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
Nature and Scope of Marketing Research
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
RUP Requirements RUP Artifacts and Deliverables
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
1 BTS330 Vision & Scope. 2 IT Projects What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5.
A Typical Business Plan
Chapter 1 marketing dynamics.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Business Analysis and Essential Competencies
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Feasibility Study.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
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.
© 2011 Underwriters Laboratories Inc. All rights reserved. This document may not be reproduced or distributed without authorization. ASSET Safety Management.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Copyright  2007 McGraw-Hill Pty Ltd PPTs t/a Marketing Research 2e by Hair, Lukas, Bush and Ortinau Slides prepared by Judy Rex 1-1 Chapter One Overview.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
BUSINESS PLANNING AHMED JAMAL IDDRISU MDPI ACCRA TEL:
Center for cei Entrepreneurship & Innovation Technology Venture Sequence 9/6/05.
Welcome to Session 3 – Project Management Process Overview
Miguel Garzón, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher with material from: Wiegers: Software Requirements, Chapter 5 Leffingwell.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Requirement engineering Good Practices for Requirements Engineering
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 16/25/2015 V2.
Simple rules to follow when creating the business plan.
Define Research Problem. 2 Management objectives: –To solve current problem facing company –To improve efficiency –To plan for future Current problems.
Knowledge Translation Conference KT Solutions for Overcoming Barriers to Research Use Hosted by SEDL’s Center on Knowledge Translation for Disability and.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Team Skill 3: Defining the System The Vision Document (16) 1.
Outlines Overview Defining the Vision Through Business Requirements
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Requirements Inception
The Vision Document Group members: Zainab BSEF07M025 Noreen BSEF08M021
Modern Systems Analysis and Design Third Edition
Chapter 6 Initiating and Planning Systems Development Projects
PRODUCT NAME Team Leader: Faculty/ Research Alliance: Address:
Identify the Risk of Not Doing BA
Chapter 4 Systems Planning and Selection
Requirements Inception
Software Engineering Lecture #5.
Lecture 6 Initiating and Planning Systems Development Projects
Modern Systems Analysis and Design Third Edition
Requirements Inception
Chapter 6 Initiating and Planning Systems Development Projects
Presentation transcript:

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

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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,

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.

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.

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.

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].

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.

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.

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.

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.