Task: Define Vision |
Define the vision for the future system. Describe the problem and features based on stakeholder requests.
Disciplines: Requirements
Purpose
The solution is proposed for a problem that everybody agrees on. Stakeholders express their problems, needs and potential features for the system to be, so the project team can better understand what has to be done.
Relationships
Roles | Primary Performer: Analyst | Additional Performers: Stakeholder
Inputs | Mandatory: None | Optional: Vision
Outputs | Vision Glossary
Steps
Identify stakeholders
Identify the decision-makers, customers, potential users, partners, domain experts, industry analysts and other interested parties (see Role: Stakeholder). Develop profiles of potential (or actual) users of the system, which maps to the roles of human actors of the system being developed. Document the initial information on key users and their environment in the Artifact: Vision.
Gain agreement on the problem being solved
Gain agreement on the definition of the problem by asking the stakeholders what is the problem, without rushing into defining the solution. Then search for root causes, or the “problem behind the problem” (use techniques like like the ones describe in Guideline: Requirements Gathering Techniques). Formulate the problem statement and fill in the corresponding section found on Template: Vision. The purpose of this is to help you distinguish solutions/answers from problems/questions.
Capture a common vocabulary
Every project has its own specialized terminology that must be well understood for effective communication with stakeholders. Start by defining acronyms, abbreviations and relevant business and tecnical terms in a Glossary. The Glossary will be refined throughout requirements activities in the the project lifecycle.
Gather stakeholder requests
Use the most appropriate method to gather information, like the ones describe in Guideline: Requirements Gathering Techniques. Each one is applicable in a particular situation or type of stakeholders. If you can meet stakeholders in person, then an interview may be conducted. If you don't have direct access to stakeholders, or they are a large and spread out number of individuals, then a questionnaire may be helpful. Besides, questionnaires provide statistical data reflecting what stakeholders really need. For more information, see Task: Find and Outline Requirements.
Define the system boundaries
Identify the border between the solution and the real world that surrounds the solution. Identify interfaces, as well as input and output information exchanged with users, machines or systems.
Identify constraints to be imposed on the system
There are various sources of constraints to be considered, which can impact the design or the project itself. They are: Political, Economical (budget, licensing), Environmental (regulatory constraints, legal, standards), Technical (platforms, technology), Feasibility (schedule, resources allocation, outsourcing) and System (solutions compatibility, support to operating systems and environments).
Define features of the system
Make a list of features that stakeholders want in the system, briefly describing them and giving attributes to help define their general state and priority in the project.
Achieve Concurrence
A review of the Vision is conducted with relevant stakeholders to ensure agreement, assess quality, and/or identify changes required. See Guideline: Effective Requirement Reviews for more information.
More Information
Checklists | Vision Qualities of Good Requirements
Concepts | Requirements
Guidelines | Requirements Gathering Techniques Effective Requirement Reviews
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