Artifact: Business Vision
|
The Business Vision defines the set of goals and objectives at which the business modeling effort is aimed. |
|---|---|
| Role: | Business-Process Analyst |
| Optionality/Occurrence: | Can be excluded. |
| Templates and Reports: | |
| Examples: | |
| UML Representation: | Not applicable. |
| More Information: |
| Input to Activities: | Output from Activities: |
Purpose
The Business Vision document captures very high-level objectives of a business modeling effort. It provides input to the project-approval process and is, therefore, intimately related from a software engineering effort to the Business Case as well as the Vision document. It communicates the fundamental "whys and whats" related to the project and is a gauge against which all future decisions should be validated.
The Business Vision document will be read by managers, funding authorities, business workers in business modeling, and developers in general.
Timing
The Business Vision document is created early in the Inception phase, and is used as a basis for the Business Case (see Artifact: Business Case) and as the first draft of the (project) Vision document (see Artifact: Vision).
Responsibility
A Business-Process Analyst is responsible for the integrity of the Business Vision document, ensuring that:
- the Business Vision document is updated and distributed
- input from all concerned stakeholders is addressed
Tailoring
The full version of this document is only applicable if you are doing business creation or business reengineering. If the purpose of your effort is business improvement, you may still produce a Business Vision, but only focus on the sections titled Introduction, Positioning, and Business Modeling Objectives.
Various documents may already exist in your organization that cover some of the topics found in the Business Vision. In such cases, there is no need to do the work again and you could let the Business Vision document refer to existing documents.
