Enterprise Architecture Principles Maps are EA diagrams of high value.
With Dragon1 you generate and create diagrams faster using templates or with the JSON-API. It allows you to focus more on collecting the data and improving the quality of the data. This results in better effective analysis of the data.
Principles of architecture are the most important part of EA.
Architecture is a coherent set of concepts. Principles are the working mechanisms of concepts.
In mainstream EA, architecture principles are often defined as general rules or guidelines. But that is a misconception. Principles should describe the way things work within a context or a system. A principle statement should describe a cause and effect. It helps by starting the principle statement with the word By.
An example of a correct principle is:
You may wonder why it is so important to make a distinction between correct and false principles. The thing is that with correct principles (= working mechanisms) you can do predictions and tests. With false principles (= rules or guidelines) you cannot do that. It is also a best practice not to invent principles and principles statements yourself, but to take them from literature and refer to that.
Read more about enterprise architecture principles here.
You can create a principles diagram like the one above yourself. Just download the .dragon1 example file and replace the demo data with your data. Next you upload the .dragon1 file in the viewer and the diagram is generated.