This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Pattern-Based Architecture Reviews
Nov.-Dec. 2011 (vol. 28 no. 6)
pp. 66-71
ASCII Text
x 
 
Neil B Harrison, Paris Avgeriou, "Pattern-Based Architecture Reviews," IEEE Software, vol. 28, no. 6, pp. 66-71, Nov.-Dec., 2011.
 
 
BibTex
x
 
@article{ 10.1109/MS.2010.156,
author = {Neil B Harrison and Paris Avgeriou},
title = {Pattern-Based Architecture Reviews},
journal ={IEEE Software},
volume = {28},
number = {6},
issn = {0740-7459},
year = {2011},
pages = {66-71},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.156},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Pattern-Based Architecture Reviews
IS - 6
SN - 0740-7459
SP66
EP71
EPD - 66-71
A1 - Neil B Harrison,
A1 - Paris Avgeriou,
PY - 2011
KW - Software Architecture
KW - Patterns
KW - Software Engineering Process
KW - Review and Evaluation
VL - 28
JA - IEEE Software
ER -
 
Neil B Harrison, Utah Valley University
Paris Avgeriou, University of Groningen
Software architecture reviews are effective in identifying potential problems in architectures, however, are expensive, time-consuming, and generally rely on extensive architecture documentation. An architecture review that accommodates projects with very short development cycles, minimal documentation, or frequently changing requirements could be useful if it identifies important architectural issues. We developed a useful, inexpensive architecture review method that uses the architecture patterns in a system to identify important issues in the achievement of quality attributes.

1. P. Clements, R. Kazman, and M. Klein, Evaluating Software Architectures: Methods and Case Studies, Addison-Wesley, 2001.
2. G. Abowd et al., Recommended Best Industrial Practice for Software Architecture Evaluation, tech. report CMU/SEI-96-TR-025, Carnegie Mellon Univ., Software Eng. Inst., 1997.
3. J.F. Maranzano et al., "Architecture Reviews: Practice and Experience," IEEE Software, vol. 22, no. 2, 2005, pp. 34–43.
4. L. Bass et al., Risk Themes Discovered through Architecture Evaluations, tech. report CMU/SEI-2006-TR-012, Carnegie Mellon Univ., Software Eng. Inst., Sept. 2006.
5. K. Beck and K. Andrus, Extreme Programming Explained: Embrace Change, 2nd ed., Addison-Wesley, 2004.
6. A. Cockburn, Crystal Clear: A Human-Powered Methodology for Small Teams, Addison-Wesley, 2004.
7. M. Poppendieck and T. Poppendieck, Implementing Lean Software Development: From Concept to Cash, Addison-Wesley, 2006.
8. L. Dobrica and E. Niemelä, "A Survey on Software Architecture Analysis Methods," IEEE Trans. Software Eng., vol. 28, no. 7, 2002, pp. 638–653.
9. R. Kazman and L. Bass, "Making Architecture Reviews Work in the Real World," IEEE Software, vol. 19, no. 1, 2002, pp. 67−73.
10. E. Gamma et al., Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, 1994.
11. F. Buschmann et al., Pattern-Oriented Software Architecture: A System of Patterns, vol. 1, Wiley, 1996.
12. N. Harrison, P. Avgeriou, and U. Zdun, "Using Patterns to Capture Architectural Decisions," IEEE Software, vol. 24, no. 4, 2007, pp. 38–45.
13. P. Avgeriou and U. Zdun, "Architectural Patterns Revisited: A Pattern Language," Proc. 10th European Conf. Pattern Languages of Programs (EuroPLoP 05), Butterworth-Heinemann, 2005, pp. 1003–1034.
14. N. Harrison and P. Avgeriou, "Analysis of Architecture Pattern Usage in Legacy System Architecture Documentation," Proc. 7th Working IEEE/IFIP Conf. Software Architecture (WICSA 08), IEEE CS Press, 2008, pp.147–156.

Index Terms:
Software Architecture, Patterns, Software Engineering Process, Review and Evaluation
Citation:
Neil B Harrison, Paris Avgeriou, "Pattern-Based Architecture Reviews," IEEE Software, vol. 28, no. 6, pp. 66-71, Nov.-Dec. 2011, doi:10.1109/MS.2010.156
Usage of this product signifies your acceptance of the Terms of Use.