Course Literature

Slides

• Introduction: 2010-2011 version.
• Requirements, Quality aspects, their realization: 2010-2011 version.
• Patterns: for architecture, for enterprise applications: 2010-2011 version.

Project topics: systems

You are welcome to investigate a system not on the list, however there are some side conditions:

• The system must be documented.
• The documentation and (great part of) the source code must be publicly available.
• The system must not overlap too much with topics from the list below, or must be replacement for a topic not chosen.

To choose from

• Content mangement systems: Joomla, Wordpress, OpenCMS
  • http://www.joomla.org/
  • http://wordpress.org/
  • http://www.opencms.org

• Version management: git, svn, mercurial
  • http://git-scm.com/
  • http://subversion.tigris.org/
  • http://mercurial.selenic.com/

• Online chatting (with reservations as project topic): Twitter
  • http://twitter.com/about/opensource
  • Doc on architecture of twitter itself is not readily available, but starting point(s) may be: scaleability

• Rich internet application development framework: Open Laszlo
  • http://www.openlaszlo.org/

• Better UNIX: plan 9
  • http://plan9.bell-labs.com/plan9/

• Distributed file system: AFS
  • http://en.wikipedia.org/wiki/Andrew_File_System

• Platform transparent user interface: X window system
  • http://en.wikipedia.org/wiki/X_Window_System

• Deployment: Nix, NixOS
  • http://www.st.ewi.tudelft.nl/~dolstra/software.html

• Middleware: Corba, Tibco, Java RMI, etc
  • http://www.corba.org/
  • http://www.tibco.com/
  • http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp

• Editor framework: Proxima
  • Proxima
  • http://www.cs.uu.nl/research/techreps/UU-CS-2002-030.html

Explored previously

• Web based application framework: Google Chrome
  • http://www.chromium.org/
  • http://www.chromium.org/chromium-os

• Realtime highperformance graphics environment: Ogre
  • http://www.ogre3d.org/

• Operating System on low energy consumption systems: Android
  • http://www.android.com/

• Large scale GIS (Geographical Information System): OpenStreetMap
  • http://www.openstreetmap.org/

• Fault tolerant, distributed database support for Web applications: Cassandra
  • http://cassandra.apache.org/

• Large scale implementations of otherwise simple problems: Google MapReduce
  • http://labs.google.com/papers/mapreduce.html
  • http://en.wikipedia.org/wiki/MapReduce

• Development environment: Eclipse
  • http://eclipse.org/documentation/

• Extensible application framework: OpenDoc
  • http://en.wikipedia.org/wiki/OpenDoc

Books

• The Software Engineering Institute (Carnegie Mellon) has various books on software architecture and related topics. Though slightly biased towards their own techniques the following are worthwhile and helpful, the first book offering a more general treatment, the remaining zoom in on subtopics:
  • Len Bass, Paul Clements & Rick Kazman; Software Architecture in Practice, Addison-Wesley, 2003 2nd ed. (1998 1st ed.).
  • Paul Clements et al. Documenting Software Architectures: Views and Beyond, Addison-Wesley, 2003.
  • Paul Clements et al. Evaluating Software Architectures: Methods and Case Studies, Addison-Wesley, 2002.

• Books on patterns are useful to become familiar with standard solutions for frequently occurring problems. Patterns allow you to think and talk about such problems in higher level concepts. Much more material on patterns exists nowadays, but the books below belong to the first to have appeared.
  • (BBL) Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal, Pattern-Oriented Software Architecture, Volume 1: A System of Patterns, Wiley & Sons, 1996.
  • Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. Design Patterns. Elements of Reusable Object-Oriented Software. 1995. Addison-Wesley.
  • Martin Fowler, Patterns of Enterprise Application Architecture. Addison-Wesley, 2003.

• UML
  • Martin Fowler, UML Distilled, Addison-Wesley, 1997. (If desired so, a team can have a copy of this book on loan for use during the project)

Use the following books to find more information on the subjects of the course, for instance to supplement your understanding of issues arising in the project phase.

• Stephen T. Albin, The Art of Software Architecture. Wiley Publishing, 2003. (this book has been used as the default SWA book in previous years)

• Thomas Erl, Service-Oriented Architecture: Concepts, Technology, and Design. Prentice-Hall PTR, 2005.

• Gert Florijn et al., Softwarearchitectuur: overzicht en compendium. Ten Hagen Stam, 2003. (In Dutch!)

• Christine Hofmeister, Robert Nord, and Dilip Soni, Applied Software Architecture. Addison-Wesley, 2000.

• Gregor Hohpe and Bobby Woolf, Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley, 2004.

• Gerald Kotonya and Ian Somerville, Requirements Engineering. Wiley Publishing, 1998.

• Leszek A. Maciaszek, Requirements Analysis and System Design. 2nd ed., Addison-Wesley, 2005.

• Bertrand Meyer, Object-Oriented Software Construction. 2nd ed., Prentice-Hall PTR, 1997.

• Nick Rozanski and Eoin Woods, Software Systems Architecture. Addison-Wesley, 2005.

• Clemens Szyperski, Component Software: Beyond Object-Oriented Programming. 2nd ed., ACM Press and Addison-Wesley, 2002.

• B. van Zeist, P. Hendriks, R. Paulussen en J. Trienekens, Kwaliteit van softwareprodukten - Praktijkervaringen met een kwaliteitsmodel, Kluwer Bedrijfswetenschappen, 1996. (In Dutch!)

Background reading material, papers

Introduction to software architecture

• Paul Clements, Understanding Architectural Influences and Decisions in Large-System Projects (or pdf). Invited talk, First International Workshop on Architectures for Software Systems. Seattle, WA, April 1995.

• Scott W. Ambler, Agile Architectural Modeling, 2001-2006.

• Martin Fowler, Who Needs an Architect?, 2003.

Software requirements, describing and evaluating software architectures

• Ho-Won Jung, Seung-Gweon Kim, and Chang-Shin Chung, Measuring Software Product Quality: A Survey of ISO/IEC 9126, IEEE Software 21 (2004), (5) 88-92

• Francisca Lovasio, Quality Models to Design Software Architecture. Journal of Object Technology 1 (2002), (4) 165-178.

• QUINT2: the Extended ISO Model of Software Quality (or pdf).

• Rohit Khare, Michael Guntersdorfer, Nenad Medvidovic, Peyman Oreizy, and Richard N. Taylor, xADL: Enabling Architecture-Centric Tool Integration With XML, in: 34th Annual Hawaii International Conference on System Sciences (HICSS-34), Maui, Hawaii, January 2001; pp. 9053-9061.

• Robert Allen and David Garlan, A Formal Basis for Architectural Connection. ACM Transactions on Software Engineering and Methodology 6 (1997), 213-249.

• Philippe Kruchten, Architectural Blueprints: The 4+1 View Model of Architecture. IEEE Software 12 (1995), (6) 42-50.

• M. Lankhorst (ed.), ArchiMate Language Primer. Report TI/RS/2004/024, Telematica Instituut Enschede, 2004.

Patterns: for architecture, for enterprise applications

• M. Klein, R. Kazman, L. Bass, J. Carriere, M. Barbacci, H. Lipson, Attribute-Based Architecture Styles, in: Proceedings of the First Working IFIP Conference on Software Architecture (WICSA1), San Antonio, TX, February 1999, pp. 225-243.

• Robert T. Monroe, Andrew Kompanek, Ralph Melton, and David Garlan, Architecture Styles, Design Patterns, and Objects. IEEE Software 14 (1997), (1) 43-52.

• Martin Fowler, Domain Logic and SQL. 2003.

• Martin Fowler, Organizing Presentation Logic. 2006.

• Also: Fowler's site on enterprise integration patterns, a case study of their use, and his catalog of enterprise application patterns (follow Catalog link, points to entries in his book), and more recent enterprise application patterns.

• Gregor Hohpe and Bobby Woolf, Solving Integration Problems Using Patterns. 2003.

• Sean Neville, Emerging Standards and Futures in Enterprise Integration. 2003.

Previous year remaining reading material

In previous years (relative to SWA edition 2008/2009) the book by Albin (see books) has been used. References to the relevant chapters are included in this lecture overview.

Component software

• Michi Henning, The Rise and Fall of CORBA. ACM Queue 4 (2006), (5) 2-8.

• G. Vetere and M. Lenzerini, Models for Semantic Interoperability in Service-Oriented Architectures. IBM Systems Journal 44 (2005), 887-903.

• Albin chapter 5

Design by contract

• R. Helm, I.M. Holland, and D. Gangopadhyay, Contracts: Specifying Behavioral Compositions in Object-Oriented Systems, in: Proceedings of the 1990 OOPSLA/ECOOP Conference, Ottawa, Canada, October 1990, pp. 169-180.

• Soon-Kyeong Kim and David Carrington, A Rigorous Foundation for Pattern Based Design Models. In Proceedings of the 4th International Conference on Z and B Users (ZB2005), Formal Specification and Development in Z and B, Guildford, UK, April 2005, LNCS 3455, Springer; pp. 242-261.

• Flavio Oquendo, Formally Modelling Software Architectures with the UML 2.0 Profile for p-ADL. ACM SIGSOFT Software Engineering Notes 31, (2006), (1) 1-13.

• Albin chapter 6

Service-oriented architecture

• Eric Newcomer and Greg Lomow, Introduction to SOA with Web Services. Chapter 1 of Understanding SOA with Web Services. Addison-Wesley Professional, 2005.

• Lee Provoost, A SOA-enabled enterprise content management system. M.Sc. thesis, Utrecht University, 2006.

(Requirements) Change impact analysis, Risk analysis

• Change impact analysis
  • General starting point
  • Book: Software Change Impact Analysis, Robert S. Arnold
• Requirements change impact analysis
  • paper: An Integrated, Probabilistic Framework for Requirement Change Impact Analysis, Simon Lock, Gerald Kotonya
  • paper: Requirements Tracing Strategies for Change Impact Analysis and Re-Testing, Matthias Heindl, Stefan Biffl
  • checklist 1, checklist 2
• Risk analysis
  • At SEI: webinar on risk management (+ links from there)

Project Material

• Templates for various architecture design related activities on RUP op maat.

Submitted Material (2010-2011)

Team	Presentation about system	Presentation about quality aspects/tradeoffs	Paper about architectural findings	Presentation about architectural findings	Review paper
A	talk1-A.pdf	talk2-A.pdf	arch-A.pdf	talk3-A.pdf	review-A-ofB.pdf
B	talk1-B.pdf	talk2-B.pdf	arch-B.pdf	talk3-B.pdf	review-B-ofC.pdf
C	talk1-C.pdf	talk2-C.pdf	arch-C.pdf	talk3-C.pdf	review-C-ofD.pdf
D	talk1-D.pdf	talk2-D.pdf	arch-D.pdf	talk3-D.pdf	review-D-ofE.pdf
E	talk1-E.pdf	talk2-E.pdf	arch-E.pdf	talk3-E.pdf	review-E-ofF.pdf
F	talk1-F.pdf	talk2-F.pdf	arch-F.pdf	talk3-F.pdf	review-F-ofG.pdf
G	talk1-G.pdf	talk2-G.pdf	arch-G.pdf	talk3-G.pdf	review-G-ofA.pdf