|
Architectural Decisions consulted
| Ensure that all relevant Architectural Decisions have been addressed by the IT Architecture (artifact) under review. Add
actions as necessary to correct omissions. |
Similar solutions have been considered
| Reinventing the wheel Issues are flagged and actions defined to correct them. |
Consistent level of abstraction
The models should have a similar level of complexity and a consistent level of abstraction (but perhaps
tempered by the objectives of the IT Architecture). This is a relative evaluation, therefore as always when creating an
architecture the level of complexity and detail required is always a judgment call. The level required should be driven
by the intended use for the IT architecture. The level of abstraction for a give level of detail must however be
consistent. Issues are flagged and actions defined to correct them.
|
Components in the models are highly cohesive
| One of the main objectives in doing IT architecture is to define the overall structure of the "system". The components that
define this structure must be cohesive, which is enabled by having clear separations of concerns in the model
and in having clear relationships between components. Issues are flagged and actions defined to correct them. |
The proposed solution can be easily understood
| Clear understanding of the IT architecture is greatly facilitated through the use of standard domain 'language' in the
models (which may need to be clarified in order to be more precise). Visual models are also an aid to understanding.
Complexity (in models and descriptions) can be reduced through the layering of the models (i.e. encapsulation to hide
detail). This peer review (and other reviews) also facilitate and aid in documenting architectures in a manner and language
understandable by all, and consistent across the enterprise. Issues are flagged and actions defined to correct them. |
There is consensus on the model as presented by the architect
| Stakeholders should all share the same view—this is where getting consensus on the language and other aspects is very
important. This IT architecture review is where to get feedback and to develop a solid consensus and understanding. |
Modeling guidelines have been followed
| Presenting a consistent set of views and structures aids in understanding, eases maintenance of the models, and generally
speeds up the process. These modeling guidelines and standards are either from UAM or defined and used within the
enterprise. |
Models are not overly complex
| Given the objectives of the IT architecture, the models developed should be only as complex as needed. Overly complex model
will not add value, will be more difficult to maintain and take longer to develop. |
Number of model layers defined
-
There are no more than seven (plus or minus two) layers;
-
The rationale for layer definition is clearly presented and consistently applied;
-
Layer boundaries are respected within the architecture;
-
Layers are used to encapsulate conceptual boundaries between different kinds of services and provide useful
abstractions which makes the design easier to understand.
|
|
