Advertisement

Agile Architecture

  • M. M. Lankhorst
  • H. A. Proper
Chapter
Part of the The Enterprise Engineering Series book series (TEES)

Abstract

In this chapter, we will elaborate on the use of architecture in relation to agility. We start by clarifying what we mean by ‘architecture’ and ‘enterprise architecture’, since these notions are used in various ways within our field. Next, we explain what the roles of architecture can be: on the one hand, it can be used explicitly to design agile systems; on the other hand, it helps an organization to control agility and to keep a balance between stability and change. Finally, we outline how architecture processes fit within an agile context.

Keywords

Business Process Enterprise Architecture Architecture Process Agile Method Agile Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. Amdahl GM, Blaauw GM, Brooks FP (1964) Architecture of the IBM System/360. IBM J Res Dev 8(2):87–101CrossRefGoogle Scholar
  2. Conway ME (1968) How do committees invent? Datamation 14(5):28–31Google Scholar
  3. Cunningham W (1992) The WyCash portfolio management system. http://c2.com/doc/oopsla92.html. Retrieved 21 Jul 2011
  4. Dietz JLG (2006) Enterprise ontology: theory and methodology. Springer, BerlinCrossRefGoogle Scholar
  5. Fehskens L (2008) Re-thinking architecture—the architecture of enterprise architecture. In: 20th Enterprise architecture practitioners conference, The Open Group, Reading, UKGoogle Scholar
  6. Fowler M (1999) Refactoring: improving the design of existing code. Addison-Wesley, Boston, MAGoogle Scholar
  7. Govers MJG (2003) Met ERP-systemen op weg naar moderne bureaucratieën? PhD Thesis, Radboud University NijmegenGoogle Scholar
  8. Govers MJG, Südmeier P (2011) De Sitter in het informatietijdperk. Management en Organisatie 65(2):31–45Google Scholar
  9. Greefhorst D, Proper E (2011) Architecture principles—the cornerstones of enterprise architecture. Springer, HeidelbergGoogle Scholar
  10. IEEE Computer Society (2000) IEEE recommended practice for architecture description of software-intensive systems, IEEE Std 1471-2000. IEEE, New YorkGoogle Scholar
  11. ISO/IEC/IEEE (2011) Systems and software engineering—architecture description, ISO/IEC/IEEE FDIS 42010:2011. International Organization for Standardization, GenevaGoogle Scholar
  12. Lankhorst M et al (2009a) Enterprise architecture at work: modelling, communication and analysis, 2nd edn. Springer, BerlingCrossRefGoogle Scholar
  13. Lankhorst M et al (2009b) Enterprise architecture at work, 2nd edn. Springer, BerlinCrossRefGoogle Scholar
  14. Meyer B (1991) Design by contract. In: Mandrioli D, Meyer B (eds) Advances in object-oriented software engineering. Prentice Hall, Englewood Cliffs, NJ, pp 1–50Google Scholar
  15. Op‘t Land M, Proper E, Waage M, Cloo J, Steghuis C (2009) Enterprise architecture: creating value by informed governance. Springer, BerlinGoogle Scholar
  16. Ross JW, Weill P, Robertson DC (2006) Enterprise architecture as strategy: creating a foundation for business execution. Harvard Business School Press, Boston, MAGoogle Scholar
  17. The Open Group (2011) The open group architectural framework (TOGAF) version 9.1 ‘Enterprise edition’. The Open Group, Reading, UK, http://www.opengroup.org/togaf/ Google Scholar
  18. The Open Group (2012) ArchiMate 2.0 specification, technical standard. The Open Group, Reading, UK, http://www.opengroup.org/archimate/ Google Scholar
  19. Wagter R, van den Berg M, Luijpers J, van Steenbergen M (2005) Dynamic enterprise architecture—how to make it work. Wiley, Hoboken, NJGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • M. M. Lankhorst
    • 1
  • H. A. Proper
    • 2
    • 3
  1. 1.NovayEnschedeThe Netherlands
  2. 2.CRP Henri TudorLuxembourgLuxembourg
  3. 3.Radboud University NijmegenNijmegenThe Netherlands

Personalised recommendations