Example 23: Business Active Structure Elements
For internal consistency, this example should be updated as it describes the same collaboration than in "Figure 13. : Common Domain Elements", but with different members. (JB)
34 Matching Annotations
- Jul 2025
-
archimate.projects.opengroup.org archimate.projects.opengroup.org
-
-
Application Active Structure Elements
Please avoid examples with application collaboration for the reason mentioned above.
-
Cooperating application components can be aggregated in collaborations.
I would remove it. Applications cannot agree by themselves to create a collaboration, for this domain it makes the least sense and I would not mention it at all. Allow it in the definitions and relationships but not proactively propose using that.
-
Alternatively, an access relationship can be expressed by nesting the passive structure element inside the behavior or active structure element that accesses it; for example, nesting a data object inside an application component.
I thin access nesting is not needed anymore as we allowed assignments for passive objects.
-
Relationships Between Strategy Elements and Motivation and Core Elements
Do we need to show Service and Internal Behaviour Element? Wouldn't it be easier just to show Behaviour element? Or do we want to say by the picture that Work package does not realize Strategy Behaviour Element?
-
elements
singular should be used
-
Example 22: Value Stream with Capability Cross-Mapping
Isn't the value realized byt the value stream? We may be missing this relationship for value.
-
Example 22: Value Stream with Capability Cross-Mapping
The icon notation for values treams looks odd. Value stream stages are not aligned within the bigger values stream and the flow arrows are not well visible. What about changing it to boxed notation?
-
Relationships Between Motivation Elements and Core Elements
Role should be added to Business Actor to be assigned Stakeholder as it is part of the stakeholder definition.
-
conforms
And the best way to express the conformance is the influence and not a realization... (Still having troubles with requirements realizing principles ...
-
Another useful application
I would maybe add the third which is the structuring of a diagram to become more easily readable.
-
-
archimate.projects.opengroup.org archimate.projects.opengroup.org
-
Application Active Structure Elements
Please avoid examples with application collaboration for the reason mentioned above.
-
Cooperating application components can be aggregated in collaborations.
I would remove it. Applications cannot agree by themselves to create a collaboration, for this domain it makes the least sense and I would not mention it at all. Allow it in the definitions and relationships but not proactively propose using that.
-
elements
singular should be used
-
Example 23: Business Active Structure Elements
For internal consistency, this example should be updated as it describes the same collaboration than in "Figure 13. : Common Domain Elements", but with different members. (JB)
-
Relationships Between Strategy Elements and Motivation and Core Elements
Do we need to show Service and Internal Behaviour Element? Wouldn't it be easier just to show Behaviour element? Or do we want to say by the picture that Work package does not realize Strategy Behaviour Element?
-
Example 22: Value Stream with Capability Cross-Mapping
Isn't the value realized byt the value stream? We may be missing this relationship for value.
-
Example 22: Value Stream with Capability Cross-Mapping
The icon notation for values treams looks odd. Value stream stages are not aligned within the bigger values stream and the flow arrows are not well visible. What about changing it to boxed notation?
-
Relationships Between Motivation Elements and Core Elements
Role should be added to Business Actor to be assigned Stakeholder as it is part of the stakeholder definition.
-
conforms
And the best way to express the conformance is the influence and not a realization... (Still having troubles with requirements realizing principles ...
-
Alternatively, an access relationship can be expressed by nesting the passive structure element inside the behavior or active structure element that accesses it; for example, nesting a data object inside an application component.
I thin access nesting is not needed anymore as we allowed assignments for passive objects.
-
Another useful application
I would maybe add the third which is the structuring of a diagram to become more easily readable.
-
a unit
The word unit is a bit confusing. As the process may be divided into fin-grained processes while the word unit may be impoperly understood as something that cannot be split into pieces.
-
cannot perform behavior
Almost anything can perform behaviour, e.g. paper can burn, stone can melt etc. Should we somehow reflect that in the description? I usually use the explanation that passive element is something we manipulate with but not sure if it fits better.
-
can be accessed by behavior elements
can be accessed or manipulated by behavior elements (AP)
-
Hierarchy of Behavior and Structure Elements
inconsistency between the way how interface and service are described. Either both should be white with name in brackets or both should be grey.
-
- May 2021
-
twitter.com twitter.com
-
Tom Chivers on Twitter. (n.d.). Twitter. Retrieved 22 February 2021, from https://twitter.com/TomChivers/status/1353622817904975878
-
- Feb 2021
-
10.11.66.200 10.11.66.200
-
If the cardholder refuses to be transferred to the IVR
-
If No
-
- Oct 2020
-
final-form.org final-form.org
-
Returns a Promise<?Object> that resolves with no value on success or resolves with an Object of submission errors on failure. The reason it resolves with errors is to leave rejection for when there is a server or communications error.
-
- Jul 2020
-
edpb.europa.eu edpb.europa.eu
-
Article 7(3) of the GDPR prescribes that the controller must ensure that consent can be withdrawn bythe data subject as easy as giving consent and at any given time. The GDPR does not say that givingand withdrawing consent must always be done through the same action.
-
consent is obtained through use of a service-specific user interface (for example, via a website, an app,a log-on account, the interface of an IoT device or by e-mail), there is no doubt a data subject must beable to withdraw consent via the same electronic interface, as switching to another interface for thesole reason of withdrawing consentwould require undue effort.
-
The controller informs customers that they havethe possibility to withdraw consent. To do this, they could contact a call centre on business daysbetween 8am and 5pm, free of charge. The controller in this example doesnotcomply with article 7(3)of the GDPR. Withdrawing consent in this case requires a telephone call during business hours, this ismore burdensome than the one mouse-click needed for giving consent through the online ticketvendor, which is open 24/7.
-
- May 2020
-
www.analyticsmania.com www.analyticsmania.com
-
To be fully compliant with GDPR, you would also need to enable Show Reject All Button setting.
-