Architecture Requirement

From OIAr Archive 2013
Revision as of 12:19, 3 March 2013 by Jan Schoonderbeek (talk | contribs) (new)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Architecture Requirement
Architecture Requirement

An Architecture Requirement is a guideline that is used to influence the way (part of) an infrastructure facility will be realized. Thus, Architecture Requirements form an integral part of the documentation that the infrastructure architect hands over to the infrastructure designer.

Architecture Requirements can be associated with both Pattern Variants and Building Blocks). Within the OIAm method, it's possible to declare an Architecture Requirement to be:

  • mandatory: this dictates how the facility is going to be realized;
  • encouraged: this only advises the designer;
  • discouraged: it's possible to steer the designer away from certain solutions, e.g. when a technology is declared deprecated;
  • forbidden: can be used to phase out the implementation of certain guidelines, technologies etcetera.


0 Architecture Requirements are currently present in this Wiki, and (up to 100 Architecture Requirements) can be found in the table below.

Architecture Requirement type(s) Owner Maturity