ArchiMate is an industry standard notation developed by The Open Group for the graphical modeling of enterprise architectures. The notation has evolved to be fully aligned with TOGAF. Many companies recognise the value of these architectural models in understanding the dependencies between their people, processes, applications, data and hardware. Using ArchiMate allows them to integrate their business and IT strategies.
Gillian Adens, Director of Hippo Software, demonstrates how Enterprise Architect can be used to create ArchiMate models and viewpoints to help in understanding, documenting and communicating knowledge of the enterprise architecture. The webinar:
Don't miss this opportunity to learn more about Enterprise Architect
Enterprise Architect Ultimate edition, version 11, Build 1105.
ArchiMate is built-in as a standard feature of all editions of Enterprise Architect. There is no need to purchase an additional plug-in.
For more information, please view the Compare Editions page on the Sparx Systems website: http://www.sparxsystems.com/products/ea/index.html
ArchiMate version 1 has been supported since Enterprise Architect version 7.5
ArchiMate version 2 has been supported since Enterprise Architect version 9.3
Yes, the project file is using-archimate-in-enterprise-architect.eap.
Please enter your email address and press the Subscribe button, using the page listed below.
To complete the process, you will need to reply to an email to confirm your subscription. Once you subscribe you will receive notifications about all upcoming webinars and newsletters, helping you learn about the latest Enterprise Architect features and innovations from Sparx Systems.
Yes. To place a diagram behind a topic in a Mind Map you use a composite diagram.
Right-click on the Topic element and choose ‘New Child Diagram | Composite Structure Diagram’ from the context menu. This creates another Mind Map diagram attached to the Topic. A small infinity symbol indicates that the topic is now a composite element. Double-click on the topic to open the new Mind Map diagram. If you would prefer a different type of diagram you can use the ‘Diagram | Advanced | Change Type…’ menu to change the diagram type.
Alternatively if the diagram you wish to attach to the Topic already exists, then simply select the topic, right-click and choose ‘New Child Diagram | Select Composite Diagram’ from the context menu. This allows you to browse the project structure and select an existing diagram to attach to the topic. As before, you can now double-click on the topic to open the attached diagram.
Note: This is a general purpose mechanism that can be used for any element type on any diagram.
Yes, you could create a set of diagrams that focus on the aspects of the model that are relevant to each of the key stakeholder groups. These diagrams can contain hyperlinks to relevant diagrams and matrices.
You can also set up your own documents to extract model content and produce a document that pulls together all the material relevant to a particular stakeholder.
The Business Layer of ArchiMate supports both a ‘Business Process’ and a ‘Business Function’ concept. A ‘Business Function’ represents any business competency or area of skill, e.g. Sales. A ‘Business Process’ represents a set of activities carried out to support a product or service, e.g. Make a Sale.
You can decide to split your business behaviour into functions or processes, or even create functions and then further sub-divide each function into a set of processes.
The Business Process Viewpoint is one of the standard ArchiMate diagrams that describes business processes. There is also a Business Function Viewpoint that describes business functions. If it is more helpful to your organisation, you can create a viewpoint that is a combination of both functions and processes.
ArchiMate has its own concepts for modelling data across the enterprise. ‘Business Objects’ in the Business Layer represent conceptual data of interest to business people. ‘Data Objects’ in the Application Layer represent logical data elements that applications create and update. ‘Artifacts’ in the Technology Layer represent the physical storage of data.
An ArchiMate Information Structure Viewpoint diagram shows how all three concepts relate – artifacts that realize data objects which in turn realize business objects. It cuts across all 3 layers of ArchiMate.
Alternatively UML Class diagrams can be used to create data models cross-referenced with your ArchiMate models.
Enterprise Architect does not directly create or show derived relationships.
However, you can explore derived relationships using the Traceability window to walk through the relationships between ArchiMate elements in your model.
Similarly, you can use the ‘Insert Related Elements…’ option on the right-click context menu to create a Traceability diagram, and quickly reveal derived relationships.
You can visit The Open Group website to access resources for ArchiMate:
The Open Group publish an ArchiMate specification which is a very helpful resource:
I would also recommend that you consider a short training course as this is a quick way to get your team up-to-speed with both ArchiMate and Enterprise Architect. Hippo Software offers a range of training courses and workshops that may be of interest:
Yes. There is a Requirements element in the Motivation extension of ArchiMate.
The Goal Realization Viewpoint shows how goals are implemented as a set of requirements and the Requirements Realization Viewpoint allows you to demonstrate how requirements will be implemented as business processes, software applications and/or hardware etc.
There is no specific diagram type for layered viewpoints – you can use a business, application or technology diagram. Simply drag and drop elements from any layer onto the diagram and create relationships between them.
If you want to add new elements from different layers, click on the ‘More tools…’ button at the top of the Toolbox and select the required ArchiMate2 toolbox. To combine toolboxes, right-click on any toolbox page and select ‘Pin in Toolbox’ from the context menu, then open each of the other toolboxes and repeat this procedure.
If you wish to use a matrix or Traceability diagram to show relationships between elements, it is important that your whole team is using the ArchiMate standard consistently, and creating relationships in a consistent and valid direction.
If you have a large team, the best way to reinforce this is by restricting the notation that your team uses to the core ArchiMate elements and relationships, communicating what is expected in a guidelines document, and providing presentations or short training courses to reinforce these standards within your team.
Your governance team can also create scripts to verify that standards are being followed and correct any relationships that have been created in the wrong direction. Hippo Software has a workshop that teaches delegates how to create scripts, or you can refer to the ‘Automation and Scripting’ help topics in Enterprise Architect.
ArchiMate is a fairly straightforward notation to learn (easier than UML). Those wishing to create ArchiMate diagrams in Enterprise Architect will get up-to-speed with a couple of days training.
If you have a large team that is very new to the notation, it can be helpful to limit yourself to using only a few viewpoints – those that you consider to be most helpful for your projects. Focus on producing this subset of viewpoints initially and as the team gets more familiar with the notation, you can start to add additional extra viewpoints where necessary.
Senior management will find it easier to understand diagrams if they are kept simple and elegant. Try to create high-level diagrams for senior managers. Also try to keep the layout and format of these diagrams in a consistent look and feel. It can be helpful to annotate the diagrams. Alternatively, have a team member provide a walkthrough of the diagram.
Most companies create separate Enterprise Architect models for the 'as-is' enterprise architecture and the 'to-be' target architecture. Diagrams and elements can be promoted from the target architecture into the ‘as-is’ architecture as projects implement aspects of the target model.
You can to use the Baseline feature in Enterprise Architect to take a snapshot of the 'as-is' architecture at each significant stage in its development. This allows you to compare differences.
You can copy packages, diagrams and elements between these models (or transfer them using XMI) to provide a start point. For example, you can copy the 'as-is' diagram and then alter it to show the future target vision.
You can automatically add a set of tagged values to elements by creating a Profile. The Profile defines your own stereotype elements and you can associate a set of pre-defined tagged values with these. You can even create your own diagram type and associated toolbox.
Hippo Software has a workshop that teaches delegates how to create Profiles or you can refer to the ‘Extending UML Models’ help topics in Enterprise Architect.