This activity is focused on organizing and doing reviews of the Business, Logical or Technical Perspective of the IT architecture. Appropriate materials are gathered, venues booked and participants informed.

The IT architecture review is done in two phases, the first focuses on the generated architecture, ensuring that it is complete and consistent, which is normally an IT architect peer review. Typically, once an architecture view is completed, this peer review is done prior to moving on to next steps; this is, therefore, the last step in finalizing a view within the Perspective (i.e. a set of models, the process models for example). See for example: Activity: Define Logical Perspective and the final step Task: Assess the Architecture.

The second step, the stakeholder review described here, is a review of 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.

Actions are documented, assigned and tracked.

These activities are best carried out by a small team staffed by cross-functional team members. The team should include members with domain experience who can identify key abstractions, and ideally system and technical level IT architects and experts. The team should also have experience and knowledge of a wide range of technologies along with model organization and layering.