Foundations for the study of software architecture

ABSTRACT

The purpose of this paper is to build the foundation for software architecture. We first develop an intuition for software architecture by appealing to several well-established architectural disciplines. On the basis of this intuition, we present a model of software architecture that consists of three components: elements, form, and rationale. Elements are either processing, data, or connecting elements. Form is defined in terms of the properties of, and the relationships among, the elements --- that is, the constraints on the elements. The rationale provides the underlying basis for the architecture in terms of the system constraints, which most often derive from the system requirements. We discuss the components of the model in the context of both architectures and architectural styles and present an extended example to illustrate some important architecture and style considerations. We conclude by presenting some of the benefits of our approach to software architecture, summarizing our contributions, and relating our approach to other current work.

REFERENCES

• 1: G S Avrunin , L K Dillon , J C Wileden , W E Riddle, Constrained expressions: Adding analysis capabilities to design methods for concurrent software systems, IEEE Transactions on Software Engineering, v.12 n.2, p.278-292, Feb. 1986
• 2: Jon Louis Bentley, Writing efficient programs, Prentice-Hall, Inc., Upper Saddle River, NJ, 1982
• 3: [3] G.D. Bergland, A Guided Tour of Program Design Methodologies, IEEE Computer, Vol. 14, No. 10, Oct. 1981, pp. 13-37.
• 4: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 5: Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Softw, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1978
• 6: Roy H. Campbell , A. Nico Habermann, The specification of process synchronization by path expressions, Operating Systems, Proceedings of an International Symposium, p.89-102, April 23-25, 1974
• 7: Elliott J. Chikofsky, Computer-Aided Software Engineering (Case), IEEE Computer Society Press, Los Alamitos, CA, 1994
• 8: G Estrin , R S Fenchel , R R Razouk , M K Vernon, SARA (system architects apprentice): modeling, analysis, and simulation support for design of concurrent systems, IEEE Transactions on Software Engineering, v.12 n.2, p.293-311, Feb. 1986
• 9: Anthony Wasserman, Tutorial on Software Design Techniques, IEEE Computer Society Press, Los Alamitos, CA, 1990
• 10: D. Jackson, COMPOSING DATA & PROCESS DESCRIPTIONS IN THE DESIGN OF SOFTWARE SYSTEMS, Massachusetts Institute of Technology, Cambridge, MA, 1988
• 11: [11] F.C. Mish, Webster's Ninth New Collegiate Dictionary, Merriam Webster, Springfield, MA, 1983.
• 12: J. E Moss , Alexander L. Wolf, Toward Principles of Inheritance and Subtyping in Programming Languages, University of Massachusetts, Amherst, MA, 1988
• 13: John D. Musa , Anthony Iannino , Kazuhira Okumoto, Software reliability: measurement, prediction, application (professional ed.), McGraw-Hill, Inc., New York, NY, 1989
• 14: Dewayne E. Perry, The inscape environment, Proceedings of the 11th international conference on Software engineering, p.2-11, May 1989, Pittsburgh, Pennsylvania, United States [doi>10.1145/74587.74588]
• 15: [15] D.E. Perry, Industrial Strength Software Development Environments, Proc. IFIP Congress '89, The 11th World Computer Congress, San Francisco, CA, Aug. 1989.
• 16: James L. Peterson, Petri Nets, ACM Computing Surveys (CSUR), v.9 n.3, p.223-252, Sept. 1977 [doi>10.1145/356698.356702]
• 17: [17] W.E. Riddle and J.C. Wileden, Tutorial on Software System Design: Description and Analysis, Computer Society Press, 1980.
• 18: W. R. Rosenblatt , J. C. Wileden , Alexander L. Wolf, OROS: toward a type model for software development environments, Conference proceedings on Object-oriented programming systems, languages and applications, p.297-304, October 02-06, 1989, New Orleans, Louisiana, United States
• 19: Erik Sandewall , Claes Strömberg , Henrik Sörensen, Software architecture based on communicating residential environments, Proceedings of the 5th international conference on Software engineering, p.144-152, March 09-12, 1981, San Diego, California, United States
• 20: R. W. Schwanke , R. Z. Altucher , M. A. Platoff, Discovering, visualizing, and controlling software structure, Proceedings of the 5th international workshop on Software specification and design, p.147-154, April 1989, Pittsburgh, Pennsylvania, United States
• 21: [21] M. Shaw, Larger Scale Systems Require Higher-Level Abstractions, Proc. Fifth Inter. Workshop on Software Specification and Design, Pittsburgh, PA, May 1989, appearing in ACM SIGSOFT Notes, Vol. 14, No. 3, May 1989, pp. 143-146.
• 22: A. Z. Spector, Invited talk: modular architectures for distributed and databases systems, Proceedings of the eighth ACM SIGACT-SIGMOD-SIGART symposium on Principles of database systems, p.217-224, March 1989, Philadelphia, Pennsylvania, United States [doi>10.1145/73721.73743]
• 23: John A. Zachman, A framework for information systems architecture, IBM Systems Journal, v.26 n.3, p.276-292, 1987

INDEX TERMS

Primary Classification:
  D. Software

General Terms:
Design, Theory