Dragon1 Open Standard Architecture Visualization

From Dragon1 | wiki
Jump to: navigation, search

This is Dragon1 Wiki page. http://wiki.dragon1.org



Dragon1 maakt betreffende visualisaties verschil tussen A) metamodellen, B) modellen, C) aanzichten (views), D) perspectieven (perspectives) en E) soorten visualisaties.

Door dit verschil te maken heeft de architect de maximale controle over het presenteren van architectuur en structuur van bouwwerken en solution in op de belanghebbende afgestemde visualisaties.

Een voorbeeld waarbij het kunnen maken van het verschil van toepassing is, is bijvoorbeeld:

  1. het maken van een ontwerpschets van het toekomstige business model 'Customer-Intelligence-Is-Key' van een organisatie voor investeerders waarbij in het business model alle gegevens van alle klanten voor alle medewerkers overal en altijd beschikbaar zijn zodat ze meer en beter de klanten kunnen bedienen.
  2. het maken van een toekomstige ICT-view op hetzelfde businessmodel voor ICT-engineers om te zien waar systemen aan elkaar gekoppeld dienen te worden zodat ook daadwerkelijk de informatie overal en altijd voor iedereen up-to-date beschikbaar is.

De open standaard Architecture Visualization Standard zet uit een wat de generieke soorten modellen, aanzichten, perspectieven en visualisaties zijn die Dragon1 onderkend en hoe deze in praktische zin zijn te maken. Daarbij wordt ook aandacht besteedt aan hoe van een model een aanzicht is te maken.

Glossary of Terms

Main Concept and Principle

Overview of Concepts and Principles


In organization there are certain stakeholders of innovations and solution that need to look at architecture visualizations and take decision based on what they see. These people we call viewers. The alway have certain (types of) concerns, jobs, interest, need and requirements.

If you now the type of viewer you create the visualization for, make sure you align the visualization (color, words, composition) to the information needs and knowledge the viewers has. What does he or she look at and what do they see? What are they looking for? What do they (don't) want to see?

Common types of viewers in organizations are stakeholders of innovations and solutions like: owner/clients, contractor, managers, workers, projectmanagers, engineers, employees and enterprise clients/customers.


Viewers look at visualization from a certain point of view.

Common types of viewpoints are functional area in the organization: A management point view, A financial point of view, A strategic point view


A view is what a viewer sees looking at a visualization from a certain point of view.

Common types of process/activity oriented views are:

  • design view
  • analysis view
  • management view
  • maintenance view

Common types of subject oriented views are:

  • overview
  • default view
  • environment view
  • structure view
  • architecture view
  • financial view
  • business view
  • strategic view

a view often has a process or activity name in it or the subject one is looking at.

A manager (the viewer) can look from financial point of view (the viewpoint) at the AS-IS business view of the enterprise. Because the manager has interest in standardization he sees where activities and processes are and are not compliant with standards. This you will only see if you have knowledge on standardization. This example is only to show you that what see in a view depends on what you now and what your looking at (because of that).

A default view of a model or situation is the entity relationship view of a model or situation.

Other types of standard views are:

  • (structure / architecture) framework
  • (structure / architecture) vision
  • (structure / architecture) landscape
  • (structure / architecture) blueprint
  • artist impression
  • situation sketch
  • design sketch
  • concept sketch
  • principle (detail) drawing
  • use case (UML)
  • mindmap
  • experience map
  • roadmap
  • entity relationship diagram


A perspective is a combination of views. Often the views or models have to be altered slightly to have then fit in one perspective. For instance for a consistent financial analysis perspective or information system design perspective on processes and applications.


Common types of viusalizations are:

  • Sketch
  • Drawing
  • Cartoon
  • Diagram (Schema)
  • Photographic image (Photo)
  • Mental Image
  • Infographic

Reference Models

Rules and Guidelines

  • Always distinct between two types of visualizations: 1) first a global-overview-visualisation and (context)definition a whole and 2) second in depth detail visualisation and definition of parts of the whole that are in need of control (at design times and realization times). And this is iterated into a depth of one to ten times. (Underlying Principle: By doing this it is more clear for every what is part of the whole and what is not (f.i. in financial and legal terms) and that all the parts are recognized early enough and correct and when parts are developed independently the parts will work better and have possible maximal coherence and minimal dependency (no gaps or overlaps).
  • Everyone knows that a certain smell or sound can bring back those memories of the good old days. There are so many ways to communicate effectively as architect next to creating drawing and illustrations. If you are an architect, but not able to communicate visually, than what you can do is mental imaging, use the technique of story stelling or work with LEGO to create macquettes. Visualizations are meant to create sphere, emotions, feelings and experience in order to have a stakeholder take a decisions. If someone closes their eyes and their senses of hearing, smelling and touching are stimulated the right way you can create the same effect as with showing a visualization.
  • In marketing we have this principle/wisdom: If you what you want to tell the public, you also know how you are going to tell it to the public. If you as architect know WHAT to you want to tell to a certain type of stakeholder and WHY you want to tell it, then immediately from that follows HOW you can tell it at best. And suppose a nice visual is needed and there is a budget of $100, you can always call a graphic designer to create something for you based on a description you have send.

Example Products (Documents and Visualizations)


Document Templates