|
The purpose is to ensure that there is cohesion and agreement in the models, from the architecture perspective and get
agreement from stakeholders. And to also generally improve the quality of the architecture and the architects through
the provision of feedback.
Once an IT architecture perspective is completed, two types of reviews are undertaken:
-
A peer review of the results is done prior to moving on to next steps, which focuses on the
consistency, completeness and cohesiveness of the architecture. This review is done at the end of the development
of the perspective, for example: Milestone: Business Perspective Milestone.
-
A second phase, the stakeholder review described here, focuses on the content of the architecture in terms
of how accurately it captures the business, which normally involves a number of stakeholders that have intimate
knowledge of the area of the business in question, and at the correct level, namely Business, Logical or
Technical. This is the final "approval" step for the IT architecture perspective.
These reviews document deficiencies, errors and omissions in a "Review Record", which the architect then actions (i.e.,
models etc. are updated or changed as needed). The recommended next steps are also identified for later approval and
action.
|
