1 / 11

Architecture Review

Architecture Review. Post Implementation Review. vs. Definitions. Software architecture. Implementation. The set of structures needed to reason about the system, which comprises software elements, relations among them, and properties of both. SEI.

bemmerich
Download Presentation

Architecture Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ArchitectureReview Post ImplementationReview vs.

  2. Definitions Software architecture Implementation 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.

  3. Why to review AR PIR • 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

  4. 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 When to review AR PIR

  5. What to review - AR • Logical -functional requirements: • Abstraction & Encapsulation • Information hiding • Separation • Modularization • Quality attributes: • Flexibility • Security • Scalability • Performance • Reliability • Availability • Maintainability

  6. 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

  7. 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

  8. 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 How to review AR PIR • Ask for openness • Be objective • Document success • Look with hindsight • Be future-focused • Look at both positives and negatives

  9. After the review

  10. Q&A

  11. 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

More Related