Skip to end of metadata
Go to start of metadata
  1. Thou shalt always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures
  2. Thou shalt be kept accountable for all architectural decisions
  3. Above all, do no harm
  4. Thou shalt strive to build a learning organization and culture
  5. Thou shalt make consistent and balanced decisions throughout the organization
  6. Thou shalt never default to silver bullets or magic
  7. Thou shalt support and maintain functional and business data building blocks and communicate these to projects
  8. Thou shalt never micromanage project decisions
Architect categorization used here
We use Organizational Architect to classify software architects which are responsible for the organizational context, i.e. across projects and products. These architects are commonly called Chief Architects, Enterprise Architects, Solution Architect, System Architects, Integration Architects or Infrastructure Architects.

We use Project Architect to classify architects who work on a specific project and within a project scope. These architects are commonly called Solution architects, Software architects or Tech leads.

We use Product Architect to classify architects who work on a specific product and within the product lifeline scope. Commonly used names for such architects are: Chief Product Architect, Product Architect, System Architect, Sub-system Architect, Build Architect or Tech leads.

See also Laws for Project Architects

architecture architecture Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. May 25, 2009

    Nice! I like the form of laws or the like. A pattern form is more reactive than proactive, and I think it is not optimal for describing the right set of attitudes and human behavior I would like from an Architect.

    One law I would like too see here is one that captures the way that the Architect communicates her decisions to the ongoing projects. How she should do that very important part of her job, a principle maybe for how to implement changes in organizational architecture decisions, and in such a way that it will not be seen as a burden and an unnecessary evil for the other projects.

    1. May 26, 2009

      Hi Knut.

      That is one of the aspects we try to capture in "Thou shalt strive to build a learning organization and culture."

      Also have a look at

      If you have any suggestion for changed/added law is appreciated.