aiExpert In Practice – #2 – Archimate 3
This example gets aiExpert to provide feedback on an Archimate3 Motivation Model.
Source diagram
The source of this model is the Archimate example which is delivered in the Sparx ‘EAExample’ model, which is installed when you install EA.
This diagram can be found at: Example Model.Enterprise Architecture.Architectural Frameworks.ArchiMate3.Example 18 – Stakeholder, Driver and Assessment, in the EA v17 version of EAExample.
The purpose of this document is to describe what the results were when parts of this model were analyzed by the aiExpert ‘Archimate Motivation Model’ query, which is used to examine the ‘purple layer’ of an Archimate model.
Please note that this is using the out-of-the-box function of aiExpert, with no tailoring of the prompts to suit the domain.
Model Diagram 'Example 18 - Stakeholder, Driver and Assessment'
The diagram which aiExpert analyzed was “Example 18 – Stakeholder, Driver and Assessment” which is an example of an Archimate ‘Motivation layer’ model.
Inputs
We chose the ‘Archimate Motivation Model’ query for this analysis, which collects all the data about each Archimate element, and all their connectors, and submits this to the LLM with the prompts:
System instructions: “You are an expert in the style and structure of Archimate 3 Motivation layer models”
Rules: “
Here are some parts of an Archimate 3 Motivation model.
Use these authoritative sources for best-practice rules and guidance:
– The Open Group ArchiMate® 3.2 Specification (Motivation layer semantics, allowed relationships).
– The Open Group ArchiMate® Practitioners’ Guide (recommended usage patterns).
– The TOGAF® Standard, Business Architecture guidance (linking drivers, goals, principles, and requirements).
– Wierda, G. *Mastering ArchiMate* (practical modeling style and pitfalls to avoid).
– Practitioner blogs/white papers from the ArchiMate Forum (Open Group) for clarity and good practice.
When checking a model:
– Ensure all elements and relationships conform to the ArchiMate 3.2 metamodel.
– Flag common misuse highlighted in the Practitioners’ Guide and *Mastering ArchiMate*.
– Provide short, clear feedback. Where relevant, cite which source (e.g. “ArchiMate Spec”, “Practitioners’ Guide”) the rule comes from.
– Do not invent new rules beyond these sources.
When you respond, grade the severity from 1 – a minor issue, to 5 – a serious problem.
Always include the ID of each element with any feedback”
LLM used: gpt-5-mini
Data collector: ConnectorDetail
Important note:
We present the details of the Ai analysis largely without comment. This is not our model: we don’t understand the domain, so we are not in a position to say whether the feedback from the LLM is good or bad, useful or useless. What we can say is whether the feedback might be useful, or whether it seems silly.
In the ‘suggested fix’ information which is returned by the AI, we highlight in italics the part of the input message to which the feedback refers.
Feedback form AI on the item ‘Market Share is declining’
Issue 1: This Assessment is modelled with outgoing ‘ControlFlow’ relationships labelled as influences. Use the Motivation-layer Influence relationship instead of Control Flow (behavioural). (Source: ArchiMate Spec, Practitioners’ Guide)
Suggest fix for this issue: Change “Market share is declining is connected to Competitors are including advanced features… connection type is: ControlFlow and stereotype Archi Mate Influence (connector name ‘++’)” to: “Market share is declining is connected to Competitors are including advanced features… connection type is: Influence and (optionally) annotate polarity/strength in the name or attribute (e.g. ‘positive influence’ or ‘++’)”
Issue 2: Connector names use ‘++’ and ‘–‘ to indicate polarity/strength. The ArchiMate specification and Practitioners’ Guide recommend using the Influence relationship (with an explicit name or property describing positive/negative effect) rather than relying on compact symbols alone. The current notation is ambiguous and reduces model clarity for stakeholders. (Source: Practitioners’ Guide, Mastering ArchiMate)
Suggested fix for this issue: Change “Market share is declining -> Discounts provided to remain competitive connection name: ‘–‘” to: “Market share is declining -> Discounts provided to remain competitive connection type: Influence, name: ‘reduces decline’ (or name: ‘negative influence on decline’), and document polarity/strength in a property or diagram legend”
Feedback form AI on the item ‘Profitability is declining’
Issue 1:Relationships from this Assessment are modeled with relationship type ‘ControlFlow’ and stereotype ‘Archi Mate Influence’. ‘Control Flow’ is a behavioral relationship and is not appropriate in the Motivation layer. Replace with the Influence relationship. (Source: ArchiMate Spec, Practitioners’ Guide)
Suggest fix for this issue: Change “Profitability is declining is connected to Revenue is declining connection type is: ControlFlow and stereotype Archi Mate Influence (connector name ‘++’)” to: “Profitability is declining is connected to Revenue is declining connection type is: Influence (Motivation layer Influence) and (optionally) annotate polarity/strength in the name or attribute (e.g. ‘positive influence’ or ‘++’)”
Issue 2: Profitability is declining and Revenue is declining influence each other (mutual ControlFlow/Influence). Circular assessment influence can create tautological explanations and reduce usefulness of the model. Consider modeling causal chains with drivers -> assessments (cause -> effect) or adding intermediate causes rather than two assessments mutually reinforcing each other. (Source: Practitioners’ Guide, Mastering ArchiMate)
(These aren’t the only suggestions for other items in this diagram. aiExpert suggested others too. Try it yourself to see)
Suggested fix for this issue: Change “Profitability is declining <-> Revenue is declining (mutual influence, modeled as ControlFlow/Influence)” to: “Model causal direction explicitly, e.g. ‘Revenue is declining (Assessment) –positive influence–> Profitability is declining (Assessment)’ and remove the reverse link unless you can justify a clear causal mechanism. Alternatively, introduce a Driver or more specific Assessment that explains the feedback loop.”
More Insights
aiExpert In Practice - #4 - Healthcare Data Model
11 November 2025
Shows a summary of the feedback on some parts of a large, public domain healthcare model from Canada
Learn MoreaiExpert In Practice - #3 - BPMN Process Models
7 November 2025
This example gets aiExpert to provide feedback on an BPMN 2 process model diagram
Learn MoreaiExpert In Practice - #1 - Aeronautical Data model
5 November 2025
This worked example shows how aiExpert was applied to a public-domain data model, and shows the results which the LLM returned
Learn MoreA model without validation is just some pictures
22 June 2023
Why you need your models to be validated.
Learn MoreUsing Derived Connectors to simplify your models
7 June 2023
..and make them more valuable
Learn MoreTechnical and Content-quality
1 June 2023
Maintain quality with tools to find and fix mechanical errors in your modeling
Learn MoreTop 11 model quality tips for Sparx EA modelers
3 November 2022
Discover new insights into your model, and spot and resolve problems.
Learn MoreHow to get your EA models ready for Prolaborate
6 July 2022
To make the most of Prolaborate it's a good idea to start by doing some housekeeping
Learn MoreStep by step to a tailored UI for Enterprise Architect
28 March 2022
The 'out-of-the-box' EA element properties window can be intimidating for a new user, and it's easy to get overwhelmed, miss critical data, or more...
Learn MoreOnly Connect - Exploring traceability in Sparx EA models
1 November 2021
This webinar looks at the importance of consistency to get value from traceability.
Learn MoreWebinar - How to improve model quality and consistency
16 June 2020
This webinar from the EA Global Summit 2020 provides hints and tips for managing models as they grow.
Learn MoreHard and Soft
11 October 2017
No, not about Brexit… More about styles of Business Analyst.
Learn MoreModel curation techniques for EA
6 September 2016
How cleaning, navigating and validating your EA model makes sharing and collaborating much more effective.
Learn More