Step by step plan architecture

Introducing an architecture process based on an architecture repository is actually an organizational change. It consists of a number of sequential activities. These sequential activities are generic in this document, but can easily be adapted and expanded to your own context. This step-by-step plan describes a number of steps that you can follow to approach the introduction of an architecture repository in a structured manner. The chapter on tools for introducing an architecture repository explains a number of supporting concepts and methods later in this document. This diagram details the various steps (with underlying diagrams) to arrive at a working method for an architecture repository.

Diagram in standard mode

Relate goals to assessments

Assessments can be linked based on goals, making the achievement of goals measurable.


Details van Relate goals to assessments

Determine relevant parts repository

Determine functionalities, components and modules in the architecture repository relevant to the organization.


Details van Determine relevant parts repository

Describe baseline and target

What is the baseline (document-oriented architecture) and the target (architecture repository).


Details van Describe baseline and target

SWOT analysis

Using ArchiMate Assessments, determine which tests determine whether the goals will be achieved during implementation.


Details van SWOT analysis

Determine stakeholders

We have interests and concerns surrounding the use of an architecture repository.


Details van Determine stakeholders

Determine roles

Which business roles are involved in the introduction of the architecture repository and its future use in the organization.


Details van Determine roles

Set goals

Update the list of goals to be achieved by introducing working with an Architecture repository.


Details van Set goals

Determine requirements

Generic and specific requirements when deploying an architecture repository in the organization.


Details van Determine requirements

Relate requirements and goals

Make connections between requirements and goals.


Details van Relate requirements and goals

Select modeling languages

Which modeling languages are relevant within the field of your own organization.


Details van Select modeling languages

Determine work processes

Work processes supported by an architecture repository.


Details van Determine work processes

Create SIPOCs (optional)

Drawing up SIPOC for the various work processes.


Details van Create SIPOCs (optional)

Analyze required application functions

What are the relevant application functions to support the stated work processes. These can then be linked to modules in the architecture tool or to requirements (during a selection process).


Details van Analyze required application functions

Define architectural domains

Which architectural domains are important within the organization.


Details van Define architectural domains

Determine tool design

This is a process that consists of a number of sub-steps to organize the chosen tool in such a way that modelers can easily work in it and other stakeholders can easily find the material relevant to them.


Details van Determine tool design

Determine repository tool choice

There are several tools on the market for repositories. A small overview in this repository.


Details van Determine repository tool choice