architecture review vs post implementation review
TRANSCRIPT
![Page 1: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/1.jpg)
ArchitectureReview vs.
Post ImplementationReview
![Page 2: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/2.jpg)
Definitions
The set of structures needed to reason about the system, which comprises software elements, relations among them, and properties of both.
SEI
Realization of a technical specification or algorithm as a program, software component, or other computer system through computer programming and deployment.
Software architecture Implementation
![Page 3: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/3.jpg)
Why to review
Identify potential risks in the proposed architecture
Reduce project cost caused by undetected design problems
Uncover problems and conflicts in requirements
Assess quality attributes Identify skills required to
implement the proposed architecture
Promote good architecture design and evaluation practices
Improve architecture documentation quality
Determine whether the project goals were achieved
Determine the satisfaction of stakeholders
Determine the project's costs and benefits
Identify areas of further development
Identify lessons learned Report findings and
recommendations
AR PIR
![Page 4: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/4.jpg)
When to review
Project initiation Initial design Major design changes
Shortly after a project has been completed
After the deliverables have been handed to the customer
When most of the problems have been eliminated
But not too late - while members of the project team still remember the most
AR PIR
![Page 5: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/5.jpg)
What to review - AR
Logical -functional requirements: Abstraction & Encapsulation Information hiding Separation Modularization
Quality attributes: Flexibility Security Scalability Performance Reliability Availability Maintainability
![Page 6: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/6.jpg)
What to review - AR
Infrastructure Components 1.Clients
e.g. web browsers or telephones 2.Network components
Includes firewalls and web traffic dispatchers 3.Web servers
Handles HTTP requests and securing communications via SSL 4.Application servers
Focuses on presentation and session management services 5.Business logic and transaction servers
Manage and execute transactions 6.Database servers
Data storage and management 7.Server Operating Systems 8.Development languages and tools
Create logic, design GUI interfaces, and customize services 9.Network and systems management tools
Monitor and manage system / network events
![Page 7: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/7.jpg)
What to review - PIR
Measure the benefits and objectives Assess the final deliverables produced Decide whether the project was within scope Review the project against schedule Compare the expenditure against budget State the final outcome of the project Document any lessons learned for future projects
![Page 8: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/8.jpg)
How to review
Prior to the review, gather inputs that describe the architecture
Use scenarios to evaluate the quality attributes in specific contexts
Review and identify gaps between architecture characteristics / attributes and business requirements
Ask for openness Be objective Document success Look with hindsight Be future-focused Look at both positives
and negatives
AR PIR
![Page 9: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/9.jpg)
After the review
![Page 10: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/10.jpg)
Q&A
![Page 11: Architecture review vs Post Implementation Review](https://reader035.vdocuments.site/reader035/viewer/2022073118/55a662221a28ab56538b486f/html5/thumbnails/11.jpg)
Sources
Samir Roshan, IT Architecture Review: The Basics, The Approach, The Outcome, Nov. 9, 2012, http://thinkingloudoncloud.com/2012/11/architecture-review-basics-approach-outcome/ (last visited Feb. 24, 2014)
Alexander Nowak, Software Architecture Review Guidelines, Sep. 12, 2007, http://www.codeproject.com/Articles/20467/Software-Architecture-Review-Guidelines (last visited Feb. 24, 2014)
Denise Cook, Architecture Evaluation and Review Practices, June 2007, https://msdn.microsoft.com/en-us/library/bb896741.aspx (last visited Feb. 24, 2014)
ISACA Conference Fall 2003, IT Architecture Review. http://www.sfisaca.org/download/C5ITArchitecture.pdf (last visited Feb. 24, 2014)
TOGAF, Chapter 48: Architecture Compliance, http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap48.html (last visited Feb. 24, 2014)
MindTools, Post-Implementation Reviews. http://www.mindtools.com/pages/article/newPPM_74.htm (last visited Feb. 25, 2014)
Method123, Post Implementation review. http://www.method123.com/post-implementation-review.php (last visited Feb. 26, 2014)
Software Engineering Institute, Glossary, http://www.sei.cmu.edu/architecture/start/glossary/index.cfm#Modern (last visited Feb. 24, 2014)
Holon Solutions, http://www.holonsolutions.com/wp-content/uploads/2013/06/blocks.jpg