Orthographic Software Modeling: A Practical Approach to View-Based Development

  • Colin Atkinson
  • Dietmar Stoll
  • Philipp Bostan
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 69)


Although they are significantly different in how they decompose and conceptualize software systems, one thing that all advanced software engineering paradigms have in common is that they increase the number of different views involved in visualizing a system. Managing these different views can be challenging even when a paradigm is used independently, but when they are used together the number of views and inter-dependencies quickly becomes overwhelming. In this paper we present a novel approach for organizing and generating the different views used in advanced software engineering methods that we call Orthographic Software Modeling (OSM). This provides a simple metaphor for integrating different development paradigms and for leveraging domain specific languages in software engineering. Development environments that support OSM essentially raise the level of abstraction at which developers interact with their tools by hiding the idiosyncrasies of specific editors, storage choices and artifact organization policies. The overall benefit is to significantly simplify the use of advanced software engineering methods.


Atlas Transformation Language Product Line Engineering Storage Choice Platform Independent Model Mobile Tourist 
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. 1.
    Atkinson, C., Bayer, J., Bunse, C., Kamsties, E., Laitenberger, O., Laqua, R., Muthig, D., Paech, B., Wüst, J., Zettel, J.: Component-Based Product Line Engineering with UML. Addison-Wesley Publishing Company, Reading (2002)CrossRefGoogle Scholar
  2. 2.
    Atkinson, C., Bostan, P., Brenner, D., Falcone, G., Gutheil, M., Hummel, O., Juhasz, M., Stoll, D.: Modeling Components and Component-Based Systems in KobrA. In: Rausch, A., Reussner, R., Mirandola, R., Plášil, F. (eds.) The Common Component Modeling Example. LNCS, vol. 5153, pp. 54–84. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  3. 3.
    Szyperksi, C., Gruntz, D., Murer, S.: Component-Software – Beyond Object-oriented Programming, 2nd edn. Addison Wesley / ACM Press (2002)Google Scholar
  4. 4.
    Object Management Group: Object Constraint Language Specification, Version 2.0 (May 2006),
  5. 5.
    Finkelstein, A., Kramer, J., Goedicke, M.: ViewPoint Oriented Software Development. In: Proc. of 3rd Int. Workshop on Software Engineering and its Applications, Toulouse (1990)Google Scholar
  6. 6.
    Eclipse Development Platform (visited May 2008),
  7. 7.
    The ATLAS Transformation Language (Visited May 2008),
  8. 8.
    Object Management Group, Human-Usable Textual Notation, v1.0 (April 2008),
  9. 9.
    MagicDraw (Visited May 2008),
  10. 10.
    Glinz, M., Berner, S., Joos, S.: Object-oriented Modeling with Adora. Information Systems 27(6), 425–444 (2002), CrossRefzbMATHGoogle Scholar
  11. 11.
    Zachman, J.A.: The Zachman Framework: A Primer for Enterprise Engineering and Manufacturing (Visited September 2009),
  12. 12.
    ISO/IEC and ITU-T. The Reference Model of Open Distributed Processing. RM-ODP, ITU-T Rec. X.901-X.904 / ISO/IEC 10746 (1998)Google Scholar
  13. 13.
    Romero, J.R., Jaen, J.J., Vallecillo, A.: Realizing Correspondences in MultiViewpoint Specications. In: Proceedings of the Thirteenth IEEE International EDOC Conference, Auckland, New Zealand (September 2009)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Colin Atkinson
    • 1
  • Dietmar Stoll
    • 1
  • Philipp Bostan
    • 1
  1. 1.Institute of Computer ScienceUniversity of MannheimMannheimGermany

Personalised recommendations