Artifacts >
Business Modeling Artifact Set >
Business Vision
Artifact:
|
|
The Business Vision defines the set of goals and objectives the business modeling effort is aiming at. |
Role: | Business-Process Analyst |
Optionality: | Can be excluded. |
Template: | |
More Information: | |
|
Input to Activities: | Output from Activities: |
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 to the Business Case, as well as the Vision document of a software engineering effort. It communicates the fundamental "why's and what's" 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.
(hyperlinks into HTML template in a new window)
The Business Vision document is created early in the inception phase, and it is used as a basis for the Business Case (see Artifact: Business Case) and the first draft of the (project) Vision document (see Artifact: Vision).
A business-process analyst is responsible for the integrity of the Business Vision document, ensuring that:
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 of 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.
Rational Unified
Process
|