DisplayArchiMateGlossary
Naar navigatie springen
Naar zoeken springen
ArchiMate begrippenlijst
| Bedrijfslaag | ||
|---|---|---|
| BusinessActor |  | A business actor is a business entity that is capable of performing behavior. |
| BusinessCollaboration |  | A business collaboration is an aggregate of two or more business internal active structure elements that work together to perform collective behavior. |
| BusinessEvent |  | A business event is a business behavior element that denotes an organizational state change. It may originate from and be resolved inside or outside the organization. |
| BusinessFunction |  | A business function is a collection of business behavior based on a chosen set of criteria (typically required business resources and/or competencies), closely aligned to an organization, but not necessarily explicitly governed by the organization. |
| BusinessInteraction |  | A business interaction is a unit of collective business behavior performed by (a collaboration of) two or more business roles. |
| BusinessInterface |  | A business interface is a point of access where a business service is made available to the environment. |
| BusinessObject |  | A business object represents a concept used within a particular business domain. |
| BusinessProcess |  | A business process represents a sequence of business behaviors that achieves a specific outcome such as a defined set of products or business services. |
| BusinessRole |  | A business role is the responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event. |
| BusinessService |  | A business service represents an explicitly defined exposed business behavior. |
| Contract | | A contract represents 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. |
| Location |  | A location is a place or position where structure elements can be located or behavior can be performed. |
| Meaning |  | Meaning represents the knowledge or expertise present in, or the interpretation given to, a core element in a particular context. |
| Product |  | A product represents a coherent collection of services and/or passive structure elements, accompanied by a contract/set of agreements, which is offered as a whole to (internal or external) customers. |
| Representation |  | A representation represents a perceptible form of the information carried by a business object. |
| Value |  | Value represents the relative worth, utility, or importance of a core element or an outcome. |
| Applicatielaag | ||
| ApplicationCollaboration | | An application collaboration represents an aggregate of two or more application components that work together to perform collective application behavior. |
| ApplicationComponent |  | An application component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable. It encapsulates its behavior and data, exposes services, and makes them available through interfaces. |
| ApplicationFunction | | An application function represents automated behavior that can be performed by an application component. |
| ApplicationInteraction | | An application interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components. |
| ApplicationInterface | | An application interface represents a point of access where application services are made available to a user, another application component, or a node. |
| ApplicationService | | An application service represents an explicitly defined exposed application behavior. |
| DataObject | | A data object represents data structured for automated processing. |
| Technologielaag | ||
| Artifact |  | An artifact represents a piece of data that is used or produced in a software development process, or by deployment and operation of an IT system. |
| CommunicationPath |  | A communication path is defined as a link between two or more nodes, through which these nodes can exchange data. |
| Device |  | A device is a physical IT resource upon which system software and artifacts may be stored or deployed for execution. |
| InfrastructureFunction | | An infrastructure function is defined as a behavior element that groups infrastructural behavior that can be performed by a node. |
| InfrastructureInterface | | An infrastructure interface is defined as a point of access where infrastructure services offered by a node can be accessed by other nodes and application components. |
| InfrastructureService | | An infrastructure service is defined as an externally visible unit of functionality, provided by one or more nodes, exposed through well-defined interfaces, and meaningful to the environment. |
| Network |  | A network is defined as a communication medium between two or more devices. |
| Node |  | A node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources. |
| SystemSoftware |  | System software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it. |
| Rationale-extensie | ||
| Assessment |  | An assessment represents the result of an analysis of the state of affairs of the enterprise with respect to some driver. |
| Constraint |  | A constraint represents a factor that prevents or obstructs the realization of goals. |
| Driver |  | A driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them. |
| Goal |  | A goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders. |
| Principle |  | A principle represents a qualitative statement of intent that should be met by the architecture. |
| Requirement |  | A requirement represents a statement of need that must be met by the architecture. |
| Stakeholder |  | A stakeholder is the role of an individual, team, or organization (or classes thereof) that represents their interests in the outcome of the architecture. |
| Implementatie-en-migratie-extensie | ||
| Deliverable |  | A deliverable represents a precisely-defined outcome of a work package. |
| Gap |  | A gap represents a statement of difference between two plateaus. |
| Plateau |  | A plateau represents a relatively stable state of the architecture that exists during a limited period of time. |
| WorkPackage |  | A work package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints. |
| Structuurrelaties | ||
| AccessRelationship | The access relationship models the ability of behavior and active structure elements to observe or act upon passive structure elements. | |
| AggregationRelationship | The aggregation relationship indicates that an element consists of one or more other concepts. | |
| AssignmentRelationship | The assignment relationship expresses the allocation of responsibility, performance of behavior, or execution. | |
| AssociationRelationship | An association relationship models an unspecified relationship, or one that is not represented by another ArchiMate relationship. | |
| CompositionRelationship | The composition relationship indicates that an element consists of one or more other concepts. | |
| RealisationRelationship | The realization relationship links a logical entity with a more concrete entity that realizes it. | |
| UsedByRelationship | The used by relationship models the use of services by processes, functions, or interactions and the access to interfaces by roles, components, or collaborations. | |
| Dynamische relaties | ||
| FlowRelationship | The flow relationship represents transfer from one element to another. | |
| TriggeringRelationship | The triggering relationship describes a temporal or causal relationship between elements. | |
| Overige relaties | ||
| InfluenceRelationship | The influence relationship models that an element affects the implementation or achievement of some motivation element. | |
| SpecialisationRelationship | The specialization relationship indicates that an object is a specialization of another object. | |
| Relatieconnectoren | ||
| Junction |  | A junction is used to connect dynamic relationships of the same type. |
De definities op deze pagina zijn overgenomen uit de ArchiMate-specificatie van The Open Group. Deze specificatie is hier te vinden.