Enterprise Architecture Dossier

In every organization architecture visualizations are or will be created at one point in time. It is a best practice, to not only make use of a repository to place the visualizations and their objects in for reuse, it is also a best practice to structure the repository for change. The Dragon1 Enterprise Dossier provides a maturity level focused practice for this.

Maturity Level 1

On this level the organization often makes use of architecture in projects, architecture teams create overviews, but there are no architecture working processes or architecture plans yet.

Structure your dossier the following way:

  • Enterprise Processes
  • Enterprise Applications
  • Enterprise IT-Infrastructure Services
  • Principles (Process, Application, Service)
  • Standards (Process, Application, Service)
  • Process Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • Application Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • IT-Infrastructure Services Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • Project Start Architectures

Architecture has a direct effect on everything when you make sure the current and future standards and principles that should be used are known and available to decision makers and projects.

If no use is made of an Enterprise Architecture Tool (modeling tool) or repository, but of drawing tools only, this has the drawback that no dynamic interactive views can be created for stakeholders.

Maturity Level 2 and 3

At this level the organization often makes use of architecture in projects, has architecture teams creating overviews, there are architecture processes and plans, but no owner at strategic level. Architecture not (consistently and continuously) aligned with the strategies or business model

Structure your dossier the following way:

  • Architectures
  • Architecture Plans
  • Architecture Processes
  • Architecture Teams
  • Architecture Products
  • Architecture Services
  • Enterprise Solutions
  • Enterprise Projects
  • Enterprise Functions
  • Enterprise Processes
  • Enterprise Capabilities
  • Enterprise Applications
  • Enterprise IT-Infrastructure Services
  • Principles (Process, Application, Service)
  • Standards (Process, Application, Service)
  • Process Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • Application Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • IT-Infrastructure Services Landscapes (AS-IS, Plateau1, n, TO-BE, Envision)
  • Enterprise and Business Blueprints (AS-IS, Plateau1, n, TO-BE, Envision)
  • Roadmaps
  • Heatmaps
  • Project Start Architectures
  • Concept Designs
  • Principle Diagrams
  • Solution Architectures (AS-IS, TO-BE)

If use is made of an Enterprise Architecture Tool (modeling tool) and repository, instead of only drawing tools, this has the benefits that easily dynamic interactive views can be created for any type of stakeholder. Thus providing them instantly with decision supporting visualization they need.

Maturity Level 4 and 5

Structure your dossier the following way:

  • Strategies
  • Business Models
  • Architectures
  • Plans
  • Processes
  • Teams
  • Products
  • Services
  • Solutions
  • Projects
  • Changes

An Enterprise Architecture Dossier is focused on an era of three to five years and consists of a permanent enterprise & reference part, and a dynamic projects & solutions part.

The EAD contains an Architecture Baseline (the permanent part). It holds the first set of products that always should be created, no matter what.

The permanent part always holds the following products:

  • Enterprise Architecture (EA) Baseline
  • Enterprise Architecture Framework
  • Enterprise Performance Framework
  • ERA and Architecture plateau (Horizon) diagram
  • Enterprise Architecture Description Document
  • Architecture Sketch Book and Architecture Design Book (for EA, GA, BA, IA, TA, SecA and SA) (A3 sized Glossy)
  • Models Atlas
  • Architecture Vision Design Sketch
  • Structure Vision Drawing
  • Concept Design sketch / drawing + maturity view
  • Situation sketch / drawing
  • Principle details sketch /drawing
  • Principles / Patterns / Building Blocks Booklet
  • Stakeholder onion diagram
  • Requirements analyses diagram (including domain, functions and services model)
  • (layered 3d) Enterprise Architecture blueprint (A0-sized poster)
  • Capabilities Map
  • Governance Landscape Diagram
  • Business Landscape Diagram
  • Process Landscape Diagram (A0-sized poster)
  • Application Landscape Diagram (A0-sized poster)
  • Integral Solution Architecture, Design & Realization Landscape Diagram (A0-sized poster)
  • IT Infrastructure Blueprint (A0-sized poster) + report view
  • Technology Roadmap (A0-sized poster)
  • Enterprise Transformation Roadmap (A0-sized poster)
  • Architecture Principles Document
  • Storyboard, User Story, Migration Scenario Diagram & Animation
  • Glossary of Terms document
  • Architecture Team Working Schema
  • QAA-list
  • IAD-list