Dibujo

<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 beset 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 pressingF9, 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.]

Revision History
Date | Version | Description | Author |
<dd/mmm/yy> | <x.x> | <details> | <name> |
| | | |
| | | || | | |

Table of Contents
1. Introduction 3
1.1 References 3
2. Positioning 3
2.1 Problem Statement 3
2.2 Product Position Statement 3
3. Stakeholder and User Descriptions 3
3.1 Stakeholder Summary 3
3.2 User Summary 3
3.3 User Environment 3
3.4 Summary of Key Stakeholder or User Needs 3
3.5 Alternatives and Competition 3
4. Product Overview 3
4.1 ProductPerspective 3
4.2 Assumptions and Dependencies 3
5. Product Features 3
6. Other Product Requirements 3

Vision (Small Project)
Introduction
[The purpose of this document is to collect, analyze, and define high-level needs and features of the <<System Name>>. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist. The details of howthe <<System Name>> fulfills these needs are detailed in the use-case and supplementary specifications.]
[The introduction of the Vision document provides an overview of the entire document. It includes the purpose and references of this Vision document.]
References
[This subsection provides a complete list of all documents referenced elsewhere in the Vision document. Identify eachdocument by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
Positioning
Problem Statement
[Provide a statement summarizing the problem being solved by this project. The following format may be used:]
The problem of |[describe the problem] |
affects | [the stakeholders affected by the problem] |
the impact of which is | [what is the impact of the problem?] |
a successful solution would be | [list some key benefits of a successful solution] |
Product Position Statement
[Provide an overall statement summarizing, at the highest level, the unique position the product intends to fill in the marketplace. Thefollowing format may be used:]
For | [target customer] |
Who | [statement of the need or opportunity] |
The (product name) | is a [product category] |
That | [statement of key benefit; that is, the compelling reason to buy] |
Unlike | [primary competitive alternative] |
Our product | [statement of primary differentiation] |
[A product position statement communicates the intent of theapplication and the importance of the project to all concerned personnel.]
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...