Principle

From Dragon1 | wiki
Jump to: navigation, search

-under construction until 1 november 2013-

Contents

Introduction of Principles

This page contains examples of principles to get started formulating principles compliant to Dragon1.

The Dragon1 theory for principles and architecture principles is unique and new and differs from mainstream EA, but is much more effective than mainstream EA theories on principles (i.e. guiding statements).

In Dragon1 a principle is defined as: The enforced way an entity works in a context producing results.

Principles are the most important concept of architecture, so it is very important to get them right and at least formulate them right.

And know that an unproven or untested principle in fact is a hypothesis, so always a literature reference or test is needed before it may be used in practice.

Once you get hold of the feeling, you will see there is really nothing to it, formulating principles compliant to Dragon1.

Often guiding statements are labeled as principles. This is not a good practice, because not every guiding statement states an enforced way of working or the results produced.

On this page we give also some example of wrongly formulated principles and a technically correct version of it.

Basic Rules for formulating principles compliant to Dragon1

  1. Name the concept or phenomenon (these are two types of entities) for which you are writing down the way of working for (i.e. principles)
  2. Name the principle that you are stating within that concept. What part of the concept are you stating? If you name a principle that covers the whole concept it is called the first principle of the concept.
  3. Be sure to enclose three parts in your formulation. A Dragon1-syntax for human-oriented principles is: By ...[action]... you will...[usage]... so ...[effect]...
  4. For documentation purposes it is advised to give every principle a unique (meaningless) identifier, a name, title and type.
  5. For effective commonication purposes try to find or create a picture showing exactly what is stated in the short statement
  6. Do not mix derived design rules or policies with the principle itself. It is obvious you need policies and rules to take the principle in to account once you know of the princple. But rules and policies are not part of the principle!

The more fundament Dragon1-principle syntax for the short statement of the principle is: By ...[action]...From...[enforcement]... it is ensured...[usage]... so ...[effect]....

In this more fundamental syntax the fourth part introduced is the explicit mentioning of an enforcement mechanism. It is to make sure 'always' in the principle really is 'always'.

Example principles of survival

Below are six reformulated example principles of survival that were stated unformatted on http://azbw.com/Five_Principles_Of_Survival.php

This information is only used for practicing formulation of principles. For people who actually practice survival should not use the information on this Dragon1 wiki page.

Name of the concept: SURVIVAL

Survival Principle 1: the first principle of survival

About Principle 1: Prepare yourself for weather conditions and you will survive!
  • Principe ID: SP01
  • Name of principle 1: the principle of Survival
  • Principle Type : human concept principle
  • Catchy Principle Title: Preparation will make you survive danger
  • Principle Short statement: By always being sufficiently prepared to deal with the most common unexpected and hazardous situations you will certainly be able to stay alive long enough (72 hours) to be found by search and rescue teams, so you will live.
  • Status: Hypothesis or Proven Principle ?
  • Literature references: SAS survival Handboek, http://www.survivaltopics.com
  • Example guiding statements (derived rules and policies) not to be confused with principles : 1) Prepare yourself when going on a survival, 2) We always prepare ourselves

Survival Principle 2: the principle of Preparation

About Principle 2: Pack your bag with the right stuff!
  • Principe ID: SP02
  • Name of principle 2: the principle of Preparation
  • Principle Type : tbd
  • Catchy Title: tbd
  • Short statement: By practicing a lot, staying fit, healthy, taking time to assemble outfit and gear and do thorough rsearch your journey it is ensured you are prepared physical and mentally so you will be able to handle survival situation better.
  • Status: Hypothesis or Proven Principle ?
  • Literature reference: Survival Preparedness, http://www.survivalfood.com/guardian-1-person-essentials-backpack-survival-kit/

Survival Principle 3: the principle of Fear Management

About Principle 3: Keep thinking straight!
  • Principe ID: SP03
  • Name of principle 3: the principle of Fear Management
  • Principle Type : tbd
  • Catchy Title: tbd
  • Short statement: By always keep thinking rationally but also follow your instinct from training and experience you will avoid making fatal choices so you will live and wont die because of exposure.
  • Status: Hypothesis or Proven Principle ?
  • Literature reference: tbd

Survival Principle 4: the principle of Hydration

About Principle 4: Having drinkable water keeps you going!
  • Principe ID: SP04
  • Name of principle 4: the principle of Hydration
  • Principle Type : tbd
  • Catchy Title: tbd
  • Short statement: By always drinking water regularly from the availability of drinkable water it is ensured your body receives the necessary minerals and your body tempature won't increase, you can keep concentrating, you won't have cramps, chills, nausea, rapid pulse, headaches, dizziness, stomach cramps so will making the right decisions on your survival journey.

Survival Principle 5: the principle of Body Core Management

About Principle 5: Take time to relax, enjoy and eat!
  • Principe ID: SP05
  • Name of principle 5: the principle of Body Core Management
  • Principle Type : tbd
  • Catchy Title: tbd
  • Short statement: By exercising, eating, drinking, resting, sleeping and relaxing regulary you will keep all your core body in a good condition and prevent having depressive thoughts so will be able to handle you survival situation better.
  • Status: Hypothesis or Proven Principle ?
  • Literature reference: tbd

Survival Principle 6: the principle of How to be Found

About Principle 6: Always wear orange clothing and have a signaling device!
  • Name of principle 6: the principle of How to be Found
  • Principle Type : tbd
  • Catchy Title: tbd
  • Short statement: By always (anytime and everywhere) carrying an electronic signaling device and illuminating clothing and letting people know when and where you are from training, experience, club-rules and insurance-rules it is ensured that search and rescue teams find you quickly enough in case of emergency so you will outlive your event.
  • Status: Hypothesis or Proven Principle ?
  • Literature reference: tbd

Survival Principle references

Survival












Example principles of public transport

Below are some common guiding public transport statement often wrongly labeled as principles:

  • guiding statement, labelled as principle: People choose rail travel because it is convenient, easy and flexible.

Rewritten as Dragon1 compliant principle: to do...

  • Rail booking is only one part of people's larger travel process

Rewritten as Dragon1 compliant principle: to do...

  • People build their travel plans over time.

Rewritten as Dragon1 compliant principle: to do...

  • People value service that is respectful, effective and personal.

Rewritten as Dragon1 compliant principle: to do...

How Important are Principles?

Principles are the most important things for an architect.

A principle is the enforced way an entity works in a context producing certain results.

An entity is a whole or a thing that has seperate and distinct existence and can be identified or characterized by or through its combination of attributes. (the principle of a dieselengine, the espresso machine principle, the service-principle, the principle of re-use, etc..)

The architecture of a structure is the coherent set of constructive, operative and decorative concepts of a structure. (Dragon1: http://wiki.dragon1.org/index.php?title=Architecture)

Concepts are a type of entity.

So the challenge for an architect is to select the right concepts in order to create the architecture. And he uses the concept-principles as argument for that.

A concept, for instance the concept 'self service', has a principle, the concept-principle, telling us the way this concept work and produces results.

The enterprise architect uses the concept-principle as argument to select the concept as part of architecture because the results this concept produces fits the needs, concerns, goals and requirements of the enterprise stakeholders.

So depending on the goals and requirements of stakeholders an enterprise architect may propose the owner/client (CEO) of the enterprise to make self service as a concept part of the enterprise architecture.

An architecture principle is a principle of concept that was made part of the architecture.

Summary

This page shows the fundamentals on formulating principles

Use this information about principles to study your enterprise architecture principles. What concepts and phenomena do you have in your organization? How would you reformulate the principles in your organization?

Feedback

Any feeback on this example page of formulating principles is welcome. Send to remarks to mark@paauwe.info


References

Also read: