Create an Architecture Principle

Dragon1 supports you in creating and editing concept principles and architecture principles.

A principle is defined in the Dragon1 open EA method as: a working mechanism of a concept.

A principle consists of collaborating elements of a concept.

To create an architecture principle, do the following:

Create a concept entity
Create concept elements. At least seven key elements.
Create a principle entity
Write a principle description that describes how the element collaborates and produces results.
Have every element mentioned in the description.
Link the concept or principle to an architecture entity.
Your concept principle is an architecture principle, and we can measure if it is implemented completely.

Example Architecture Principles

The example use case FSwin-USA uses the following architecture principles:

Trained workers perform better
The client is always right
A process always has input and output
A process always has an owner
Clouds scale better than physical networks
Firewall increases the security of the network
Optimistic locking is better than pessimistic locking for high-volume transactions

Each of the principles is made measurable as working mechanisms.

That is done by defining the key elements of concepts that need to be in place and collaborating for the principles.

In the use case FSwin-USA, you can check the queries and rules for the principles.

The statement/description of the principle, naming the key concept elements is: by having [actors] trained in the [tasks] they execute, their [performance] is increased.

The query definition/rule condition of the principle "trained workers perform better" looks like this: actor.training related to actor.tasks = 0 The rule action of the principle is actor.performance = 0.

The query definition/rule condition of the principle "trained workers perform better" looks like this: actor.training related to actor.tasks > 10 The rule action of the principle is actor.performance = 100.