2. Trademarks
• ArchiMate®, and The Open Group® logo are trademarks of The Open
Group.
• All other brand, company, and product names are used for
identification purposes only and may be trademarks that are the sole
property of their respective owners.
2
4. Exam Info
• Quoted from ArchiMate® 3 Practitioner fact sheet:
• Examination Name: ArchiMate 3 Part 2
• Examination Type: Complex multiple-choice scenario-based examination, 8
questions/90 minutes
• Supervised: YES
• Open Book: YES
• Scoring is done based on the following:
• 5: Best answer
• 3: Second best
• 1: Third best
• 0: Incorrect / Distractor
4
5. Similar to “Spot the differences” game
5
Source from Disney clips (Link)
6. General Advices
• Skim (Read fast) the scenario, most probably you will need to focus on part of it
not all the scenario. So, you might need to re-read this portion only later.
• You have 11.25 mins (ESL: 15 mins) please pay close attention to time.
• If you are taking the exam from home you can’t use white paper to write your
thoughts. You must have a way to document your thoughts for every question in
a notepad (Digitally: ). Example:
• Q1:
• A: Weak association relation between work package and deliverable.
• B: …
• C: …
• D: Wrong as diagram is missing motivation layer
• If the scenario is hard, just select any answer from what you have marked as
possible answer, and mark for review, then go to next question.
6
7. Tip 1 : Question not answered
• Missing layer / components that the question was clearly asking to
include / describe (i.e. Missing deliverables).
7
8. Tip 2 : Missing component from scenario
• Missing component(s) that the was described in scenario and found
in other diagrams.
8
9. Tip 3 : Missing junction
• Junction (Or/And) doesn’t exists in the diagram while it was
mentioned in the scenario.
9
10. Tip 4 : Wrong component usage
• Wrong component usage ==> Check the meaning in scenario.
• Pay close attention to “Business Object” vs “Contract”.
• Pay close attention to “Actor” vs “Role”.
• Pay close attention to “Application component” vs “System Software”.
• Pay close attention to “Requirement” vs “Constraint”.
10
11. Tip 5 : Diamond direction in relation
• Pay close attention to diamond in composition / aggregation relation,
is it specified in the right direction?
11
12. Tip 6: Relation not supported by meta-model
• Wrong relation usage. Having doubts? It is open book exam: Check in
Meta-model / examples if relationship is allowed or not.
12
13. Tip 7: Undirected association is weak relation
• Association without directions are weak; normally this won't denote a best
answer as long as there is another model containing more specific
relationships.
13
14. Tip 8: Composition is strong relation
• Pay close attention to composition / aggregation relation in all diagrams.
Composition is strong relation. Does the scenario really require/imply
composition? Look for words like “main”, “key”, “consists”, … etc to apply
composition or it is implicitly understood.
14
15. Tip 9: Undirected access relation
• Pay close attention to unspecified arrows in access relation, it is weak,
is there other diagram have more specified relation?
15
16. References & Credits
• Credits for free ArchiMate tool Archi.
• Some diagrams included in this presentation based on purchased
license from Infograpia.
• This presentation is intended for non-commercial use, credits goes to:
• Disney Clips for spot the difference game.
16