In a world of agile development and DevOps is architecture still relevant? Yes but having a lightweight approach that is compatible with an agile approach makes a lot of sense in the age of digital disruption.

1. Why Do Architecture
Reviews?
Riaz A. Khan, BSc (Hons.) CS, TOGAF, ITAC-M
Instructor,
Course
Designer,
Faculty
Advisor
Divisional Vice
President & Chief
Architect

2. Architecture Review’s at
Sears
 Architecture
reviews are a
critical part of the
SDLC.
 Identify potential
issues prior to
construction
 Think of
investigative
journalism

3. When should a review be
conducted
 As soon as possible after
requirements have been defined and
key architectural decisions are
understood
 Again prior to the test phase.
 For projects using iterative
development during each iteration

4. What is an architecture
review?
 A process by which conclusions can
be drawn about the suitability of the
architecture
 Do the architectural decisions enable
or restrict the architectural significant
requirements?
 Scope can be the whole architecture
or a specific subset such as
performance or security

5. Who should be included?
 Cover the three main contingencies
◦ Evaluation Team (ARB Board)
◦ Project Stakeholders - Sponsor
◦ Project Practitioners – PM, BA, Lead Dev,
etc

6. How do you conduct a review
 Your lead architect will send a request
to the ARB board for an architecture
review.
 For most projects we will use a
lightweight review process called:
Decision centric Architecture review

7. Requirements for DCAR
 Lightweight compared to other
methods
 Incremental
 Evaluators can say something about
the coverage

8. Sample Agenda

9. Architecture Decision
Summary

10. DCAR Report output