A trigger that starts, modifies, or completes a process. this include message, timer, error, compensation, signal, cancel, escalation, link, etc. An event can be classified as either "throwing" or "catching," depending on their function.

A particular task performed by a person or system. It can include sub-processes, loops, multiple loops, and compensations.

A decision point that can adjust the path based on conditions or events. A

This shows the order of activities to be performed

This depicts messages that flow across pools, or organizational boundaries such as departments. It should not connect events or activities within a pool.

This associates an artifact or text to an event, activity, or a gateway

It represents major participants in a process. A different pool may be in a different company or department but still involved in the process.

It is a sub-part of a pool. It shows the activities and flow for a certain role or participant, defining the accountability within the processes

This shows the necessary data for an activity

This shows a logical grouping of activities, but does not change the diagram's flow.

This provides further explanation to a part of the diagram.

This involves internal processes to a specific organization and do not cross pools or organizational boundaries.

This occurs between a private BP and an external participant or process. This does not show the private BP itself.

This shows the interactions between two or more business entities.

This concept involves use case diagrams, which describes system functionality from the point of view of a user.

This concept involves class diagrams, which describes the structure of a system in terms of objects, attributes, associations, and operations.

This concept involves interaction diagrams, state machine diagrams, and activity diagrams, which are used to describe internal behavior of the system.

It describes the static structure of a system

It is a subset of a class diagram used to organize elements of a system into related groups.

It describes the static structure of a system at a particular time, and can be used to test class diagrams for accuracy.

This describes the organization of physical software components, including source codes, run-time code, and executables.

This diagram shows the internal parts of a class.

This depicts the physical resources in a system, including nodes, components, and connections.

This illustrates the dynamic nature of a system by modeling the flow of control from activity to activity.

This describes the interactions among classes in terms of an exchange of messages over time.

This models the functionalities of a system using actors and use cases, and can be considered as a simplified version of a collaboration diagram introduced in UML 2.0.

This describes the dynamic behavior of a system in response to external stimuli.

It models the interactions between objects in sequence.

It is a combination of an activity and a sequence diagram, which models a more complex interaction.

It is an interaction UML diagram that focuses on processes that take place during a specific period of time, wherein time is shown to increase from left to right.

It is the role of an individual, team, department, or organization that represents their interest in the outcome of the architecture.

It is an external or internal condition that motivates an organization to define its goals and implement the necessary change to achieve them.

It is the result of an analysis of a particular business issue within the enterprise with respect to some drivers.

It is a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.

It is a specific statement of need that architectural designers must meet.

It is a factor that averts or hinders the realization of goals.

It is strongly related to the organization’s goals and requirements. It is considered a qualitative statement of intent that should

It is a result that has been achieved.

It is the relative worth, usefulness, or importance of a core element or an outcome

It is the knowledge or expertise present in a business object or its representation, given a particular context.

This represents what an enterprise has decided to do to realize its goals. This is an approach or plan for configuring capabilities and resources of an enterprise undertaken to achieve a goal.

These are considered the key building blocks of a business, unique and independent from each other, and tend to be stable over time. These are typically aimed at achieving some goal or delivering value by realizing an outcome. These are abilities that an active structure element, such as an organization, person, or system, possesses.

These are assets owned and/or controlled by an individual or organization. These are structured elements that are assigned to capabilities

This business entity is capable of performing behavior

It is the responsibility for performing specific behavior, to which an actor can be assigned.

It is an aggregate of two (2) or more active internal business structure elements that work together to perform collective behavior.

It is a point of access where a business service is made available to the environment.

It is used to model an object type in which several instances may exist within an organization. It represents important information or conceptual elements within a particular business domain

It is a perceptible form of the information carried by a business object.

It is considered as an explicitly defined perceptible business behavior. It is mainly used to manifest business functionality to the environment.

It is a sequence of business behaviors that achieve a specific outcome, such as a defined set of products and services.

It is a collection of business behaviors based on a chosen set of criteria closely aligned to an organization, but not explicitly governed by the organization

It is a unit of collective business behavior collaboratively performed by two (2) or more business roles.

It denotes an organizational state change. It is instantaneous and does not have a specific duration.

It is a coherent collection of services and/or passive structure elements, accompanied by a contract or a set of agreements, which is offered as a whole to customers

It is a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product and establishes functional and non-functional parameters for interaction.

It is an encapsulation of an application’s functionality that is aligned to the implementation structure, which is modular and replaceable.

It is an aggregate of two (2) or more application components working together to perform collective application behavior.

It is a point of access where an application service is made available to users to another application component or a node.

It is a data that is structured for automated processing

It is an explicitly defined and visible application behavior. It is used to specify services provided by the business.

It is an automated behavior that can be performed by an application component

It is a sequence of application behaviors that realizes a specific outcome.

It is a unit of collective application behavior collaboratively performed by two (2) or more application components.

It refers to an application behavior that denotes a state of change.

It is a computational or a physical resource that hosts, manipulates, or interacts with other computational or physical resources.

It is an aggregate of two (2) or more nodes that work together to perform collective behavior

It is a point of access where technological services offered by a node can be accessed.

It is a physical information technology resource wherein system software and artifacts can be deployed for execution.

It is a software that supports a business environment in storing, executing, and utilizing applications, including the data deployed within the environment.

It is a link between two (2) or more nodes through which the exchange of data or material happens

It is a set of structures that connects computer systems or other electronic devices for transmission, routing, and reception of data or information.

It is a piece of data that is used and/or produced in a software development process or a system deployment and operation.

It is an external visible unit of functionality, provided by one or more nodes accessible through well-defined interfaces.

It is a behavior element that groups infrastructural behavior, which can be performed by a node.

It is a sequence of technological behavior that achieves a specific outcome.

It is a unit of collective technology behavior collaboratively performed by two (2) or more nodes

It is a technology behavior element that denotes a state change.

It is a physical machine, tool, or instrument that can create, use, store, move, or transform materials.

It is a physical structure or environment interconnected by distribution networks.

It is a physical network used to transport materials, data, or information.

It is a tangible matter or physical element that can be accessed by equipment.

It is a series of actions identified and designed to achieve a specific goal or result within a clearly defined beginning and end date and resource constraints.

It is a behavior element that denotes a state of change related to implementation or migration that can encompass a time attribute.

It is a precisely defined outcome of a work package.

It is a relatively stable state of an enterprise architecture that exists during a specific period of time.

It is a statement of difference between two (2) plateaus.