<System>

Vision Document
Prepared by <Company>

Prepared for <Client>

Version <1.0>
Date <yyyy-mmm-dd>

[Note: Text (such as that you are reading) enclosed in square brackets and displayed in pink italics
(style=TemplateText) is included to provide guidance to the author and should be deleted before
publishing the document. A paragraph entered following this style will set to the standard document
paragraph style.]
[This document uses automatic fields that are displayed on a gray background. These should be changed
to appropriate values for the project. This can be done through the Insert>Fields>Other (Cntl-F2)
dialog. The following are the automatic fields used in this document and the tab in that dialog which can
be used to change the value:]
Field Name Field Description
Client The name of the company for which the system is being built.
Company The name of the software development company.
DocVersion The version number of this document.
DocDate The date that this version of the document was finished.
System The name of the software system.

Revision History
Date Version Author Description
<yyyy- <x.x> <name> <details>
mmm-dd>

Document Review
Date Version Reviewer Name Contact Info.
<yyyy- <x.x> <name> <email address or phone number>
mmm-dd>

Document Approval
Date Version Approver Name Contact Info.
<yyyy- <x.x> <name> <email address or phone number>
mmm-dd>
<System> Version: <1.0>
Vision Document Date: <yyyy-mmm-dd>

Table of Contents
1.Introduction..................................................................................................................................................................4
1.1Purpose.......................................................................................................................................................................4
1.2Scope..........................................................................................................................................................................4

2.Business Opportunity...................................................................................................................................................4
2.1Background................................................................................................................................................................4
2.2Positioning.................................................................................................................................................................4
2.3System Context..........................................................................................................................................................4
2.4Primary Stakeholders.................................................................................................................................................5
2.5Impact of Missed Opportunity...................................................................................................................................5

3.Proposed Solution........................................................................................................................................................5
3.1Primary Features........................................................................................................................................................5
3.1.1Essential Features...................................................................................................................................................6
3.1.2High-Value Features...............................................................................................................................................6
3.1.3Follow-on Features.................................................................................................................................................6
3.2Priority Systemic Qualities........................................................................................................................................6
3.2.1Performance, Throughput, and Scalability............................................................................................................6
3.2.2Reliability and Availability.....................................................................................................................................6
3.2.3Security...................................................................................................................................................................6
3.2.4Manageability.........................................................................................................................................................6
3.2.5Serviceability..........................................................................................................................................................6
3.2.6Usability..................................................................................................................................................................6
3.2.7Accessibility............................................................................................................................................................6
3.2.8Maintainability.......................................................................................................................................................6
3.2.9Flexibility and Extensibility...................................................................................................................................6
3.2.10Reusability............................................................................................................................................................6

4.Constraints...................................................................................................................................................................6
4.1Development Process and Team Constraints............................................................................................................6
4.2Environmental and Technology Constraints.............................................................................................................6
4.3Delivery and Deployment Constraints......................................................................................................................6

Confidential <Client>, 2009 Page 3 of 6

1.Introduction
1.1Purpose
This document defines the project scope for the <System>. It establishes the business need for <System>,
and outlines its high level requirements as needed to satisfy the specified business need. This document is
not an exhaustive requirements description, but will instead provide overall direction for a separate more
detailed set of system requirements. This documents primary purpose is to establish priority among the
most important issues, considerations, features, and overall goals.

1.2Scope
[Briefly describe the target system in terms of how it supports major business processes. This can
explicitly or implicitly summarize one or several key usage scenarios such as This system enables online
ordering of office supplies for businesses, This system provides service technicians with diagnostic
support, This Internet point-of-sale system includes client terminal software as well as key server
functions such as payment authorization and receipt number generation, etc. Note that a longer list of
features and qualities will be provided in later sections, so the coverage here should be more high level
and less exhaustive, probably not referencing more than 5 such usage scenarios. Include other high-level
scooping information where it applies.]
[Also, bound the scope of this document by referencing other documents, if any, where appropriate. This
might include any form of report, study, memo, documentation related to existing systems, etc.]

2.Business Opportunity
2.1Background
[Describe the primary factors that motivate incurring the expense of building this system. This is
expressed as a business problem(s) resulting in an expense, dissatisfaction, inefficiency, loss-of-market,
redefinition-of-market, etc. to one or more principle stakeholders. Briefly provide background description
of the relevant business process in order to be understandable by a wide variety of readers. Describe how
the business problem is solved now. Set the stage in this opening section somewhere along the continuum
between carefree opportunity and desperate need. Conclude by enumerating the top three features of the
system, or what will most attract its primary stakeholders.]

2.2Positioning
[Distinguish internal vs. external product development. Distinguish a new system versus an enhancement.
Distinguish a self-contained system vs. a shared infrastructure system. Describe the relationships between
the proposed system and any sibling, compatible, competitive, or replaced systems. Outline cost and
marketing strategy where applicable.]

2.3Impact of Missed Opportunity

[Discuss the business impact if the proposed system does not meet its goals. For example, revenue might
be lost, market opportunity and/or position might be lost, internal costs might be incurred, internal
resources might have to be redirected in an undesirable way, user dissatisfaction may mount, reputations
may be tarnished, the businesss viability might even be called into question. Working through these
undesirable outcomes will help to clarify the overall business context in a specific and quantifiable way,
and can help when a decision must be made as to continuing the project.]
[Quantifying revenue, expense, or other items is preferable to broad statements. These may be high-level
estimates. They should also be related to a timeframe, and several cost/time statements can be made
about the same goal. An example might read as follows: This internet retail solution represents an
opportunity for $65M in new revenue if in operation within 6 months, but only $15M if within 10 months
due to the missed opportunity to establish our position as a market and technology leader. Various
 deployment options might also be considered (e.g. worth $15M if deployed in full, less than half that
with the XXX functionality delivered within YYY months)]

3.Proposed Solution
3.1Primary Features
[Define and categorize the primary features. Attempt to avoid placing everything in Essential Features
only.]
In this section, we classify the primary features for <System> across three categories. Essential features
cannot be done without. High-value features can be done without, although it may be very undesirable to
do so. Follow-on Features are those for which it is not clear they should be included in the first release. In
all cases, the lists are not exhaustive but are the most important from a business perspective.

3.1.1Essential Features

3.1.2High-Value Features

3.1.3Follow-on Features

3.2Priority Systemic Qualities

[Address the three or four systemic qualities that are essential to the systems success. A complete and
exhaustive list will be provided in the detailed requirements; here we focus on establishing priority.
Therefore, this need not be an exhaustive discussion but instead focus on the summary issues with the
most business impact. Reorder this list to reflect priority and delete items that are not of primary concern.
In the discussion for each section, distinguish current vs. future release issues where applicable.]
In this section, we identify the primary service-level requirements for <System>. This list is not
exhaustive but is intended to capture the most important requirements from a business perspective.

3.2.1Performance, Throughput, and Scalability

3.2.2Reliability and Availability

3.2.3Security

3.2.4Manageability

3.2.5Serviceability

3.2.6Usability

3.2.7Accessibility

3.2.8Maintainability

3.2.9Flexibility and Extensibility

3.2.10Reusability

4.Risks
[Describe any prominent risks relative to technology issues, staffing concerns, political problems, and so
on. Mitigation strategies can be provided or put off until the SRS document is written.]
5.Constraints
5.1Development Process and Team Constraints
[Describe any prominent constraints relative to the manner in which a project may be formed, staffed, or
operated to build the proposed system.]

5.2Environmental and Technology Constraints

[Describe any prominent constraints on the system implementation. This may include constraints on the
selection, use, or coordination with teams responsible for the required development, test, integration, and
production environments. This may also include pre-defined technology or tool choices (e.g. because of
licensing or cost), etc.]

5.3Delivery and Deployment Constraints

[Describe any remaining prominent constraints that the product must meet to provide a complete
solution. This anticipates system transition.]