This overview contains German- and English-language references. These are referenced in both the German and English curricula. German references are denoted using the [DE] addendum.
[ARC42] The arc42 Template. https://arc42.org/.
[Bal00] [DE] Balzert, H.: Lehrbuch der Software-Technik – Software-Entwicklung. 2. Aufl., Spektrum Akademischer Verlag, Heidelberg, 2000.
[BCK03] Bass, L.; Clements, P.; Kazmann, R.: Software Architecture in Practice. 2nd ed., Addison-Wesley Professional, 2003.
[BJ+06] [DE] Broy, M. et al.: Dagstuhl-Manifest zur Strategischen Bedeutung des Software Engineering in Deutschland. Dagstuhl Seminar Proceedings, 2006. http://drops.dagstuhl.de/opus/volltexte/2006/585.
[BM00] [DE] Bundesministerium für Bildung und Forschung (BMBF): Analyse und Evaluation der Softwareentwicklung in Deutschland, 2000. https://www.iese.fraunhofer.de/content/dam/iese/de/documents/Softwareentwicklung_Deutschland_Evasoft_tcm122-7431.pdf.
[BM++96] Buschmann, F.; Meunier, R.; Rohnert, H.; Sommerlad, P.: A System of Patterns: Pattern-Oriented Software Architecture, Volume 1. John Wiley & Sons, 1996.
[BW97] Buchi, M.; Weck, W.: A Plea for Gray-Box Components. Turku Centre for Computer Science, 1997.
[CB++10] Clements, P.; Bachmann, F.; Bass, L.; Garlan, D.; Ivers, J.; Little, R.; Merson, P.; Nord, R.; Stafford, J.: Documenting Software Architectures: Views and Beyond. 2nd ed., Addison-Wesley, 2010.
[CKH05] [DE] Conrad, S.; Koschel, A., Hasselbring, W.: Enterprise Application Integration. Spektrum Akademischer Verlag, Heidelberg, 2005.
[CKK02] Clements, P.; Kazman, R.; Klein, M.: Evaluating Software Architectures – Methods and Case Studies. Addison-Wesley Professional, 2002.
[Clem03] Clements, P.: Documenting software architectures: views and beyond. Addison-Wesley, 2003.
[CoCoME] Modelling Contest: Common Component Modelling Example (CoCoME). GI-Dagstuhl Research Seminar. http://www.cocome.org.
[DE++09] [DE] Dunkel, J.; Eberhardt, A.; Fischer, F.; Kleiner, C.; Koschel, A.: Systemarchitekturen für Verteilte Anwendungen, Hanser Verlag, München, 2009.
[Die00] [DE] Diethelm, G.: Projektmanagement, Bd. 1: Grundlagen. NW Verlag, Berlin, 2000.
[Dij72] Dijkstra, E. W.: The humble programmer. Communications of the ACM CACM, Vol. 15, Issue 10, Oct., pp. 859–866, 1972.
[D’SW98] D’Souza, D. F.: Objects, Components, and Frameworks with UML: The Catalysis Approach. Addison-Wesley Professional, 1998.
[Dum01] [DE] Dumke, R.: Software Engineering: Eine Einführung für Informatiker und Ingenieure. 3. Aufl., Vieweg, Braunschweig, Wiesbaden, 2001.
[Eel05] Eeles, P.: Capturing Architectural Requirements, IBM, 2005. http://www.ibm.com/developerworks/rational/library/4706.html.
[EH+08] [DE] Engels, G.; Hess, A.; Humm, B.; Juwig, O.: Quasar Enterprise – Anwendungslandschaften serviceorientiert gestalten. dpunkt.verlag, Heidelberg, 2008.
[EK08] El Emam, K.; Koru, A. G.: A Replicated Survey of IT Software Project Failures. IEEE Software, Vol. 25, No. 5, pp. 84–90, 2008.
[ES10] [DE] Eilebrecht, K.; Starke, G.: Patterns kompakt: Entwurfsmuster für effektive Software-Entwicklung. 3. Aufl., Spektrum Akademischer Verlag, Heidelberg, 2010.
[EV10] Eveleens, J. L.; Verhoef, C.: The Rise and Fall of the Chaos Report Figures. IEEE Software, Vol. 27, No. 1, pp. 30–36, 2010.
[Eva04] Evans, E.: Domain Driven Design. Addison-Wesley, 2004. http://dddcommunity.org/book/evans_2003/.
[Fow99] Fowler, M.: Refactoring – Improving the Design of Existing Code. Addison-Wesley, 1999.
[Fow03] Fowler, M.: Patterns of Enterprise Application Architecture. Addison-Wesley, Boston, 2003.
[GB03] Ganssle, J.; Barr, M.: Embedded Systems Dictionary. 2003.
[GEM04] Grünbacher, P.; Egyed, A.; Medvidovic, N.: Reconciling software requirements and architectures with intermediate models. Software and System Modeling 3(3), pp. 235–253, 2004.
[GHJ94] Gamma, E.; Helm, R.; Johnson, R. E.: Design Patterns. Elements of Reusable Object-Oriented Software. Addison-Wesley Longman, Amsterdam, 1994.
[HM+07] Herold, S.; Metzger, A.; Stallbaum, H.; Rausch, A.: Towards Bridging the Gap between Goal-Oriented Requirements Engineering and Compositional Architecture Development. Proc. of the Second Workshop on Sharing and Reusing Architectural Knowledge – Architecture, Rationale, and Design Intent. ICSE 2007, Minneapolis, May 2007.
[HNS99] Hofmeister, C.; Nord, R.; Soni, D.: Applied Software Architecture. Addison-Wesley Professional, 1999.
[HS11] [DE] Hruschka P.; Starke, G.: arc42 – Ressourcen für Software-Architekten, 2011. http://www.arc42.de.
[isaqb-curriculum] International Software Architecture Qualification Board e. V. (iSAQB), Downloads Documents. https://www.isaqb.org/wp-content/uploads/2017/11/isaqb-Curriculum-foundation-v4-1-1-2017-EN_new.pdf.
[isaqb-PuB_2017] Examination Rules and Examples – Certified Professional for Software Architecture Foundation Level. International Software Architecture Qualification Board e. V., Version: 1.5. 2017-11-27. https://www.isaqb.org/wp-content/uploads/2017/11/iSAQB_CPSA_Foundation_Examination_Guide_EN_1.5.pdf.
[Kru95] Kruchten, P.: Architectural Blueprints – The “4+1” View Model of Software Architecture. IEEE Software 12 (6), Nov., pp. 42–50, 1995.
[Lit05] [DE] Litke, H.-D. (Hrsg.): Projektmanagement – Handbuch für die Praxis. Hanser Verlag, München, 2005.
[Mar03] Martin, R.C.: Agile Software Development, Principles, Patterns, and Practices. Pearson Education, Upper Saddle River, 2003.
[May05] [DE] Mayr, H.: Projekt Engineering: Ingenieurmäßige Softwareentwicklung in Projektgruppen. 2. Aufl., Fachbuchverlag, Leipzig, 2005.
[McC76] McCabe, T. J.: A Complexity Measure. IEEE Transactions on Software Engineering, Vol. SE-2, pp. 308–320, 1976.
[MDA Guide 2.0] Object Management Group: Model Driven Architecture (MDA): The MDA Guide rev. 2.0, http://www.omg.org/mda.
[Mey88] Meyer, B.: Object Oriented Software Construction. Prentice Hall, 1988.
[MRW77] McCall, J. A.; Richards, P. K.; Walters, G. F.: Factors in Software Quality, Vol. I–III, Rome Air Development Centre. Technical Report, New York, 1977.
[NSPE] NSPE Code of Ethics for Engineers. http://www.nspe.org/Ethics/CodeofEthics/index.html.
[Nus01] Nuseibeh, B.: Weaving the Software Development Process Between Requirements and Architecture. Proc. of ICSE 2001 Workshop STRAW-01, Toronto, May 2001.
[OS13] [DE] Oestereich, B.; Scheithauer, A.: Analyse und Design mit UML 2.5: Objektorientierte Softwareentwicklung. 11. Aufl., Oldenbourg Verlag, München, 2013.
[O’RF+03] O’Rourke, C.; Fishman, N.; Selkow, W.: Enterprise Architecture Using the Zachman Framework. Course Technology, 2003.
[PR15] Pohl, K.; Rupp, C.: Requirements Engineering Fundamentals: A Study Guide for the Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant. 2nd ed., Rocky Nook, San Rafael, CA, 2015.
[Reu12] Reuters, T.: Web of Knowledge. www.knowledge.reuters.com.
[RH06] [DE] Reussner, R.; Hasselbring, W. (Hrsg.): Handbuch der Software-Architektur, dpunkt.verlag, Heidelberg, 2006.
[RM-ODP] RM-ODP Wiki. https://en.wikipedia.org/wiki/RM-ODP.
[RQ+12] [DE] Rupp, C.; Queins, S.: UML 2 glasklar: Praxiswissen für die UML-Modellierung. 4. Aufl., Hanser Verlag, München, 2012.
[RR++08] Rausch, A.; Reussner, R.; Mirandola, R.; Plásil, F.: The Common Component Modeling Example. LNCS 5153, Springer-Verlag, Heidelberg, Berlin, 2008.
[SAGA08] [DE] Standards und Architekturen für E-Government-Anwendungen (SAGA), Bundesministerium des Innern (BMI), Version 4.0, Stand: März 2008.
[SD00] [DE] Siedersleben, J.; Denert, E.: Wie baut man Informationssysteme? Überlegungen zur Standardarchitektur. Informatik Spektrum, Vol. 23, No. 4, S. 247–257, 2000. http://www.springerlink.com/content/jdfaxdb44n15levh.
[SEI Def] Software Architecture, Community Software Architecture Definitions. http://www.sei.cmu.edu/architecture/start/glossary/community.cfm.
[Sie03] [DE] Siedersleben, J. (Hrsg.): Quasar: Die sd&m Standardarchitektur, Teil I. https://docplayer.org/19346553-Quasar-quasar-die-sd-m-standardarchitektur-teil-1-johannes-siedersleben-hrsg.html.
[Sie04] [DE] Siedersleben, J.: Moderne Softwarearchitektur – Umsichtig planen, robust bauen mit Quasar. dpunkt.verlag, Heidelberg, 2004.
[Sta15] [DE] Starke, G.: Effektive Softwarearchitekturen: Ein praktischer Leitfaden. 7. Aufl., Hanser Verlag, München, 2015.
[Sta99] Standish Group International, Inc.: CHAOS: A Recipe for Success, 1999.
[SV99] Sharipo, C.; Varian, H. R.: Information Rules. A Strategic Guide to the Network Economy. Harvard Business School Press, Boston, Mass., 1999.
[Szy98] Szyperski, C.: Component Software: Beyond Object-oriented Programming. Addison-Wesley Longman, Amsterdam, 1998.
[TOGAF] TOGAF Version 9.2 “Enterprise Edition”. http://www.opengroup.org/togaf.
[TT+00] Tapscott, D.; Ticoll, D.; Lowry, A.: Digital Capital. Harnessing the Power of Business Webs. Harvard Business School Press, Boston, Mass., 2000.
[UML-1a] UML-Specification: http://www.omg.org/technology/documents/formal/uml.htm.
[UML-1b] Object Management Group (OMG), UML 2.3 Infrastructure Specification, 2010. http://www.omg.org/spec/UML/2.3/Infrastructure/PDF.
[UML-1c] Object Management Group (OMG), UML 2.3 Superstructure Specification, 2010. http://www.omg.org/spec/UML/2.3/Superstructure/PDF.
[VA++09] [DE] Vogel, O.; Arnold, I.; Chughtai, A.; Ihler, E.; Kehrer, T.; Mehlig, U.; Zdun, D.: Software-Architektur, Grundlagen – Konzepte – Praxis. 2. Aufl., Spektrum Akademischer Verlag, Heidelberg, 2009.
[Vit60] Vitruvius: The Ten Books on Architecture. Dover Publications, 1960.
www.ireb.org International Requirements Engineering Board e.V. (IREB)
www.isaqb.org International Software Architecture Qualification Board e.V. (iSAQB)
www.istqb.org International Software Testing Qualifications Board (ISTQB)
www.pmi.org Project Management Institute (PMI)
[DIN 55350-11:2008-05] DIN 55350-11:2008-05– Concepts for quality management - Part 11: Supplement to DIN EN ISO 9000:2005.
[DIN 66272, 1994-10] DIN 66272, 1994-10 – Information technology – Software product evaluation – Quality characteristics and guidelines for their use.
[IEEE 610.12-1990] IEEE Standard Glossary of Software Engineering Terminology, http://standards.ieee.org/findstds/standard/610.12-1990.html.
[ISO/IEC 9126] ISO/IEC 9126-1:2001 Software engineering – Product quality – Part 1: Quality model (identical with [DIN 66272, 1994-10], Information technology – Software product evaluation – Quality characteristics and guidelines for their use).
ISO/IEC TR 9126-2:2003 Software engineering – Product quality – Part 2: External metrics.
ISO/IEC TR 9126-3:2003 Software engineering – Product quality – Part 3: Internal metrics.
[ISO/IEC 25010] ISO/IEC 25010:2011 Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – System and software quality models.
[ISO/IEC/IEEE 42010:2011] ISO/IEC/IEEE 42010:2011 – Systems and software engineering – Architecture description.