Generative AI Recipes

You can combine ArchiMate elements in a hierarchy to produce a large diversity of views.

The View Recipes section describes what ArchiMate elements can be combined to create useful views.

The Deliverable Recipes section describes common deliverables and how to create each view.

View Recipes

The notation “Driver > Goal” means the first level of the diagram is Drivers, and under each Driver are goals that can be used to address each Driver.

The “* > Resources” notation signifies that any element (represented by “*”) can be at the top of the diagram, with “Resources” listed beneath as supporting elements.

For example, if the top-level element is a “Capability”, “Business Function”, or “Product”, the “Resources” below would be those needed to support it.

You can also start a diagram without a specific top-level element. In that case, you might create a “Resources” view, representing all the resources required for your overall context or scenario.

See ArchiMate Elements for an explanation of all elements, not all listed in the table below. The items below are a small subset of the overall set of possibilities.

RecipeDescription
Capability“What are the fundamental abilities of our organization that enable us to execute our business strategy?”
It can also have other element types as child elements. Examples of having other element types underpinning the capabilities
– Resource – shows what resources are required to support a capability
– Course of Action – shows the strategic actions needed to build a capability.
Driver > Goal“What are the primary motivations (drivers) that are directing our business goals?”
“What goals are we trying to achieve in response to each specific driver?”
Assessment“What is the risk posture for the initiative?”
How To: Initial Risk Assessment
Business Actor > Product“Who is the market for my services (business actor), and what products are they interested in purchasing (product)?”
A market segmentation view defines the types of businesses that might buy your product, under which are the product variations they might buy.
Use the prompt “What types of businesses might buy <service>?”, e.g. advertising services, since otherwise, the default behaviour might be to list business actors that perform a role in your business/domain.
* > Goal“What are the goals to achieve [*]”
Stakeholder > Driver“What are the key factors or conditions (drivers) influencing our stakeholders?”
* > Value“What is the value produced out of [*]?”
* > Work Package“What logical application services are needed to support [*]?”
where * could for example be a business function, or capability.
* > Application Service“What are the logical application services needed to support [*]?”
where * could for example be a business function, or capability.
* > Requirement“What are the requirements for [*]?”
where * could for example be an application function, business function, capability, goal, or a range of other element types.
* > Business Event“What are the business events that can occur in relation to *?”
where * could be a business function, business actor, capability, or range of other elements.
Business Service > Application Service“How do our application services support and enable the delivery of our business services?”
Business Function > Business Object“How does each Business Function in our organization interact with and add value to our Business Objects?”
Business Actor > Business Function“How do our Business Actors perform the various Business Functions?”
* > Technology Service“What are the technology services needed to support [*]?”
where * could be a capability, application function, application service, or range of other elements.
* > Equipment“What equipment is needed to support [*]?”
where * could be a capability, business function, business service, application service, or range of other elements.
Business Process > Business Function > Requirement“What is the decomposition of a Business Process into its constituent steps?”
“For each Business Function, what are the requirements?”
ContractUse the prompt “What contract types are required to run the business?” to get a list of contact types.
* > Principle“What fundamental rules or guidelines does [*] follow?”

You might find these standard views helpful when using the AIM generative AI features to create architecture views.

Deliverable Recipes

Project Charter

1. Identify the Project Vision: Before you get into the nitty-gritty, you should have a clear vision for the project. This includes understanding the project’s purpose, objectives, and the value it will bring to the organization or stakeholders.

ArchiMate elements: Goals

2. Define the Project Scope: This includes defining what is included and excluded from the project. This involves listing deliverables, specifying the geographical area, time period, processes, technologies, etc.

ArchiMate elements: Business Processes, Logical Application Services or Technology Services

3. Identify Stakeholders: Identify the people, groups, or organizations that will have an interest or role in your project. This includes the project sponsor, team members, beneficiaries, and possibly others within or outside your organization.

ArchiMate elements: Stakeholders, Drivers, Goals

4. Define Project Objectives and Success Criteria: Define what needs to be accomplished and how success will be measured. This could be in terms of specific metrics, deliverables, or outcomes.

ArchiMate elements: Goal, Requirements

5. Define Project Milestones and Timeline: This includes major activities or deliverables and when they are expected to be completed. A high-level project schedule could be included.

ArchiMate elements: Course Of Actions

6. Identify Risks and Issues: This includes both potential risks and known issues that might impact the project’s success. Also consider mitigation strategies for each risk.

ArchiMate elements: Assessmente

7. Detail Project Budget: This includes an estimated cost for the project. The budget might not be finalized at the time of the project charter, but an estimate should be included.

ArchiMate elements: Resourcee

8. Designate the Project Team: This includes who will be involved in the project, their roles, and responsibilities.

ArchiMate elements: Business Actore

9. Define the Project Structure: This includes how the project will be managed, such as project governance, communication plan, change management plan, etc.

ArchiMate elements: Business Actore, Business Functione

10. Project Approvals: The project charter should be signed off on by key stakeholders, such as the project sponsor and key team members.

ArchiMate elements: Stakeholders