Describing the outcomes
The outcomes of a business capability, a functionality, or a skill are represented by a content.
The content designates the content of a message or an event, independent of its structure. This structure is represented by an XML schema linked to the content. A content may be used by several messages, since it is not associated with a sender and a destination. There can be only one content per message or event, but the same content can be used by several messages or events.The contents associated with the outcomes are used to describe the content of flows exchanged in the value streams, see Value streams.
The outcomes are used to define the dependencies between:
• The business capabilities in the business capability maps, see Defining business capability dependencies.
• The sub-functionalities in the functionality maps, see Defining Functionality dependencies.
• The sub-skills in the skill maps, see Defining the business skill dependencies.
The properties of an outcome
The Characteristics property page of the outcome provides access to:
• its Owner, by default on creation of the result, the current enterprise.
• its Name,
• the text of its Description.
Connecting an outcome to a business capability
An outcome can be used by a business capability or by an exhibited business capability. It appears in the Desired Capability Effect section of the Characteristics page of the capability property pages.
For example, the desired capability effect of "Billing" is an "Invoice"
To connect an existing outcome to a business capability, for example:
1. Open the property pages of the business capability that interests you.
2. Select the Characteristics page.
3. In the Desired Capability Effect section, click New.
The Creating a Desired Business Effect window opens.
4. Select Reusing an existing content.
5. Select the content that interests you and click OK.
The content appears in the list of Desired Capability Effects.