Scribd
Upload
142 views4 pages

Architecture Review - CRs-existing Projects

Uploaded by

Edwin Mbogo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
142 views4 pages

Architecture Review - CRs-existing Projects

Uploaded by

Edwin Mbogo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

<Project>

Architectural Review Report


Date: <please do not use automatic fields>
Reviewer: <name>

[Note: The following template is provided for use with the Unified Architecture Method. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the
author and should be deleted before publishing the document. A paragraph entered following this style
will automatically be set to normal (style=Body Text).]

Executive Summary

[This is a one-page reiteration of the key objectives for the assessment and a summary of the most
important findings and recommendations.]

Goals & Objectives


https://metasun.blogspot.com/2018/02/togaf-diagram-examples.html

[See the architecture review checklist


List the members of the architecture review team and other key contributors. Briefly describe the
information gathering and analysis methods applied. The purpose of an architecture review is to
understand the impact of every architecturally significant decision on every architecturally significant
requirement. Review objectives focus on specific aspects of an architecture. These aspects can include:
 The fit of the architecture to the problem or mission statement,
 The partitioning of system responsibilities to subsystems and components,
 The specific qualities (i.e., scalability, performance, etc.) to be architecturally controlled,
 The partitioning of the architectural design responsibilities,
 The identification of skills to implement the system,
 The verification of scenarios representing the critical functionality of the system, and
 The overall feasibility and specific risks of the architecture
Review objectives fall into the following categories:
 Certifying conformance to some standard:
o Does the architecture fulfill the constraints and requirements of the relevant standards?
 Assessing the quality of the architecture:
o Does the architecture fit to the problem or mission statement?
o Is the architecture a suitable basis for fulfilling the present and future requirements?
o Can specific qualities (e.g., scalability, performance. etc.) be architecturally controlled?
o Are there open issues that have to be clarified?
o Can the architecture be implemented using existing skills?
o Which new skills are needed to implement the system?
o Does the architecture support the realization of scenarios representing the critical
functionality of the system?
o Is the realization of the architecture and its underlying technical concepts feasible?
o What are specific technical risks of the architecture?
o How are the responsibilities of the architecture partitioned?
 Identifying of opportunities for improvement:
o Which design decisions should be revised in order to improve the architecture?
o Which improvement measures should be taken?

©<company name>, 2021 1 of 4


<Project>

 Improving communication between stakeholders. ]

Scope

[Define the scope of the review:


 List the work products and other deliverables being reviewed
 Does the review include the whole system or only some parts?
 Does the review include all the stakeholders?
 Does the review involve all architectural view?
 Does the review include all the Architectural Decisions or only a subset?]

Review Participants

[List the individuals who will participate in the review and their roles during the meeting; for example,
moderator, note-taker, reviewer, author. ]

Overall Architecture
[Identify the high–level architectural concerns regarding areas such as:
 High–level Architecture
o Topology and scalability structure/patterns issues
o Communication structure/patterns issues
o Persistence structure/patterns issues
o Fault tolerance and redundancy issues
o Security solutions structure/patterns issues
o User experience and GUI structure/patterns issues
o Integration of hardware and hardware dependencies
o Integration of software and software dependencies]
 Strengths – Identify the strengths of the architecture and how the can be related to the
architecture concerns.
 Issues – Identify which topics are subject to further investigation; for all issues a plan needs to be
defined with assigned tasks and responsibilities.]

Specific Architecture Aspects

 [See the architecture review checklist]


Requirements

 [See the architecture review checklist]


Application Architecture

 [See the architecture review checklist]

©<company name>, 2021 2 of 4


<Project>

Information Architecture

 [See the architecture review checklist]


Operational Architecture

 [See the architecture review checklist]


Systems Management

 [See the architecture review checklist]


COTS Products Integration

 [See the architecture review checklist]


Change Management, Development & Testing

 [See the architecture review checklist]


Security Architecture

 [See the architecture review checklist]

Key Findings & Actions

[Document the architecture recommendations and findings. New Architectural Decisions (ADs) found in
the review must be referenced here.]
Strengths

[Describe the positive findings of the assessment. Rank them from most significant to less significant.]
Issues

[Describe issues identified during the evaluation. Rank them from most severe to less severe. Use the
following structure for consistency:
 Issue Give the issue a name
 Describe the nature of the issue and its consequences
 Propose an approach to addressing the issue
 Provide references to the information sources
Also see the architecture review checklist]
Recommendations

©<company name>, 2021 3 of 4


<Project>

[During team discussion, recommendations need to be collected that might help the project at a later
date, or are optional in the given context. The report should be concise. If there is an issue that needs an
extended discussion, such discussion should be moved to the Appendixes section. Hence, the
recommendations should be short and to the point.]
Action Plan

[Describe any actions required as a result of the review.


Also see the architecture review checklist]
Issues for the Architecture Review Board

[Certain problems or anomalies may be discovered for which a course of action cannot be agreed on by
the review team, and which needs to be escalated for resolution.]
Follow-up Review

[Describes the review team's recommendations for follow-up (for example, whether another review is
necessary) and what, if any, additional information or data is needed.]

©<company name>, 2021 4 of 4

You might also like