VISION

Version <current version>

Page 1 of 8
 Vision

Revision History

Date Version Summary of Change Author

<dd/Mmm/ <x.y> <Section> - <Change> <First Name +
yyyy> Last Name>
12 Apr 2014 0.1 Initial version Thuy Tran
15 May 2014 0.2 Update upon review with internal team: Thuy Tran
Section 3 – Updated flow diagram #
Section 4 - Removed flow #
Section 1 – Add new rule XYZ
1 Jun 2014 0.3 Update upon review with customer: Thuy Tran
Section 2 – Change field label from A to B
Section 4 - Update flow # - step #

Distribution for Review/Approval

Name Title & Company Issue Issue Review Approval

Version Date Date Date
<First Name + <Title> - <Company> <x.y> <dd/ <dd/ <dd/
Last Name> Mmm/ Mmm/ Mmm/
yyyy> yyyy> yyyy>

Contents
1 Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 References 4
2 Positioning 4

Page 2 of 8
 Vision

2.1 Business Opportunity 4

2.2 Problem Statement 4
2.3 Product Position Statement 4
3 Stakeholder and User Description 5
3.1 Market Demographics 5
3.2 Stakeholder Summary 5
3.3 User Profiles 6
3.4 User Environment 6
4 Product Overview 6
5 Product Features 6
6 Precedence and Priority 7
7 Assumptions and Dependencies 7
8 Cost and Pricing 7
9 Other Requirements 7
9.1 Documentation Requirements 7
9.2 Licensing Requirements 7
9.3 Constraints 7
10 Appendix 7

Page 3 of 8
 Vision

1 Introduction
1.1 Purpose
<State the purpose of this Vision:
- Collect user needs and why these needs exist
- Describe target user profiles
- Define and high-level features and Non-function requirements of the project>

1.2 Scope
<State the scope of this document>

1.3 References
<Provide a list of all documents referenced somewhere in this document. Each document
should be identified by ID, Name, Published Version (optional), Author and Storage
Location (optional)>

2 Positioning
<This section is normally used for in-house projects.>
2.1 Business Opportunity
<Briefly describe the business opportunity being met by this project>

2.2 Problem Statement

<Provide a summary of the problem being solved by this project>
The following format is recommended:

The problem of <describe the problem)>

affects <the stakeholders affected by the problem>

The impact of which is <the impact of the problem>

A successful solution would <list some key benefits of a successful solution>

>

Page 4 of 8
 Vision

2.3 Product Position Statement

<Provide an overall statement of the unique position of the project which intends to fill in
the marketplace>
Provide an overall statement summarizing at the highest level, the unique position the
project intends to fill in the marketplace.]
The following format is recommended:

For <target customer>

Who <statement of the need or opportunity>
The <project <provide key benefits>
name> that
Unlike <primary competitive alternatives>
Our project <state primary differentiation>

3 Stakeholder and User Description

3.1 Market Demographics
<Summarize the key market demographics that motivate your project decisions. Describe
and position target market segments. Estimate the market’s size and growth by using the
number of potential users, or the amount of money your customers spend trying to meet
needs that your project/enhancement would fulfill. Review major industry trends and
technologies. Answer these strategic questions:

● What is your organization’s reputation in these markets?

● What would you like it to be?

● How does this project or service support your goals? >

3.2 Stakeholder Summary

<Present a summary list of all the identified stakeholders and their responsibilities.
Make clear what role(s) each stakeholder will play:

● Who will provide the requirements?

● Who will make the final decision in case of conflicting requirements from different
stakeholders?
● Who will pay for the system?
Note: one stakeholder might combine several roles.>
Stakeholder Name Represents Responsibilities

Page 5 of 8
 Vision

3.3 User Profiles

<Describe each user type of the system and their profile. Each user profile covers the
following topics:

● Technical background

● Degree of sophistication (e.g. Novice user vs. Guru user)

● Key responsibilities

● Deliverables the user produces, and for whom

● Trends that make the user’s job easier or harder

● How does the target user define success?

● Problems that interfere with success of the user

● How is the user rewarded?

And how do Alternative and Competitive solutions/products support each profile>
User Name Profile

3.4 User Environment

<Detail the working environment of the target user. Here are some suggestions:

● Number of people involved in completing the task? Is this changing?

● How long is a task cycle? Amount of time spent in each activity? Is this
changing?
● Any unique environmental constraints: mobile, outdoors, in-flight, etc.?

● Which systems platforms are in use today? Future platforms?

Page 6 of 8
 Vision

● What other applications are in use? Does your application need to integrate with
them?>

4 Product Overview
<Draw a context diagram of the to-be-developed system with other systems/interfaces,
relationships between main modules within the system.>

5 Product Features
<Provide of list of features to be developed in the project. Each feature is a high-level capability
which must deliver specific benefits to end users.
Please note that Vision document is normally reviewed by a wide variety of involved personnel,
the level of details must be general enough for easy understanding. Details of each feature will
be covered in Use Case document.>
No. Feature End User Benefits

6 Precedence and Priority

<In case any precedence/priority of any feature is important /necessary, it is suggested to use
the table of product features and add the priority of each feature.>

7 Assumptions and Dependencies

<List all factors that affect the features stated in the Vision document. List all assumptions that,
if changed, this Vision document needs to be changed.>

8 Cost and Pricing

<This section is normally used for in-house projects.
List all kinds of costs for the implementation and go-live of the system.>

9 Other Requirements
<This section normally captures Non-function requirements that customer can provide early.
Otherwise, they will be later described in Supplementary Specifications document>

Page 7 of 8
 Vision

9.1 Documentation Requirements

<This section describes the documentations that are necessary for a successful
application deployment such as User Manual, Installation Guides, Configuration, Read Me
File, etc.>

9.2 Licensing Requirements

<List all purchased softwares or 3rd party components.>

9.3 Constraints
<Include all design constraints, domain industry constraints>

10 Appendix
<Include any additional documents that assist to understand the proposed solution better
before having all detailed documentation such as business process workflows, sample
data, etc.>

Page 8 of 8