Linked.Archi

Linked.Archi ArchiMate 4.0 Deliverable Templates

Deliverable Templates

https://meta.linked.archi/archimate4/deliverable-templates#

Kalin Maldzhanski

Deliverable template definitions for generating architecture documents from ArchiMate 4.0 models: each section answers the concerns it names by asking model questions of the model.

Architecture Definition Document

The primary ArchiMate 4.0 deliverable documenting the target architecture across business, application, and technology domains, and answering for each domain the concerns its viewpoint frames.

Required Viewpoints: OrganizationViewpoint ProcessCooperationViewpoint ApplicationStructureViewpoint TechnologyViewpoint LayeredViewpoint ImplementationAndDeploymentViewpoint ImplementationAndMigrationViewpoint
Target Purposes: Designing, Informing
Available Formats: MarkdownFormat, HTMLFormat, PDFFormat
Produced for: ?model

Sections

1 1. Business Domain
Who are the actors and roles, and who is responsible for what?
Viewpoint: OrganizationViewpoint Result key: businessDomain
Concerns: CompetenciesAuthorityResponsibilities
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. Who is responsible for what?
2 2. Process Cooperation
How do processes cooperate, is each performed by someone, and is every service delivered?
Viewpoint: ProcessCooperationViewpoint Result key: processCooperation
Concerns: Completeness ProcessDependencies Responsibilities
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. Which processes and functions has nobody been assigned to?
  3. Which services does nothing realise?
3 3. Application Domain
Which applications are there, how do they depend on each other, and who reads and writes which data?
Viewpoint: ApplicationStructureViewpoint Result key: applicationDomain
Concerns: ApplicationDependencies ApplicationStructure InformationStructure
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. Which applications depend on which?
  3. Who reads and writes which information?
  4. Which information is read but never written?
4 4. Technology Domain
What infrastructure is there, and does every application run on some of it?
Viewpoint: TechnologyViewpoint Result key: technologyDomain
Concerns: ApplicationPlatforms InfrastructureQuality
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. Which application components run on no technology?
5 5. Cross-Domain Overview
How do the domains connect, and where would a change propagate across them?
Viewpoint: LayeredViewpoint Result key: crossDomainOverview
Concerns: Consistency ImpactOfChange ReductionOfComplexity
Asks:
  1. How is the model spread over the ArchiMate domains?
  2. Which relationships cross domains, and of which kind?
6 6. Implementation & Deployment
Which artifacts realise which applications, and where are they deployed?
Viewpoint: ImplementationAndDeploymentViewpoint Result key: implementationDeployment
Concerns: ApplicationPlatforms
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
7 7. Realisation Roadmap
Which work packages deliver this architecture, and what does each deliverable realise?
Viewpoint: ImplementationAndMigrationViewpoint Result key: roadmap
Concerns: ArchitectureVision
Asks:
  1. What does each work package deliver, and what does that realise?
8 Appendix. Quality of this Description
Can the reader rely on this document as a complete, consistent description?
Result key: quality
Concerns: Completeness Consistency QualityConcern
Asks:
  1. Which elements does their view's viewpoint not admit?
  2. Which elements appear in no view?
  3. Which elements take part in no relationship?
  4. Which elements have no definition?
  5. Which elements share a name with another of the same type?
  6. Which relationships are out of step with their direct triple?

Architecture Requirements Specification

Documents who the architecture is for, what they want to achieve, and the requirements that follow — and whether each requirement is traced to the design that meets it.

Required Viewpoints: StakeholderViewpoint GoalRealizationViewpoint RequirementsRealizationViewpoint MotivationViewpoint
Target Purposes: Deciding
Available Formats: MarkdownFormat, PDFFormat
Produced for: ?model

Sections

1 1. Stakeholders and Drivers
Who has a stake, and what drives and concerns them?
Viewpoint: StakeholderViewpoint Result key: stakeholders
Concerns: ArchitectureMission Motivation
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. What do stakeholders care about?
2 2. Goals and Outcomes
What do we want to achieve, and how do goals refine into outcomes and requirements?
Viewpoint: GoalRealizationViewpoint Result key: goals
Concerns: ArchitectureStrategy
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
3 3. Requirements and their Realisation
Which requirements are there, what meets each one, and which are not yet met by any design element?
Viewpoint: RequirementsRealizationViewpoint Result key: requirements
Concerns: ArchitectureTactics Completeness
Asks:
  1. How does each requirement trace to goals and to the elements that realise it?
  2. Which requirements does no architecture element realise?

Architecture Principles Document

Documents the architecture principles, what motivates each, how they are made concrete as requirements, and how the strategy they serve is realised.

Required Viewpoints: MotivationViewpoint StrategyViewpoint CapabilityMapViewpoint
Target Purposes: Governing
Available Formats: MarkdownFormat, PDFFormat
Produced for: ?model

Sections

1 1. Principles
Which principles govern the architecture, why, and which have been made concrete?
Viewpoint: MotivationViewpoint Result key: principles
Concerns: ArchitecturePolicies Motivation
Asks:
  1. What motivates each principle, and what does it constrain?
  2. Which principles has no requirement made concrete?
2 2. Strategy Alignment
Which capabilities does the strategy need, and is each one realised?
Viewpoint: CapabilityMapViewpoint Result key: strategy
Concerns: ArchitectureStrategy StrategyDevelopment
Asks:
  1. What in the model belongs in a view of this ArchiMate viewpoint?
  2. What realises each capability?
  3. Which capabilities does nothing realise?

Change Impact Assessment (ArchiMate 4.0)

Assesses a proposed change to one element: what depends on it, which views must be updated, and — where baseline and target plateaus are given — what the change adds and removes.

Required Viewpoints: LayeredViewpoint MigrationViewpoint
Target Purposes: Deciding, Governing
Available Formats: MarkdownFormat, PDFFormat, SlideFormat
Produced for: ?model ?focus ?from (optional) ?to (optional)

Sections

1 1. What Depends on the Element
What is related to the element, and what is affected if it changes?
Viewpoint: LayeredViewpoint Result key: impact
Concerns: Dependencies ImpactOfChange
Asks:
  1. What is this element directly related to?
  2. What is affected if this element changes?
2 2. Views to Update
Which views present the element and will need revising?
Result key: views
Concerns: GovernanceConcern
Asks:
  1. Which views show this element?
3 3. Baseline to Target
What does the target add and remove against the baseline?
Viewpoint: MigrationViewpoint Result key: migration
Concerns: ModelHistory
Asks:
  1. What changes between these two plateaus?
Source: linked-archi-meta • Linked.Archi