This task reviews important decisions having architectural significance, resulting in Approval, Rejection or Revision.
Purpose
The purpose of this activity is to review an architectural decision. Documenting important architectural decisions provides
a repository of decision that will help guide other architects, managers and implementors in being compliant with
enterprise and business domain standards and solutions. They also provide a source of information for re-visiting decisions
over time.
The purpose of this activity is to review an Architecture Decision (AD), specifically to:
Review the context and description;
Examine the stated constraints;
Review the rational;
Review the implications;
Evaluate the decisions using one or more specific architectural aspects: performance, reliability,
implementability, modifiability, cost, security, safety;
Approve, reject or require revision of the AD.
Steps
Review the Context
The context is reviewed to ensure it is complete and well-defined. It is also examined to ensured that the AD does not
overlap or replace an existing AD (in which case it would be rejected and the originator told to revise the existing AD).
Examine the Constraints
The constraints are reviewed to ensure they are complete and well-defined. They are also examined to ensure that they are
valid and required; they are useful and serve a purpose.
Review the Rationale
The rationale supporting the stated decision is reviewed to ensure it is complete and well-defined. It is also placed into
the context of existing ADs to ensure that there is no conflict. The logic is also reviewed.
Review the Implications
The implications of the stated decision are reviewed to ensure they are complete and well-defined. The implications are
also placed into the context of existing ADs to ensure that there are no conflicts or gaps.
Ealuate the Decision
The decision described in the AD is reviewed to ensure it is complete and well-defined. It is also placed into the context
of existing ADs to ensure that there is no conflict. Other aspects may be further examined (e.g. cost) and clarified in
support of making a decision on the AD.
Approve, Reject or Revise
The AD is either approved, rejected or sent back to the author for
revision (with advice).
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
Usage Guidance
The AD is deemed to be a business domain-level decision, therefore this review group will approve/reject the decision.
Typically this group is lead/managed by the Domain IT Architect office.
