01 Req480 Vision Exercise

<Company Name>
<Project Name>
Vision
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered following this style will
automatically be set to normal (style=Body Text).]
[To customize automatic fields (which display a gray background when selected), select File>Properties
and replace the Title, Subject and Company fields with the appropriate information for this document.
After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select
All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for
Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See
Word help for more information on working with fields.]
For the Class Project:

• The sections that you will complete are marked with “+ + +”.
• The sections you will not complete are marked with “ - - -”.
Note: Some sections and their details have been removed.

<Project Name> Version: <1.0>
Vision Date: <dd/mmm/yy>
<document identifier>
Vision
1. Introduction
[The introduction of the Vision should provide an overview of the entire document. It should include the
purpose, scope, definitions, acronyms, abbreviations, references and overview of this Vision.]
+ + + Write a one-paragraph summary of the class project here + + +

Optional Exercise 4.2: Base your summary on Analyze the Problem (Module 4).
- - - SKIP acronyms, abbreviations, and references. - - -
2. Positioning
2.1 Business Opportunity
- - - SKIP this section. - - -
2.2 Problem Statement
+ + + [Summarize the problem being solved by this project] + + +

Exercise 4.2: Transpose the problem statement from your student workbook into the problem
statement below.
The problem of
Affects
The impact of which

is
A successful solution
would
Confidential <Company Name>, 2003 Page 2

2.3 Product Position Statement
+++ [What is the unique position the product will fill in the marketplace?]+++
Exercise 6.1: Begin with the Problem Statement (Module 4 and restated above) and add in your
perspective on the solution.
For
Who
The (product name) is a
That
Unlike
Our product
[A product position statement communicates the intent of the application and the importance of the project
to all concerned personnel.]

3. Stakeholder and User Descriptions

[To effectively provide products and services that meet your stakeholders’ and users' real needs, it is
necessary to identify and involve all of the stakeholders as part of the Requirements Modeling process.
You must also identify the users of the system and ensure that the stakeholder community represents them
adequately. This section provides a profile of the stakeholders and users involved in the project and the key
problems that they perceive to be addressed by the proposed solution. It does not describe their specific
requests or requirements. These are captured in a separate stakeholder requests artifact. Instead, it
provides the background and justification for why the requirements are needed.]
3.1 Market Demographics

[Summarize the key market demographics that motivate your product decisions. Describe and position
target market segments.]
- - - SKIP this section, because we did not yet develop the details - - -
3.2 Stakeholder Summary
+ + + [Present a summary list of all the identified stakeholders]+ + +

Exercise 4.2: List the stakeholders for your project. Base the list of the solution type you have
identified for your project.
Name Represents Role

Name the Briefly describe what they represent Briefly describe the role they play in
stakeholder type. with respect to the development. the development, i.e., “Ensure
this…”

3.3 User Summary
+ + + [Present a summary list of all the identified users:] + + +

Exercise 4.2: List the users of your system.
Hint: look at your stakeholders and identify which will be users of the system. Skip the
“Stakeholder” column because we have not developed the details.
Name Description Stakeholder

Name the user type Briefly describe what they represent with List how the user is represented
respect to the system. by stakeholders., i.e.
Represented by Stakeholder1
3.4 User environment

[Detail the working environment of the target user. This is where extracts from the Business Model could
be included to outline the task and workers involved.]
- - - SKIP sections 3.4, 3.5 and 3.6. - - -
3.5 Stakeholder Profiles
3.6 User Profiles

3.7 Key Stakeholder/User Needs

[List the key problems with existing solutions as perceived by the stakeholder. Clarify the following issues
for each problem:
• What are the reasons for this problem?
• How is it solved now?
• What solutions does the stakeholder want?
It is important to understand the relative importance the stakeholder places on solving each problem.
Ranking and cumulative voting techniques indicate problems that must be solved versus issues they would
like addressed.
+ + + [Present a summary list of all the key stakeholder/user needs] + + +
Exercise 5.1: Base your list on the brainstorming you did in Understand Stakeholder Needs. The
priorities come from the Pareto diagram you made in Analyze the Problem (Module 4).
You may want to skip some of the current and proposed solutions because we have not
developed the details.
Need Priority Stakeholder Current Solution Proposed Solutions

Trading from Home or Office High Customer Phone call to a broker Online trading over web
3.8 Alternatives and Competition

4. Product Overview

5. Product Features
[List and briefly describe the product features. Features are the high-level capabilities of the system that
are necessary to deliver benefits to the users. Each feature is an externally desired service that typically
requires a series of inputs to achieve the desired result. For example, a feature of a problem tracking
system might be the ability to provide trending reports. As the use-case model takes shape, update the
description to refer to the use cases.
Because the Vision document is reviewed by a wide variety of involved personnel, the level of detail should
be general enough for everyone to understand. However, enough detail should be available to provide the
team with the information they need to create a use-case model.
To manage application complexity effectively, we recommend that, for any new system or an increment to
an existing system, capabilities are abstracted to a high enough level so that 25 to 99 features result. These
features provide the fundamental basis for product definition, scope management, and project
management. Each feature is expanded in greater detail in the use-case model.
Throughout this section, each feature should be externally perceivable by users, operators or other
external systems. These features should include a description of functionality and any relevant usability
issues that must be addressed.
+ + + [List the top 8 features for the class project.] + + +
Exercise 6.1: Base your list on the stakeholder needs identified in the brainstorming exercise
about needs (Module 5).
5.1 Feature
5.2 Feature
5.3 Feature
5.4 Feature
5.5 Feature
5.6 Feature
5.7 Feature

5.8 Feature
6. Constraints
[Note any design constraints, external constraints, or other dependencies.]
+ + + [List 3 constraints for the class project.] + + +
Exercise 4.2: List any constraints you have identified for your project.
6.1 Constraint
6.2 Constraint
6.3 Constraint
7. Quality Ranges
[Define the quality ranges for performance, robustness, fault tolerance, usability, and similar
characteristics that are not captured in the Feature Set.]
8. Precedence and Priority

[Define the priority of the different system features.]
9. Other Product Requirements

[At a high level, list applicable standards, hardware or platform requirements, performance requirements,
and environmental requirements.]
10. Documentation Requirements

[This section describes the documentation that must be developed to support successful application
deployment.]
- - - SKIP this section. Who would know the documentation requirements? - - -
11. Appendix 1 - Feature Attributes

[Features should be given attributes that can be used to evaluate, track, prioritize, and manage the product
items proposed for implementation. All requirement types and attributes should be outlined in the
Requirements Management Plan; however, you may wish to list and briefly describe the attributes for
features that have been chosen. The following subsections represent a set of suggested feature attributes.]

01 Req480 Vision Exercise

Uploaded by

Copyright:

Available Formats

01 Req480 Vision Exercise

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 Req480 Vision Exercise

Uploaded by

Copyright:

Available Formats

<Company Name>

For the Class Project:

Note: Some sections and their details have been removed.

+ + + Write a one-paragraph summary of the class project here + + +

- - - SKIP acronyms, abbreviations, and references. - - -

2.2 Problem Statement

+ + + [Summarize the problem being solved by this project] + + +

The impact of which

Confidential <Company Name>, 2003 Page 2

2.3 Product Position Statement

The (product name) is a

Confidential <Company Name>, 2003 Page 3

3. Stakeholder and User Descriptions

3.1 Market Demographics

3.2 Stakeholder Summary

+ + + [Present a summary list of all the identified stakeholders]+ + +

Name Represents Role

Confidential <Company Name>, 2003 Page 4

3.3 User Summary

+ + + [Present a summary list of all the identified users:] + + +

Name Description Stakeholder

3.4 User environment

3.5 Stakeholder Profiles

3.6 User Profiles

Confidential <Company Name>, 2003 Page 5

3.7 Key Stakeholder/User Needs

Need Priority Stakeholder Current Solution Proposed Solutions

3.8 Alternatives and Competition

Confidential <Company Name>, 2003 Page 6

Confidential <Company Name>, 2003 Page 7

8. Precedence and Priority

9. Other Product Requirements

10. Documentation Requirements

11. Appendix 1 - Feature Attributes

Confidential <Company Name>, 2003 Page 8

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.