Skip to main content

Modelling of Software Architectures: Importance, Notions, Experiences

  • Conference paper

Part of the book series: Informatik-Fachberichte ((INFORMATIK,volume 309))

Abstract

This article is a strong pleading for the importance of architecture modelling, i.e. a careful development and maintenance of software systems, in order to solve the actual software problems, namely maintenance, quality improvement and reuse. This is due to the fact that a software architecture is the “essential” structure of a software system and that most of the software documents are directly or indirectly dependent on this structure.

For denoting software architectures we suggest two different languages: a graphical language for denoting an overview of an architecture (architecture diagram) and a textual language for discribing the details of components as well as relations between components identified in the architecture diagram. The paper sketches the syntax as well as the application of these languages to typical situations within architectures and to complete architectures. Furthermore, the mapping of these languages to relevant programming languages is discussed. Finally, we present some open problems of architecture modelling.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   54.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. W. Altmann: Description of Program Modules for the Design of Reliable Software, Ph. D. Thesis, University of Erlangen, Techn. Report IMMD 11–16 (1978).

    Google Scholar 

  2. B. W. Boehm: Software Lifecycle Factors, in Vick/Ramamoorthy (Eds.): Handbook on Software Engineering, 494–518, New York: van Nostrand Reinhold (1984).

    Google Scholar 

  3. G. Booch: Software Components with Ada, Menlo Park: Benjamin Cummings (1987).

    Google Scholar 

  4. R.J.A. Buhr: System Design with Ada, Englewood Cliffs: Prentice Hall (1984).

    Google Scholar 

  5. B. Cox: Object-oriented Programming — An Evolutionary Approach, Reading: Addison Wesley (1986).

    Google Scholar 

  6. Department of Defense (USA): Reference Manual for the Ada Programming Language, ANSI-MIL-STD 1815 A.

    Google Scholar 

  7. G. Engels/M. Nagl/W. Schafer: On the Structure of Structure-Oriented Editors for Different Applications, in P. Henderson (Ed.), Proc. 2nd ACM Symp. on Pract. Softw. Dev. Env., ACM SIGPLAN Notices 23, 1, 190–198 (1987).

    Google Scholar 

  8. G. Engels/W. Schafer: Program Support Environments, Concepts and Realization (in German), Stuttgart: Teubner-Verlag (1989).

    Google Scholar 

  9. H. Ehrig/H. Weber: Specification of Modular Systems, IEEE Trans, on Softw. Eng. SE-12, 7, 784–789 (1986).

    Google Scholar 

  10. R. Gall: Formal Description of Programming-in-the-Large by Graph Grammars (in German), Ph. D. Thesis, University of Erlangen, Techn. Report IMMD 16–1 (1983).

    Google Scholar 

  11. J.V. Guttag/J.J. Horning/J.M. Wing: The Larch Family of Specification Languages, IEEE Software 2,5, 24–36 (1985).

    Article  Google Scholar 

  12. A. Goldberg/D. Robbson: Smalltalk-80: The Language and its Implementation, Reading: Addison Wesley (1983).

    MATH  Google Scholar 

  13. HOOD Working Group: HOOD Reference Manual, European Space Agency WME 89–173/JB.

    Google Scholar 

  14. H.N. Habermann/D. Perry: Well-formed System Compositions, Technical Report CMU-CS-80–117, Carnegie-Mellon University (1980).

    Google Scholar 

  15. Th. Janning: Ph.D. Thesis forthcoming, RWTH Aachen.

    Google Scholar 

  16. G. Kaiser/D. Garlan: Melding Software Systems from Reusable Building Blocks, IEEE Software, July 87, 17–24.

    Google Scholar 

  17. C. Lewerentz: Interactive Design of Large Program Systems — Concepts and Tools (in German), Ph. D. Thesis RWTH Aachen, lnformatik-Fachberichte 194, Berlin:Springer- Verlag (1988).

    Google Scholar 

  18. C. Lewerentz/M. Nagl: Incremental Programming-in-the-Large: Syntax-aided Specification Editing, Integration and Maintenance, Proc. 18th Hawaii Int. Conf. on System Sciences, 638–649 (1985).

    Google Scholar 

  19. B. Meyer: Genericity versus Inheritance, Proc. OOPSLA ‘86, ACM SIGPLAN Notices 21, 11, 391–405 (1986).

    Article  Google Scholar 

  20. B. Meyer: Object-oriented Software Construction, New York: Prentice Hall (1988).

    Google Scholar 

  21. A.H. Müller: Rigi — A Model for Software System Construction, Integration, and Evolution based on Module Interface Specifications, Ph. D. Thesis, Rice University, Techn. Report COMP.TR 86–36, Houston (1986).

    Google Scholar 

  22. M. Nagl: Introduction to the Programming Language Ada (in German) first and second edition, Braunschweig: Vieweg-Verlag (1982, 1988).

    Google Scholar 

  23. M. Nagl: Software Engineering: Methodological Programming-in-the-Large (in German), Berlin: Springer-Verlag (1990).

    Google Scholar 

  24. Proceedings of the Conferences on Object-oriented Programming Systems, Languages and Applications, OOPSLA ‘86 – ’89, ACM SIGPLAN Notices.

    Google Scholar 

  25. D.L. Parnas: On the Criteria To Be Used in Decomposing Systems into Modules, Comm. ACM 15, 12, 1053–1058 (1972).

    Article  Google Scholar 

  26. C.V. Ramamoorthy et al.: Software Engineering — Problems and Perspectives, Computer 10/84, 191–209 (1984).

    Article  Google Scholar 

  27. W. Swartout/R. Balzer: On the Inevitable Intertwining of Specification and Implementation, Comm. ACM 25, 7, 438–440 (1982).

    Article  Google Scholar 

  28. B. Stroustrup: What is Object-oriented Programming, IEEE Software, May 88, 10–20.

    Google Scholar 

  29. I. Somerville: Interacting with an Active, Integrated Environment, in P. Henderson (Ed.): Proc. 3rd ACM Symp. on Pract. Softw. Dev. Env., ACM Software Eng. Notes 13, 5, 76–84 (1988).

    Google Scholar 

  30. P. Wegner: The object-oriented Classification Paradigm, in P. Wegner/B. Shriver: Research Directions in Object-oriented Programming Cambridge: MIT Press, 479–550 (1987).

    Google Scholar 

  31. B. Westfechtel: Revision Control in an Integrated Development Environment, PH.D. Thesis forthcoming, RWTH Aachen (1990).

    Google Scholar 

  32. M. Zelkowitz et al.: Principles of Software Engineering and Design, Englewood Cliffs: Prentice Hall (1979).

    MATH  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 1992 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Nagl, M. (1992). Modelling of Software Architectures: Importance, Notions, Experiences. In: Kreowski, HJ. (eds) Informatik zwischen Wissenschaft und Gesellschaft. Informatik-Fachberichte, vol 309. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-77449-2_9

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-77449-2_9

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-55389-2

  • Online ISBN: 978-3-642-77449-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics