Organisations need to adapt increasingly fast and anticipate changing customer requirements and business goals. This need influences the entire chain of activities of a business, from the organisational structure to the network infrastructure. How can you control the impact of these changes? Enterprise Architecture may be the answer. It isRead More →
The flow relationship represents transfer from one element to another. The example below shows a Claim Assessment function, which forwards decisions about the claims to the Claim Settlement function. In order to determine the order in which the claims should be assessed, Claim Assessment makes use of schedule information receivedRead More →
The triggering relationship describes a temporal or causal relationship between elements. The example below illustrates that triggering relationships are mostly used to model causal dependencies between (sub-)processes and/or events: he triggering relationship is used to model the temporal or causal precedence of behavior elements in a process. The usual interpretationRead More →
The dynamic relationships describe temporal dependencies between elements within the architecture. Two types of dynamic relationships are distinguished: triggering flow Related Articles: What is ArchiMate? Full ArchiMate Viewpoints Guide ArchiMate 3 Update What’s New in ArchiMate 3? Using ArchiMate Tool with TOGAF ADM Open Group Certified ArchiMate Tool – VisualRead More →
The influence relationship models that an element affects the implementation or achievement of some motivation element. The example below illustrates the use of the influence relationship to model the different effects of the same motivation element, Assign Personal Assistant. This has a strongly positive influence on Reduce Workload Of Employees,Read More →
The access relationship models the ability of behavior and active structure elements to observe or act upon passive structure elements. The example below illustrates the access relationship. The Create Invoice sub-process writes/creates the Invoice object; the Send Invoice sub-process reads that object. The access relationship indicates that a process, function,Read More →
The serving relationship models that an element provides its functionality to another element which describes how the services or interfaces offered by a behavior or active structure element serve entities in their environment. This relationship is applied for both the behavior aspect and the active structure aspect. The example belowRead More →
Dependency relationships describe how elements support or are used by other elements. Three types of dependency relationship are distinguished: The serving relationship represents a control dependency, denoted by a solid line. The access relationship represents a data dependency, denoted by a dashed line. The influence relationship is the weakest typeRead More →
The realization relationship indicates that an entity plays a critical role in the creation, achievement, sustenance, or operation of a more abstract entity.. The example below illustrates two ways to use the realization relationship. A Transaction Processing function realizes a Billing Service; the Billing Data object is realized by theRead More →
The aggregation relationship indicates that an element groups a number of other concepts. The example below includes the two ways to express the assignment relationship. The example shows two ways to express that the Customer File aggregates an Insurance Policy and Insurance Claim: The aggregation relationship has been inspired by the aggregation relationship in UMLRead More →