| Categorized Class |
Functional Asset Functional Assets encompasse all Architecture Asset Types used to describe why and how systems operate/function. This includes the Operating Eco-System where system operates to fulfill these purposes (Agents and their Behaviors). Functional Assets include: 1. Blocks defining results of Behaviors of the enterprise or its sub-systems, that benefit to it internal or external customers : Outcome Event, 2. Blocks used to describe information: Information Asset. 3. Blocks used to describe how the enterprise operates: Operating Assets (Agent, Behavior, Service Interface). |
|---|
| Name | Description |
|---|---|
Behavioral Event |
A Behavioral Event is a Temporal Bounding Type that establishes a temporal connection between Behaviors. A Behavioral Event connects a Predecessor Behavioral Event, to a Successor Behavioral Event. |
Information Asset |
An Information Asset represents anything that can be communicated or memorized by an Agent to produce and react to Outcome Events. An Information Asset is either an Information Entity or an Information Property. The difference lies in their relationship to change and to time. Information Entity(ies) can change over time and have a lifeycle while Information Propertys are immutable characteristics. |
Operating Asset |
An Operating Asset is a Functional Asset that describes the way Outcome Events are produced and consumed: how (Behaviors) and by whom (Agents). Operating Assets fulfill Capability(ies) (Fulfilled Capability). As any Functional Architecture Asset, Operating Assets are subject to Policy Conformances. In addition, they define Rule Enforcements to indicate how Policy Conformances are met. |
Operating Eco-System |
An Operating Eco-System is an Operating Context in which an Agent exists or lives for a specific purpose, interacting with partners. For instance, the operating context of an enterprise includes its customers and suppliers. |