Artifact: Vision |
This artifact contains the definition of 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 for the system.
Domain: Requirements Work Product Kinds: Concept
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. It communicates the fundamental "why and what" for the project and is a gauge against which all future decisions should be validated.
Relationships
Roles | Responsible: Analyst | Modified By: Analyst
Tasks | Input To: Find and Outline Requirements Detail Requirements Demonstrate the Architecture Define the Architecture Plan the Project Define Vision Assess Results Plan Iteration | Output From: Define Vision Detail Requirements
Description
Brief Outline | This artifact is written from the customers' perspective, focusing on the essential features of the system and acceptable levels of quality. The artifact 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.
Main Description | This artifact 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.
Illustrations
Templates | Vision
Tailoring
Impact of not having | If this artifact is not used there is a high risk that stakeholders and the development team will have different expectations. This could lead to cancellation of the project.
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 will be captured in the other requirements artifacts.
More Information
Checklists | Vision Qualities of Good Requirements
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright