Enterprise Architecture Books

An Enterprise Architect related book list.
This is my first attemt to relate books to knowledge and responsibilities of an Enterprise architect (according to IT Linchpin 2006).

The books I have chosen for now are books I have in my posession, or that are available on-line. I still have to add books to be found on two sites: Software Architecture Bibliography and Software Architecture Essential Bookshelf, and a list of books and articles I created have to be categorized. This list is based on recommended readings from lots of university courses on Enterprise Architecture:

• http://www.sts.tu-harburg.de/
• http://www2.essex.ac.uk/
• http://homepages.cwi.nl/
• http://www.cs.mcgill.ca/
• http://gaia.ecs.csus.edu/

1.Domain expertise – An enterprise architect should have expertise in at least two of the foundational architecture domains, and be conversant in all.
(the domains are: Business Architecture, Application Architecture, Information Architecture, Platform Architecture , Network Architecture, Security Architecture, Applications and Systems Management Architecture)

• Softwarearchitectuur Overzicht en compendium
• The software architect’s profession – An introduction
• Software Architecture in Practice
• Information Security Architecture
• Software Architect Bootcamp
• Practical Software Architecture For the Enterprise
• Software Architecture Action Guide Book
• Software Architect
• Mary Shaw, David Garlan: Software architecture, perspectives on an emerging discipline. Prentice-Hall, 1996

2.Industry Awareness – An enterprise architect should be aware of, and able to form opinions on, emerging and prevailing trends in information technology and the enterprise’s industry.

• Agile Software Development
• The J2EE Architect’s Handbook
• J2EE Web Services
• The mythical man-month

Architecture Skills – An enterprise architect’s skill set must include architecture practice expertise, great thinking capabilities, and strong people/professional skills. For an enterprise architect to be successful, he/she must be able to take a (valuable) idea from inception to implementation, gathering support along the way

3.Architecture Practices: Learn, Adopt, Tailor, and Teach Appropriate Architecture and Development Methodologies, Set and Enforce Standards, Identify and Apply Patterns at the Business, Architectural, Design, and Programming Levels, Drive and/or Participate in Portfolio Planning of IT Assets (tools, infrastructure, applications, information stores)

• Patterns of Enterprise Application Architecture
• Enterprise Integration Patterns
• Enterprise Solution Patterns using Microsoft .NET
• Head First Design Patterns
• Refactoring
• Erich Gamma et al: Design patterns, elements of reusable object-oriented software. Addison-Wesley, 1995.
• Bitter Java
• Core J2EE Patterns
• EJB Design Patterns
• John Vlissides: Pattern Hatching: Design Patterns Applied, Addison-Wesley (Software Patterns Series), 1998.
• Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal: Pattern-oriented software architecture. A system of patterns, John Wiley&Sons, 1996.
• Martin Fowler, Kendall Scott: UML Distilled, Addison-Wesley, 1997.
• Douglas Lea: Concurrent Programming in Java: Design Principles and Patterns, Addison Wesley, Nov 1999.

4.Thinking: Visualize and Articulate the Big Picture, Abstract Key Concepts from Detailed Problem Domains (Business, Architecture, Systems), Ability to Analyze, Synthesize, Question and Recommend, Generate Creative Ideas and Solutions, Possess Natural Curiosity, Good Decision Making, Accounting for Fit, Risks, Rewards, Time, and Expense

• Michael Jackson: Software Requirements & Specifications: A lexicon of practice, principles, and prejudices, Reading, MA: Addison-Wesley, 1995.

5.People/Professionals Skills: Lead Formally and Informally, Influence at all Organizational levels, Internally and Externally, Facilitate Diverse Groups, Mentor, Collaborator, Communicator (written and verbal), Self Motivated

• see the last post on Non-EA related books

Still to be categorized:

• Frank Griffel: Componentware: Konzepte und Techniken eines Softwareparadigmas, 1998.
• Tanenbaum, Steen: Verteilte Systeme, 2003.
• Clemens Szyperski, Component Software: Beyond Object-Oriented Programming, 2nd Edition, Addison-Wesley, 2002.
• L. Bass, P. Clements, R. Kazman, Software Architecture in Practice, Addison-Wesley, 1998.
• I. Crnkovic and M. Larsson (Eds), Building Reliable Component-based Software Systems, Artech House, 2002.
• H. Mili, A. Mili, S. Yacoub, E. Addy, Reuse-Based Software Engineering: Techniques, Organization, and Controls, Wiley Inter-Science, 2002.
• J. Rumbaugh, I. Jacobson, G. Booch, The Unified Modeling Language Reference Manual, 2nd edition, Addison-Wesley, 2005.
• F.P. Brooks II, No Silver Bullet: Essence and Accidents of Software Engineering, IEEE Computer, Vol. 20, No. 4 (Apr. 1987), pp. 10-19.
• N.G. Carr, Does Not Compute, The New York Times, 22 Jan. 2005.
       
• A.H. Eden,Software engineering state-of-the-art: Introduction to the not-so-innocent, Department of Computer Science, University of Essex, 9 Feb. 2005.
• D. Garlan, R. Allen, J. Ockerbloom, Architectural Mismatch: Why Reuse Is So Hard, IEEE Software, Vol. 12, No. 6 (Nov. 1995), pp. 17-26.
• D.E. Perry, A.L. Wolf, Foundation for the Study of Software Architecture, ACM SIGSOFT Software Engineering Notes, Vol. 17, No. 4 (1992), pp. 40-52.
• D. Garlan, M.Shaw, An Introduction to Software Architecture, in Ambriola, V. and Tortora, G. (ed.), Advances in Software Engineering and Knowledge Engineering, Series on Software Engineering and Knowledge Engineering, Vol. 2, World Scientific Publishing Company, Singapore, pp. 1-39, 1993.
• D. Schmidt ,R.E. Johnson, M. Fayad, Software Patterns, Guest editorial, Communications of the ACM, Special Issue on Patterns and Pattern Languages, Vol. 39, No. 10 (Oct. 1996).

Additional Literature

• Ivar Jacobson, Martin Griss, Patrick Jonsson, Patrik: Software Reuse. Architecture, Process and Organization for Business Success. Addison-Wesley, 1997.
• Ian Sommerville: Software Engineering, Addison-Wesley 1995
• Helmut Balzert: Lehrbuch der Software-Technik. Band I, Software-Entwicklung, Spektrum-Verlag, 1997.
• James Gosling: The Java Language Specification, Addison-Wesley, 1997.
• Michael L. Brodie, Michael Stonebraker: Migrating Legacy Systems Morgan-Kaufmann, 1995.
• A. H. Eden, Strategic Versus Tactical Design, Proc. 38th Hawaii Int'l Conf. System Sciences-HICSS (3-6 Jan. 2005), Honolulu, HI.
• P.C. Clements, A Survey of Architecture Description Languages, 8th Int. Workshop Software Specification and Design (March 1996), Germany.
• F. Deremer, H.H. Kron, Programming-in-the-Large Versus Programming-in-the-Small, IEEE Transactions in Software Engineering Vol. SE-2, No. 2, June 1976, pp. 80-86.
• A.H. Eden, O-O Modelling, Under preparation, 2006.
• M. Fayad, D.C. Schmidt, Object-Oriented Application Frameworks, Guest editorial, Communications of the ACM, Vol. 40, No. 10 (Oct. 1997).
• D. Garlan, R. Monroe, D. Wile, ACME: An Architectural Description Interchange Language, Proc. CASCON'97 (Nov. 1997), Toronto, Ontario.
• W.W. Gibbs, Software's Chronic Crisis, Scientific American (Sep. 1994), p. 86-95.
• G. Andrews, Paradigms for process interaction inistributedprograms,ACM ComputingSurveys, 23(1):49-90, 1991.
• R. Kazman, M. Klein, M. Barbacci, T.  Longstaff, H. Lipson and J. Carriere, The Architecture Tradeoff Analysis Method, in Proceedings of ICECCS, August 1998.
• D. Zantinge and P. Adriaans, Managing Client/Server, Addison Wesley, 1996.
• Stephen T. Albin, The Art of Software Architecture, Wiley, 2003
• Leonor Barroca, Jon Hall and Patrick Hall, Software Architectures, Advances and Applications, Springer 1999.
• Grady Booch, James Rumbaugh, Ivar Jacobson, The Unified Modeling Language User Guide, Addison Wesley, 1999.
• Stephen H. Kaisler, Software Paradigms, Wiley, 2005.
• Raphael Malveau and Thomas J. Mowbray, Software Architecture Bootcamp, Prentice Hall PTR, 2001.
• Wiley Series in Software Design Patterns – Pattern-Oriented Software Architecture, 3 Volumes, 1996, 2000, and 2004

Comments

[Martin]

I am surprised you didn't list the bestselling book, A practical guide to enterprise architecture

[brenda michelson]

You might consider adding Christopher Alexander's "The Timeless Way of Building" and the O'Reilly published "Open Sources 2.0"

A book at the top of my own stack is Greenfield and Short's "Software Factories".

Reading/continuous learning is critical for the enterprise architect. Applying that in real world experience is paramount.

-brenda

[Mylene Reiners]

I will check all recommendations, and choose the ones that seem most beneficial :)