Using style to understand descriptions of software architecture

ABSTRACT

The software architecture of most systems is described informally and diagrammatically. In order for these descriptions to be meaningful at all, figures are understood by interpreting the boxes and lines in specific, conventionalized ways[5]. The imprecision of these interpretations has a number of limitations. In this paper we consider these conventionalized interpretations as architectural styles and provide a formal framework for their uniform definition. In addition to providing a template for precisely defining new architectural styles, this framework allows for the proof that the notational constraints on a style are sufficient to guarantee the meanings of all described systems and provides a unified semantic base through which different stylistic interpretations can be compared.

REFERENCES

• 1: Robert B. Allen , David Garlan, A Formal Approach to Software Architectures, Proceedings of the IFIP 12th World Computer Congress on Algorithms, Software, Architecture - Information Processing '92, Volume 1, p.134-141, September 07-11, 1992
• 2: Robert Allen , David Garlan, Towards Formalized Software Architectures, Carnegie Mellon University, Pittsburgh, PA, 1992
• 3: Proceedings of the Workshop on Domain-Specijic Software Architeztums (Hidden Valley, PA, July 1990), Software Engineering Institute.
• 4: EARL, A. A reference model for computer assisted software engineering environment frameworks. Tech. Rep. HPL-SEG-TN-90-11, Hewlett Packard Laborat ries, Bristol, England, August 1990.
• 5: Anthony Wasserman, Tutorial on Software Design Techniques, IEEE Computer Society Press, Los Alamitos, CA, 1990
• 6: David Garlan , David Notkin, Formalizing Design Spaces: Implicit Invocation Mechanisms, Proceedings of the 4th International Symposium of VDM Europe on Formal Software Development-Volume I: Conference Contributions, p.31-44, October 21-25, 1991
• 7: David Garlan , Curtis Scott, Adding implicit invocation to traditional programming languages, Proceedings of the 15th international conference on Software Engineering, p.447-455, May 17-21, 1993, Baltimore, Maryland, United States
• 8: GARLAN, D., AND SHAW, M. An introduction to software architecture. In Advances in Software i?ngineering and Knowledge Engineering, Volume 1 (New Jersey, 1993), V. Ambriola and G. Tortora, Eels., World Scientific Publishing Company.
• 9: LUCKHAiM, D. C., AND VERA, J. Event-based concepts and language for system architecture. Working draft, October 1992.
• 10: METTALA, E., AND GRAHAM, M. H. The domainspecific software architecture program. Tech. Rep. CMU/SEI-92-SR-9, Carnegie MeUon Software Engineering Institute, June 1992.
• 11: Steven P. Reiss, Connecting Tools Using Message Passing in the Field Environment, IEEE Software, v.7 n.4, p.57-66, July 1990 [doi>10.1109/52.56450]
• 12: J. M. Spivey, The Z notation: a reference manual, Prentice-Hall, Inc., Upper Saddle River, NJ, 1989
• 13: Kevin J. Sullivan , David Notkin, Reconciling environment integration and software evolution, ACM Transactions on Software Engineering and Methodology (TOSEM), v.1 n.3, p.229-268, July 1992 [doi>10.1145/131736.131744]

INDEX TERMS

Primary Classification:
  D. Software
  D.1 PROGRAMMING TECHNIQUES
      D.1.0 General

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.10 Design**

General Terms:
Design, Languages, Theory