A Language for Enterprise Modelling

  • Marc Lankhorst
Part of the The Enterprise Engineering Series book series (TEES)


Architecture provides a means to handle the complexity of modern information-intensive enterprises. To this end, architects need ways to express architectures as clearly as possible: both for their own understanding and for communication with other stakeholders, such as system developers, end users, and managers. Unfortunately, the current situation is that architects in different domains, even within the same organisation, often use their own description techniques and conventions. To date, there is no standard language for describing enterprise architectures in a precise way across domain borders. They are often described either in informal pictures that lack a well-defined meaning, or in detailed design languages (such as UML) that are difficult to understand for non-experts. This frequently leads to misunderstandings that hinder the collaboration of architects and other stakeholders. Also, it makes it very difficult to provide tools for visualisation and analysis of these architectures.


Business Process Application Layer Business Service Enterprise Architecture Business Object 
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.


  1. Buuren R van, Jonkers H, Iacob, M­E, Strating P (2004), Composition of Relations in Enterprise Architecture Models. In Ehrig H et al. (eds.), Graph Transformations, Proc. Second International Conference on Graph Transformation (ICGT 2004), Rome, Italy, LNCS 3256, pp. 39–53. Springer, Berlin.Google Scholar
  2. Crystal D (1997). The Cambridge Encyclopedia of Language (2nd ed.). Cambridge University Press, Cambridge, UK.Google Scholar
  3. Davenport T, Short JE (1990), The New Industrial Engineering: Information Technology and Business Process Redesign, Sloan Management Review, Summer: 309–330.Google Scholar
  4. Eertink H, Janssen W, Oude Luttighuis P, Teeuw W, Vissers C (1999), A Business Process Design Language, Proc. 1st World Congress on Formal Methods, Toulouse, France.Google Scholar
  5. Greefhorst, D, Proper, HA (2011), Architecture Principles: The Cornerstones of Enterprise Architecture. Springer.Google Scholar
  6. Jonkers H, Lankhorst MM, Buuren R van, Hoppenbrouwers S, Bonsangue M, Van der Torre L (2004), Concepts for Modelling Enterprise Architectures, International Journal of Cooperative Information Systems, special issue on Architecture in IT, Vol. 13, No. 3, Sept. 2004, pp. 257–287.CrossRefGoogle Scholar
  7. Object Management Group (2007b), Unified Modeling Language: Superstructure. Version 2.1.2, Final Adopted Specification formal/07-11-02, Object Management Group.
  8. Sowa JF, Zachman JA (1992), Extending and Formalizing the Framework for Information Systems Architecture, IBM Systems Journal, 31(3):590–616.CrossRefGoogle Scholar
  9. Steen MWA, Lankhorst MM, Wetering RG van de (2002), Modelling Networked Enterprises, in Proc. Sixth International Enterprise Distributed Object Computing Conference (EDOC’02), Lausanne, Switzerland, September, pp. 109–119.Google Scholar
  10. The Open Group (2011), The Open Group Architectural Framework (TOGAF) Version 9.1. The Open Group, Reading, UK.
  11. The Open Group (2012), ArchiMate 2.0 Specification, Technical Standard, The Open Group, Reading, UK.
  12. Van Lamsweerde, A. (2004), Goal-Oriented Requirements Engineering: A Roundtrip from Research to Practice. Proceedings of the 12th IEEE International Requirements Engineering Conference, 4–7.Google Scholar
  13. Zachman JA (1987), A Framework for Information Systems Architecture, IBM Systems Journal, 26(3):276–292.CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Marc Lankhorst
    • 1
  1. 1.NovayEnschedeThe Netherlands

Personalised recommendations