papers banner.gif (15379 bytes)

Back to Papers and Downloads

Architecture and Related Books List

What: Architecture

How: Architecting

Who: Architects

Why: Motivation

Where and When: Context

Related Topics

 

Bibliography

Software Architecture and Related Papers Organized by Topic

 

WHAT: Architecture

Kruchten, Philippe, "The 4+1 View Model of Software Architecture", IEEE Software, pp. 42-50. November 1995.

Malan, Ruth and Dana Bredemeyer, "Software Architecture: Central Concerns, Key Decisions," May 2002. http://www.bredemeyer.com/pdf_files/ArchitectureDefinition.PDF

Malan, Ruth and Dana Bredemeyer, "Less is More with Minimalist Architecture," IEEE's IT Professional, September/October 2002. © 2002 IEEE. http://www.bredemeyer.com/pdf_files/MinimalistArchitecture.PDF Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.

Mustapic, Goran, Anders Wall, Christer Nortrom, and Ivica Crnkovic, "Real World Influences on Software Architecture - Interviews with Industrial System Experts, IEEE Working Conference on Software Architectures, 2004. http://www.mrtc.mdh.se/publications/0700.pdf

Mowbray, Thomas J., "Will the Real Architecture Please Sit Down?", Component Strategies, December 1998.

Perry and Wolf, "Foundations for the Study of Software Architecture", Software Engineering Notes, vol. 17 no 4, Oct 1992.

HOW: The Architecting Process

Bass, Len and Rick Kazman, "Architecture-Based Development", http://www.sei.cmu.edu/publications/documents/99.reports/99tr007/99tr007abstract.html

Clements, Paul and Linda Northrop, "Architecture Exploration and Definition" in A Framework for Product-Line Practice-Version 2.0, http://www.sei.cmu.edu/plp/frame_report/architectureED.htm

Emery, David, R. F. Hilliard, and T. Rice, "Experiences Applying a Practical Architectural Method", http://www.pithecanthropus.com/~awg/CaseStudies.pdf

Malan, Ruth and Dana Bredemeyer, Software Architecture Action Guide (draft book), http://www.bredemeyer.com/ArchitectingProcess/SWAActionGuideTOC.htm

Malan, Ruth and Dana Bredemeyer, "Getting Past "But": Finding Opportunity and Making It Happen" (on innovation and scaling agile with VAP) Enterprise Architecture Executive Report, Cutter Consortium, August 2008
You can download a complimentary copy from http://www.cutter.com/offers/findopportunity.html.

Muller, Gerrit, Architectural Reasoning Explained, http://www.gaudisite.nl/ArchitecturalReasoningBook.pdf

Muller, Gerrit, System Architecting, http://www.gaudisite.nl/SystemArchitectureBook.pdf

Youngs, R., D. Redmond-Pyle, P. Spaas, and E. Kahan, "A Standard for Architecture Description", IBM Systems Journal, Vol 38 No 1. http://www.research.ibm.com/journal/sj/381/youngs.html

Architectural Requirements

Architectural Requirements: General

Clements, Paul and Linda Northrop, "Domain Analysis" in A Framework for Product-Line Practice-Version 2.0, http://www.sei.cmu.edu/plp/frame_report/domain.analysis.htm

Malan, Ruth, and Dana Bredemeyer, “Architectural Requirements and the Visual Architecting Process,” February 2002. http://www.bredemeyer.com/ArchitectingProcess/ArchitecturalRequirements.htm

Malan, Ruth, “Requirements and Innovation,” July  2006. http://www.bredemeyer.com/ArchitectingProcess/VAPColumns/RequirementsAndInnovation.htm

Rust, Roland, D. Thompson, R. Hamilton, “Defeating Feature Fatigue,” Harvard Business Review, February 2006.

Architectural Requirements: Vision, Strategy and Innovation

Alfred, Charlie, "Value-Driven Architecture: Linking Product Strategy with Architecture," June 2005. http://msdn.microsoft.com/architecture/journ/default.aspx?pull=/library/en-us/dnmaj/html/Jour5Value.asp 

Dikel, Kane and Wilson, “Projecting and Unifying Vision”, Ch 3. Software Architecture: Organizational Principles and Patterns, 2001.

Highsmith, Don, “Product Vision,” This article originally appeared in the 23 August 2001 issue of Cutter Consortium's Agile Project Management E-Mail Advisor and is viewable at http://www.joelonsoftware.com/printerFriendly/articles/JimHighsmithonProductVisi.html

Malan, Ruth and Dana Bredemeyer, "Creating an Architectural Vision: Collecting Input," http://www.bredemeyer.com/pdf_files/vision_input.pdf,  July 2000. See also http://www.bredemeyer.com/pdf_files/Newspaper_Vision.PDF, which is a fictitious vision article we created as a promotion back in 2000 (when 2003 was still out in the future). It is still relevant as a way to pitch a vision.

Malan, Ruth and Dana Bredemeyer, "Enterprise Architecture as Strategic Differentiator," Enterprise Architecture Executive Report. Cutter Consortium, June 2005.
You can download a complimentary copy from http://www.cutter.com/offers/strategic.html

Architectural Requirements: Use Cases

Cockburn, Alistair, "Structuring Use Cases with Goals", http://members.aol.com/acockburn/papers/usecases.htm

Cockburn, Alistair, "Basic Use Case Template", http://members.aol.com/acockburn/papers/uctempla.htm

Coleman, Derek, "A Use Case Template -- Draft for Discussion", Fusion Newsletter, April 1998.

Malan, Ruth and Dana Bredemeyer, "Functional Requirements and Use Cases", functreq.pdf, June 1999.

Architectural Requirements: Qualities

Bachman, Felix, Len Bass, Mark Klein, “Illuminating the Fundamental Contributors to Software Architecture Quality,” Technical Report CMU/SEI-2002-TR-025, August 2002.

Bass, Len, Mark Klein and Felix Bachman, “Quality Attribute Design Primitives,” Technical Note CMU/SEI-2000-TN-017, December 2000.

Bass, Len, Mark Klein and Gabriel Moreno, “Applicability of General Scenarios to the Architecture Tradeoff Analysis MethodSM,” Technical Report CMU/SEI-2001-TN-014, October 2001.

Kazman R., and L. Bass. "Toward Deriving Software Architectures from Quality Attributes" CMU/SEI-94-TR-10. August 1994.

Clements, P.L. Bass, R. Kazman, and G. Abowd. "Predicting Software Quality by Architectural-Level Evaluation". 5th Intl Conference on Software Quality, 1995.

Malan, Ruth and Dana Bredemeyer, "Non-Functional Requirements", nonfunctreq.pdf, June 1999.

Architecture: Structuring and Specification

Architectural Style, Patterns and Reference Architectures

Booch, Grady, Patterns Catalog, Software Architecture Handbook website, http://www.booch.com/architecture/index.jsp. You must sign-in to view the patterns catalog and other pages on Booch's site.

North Carolina State Technical Architecture http://www.state.nc.us/IRM/techarch/archfrm.htm

Structuring: Concerns

Coupling

Related patterns:

 

Structuring: Mechanisms

Bass, Len, Mark Klein and Felix Bachmann, Quality Attribute Design Primitives," Technical Report: CMU/SEI-2000-TN-017, December 2000

Bass, Len, Mark Klein, and Rick Kazman, "Architecture Mechanisms," The Architect, Vol 4.1, 2001

Bass, Len, Robert Nord, William Wood, David Zubrow, "Risk Themes Discovered Through Architecture Evaluations," September 2006

Benjamin A. Lieberman, Analyze use cases by architectural relevance: Using architectural mechanisms to improve the software development life cycle," IBM DeveloperWorks, 23 Jan 2007

Interoperability

Lewis, Grace, Lutz Wrage, "Approaches to Constructive Interoperability," Technical Report: CMU/SEI-2004-TR-020, ESC-TR-2004-020, December 2004

Lewis, Grace, Edwin Morris, Dennis Smith, and Lutz Wrage, "Service-Oriented Architectures as an Interoperability Mechanism," news@sei, 2005

Modularity

Baldwin, Carliss and Kim Clark, "Modularity after the Crash," Harvard NOM Research paper No 01-05, May 2001.

MacCormack, Alan, John Rusnak, and Carliss Baldwin Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code, 2005

Simon, Herbert,  The Architecture of Complexity, 1962.

Sullivan, Kevin, Yuanfang Cai,  Ben Hallen and William Griswold, "The Structure and Value of Modularity in Software Design," UVa Technical Report, CS-2001-13. http://www.cs.virginia.edu/~sullivan/publications/UVa-CS-2001-13.PDF

Scalability

Skinner, Jim , "Extended Scalability on the Data Tier," Microsoft TechNet, 2007

Usability

Bass, Len, Bonnie E. John, and Jesse Kates, "Achieving Usability Through Software Architecture," Technical Report: CMU/SEI-2001-TR-005, ESC-TR-2001-005, March 2001

Structuring: Architecture Specification

Alfred, Charlie, "Using Architecture Challenges to Formulate Software Architecture,” www.foliage.com, Mar 19, 2003 

Buhr, R.J.A. and Casselman, R.S. Use CASE Maps for Object-Oriented Systems, Prentice-Hall 1996. Or print the book off  the web (http://www.UseCaseMaps.org/UseCaseMaps/pub/UCM_book95.pdf).

Grace, Ron, D. Coleman, M. Ogush, S. Rhodes, "Experience with Documentation of Software Architectures", published on the HP Software Architecture web site, http://www.architecture.external.hp.com/Download/PracArchDoc.pdf

HP  Software Architecture web site, "Structuring",  http://www.architecture.external.hp.com/Overview/arch_structuring.htm

Kazman, Architecture class slides, http://www.cgl.uwaterloo.ca/~rnkazman/

Kruchten, Philippe, "Modeling Component Systems with the Unified Modeling Language", Proceedings of the 1998 International Workshop on Component-Based Software Engineering, http://www.sei.cmu.edu/cbs/icse98/papers/p1.html

Ogush, M., D. Coleman, and D. Beringer, "A Template for Documenting Software Architectures", March 2000, http://www.architecture.external.hp.com/Download/arch_template_vers13_withexamples.pdf

Youngs, R., D. Redmond-Pyle, P. Spaas, and E. Kahan, "A Standard for Architecture Description", IBM Systems Journal, Vol 38 No 1. http://www.research.ibm.com/journal/sj/381/youngs.html

Architecture Tradeoff Analysis

Barbacci, M. R., S. J. Carriere, P. H. Feiler, R. Kazman, M. H. Klein, H. F. Lipson, T. A. Longstaff, and C. B. Weinstock, "Steps in an Architecture Tradeoff Analysis Method: Quality Attribute Models and Analysis", http://www.sei.cmu.edu/publications/documents/97.reports/97tr029/97tr029title.htm  

SEI Architecture Tradeoff Analysis Initiative website,  http://www.sei.cmu.edu/ata/ata_init.html

Architecture Validation

Kaman’s Scenario-based Architecture Analysis of Method (SAAM), http://www.cgl.uwaterloo.ca/~rnkazman/

Balsamo, S., Inverardi, P., and Mangano, C. "An Approach to Performance Evaluation of Software Architectures." ACM Workshop on Software and Performance, 1998.

Bass, Len and Rick Kazman, "Analyze the Architecture", Architecture-Based Development, http://www.sei.cmu.edu/publications/documents/99.reports/99tr007/99tr007chap05.html

Barber, K., Holt, J., and Baker, G. "Performance Evaluation of Domain Reference Architectures." ACM/IEEE International Conference on Software Engineering and Knowledge Engineering, 2002.

WHO: Architects

Barbacci, Mario. "Are Software Architects Like Building Architects?". SEI Interactive. http://interactive.sei.cmu.edu/Columns/The_Architect/1998/September/Architect.sept98.htm

Bredemeyer, Dana and Ruth Malan, "What it Takes to be a Great Enterprise Architect," Enterprise Architecture Executive Report, Cutter Consortium, August 2004Cutter is running a promotion, and you can download this issue free at http://www.cutter.com/offers/greatarchitect.html.

Bredemeyer, Dana. "James Madison and the Role of the Architect", madison.pdf, 1999.

Bredemeyer, Dana and Ruth Malan. Role of the Software Architect (.pdf), 1999.

Clements, Paul, "Marathon Man," http://www.sei.cmu.edu/news-at-sei/columns/software-product-lines/2004/3/software-product-lines-2004-3.htm

Crandall, Bill, "James Madison, Architect," Fusion Newsletter, May 1997. Available at http://www.hpl.hp.com

Fowler, Martin, "Who Needs an Architect?" IEEE Software, 2003. http://www.martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf

HP Software Architecture Web Site, "Who?: The Architect",  http://www.architecture.external.hp.com/Overview/arch_who_architect.htm

Kruchten, Philippe, "The Architect: The Architecture Team", Proceedings of the First International Conference  in Software Architecture (WICSA1), Feb 1999 and Software Architecture,  Patrick Donohoe Ed. Kluwer Academic Pub. 1999.

WHY: Motivating Architecture

Morris, Charles and Charles Ferguson. "How Architecture Wins Technology Wars". Harvard Business Review, March 1993.

WHERE and WHEN: Architecture in Context

Cockburn, Alistair, "On the Interaction of Social Issues and Software Architecture", http://members.aol.com/acockburn/papers/softorg.htm

Conway, M.E. "How do Committees Invent?", Datamation, (14) 4, April 1968. pp28-31.

Back to Top

Historically Important Papers on Software Architecture and Related Topics
  • Conway, Melvin, "How do Committees Invent," Datamation, 1968.

  • Djikstra E.W. “The Structure of the ‘T.H.E.’ Multiprogramming System”. Communications of the ACM. 18(8) 1968. pp. 453-7
     

  • Parnas, David L., “On the Criteria to be Used in Decomposing Systems into Modules”, Communications of the ACM , 15, 12, December 1972, pp. 1053-1058.

  • Parnas, David L. “A Technique for Software Module Specification with Examples”, Communications of the ACM , 15, 5, May 1972, pp. 330-336.

  • Parnas, David L., “On a 'Buzzword': Hierarchical Structure”, IFIP Congress '74, North Holland Publishing Company, 1974, pp. 336-339.
     

  • Stevens, W. P., Myers, G. J. and Constantine, L. L., "Structured Design," IBM Systems Journal, Vol. 13, No. 2, May 1974.
     

  • Parnas, David L., “The Influence of Software Structure on Reliability”, Proceedings International Conference on Reliable Software , April 1975, Los Angeles, Ca., pp. 358-362.

  • Parnas, David L., Siewiorek, D.L., “Use of the Concept of Transparency in the Design of Hierarchically Structured Systems”,
    Communications of the ACM, 18, 7, July 1975, pp. 401-408.

  • Parnas, David L., Handzel, G., “More on Specification Techniques for Software Modules”, Report BS I 75/1, Fachbereich Informatik, Technische Hochschule Darmstadt, April 1975, 16 pgs. 46.

  • Parnas, David L., “On the Design and Development of Program Families”, IEEE Transactions on Software Engineering , Vol. SE-2, No. 1, March 1976, pp. 1-9.

  • Parnas, David L., Würges, H., “Response to Undesired Events in Software Systems”, Proceedings of Second International Conference on Software Engineering, October 1976, pp. 437-447.

  • Parnas, David L., “Some Software Engineering Principles”, Infotech State of the Art Report on Structured Analysis and Design, Infotech International, 1978, 10 pgs.

  • Parnas, David L., “Designing Software for Ease of Extension and Contraction”, IEEE Transactions on Software Engineering, March 1979, pp. 128-138.
     

  • David J. Mishelevich, Don Van Slyke, "The Software Architecture of the IBM Health Care Support/DL/I-Patient Care System." IBM Systems Journal, Volume 19, Number 4, 1980, 478-504

  • Lampson, B., "Hints for Computer System Design", IEEE Software, January 1984, 11-30.

  • Parnas, David L. and P. Clements, “A Rational Design Process: How and Why to Fake It,” IEEE Trans. Software
    Eng., vol. 12, no. 2, 1986, pp. 251–257.

  • Parnas, David L., P. Clements, and D.M. Weiss, “The Modular Structure of Complex Systems,” IEEE Trans. Software
    Eng., vol. 11, no. 3, 1985, pp. 259–266.

  • Zachman, J., "A Framework for Information Systems Architecture", IBM Systems Journal, 26(3), 1987, 276-292.

  • Schwanke, R., R. Altucher, M. Platoff, "Discovering, Visualizing, and Controlling Software Structure", in Proceedings of Fifth International Workshop on Software Specification and Design", May 1989, 147-150.

  • W. Tracz and L. Coglianese, "An outline for a Domain Specific Software Architecture Engineering Process," in Proceedings of WISR-4, 1991.

  • D. E. Perry and A. L. Wolf. "Foundations for the study of software architecture." ACM SIGSOFT Software Engineering Notes, 17:40—52, October 1992.

  • D. Garlan and M. Shaw. "An introduction to software architecture." In Advances in Software Engineering and Knowledge Engineering, volume 1. World Scientific Publishing Co., 1993.

  • Kazman, R., Bass, L., Abowd, G., Webb, M., "SAAM: A Method for Analyzing the Properties of Software Architectures", Proceedings of ICSE 16, Sorrento, Italy, May 1994, 81-90.

  • R. Kazman, M. Klein, M. Barbacci, T. Longstaff, H. Lipson, and J. Carriere, "The Architecture Tradeoff Analysis Method," Proceedings of IEEE, ICECCS, 1998.

Related Topics

Systems Architecture

Vision, Strategy and Innovation

Alter, Allan E., "Innovation Makes Emerging Technologies Pay Off," CIO Insight, June 5, 2005. http://www.cioinsight.com/article2/0,1540,1826516,00.asp 

Baker, Edward H. and Ellen Pearlman, "Innovation Takes More than Inspiration; it Takes Investment, and Persistence,"  CIO Insight, January 6, 2006. http://www.cioinsight.com/print_article2/0,1217,a=169616,00.asp

Baldwin, Howard (interviewer) and Laurie Orlov (interviewed), "Is Someone Else In Your Company Better At IT Innovation Than You? The CIO whose department gets left behind in driving innovation has some catch-up work to do," Optimize February 2006, Issue 52

Barnes, David, "How Business Should Drive Technology: Why UPS is always asking if what it has is the best and whether it can do better," Optimize April 2006, Issue 54

Carr, Nicholas, "IT Doesn't Matter," Harvard Business Review, September 2003.

Collins and Poras, “Building Your Company’s Vision”, Harvard Business Review, Sept-Oct 1996.

Grove Graphics International,  Strategic Visioning Products, http://www.grove.com

Harmon, Paul, "Does IT Matter?," BPTrends, September 2003.

Kotter, John, “Leading Change: Why Transformation Efforts Fail”, Harvard Business Review, March-April 1995.

Malan, Ruth and Dana Bredemeyer, "Creating an Architectural Vision: Collecting Input," http://www.bredemeyer.com/pdf_files/vision_input.pdf,  July 2000. See also http://www.bredemeyer.com/pdf_files/Newspaper_Vision.PDF, which is a fictitious vision article we created as a promotion back in 2000 (when 2003 was still out in the future). It is still relevant as a way to pitch a vision.

Malan, Ruth and Dana Bredemeyer, "Enterprise Architecture as Strategic Differentiator," Enterprise Architecture Executive Report. Cutter Consortium, June 2005.
You can download a complimentary copy from http://www.cutter.com/offers/strategic.html

Rowsell-Jones, Andrew, "Know Your Advantage," CIO, September 8, 2005.

Visualization

Ferguson, E. Engineering and the Mind's Eye. Cambridge, Massachusetts: MIT Press, 1999.

Reuse and Software Product Lines

Griss, Martin, "Domain Engineering and Variability in the Reuse-Driven Software Engineering Business". Fusion Newsletter, Feb 1997. Available on the Fusion web page: http://www.hpl.hp.com

Griss, Martin, "Software Reuse: Objects and frameworks are not enough". Object Magazine, Feb 1995. Available on http://www.hpl.hp.com/reuse/papers/mlg-pubs.htm

Malan, Ruth and Tony Dicolen, "Risk Management in an HP Reuse Project". Fusion Newsletter, April 1996.

Evolutionary Development

Cotton, Todd. "Evolutionary Development", HP Journal, August 1996. Also in Ruth Malan, Reed Letsinger and Derek Coleman, editors, Object-oriented Development at Work: Fusion in the Real World. 1996.

 

Back to Top

Copyright © 1999-2008 by  Bredemeyer Consulting
URL: http://www.bredemeyer.com
Last Modified: July 29, 2009