| Interface | Description |
|---|---|
| Assessment |
Assessment vnull
An assessment may reveal strengths, weaknesses, opportunities, or threats for some area of interest.
|
| Constraint |
Constraint vnull
In contrast to a requirement, a constraint does not prescribe some intended functionality of the system to be realized, but imposes a restriction on the way it operates or may be realized.
|
| Driver |
Driver vnull
Drivers may be internal, in which case they are usually associated with a stakeholder, and are often called "concerns".
|
| Goal |
Goal vnull
In principle, a goal can represent anything a stakeholder may desire, such as a state of affairs, or a produced value.
|
| Meaning |
Meaning vnull
A meaning represents the interpretation of an element of the architecture.
|
| Outcome |
Outcome vnull
Outcomes are high-level, business-oriented results produced by capabilities of an organization, and by inference by the core elements of its architecture that realize these capabilities.
|
| Principle |
Principle vnull
Principles are strongly related to goals and requirements.
|
| Requirement |
Requirement vnull
In the end, a business goal must be realized by a plan or concrete change goal, which may or may not require a new system or changes to an existing system.
|
| Stakeholder |
Stakeholder vnull
This definition is based on the definition in the TOGAF framework [4].
|
| Value |
Value vnull
Value may apply to what a party gets by selling or making available some product or service, or it may apply to what a party gets by buying or obtaining access to it.
|