A  Business Agent is a Resource Agent which produces and reacts to Business Outcome Events of the enterprise.

A  Business Agent can be a Human Resource (Organizational Position or Department Type), a Business System (Business Software System or Concrete Hardware System) or a Capability Configuration (an assembly of Org-Units and Business Systems.

A  Business Environment Scenario is a story that describes how a Business Agent interacts with its partners (Partner Resource Agents) to achieve Business Outcome Events in a specific Eco-System (Business Agent Environment).

This includes:

1) A course of events represented by Resource Object Flows depicting the story towards the delivery of expected Business Outcome Events.

2) Interacting  Business Agents who participate to the story in the considered Eco-System.

A  Business Resource Capability is a Resource Capability provided by Business Agents, that benefits to Customers (internal or external) of the enterprise. It expresses an ability to produce Business Outcome Events.

This includes Functionality, Physical Capability and Skill.

A  Business Resource Interaction Process is a story involving the components of a Business Agent interacting in order to produce Business Outcome Events.

This includes:

1) A course of events represented by Resource Flows depicting the steps towards the delivery of expected Business Outcome Events.

2) Component Business Agents that participate to the story.

A  Business Resource Process is a  Resource Process which is conducted by Business Agents (physical resources such as Org-Unit, System of Resources ,Business Systems) and which describes how these entities act to produce and consume Business Outcome Events.

 Business Resource Processes include Business Processes and System Processes,

A  Conceptual Agent is an abstract type of Agent that depicts a functional division of labor within an enterprise, influencing the formation of its business operating model.

The concrete specializations of  Conceptual Agent follow the systemic level pattern and come in the form of Operating Domain (a Macro  Conceptual Agent) and Business Function (a Mezzo  Conceptual Agent).

A  Conceptual Operating Asset is an Operating Asset  used to describe the Conceptual Operating Model of the enterprise.

It includes Value Streams, Operating Domains and Business Functions and the way they contribute to the delivery of Business Outcome Events.

A  Data Asset  represents the abstract structure of any kind of data that can be processed and memorized by a Business Software System.

A  Data Asset is either a Data Entity or a  Data Property.

Only Data Entitys can have identity and states.  Data Propertys only handle raw data.

 Data Assets are managed in Data Catalogs.

A  Data Domain is subset of the enterprise’s data that are meant to be manipulated together in the context of business operations.

For instance, a "Sales"  Data Domain contains at least the following entities: Customers, Orders, Products.

Each Data Entity in a  Data Domain has CRUD characteristics. For instance, Products are read-only in a "Sales"  Data Domain, while Customers and Orders have all CRUD characteristics.

 Data Domains define functional data boundaries used both for Data Allocation to Business Systems (see Data Stores) and Data Governance for data stewardship (Data Catalogs).

An  Operational Risk Type is a kind of Risk Type that refers to the potential for loss due to the enterprise's inadequate functioning.

An  Operational Risk Type is either Compliance Risk Type a or an Operating Risk Type.

A  Business Capability is a conceptual Capability that benefits to Customers (internal or external) of the enterprise. It expresses an ability to produce Conceptual Outcome Events.

A  Business Capability is defined by its intended Enterprise Outcome Events and the conditions (Condition Property) under which the production of the Enterprise Outcome Events shall be proceeded.

The actual Condition Scale Values for a given Business Capability at different stages of Enterprise Initiatives is given by their exhibition (Exhibited Capability).

As part of the Conceptual Operating Model, a  Conceptual Interaction Scenario is a story that frames how the components of a Conceptual Agent interacts to achieve Conceptual Outcome Events.

This includes:

1) A course of events represented by Business Object Flows depicting the steps towards the delivery of expected Conceptual Outcome Events.

2) Conceptual Agents who participate to the story.

 Value Streams are used to frame the Conceptual Operating Model of the enterprise: they describe how the enterprise shall operate, at the conceptual level, and helps chunking responsibilities between Conceptual Agents (Operating Domain or Business Function) .

In the EA context, a  Value Stream is a conceptual Action Process that represents an overarching perspective of the organization's processes aiming at producing Conceptual Outcome Events. The focus is on shaping and understanding the functional relationships and roles within the enterprise : its functional division of labor.

This is not to be confused with Value Stream Mapping (VSM) which is focused on Lean optimization and is addressed with the concept of  Business Process (see the Organization & Processes domain).

A  Value Stream is performed by Conceptual Agents who produce Conceptual Outcome Events. It is depicted as a sequence of Value Stream Stages, controlled by events and conditions.

 Value Stream Activitys are carried out by the involvment of Conceptual Agents as participants in the  Value Stream.

During its course of action, a  Value Stream consumes, produces or stores  Business Objects.

1) It may read or write Conceptual Entity Assets in its Business Object Store.

2) It may receive Conceptual Entity Assets at its boundary:  reacted to Business Outcome Events.

3) It may produce Conceptual Entity Assets at its boundary:  produced Business Outcome Events.

The course of actions of a  Value Stream is constrained by the application of rules ( Conceptual Rule Enforcement) that define what is allowed and not allowed to do.

There are traditionnaly two kinds of  Value Streams:

1) Development development  Value Streams define all of the actions, both value-creating and nonvalue-creating, required to bring a Product from concept to launch.
2)  Operational  Value Streams define define all of the actions, both value-creating and nonvalue-creating, required from order to delivery. These include actions to process information from the  Customer and actions to transform the product on its way to the Customer.