Enter Project Name, Vision Statement, Enter Customer Name | CS 361, Study Guides, Projects, Research of Software Engineering

Material Type: Project; Class: SOFTWARE ENGINEERING I; Subject: Computer Science; University: Oregon State University; Term: Summer 2009;

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 08/31/2009

koofers-user-mcn-2
koofers-user-mcn-2 🇺🇸

9 documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Enter Project Name
VISION STA TEMEN T
ENTER CUST OMER NAME
[Directions for using template:
Read the guidance, (blue text), to understand the information that should be placed in each
section of this template. Then delete the blue guidance text and replace the placeholder
within the shaded text box with your response.
Some templates have four levels of headings. They are not indented, but can be
differentiated by font type and size:
Heading 1 – Arial Bold 16 font
Heading 2 – Arial Bold Italic 14 font
Heading 3 – Arial Bold 13 font
Heading 3 – Arial Bold Italic 12 font
You may elect to indent sections for readability.]
12/03/2020
pf3
pf4
pf5

Partial preview of the text

Download Enter Project Name, Vision Statement, Enter Customer Name | CS 361 and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Enter Project Name

VISION STATEMENT

ENTER CUSTOMER NAME

[ Directions for using template :

Read the guidance, (blue text), to understand the information that should be placed in each

section of this template. Then delete the blue guidance text and replace the placeholder

within the shaded text box with your response.

Some templates have four levels of headings. They are not indented, but can be

differentiated by font type and size:

 Heading 1 – Arial Bold 16 font

 Heading 2 – Arial Bold Italic 14 font

 Heading 3 – Arial Bold 13 font

 Heading 3 – Arial Bold Italic 12 font

You may elect to indent sections for readability.]

[ How To Use This Template : Use this template to capture output from the write vision statement activity described in the MSF for Agile Software Development process guidance. The template contains instructional text and examples (in shaded background). The output document generated from this template should be regularly reviewed and updated throughout the application life cycle. The goal of the Vision Statement is to achieve team and customer alignment and agreement on the desired solution and overall project direction. Readability and conciseness is a key part of building a good Vision Statement. It is harder to write three paragraphs, each twenty five words or less, than it is to write a ten page Vision Statement. Of course, “twenty-five words or less” is merely a guideline.] Background [ Description : The project’s background is a statement of the customer’s current situation. It is expressed in business language, not technical terms. This section should demonstrate your understanding of the customer’s current environment and its desired future state. This information creates the overall context for the project. Provide a one or two paragraph context to describe the events that determined the need for a new or improved system. In this section, we should find:

 Business History: what is the history that determined the need for this project? This may include

a new opportunity or detail about an enhancement to an existing opportunity.

 Business challenges: what are the challenges that have arisen that relate to this project?

 Dependencies: what are the existing or future projects or system that relate to this one?

Example: AdventureWorks is currently among the top three online retailers of outdoor equipment and sporting goods on the Web and is among the top ten retailers in this category nationwide. We have just signed a contract with Wingtip Toys to:

  1. Provide in-store pickup nationwide for goods ordered from our Web site
  2. Allow real-time query of inventory at local WT stores. Our companies have a long, informal relationship. This contract brings the two companies together in a tighter business relationship. The relationship with Wingtip Toys drives both potential revenue increases and cost decreases.]

Enter the background text here.

Driving Factors [ Description : This section describes the major requirements or timeframe driving the release of the product. It should be clear from this statement whether this project is driven by date (such as a major tradeshow) or functionality (such as the desire to outdo a competitor). One or two paragraphs are recommended. These paragraphs describe the external influences that shape the project timeframe, minimum bar of acceptable functionality, and required quality level. This section should maintain an overview or high-level view of the system. In this section, we should find:

 Business Opportunity: a description of the customer’s situation and needs and our window of

opportunity.

 Scope: What is the boundary of the solution defined though a high-level overview of the business

requirements? What is a release strategy, the criteria by which the solution will be accepted by users and operations, and out of scope,.

 Solution Design Strategies: Are there any constraints on the architectural and technical designs

used to create this solution? Example: The expanded Website has to go live in 30 days. We have a national marketing campaign planned to announce the Wingtip relationship and the new Website planned in 45 days. We expect that this will greatly expand our market and allow us to move our rank into the top five retailers nationally and into the top two on the web. Our goal is to increase our transaction volume from the current 6000 visitors and 500 orders averaged per day, to 20,000 visitors and 2000 orders per day. Our Service Level Agreement with Wingtip guarantees a 3-second response time for 95% of orders placed and an 8-second response time for inventory lookup. ]

Enter the driving factors text here.

Vision Statement [ Description : The Vision Statement section clearly and concisely describes the future desired state of the customer’s environment once the project is complete. This can be a restatement of the opportunity; however, it is written as if the future state has already been achieved. It should describe the users in general terms, the problem that the product is trying to solve, and if needed, how it is differentiated from other solutions. It should be written in the language of the user’s domain. One way to write vision statements is utilize a useful format introduced by Geoffrey Moore. This format promotes thinking about the key values of a product in the form of an “elevator pitch”. For (identified users) Who (narrow the scope of the problem) Our solution is (set framework) That (enumerate requirements) Unlike (competitors/alternatives) (differentiate) A sign of a successful vision statement is that everyone on the project team can recite it from memory and connect their daily work to it. Example : Our customers will be able to order outdoor equipment and sporting goods from our Website and pick them up in our stores as part of the shipping options. The new website will accommodate the new volume with adequate performance, security, and satisfactory user experience, which should cause the doubling of our market share (and stock price).]

Enter the vision statement text here.

Stakeholders [ Description : The Stakeholders section is used to describe the various entities that have a vested interest in the project. This should include at a minimum the user(s), customer(s), and development