An Information Model for Landscape Management – Discussing Temporality Aspects

  • Sabine Buckl
  • Alexander Ernst
  • Florian Matthes
  • Christian M. Schweda
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5472)


Planning, managing, and maintaining the evolution of the application landscape is a focal point of enterprise architecture (EA) management. Whereas, planning the evolution of business support provided by the business applications is understood as one challenge to be addressed in landscape management, another challenge arises in the context of traceability of management decisions.

This paper discusses the requirements regarding support for landscape management as risen by practitioners from industry, gathered in an extensive survey during which the tool support for EA management was analyzed. Thereby, a lack of support for this management discipline was discovered, which is caused by the way, application landscapes are modeled in tools. We subsequently discuss how to incorporate these requirements into an information model.


EA management modeling temporality historization 


  1. 1.
    Buckl, S., Ernst, A., Lankes, J., and Matthes, F.: Enterprise Architecture Management Pattern Catalog (Version 1.0, February 2008). Technical Report TB 0801, Chair for Informatics 19, Technische Universität München, (2008)Google Scholar
  2. 2.
    Lankhorst, M., et al.: Enterprise Architecture at Work – Modelling, Communication, and Analysis. Springer, Heidelberg (2005)Google Scholar
  3. 3.
    Winter, R., Bucher, T., Fischer, R., Kurpjuweit, S.: Analysis and Application Scenarios of Enterprise Architecture – An Exploratory Study. Journal of Enterprise Architecture 33, 33–43 (2007)Google Scholar
  4. 4.
    The Open Group: The Open Group Architectural Framework Version 8.1.1 (cited 2008-10-03),
  5. 5.
    Dern, G.: Management von IT Architekturen (Edition CIO). Vieweg, Wiesbaden (2006)Google Scholar
  6. 6.
    Fischer, R., Aier, S., Winter, R.: Enterprise Modelling and Information Systems Architectures. In: Proceedings of the 2nd International Workshop EMISA 2007, St. Goar, Rhine (2007)Google Scholar
  7. 7.
    Lankes, J., Schweda, C.: Using Metrics to Evaluate Failure Propagation in Application Landscapes. In: Multikonferenz Wirtschaftsinformatik (MKWI) 2008, München (2008)Google Scholar
  8. 8.
    Deming, W.: Out of the Crisis. Massachusetts Institute of Technology, Cambridge (1982)Google Scholar
  9. 9.
    Shewart, W.: Statistical Method from the Viewpoint of Quality Control. Dover Publication, New York (1986)Google Scholar
  10. 10.
    Braun, C., Winter, R.: A Comprehensive Enterprise Architecture Metamodel and Its Implementation Using a Metamodeling Platform. In: Desel, J., Frank, U. (eds.) Gesellschaft für Informatik 2005, Bonn (2005)Google Scholar
  11. 11.
    van der Torre, L., Lankhorst, M., ter Doest, H., Campschroer, J., Arbab, F.: Landscape Maps for Enterprise Architectures. In: Dubois, E., Pohl, K. (eds.) CAiSE 2006. LNCS, vol. 4001, pp. 351–366. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  12. 12.
    Garg, A., Kazman, R., Chen, H.-M.: Interface descriptions for enterprise architecture. Science of Computer Programming 61, 4–15 (2006)MathSciNetCrossRefGoogle Scholar
  13. 13.
    Engels, G., Hess, A., Humm, B., Juwig, O., Lohmann, M., Richter, J.-P., Voss, M., Willkomm, J.: Quasar Enterprise – Anwendungslandschaften serviceorientiert gestalten. dpunkt Verlag, Heidelberg (2008)Google Scholar
  14. 14.
    Matthes, F., Buckl, S., Leitel, J., Schweda, C.: Enterprise Architecture Management Tool Survey 2008. TU München, Chair for Informatics 19 (sebis), Munich (2008)Google Scholar
  15. 15.
    Aier, S., Schönherr, M.: Enterprise Application Integration – Flexibilisierung komplexer Unternehmensarchitekturen. Gito, Berlin (2007)Google Scholar
  16. 16.
    Krcmar, H.: Informations management, 4th edn. Springer, Berlin (2005)Google Scholar
  17. 17.
    Date, C.: An Introduction to Database Systems. Addison Wesley, Boston (2000)Google Scholar
  18. 18.
    Snodgrass, R.: Developing Time-Oriented Database Applications in SQL. Morgan Kaufmann Publishers, San Francisco (2000)Google Scholar
  19. 19.
    Anderson, F.: A Collection of History Patterns. In: Harrison, N., Foote, B., Rohnert, H. (eds.) Pattern Languages of Program Design. Addison Wesley, Boston (1999)Google Scholar
  20. 20.
    Carlson, A., Estepp, S., Fowler, M.: Temporal Patterns. In: Harrison, N., Foote, B., Rohnert, H. (eds.) Pattern Languages of Program Design. Addison Wesley, Boston (1999)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Sabine Buckl
    • 1
  • Alexander Ernst
    • 1
  • Florian Matthes
    • 1
  • Christian M. Schweda
    • 1
  1. 1.Institute for InformaticsTechnische Universität MünchenGarchingGermany

Personalised recommendations