ArchiMate Definitionen

A behavior element that groups behavior based on a chosen set of criteria (typically required business resources and/or competences).

A behavior element that describes the behavior of a business collaboration.

Something that happens (internally or externally) and influences behavior.

A service that fulfills a business need for a customer (internal or external to the organization).

A passive element that has relevance from a business perspective.

A perceptible form of the information carried by a business object.

The knowledge or expertise present in a business object or its representation, given a particular context.

The relative worth, utility, or importance of a business service or product.

A coherent collection of services, accompanied by a contract/set of agreements, which is offered as a whole to (internal or external) customers.

A formal or informal specification of agreement that specifies the rights and obligations associated with a product.

A modular, deployable, and replaceable part of a software system that encapsulates its behavior and data and exposes these through a set of interfaces.

An aggregate of two or more application components that work together to perform collective behavior.

A point of access where an application service is made available to a user or another application component.

A behavior element that groups automated behavior that can be performed by an application component.

A behavior element that describes the behavior of an application collaboration.

A service that exposes automated behavior.

A passive element suitable for automated processing.

A computational resource upon which artifacts may be stored or deployed for execution.

A hardware resource upon which artifacts may be stored or deployed for execution.

A communication medium between two or more devices.

A link between two or more nodes, through which these nodes can exchange data.

A point of access where infrastructure services offered by a node can be accessed by other nodes and application components.

A software environment for specific types of components and objects that are deployed on it in the form of artifacts.

A behavior element that groups infrastructural behavior that can be performed by a node.

An externally visible unit of functionality, provided by one or more nodes, exposed through well-defined interfaces, and meaningful to the environment.

A physical piece of data that is used or produced in a software development process, or by deployment and operation of a system.

A stakeholder is defined as the role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture.

A driver is defined as something that creates, motivates, and fuels the change in an organization.

An assessment is defined as the outcome of some analysis of some driver.

A goal is defined as an end state that a stakeholder intends to achieve.

A requirement is defined as a statement of need that must be realized by a system.

A constraint is defined as a restriction on the way in which a system is realized.

A principle is defined as a normative property of all systems in a given context, or the way in which they are realized.

A work package is defined as a series of actions designed to accomplish a unique goal within a specified time.