Artifact: Vision










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_kus_YN7DEdmsEI4YDGX2ag", "{F1F206DF-3AA0-4AC0-92EF-8E4A01B6C5B5}", "{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_N13eYAINEdq-_NKqZM1EhA", "_KVkLoN7HEdm8G6yT7-Wdqw", "{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_kus_YN7DEdmsEI4YDGX2ag", "{F1F206DF-3AA0-4AC0-92EF-8E4A01B6C5B5}", "{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_KVkLoN7HEdm8G6yT7-Wdqw", "{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_3aJCcN7REdmjRZts2c4ZjQ", "{417F089F-6636-451A-A8AB-AB4EAC7AC4F1}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Vision















This artifact defines the stakeholders view of the product to be developed, specified in terms of the stakeholders key needs and features. It contains an outline of the envisioned core requirements, so it provides a contractual basis for the more detailed technical requirements.


Domains: Requirements
Work Product Kinds: Specification






Purpose



This artifact provides a high-level, sometimes contractual, basis for the more detailed technical requirements that are visible to the stakeholders. It captures the "essence" of the envisaged solution in the form of high-level requirements and design constraints that give the reader an overview of the system to be developed from a behavioral requirements perspective. It provides input to the project-approval process and is, therefore, closely related to the Artifact: Business Case. It communicates the fundamental "why and what" for the project and is a gauge against which all future decisions should be validated. Another name used for this artifact is the Product Requirement Document. 



Relationships



RolesResponsible:



System Analyst


Modified By:



System Analyst





TasksInput To:



Architectural Analysis


Assess Viability of Architectural Proof-of-Concept


Detail the Software Requirements





Assess Iteration


Capture a Common Vocabulary


Define Project Organization and Staffing


Define Test Approach


Design the User Interface


Detail a Use Case


Develop Business Case


Develop Iteration Plan


Develop Supplementary Specifications


Develop Vision


Elicit Stakeholder Requests


Find Actors and Use Cases


Identify and Assess Risks


Identify Test Ideas


Prioritize Use Cases


Project Approval Review


Project Planning Review


Review Requirements


Output From:



Develop Vision





Process Usage


Analysis & Design
 > 
Define a Candidate Architecture
 > 
Vision


Analysis & Design
 > 
Perform Architectural Synthesis
 > 
Vision


Analysis & Design
 > 
Analyze Behavior
 > 
Vision


Project Management
 > 
Manage Iteration
 > 
Vision


Project Management
 > 
Plan for Next Iteration
 > 
Vision


Project Management
 > 
Conceive New Project
 > 
Vision


Project Management
 > 
Evaluate Project Scope and Risk
 > 
Vision


Project Management
 > 
Plan the Project
 > 
Vision


Project Management
 > 
Plan Remainder of Initial Iteration
 > 
Vision


Project Management
 > 
Refine the Development Plan
 > 
Vision


Project Management
 > 
Reevaluate Project Scope and Risk
 > 
Vision


Requirements
 > 
Analyze the Problem
 > 
Vision


Requirements
 > 
Understand Stakeholder Needs
 > 
Vision


Requirements
 > 
Define the System
 > 
Vision


Requirements
 > 
Manage the Scope of the System
 > 
Vision


Requirements
 > 
Refine the System Definition
 > 
Vision


Requirements
 > 
Manage Changing Requirements
 > 
Vision


Test
 > 
Improve Test Assets
 > 
Vision


Test
 > 
Define Evaluation Mission
 > 
Vision


Test
 > 
Test and Evaluate
 > 
Vision






Description



Main DescriptionThe Vision document provides a complete vision for the software system under development and supports the contract between the funding authority and the development organization.  Every project needs a source for capturing the expectations among stakeholders.


Brief Outline The vision document is written from the customers' perspective, focusing on the essential features of the system and acceptable levels of quality. The Vision should include a description of what features will be included as well as those considered but not included.  It should also specify operational capacities (volumes, response times, accuracies), user profiles (who will be using the system), and inter-operational interfaces with entities outside the system boundary, where applicable.



Illustrations



Templates


Vision Template (Informal)





Examples


CSPS Vision - Inception Phase






Tailoring



Representation Options Tailor this artifact as necessary for your project's needs.  It is generally good practice to keep this artifact brief in order to be able to release it to stakeholders as soon as possible, and to make it easy for stakeholders to review and absorb. This is done by including only the most important stakeholder requests and features, and avoiding detailed requirements. Details may be captured in the other requirements artifacts, or in appendices. It is important to express this artifact in terms of its Use Cases and primary scenarios as these are developed, so that you can see how this artifact is realized by the use cases.



More Information



Checklists


Vision








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();