Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Project Request Form - Software Engineering I | CS 361, Study Guides, Projects, Research of Software Engineering

Oregon State University (OSU)Software Engineering

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

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 08/31/2009

koofers-user-9e1
koofers-user-9e1 🇺🇸

8 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Request Form
I. Administrative
Project/Program Name:
Date Prepared:
Sponsor(s):
Project Team:
Desired Completion Date:
II. Overview
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.]
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.
pf3

Partial preview of the text

Download Project Request Form - Software Engineering I | CS 361 and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Project Request Form

I. Administrative

Project/Program Name: Date Prepared: Sponsor(s): Project Team: Desired Completion Date:

II. Overview

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

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

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.