Create Atlas Help Page

Dragon1 supports creating Atlases.

What is an Atlas?

An Atlas or iAtlas is a set of pages with interactive visualizations on it.

With an atlas you provide stakeholders with a set of up-to-date and decision-supporting visualizations.

Important to note is that with this you reuse visualizations you have already created on Dragon1. By providing a set of visualizations, you create more context for the stakeholders/viewers, so they can do more with the information on the visualizations.

An atlas page can also contain a video, a document page, a HTML page, a graph or a clickable list of data.

Instead of creating an atlas, one can also publish a repository (a part of or a whole Cabinet). An atlas is different from a repository, as an atlas is a set of pages with references to data and a repository is the data itself.

dragon1 atlas example

Steps to Creating a Dragon1 Atlas

To create an atlas:

  • Create several visualizations, static or dynamic
  • Go to the Architecture Repository
  • Open a Cabinet
  • Select a Folder
  • Insert an Atlas entity
  • Insert several Atlas Page entities
  • Link the Atlas Page entities to the Atlas entity via the Atlas attribute in the form
  • Place the id of a visualization in the reference field of the Atlas Page
  • Make sure the page is published (normally you keep the template pages unpublished).
  • Make sure the Atlas entity is published and have a picture, so it show up nicely in the Content Viewer overview or in the Search.
dragon1 repository atlas example

Working with Templates Pages

You can make use of template pages. For instance, if you want to apply a certain color scheme, page layout, default objects or logo on every page.

Leaving Comments

Dragon1 support creating textitems like comments, annotations, decisions and measures.

Ideas for Atlases

There are seven common applications for a Dragon1 Atlas:

  • Project Dossier: informing stakeholders about the situation in and progress of a project. For instance, how they should make use of architecture.
  • Solution Design Book: communicating the design of a solution in an interactive way.
  • Cyber Security Dossier: communicating the status and progress on cyber security.
  • GDPR Compliance Dossier: communicating the level of compliance with GDRP.
  • Architecture Design Book: communicating the architecture of a domain or a solution.
  • Architecture Dossier: providing an introduction and or overview of an architecture using often about 20 highlights.
  • Tutorial / Training Module: providing an interactive explanation of a topic with a tree of questions and answers.
  • Application Migration Report & Dashboard: communicating and updating stakeholders on progress made in migrating applications, for instance, to the cloud.

About the Example Atlas

Visit the example Dragon1 Atlas here.

The example Atlas shows three parts or stages: Strategy, Architecture and Transformation.

The idea is that an organization first has stakeholders that require changes to the company because of the strategy and new business model.

The architects create this part of the atlas first and in iterations and in interaction with the stakeholders.

Next, they design the architecture in line with the strategy and business model and also interactively with the stakeholders in iterations.Also, a process diagram is used here to communicate how people can make effective use of architecture artifacts (products).

Finally, the architects add information that shows how the projects could or should make use of the principles and standards coming from the architectures.

Note: you can have any page structure you like in the Atlas.

Ideas for Pages

Below follows a list of ideas for pages:

  • Glossary page
  • Login page
  • Using slide in effects on pages to build a story
  • Using mouse over sound to make the visualization more exciting
  • Term page
  • Concept page
  • Design Decisions page
  • Requirements pages