Академический Документы
Профессиональный Документы
Культура Документы
<Project Name>
Vision (Small Project)
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 in Microsoft Word (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.]
<Project Name> Version: <1.0>
Vision (Small Project) Date: <dd/mmm/yy>
<document identifier>
Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>
Table of Contents
1. Introduction 4
1.1 References 4
2. Positioning 4
2.1 Problem Statement 4
2.2 Product Position Statement 4
4. Product Overview 6
4.1 Product Perspective 6
4.2 Assumptions and Dependencies 6
5. Product Features 6
[Name [Briefly describe [List the user’s key responsibilities [If the user is not directly
the user what they represent with regard to the system being represented, identify which
type.] with respect to the developed; for example: stakeholder is responsible for
system.] representing the user’s
captures details
interest.]
produces reports
coordinates work
and so on]
fundamental basis for product definition, scope management, and project management. Each feature will be
expanded in greater detail in the use-case model.
Throughout this section, each feature will 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.
The following guidelines apply:
• Avoid design. Keep feature descriptions at a general level. Focus on capabilities needed and why (not how)
they should be implemented.
• If you are using the Rational RequisitePro toolkit, all need to be selected as requirements of type for easy
reference and tracking.]
[Define the priority of the different system features. Include, if useful, attributes such as stability, benefit, effort, and
risk.]
6. Other Product Requirements
[At a high level, list applicable standards, hardware, or platform requirements; performance requirements; and
environmental requirements.
Define the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics that are
not captured in the Feature Set.
Note any design constraints, external constraints, or other dependencies.
Define any specific documentation requirements, including user manuals, online help, installation, labeling, and
packaging requirements.
Define the priority of these other product requirements. Include, if useful, attributes such as stability, benefit, effort,
and risk.]