Analyzing architectural styles with alloy

ABSTRACT

The backbone of many architectures is an architectural style that provides a domain-specific design vocabulary and set of constraints on how that vocabulary can be used. Hence, designing a sound and appropriate architectural style becomes an important and intellectually challenging activity. Unfortunately, although there are numerous tools to help in the analysis of individual architectures, relatively less work has been done on tools to help the style designer. In this paper we show how to map an architectural style, expressed formally in an architectural description language, into a relational model that can be automatically checked for properties such as whether a style is consistent, whether a style satisfies some predicate over the architectural structure, whether two styles are compatible for composition, and whether one style refines another.

REFERENCES

• 1: Gregory D. Abowd , Robert Allen , David Garlan, Formalizing style to understand descriptions of software architecture, ACM Transactions on Software Engineering and Methodology (TOSEM), v.4 n.4, p.319-364, Oct. 1995 [doi>10.1145/226241.226244]
• 2: Robert Allen , David Garlan, A formal basis for architectural connection, ACM Transactions on Software Engineering and Methodology (TOSEM), v.6 n.3, p.213-249, July 1997 [doi>10.1145/258077.258078]
• 3: Daniel J. Barrett , Lori A. Clarke , Peri L. Tarr , Alexander E. Wise, A framework for event-based software integration, ACM Transactions on Software Engineering and Methodology (TOSEM), v.5 n.4, p.378-421, Oct. 1996 [doi>10.1145/235321.235324]
• 4: Frank Buschmann , Regine Meunier , Hans Rohnert , Peter Sommerlad , Michael Stal, Pattern-oriented software architecture: a system of patterns, John Wiley & Sons, Inc., New York, NY, 1996
• 5: Sagar Chaki , Alex Groce , Ofer Strichman, Explaining abstract counterexamples, Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering, October 31-November 06, 2004, Newport Beach, CA, USA
• 6: Paul Clements , David Garlan , Len Bass , Judith Stafford , Robert Nord , James Ivers , Reed Little, Documenting Software Architectures: Views and Beyond, Pearson Education, 2002
• 7: P. Clements, R. Kazman, and M. Klein. Evaluating Software Architectures: Methods and Case Studies. Addison Wesley Longman, 2001.
• 8: The Common Object Request Broker: Architecture and specification. OMG Document Number 91.12.1, December 1991. Revision 1.1 (Draft 10).
• 9: Compositional Generation of Software Architecture Performance QN Models, Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA'04), p.37, June 12-15, 2004
• 10: J. Dingel, D. Garlan, S. Jha, and D. Notkin. Towards a formal treatment of implicit invocation. Formal Aspects of Computing, 10:193--213, 1998.
• 11: D. Dvorak and K. Reinholtz. Separating essential from incidentals, an execution architecture for real-time control systems. In Proc. 7th IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, Austria, 2004.
• 12: David Garlan , Robert Allen , John Ockerbloom, Exploiting style in architectural design environments, Proceedings of the 2nd ACM SIGSOFT symposium on Foundations of software engineering, p.175-188, December 06-09, 1994, New Orleans, Louisiana, United States
• 13: David Garlan , Robert Monroe , David Wile, Acme: an architecture description interchange language, Proceedings of the 1997 conference of the Centre for Advanced Studies on Collaborative research, p.7, November 10-13, 1997, Toronto, Ontario, Canada
• 14: Paola Inverardi , Massimo Tivoli, Deadlock-free software architectures for COM/DCOM applications, Journal of Systems and Software, v.65 n.3, p.173-183, 15 March 2003 [doi>10.1016/S0164-1212(02)00037-7]
• 15: Paola Inverardi , Alexander L. Wolf, Formal Specification and Analysis of Software Architectures Using the Chemical Abstract Machine Model, IEEE Transactions on Software Engineering, v.21 n.4, p.373-386, April 1995 [doi>10.1109/32.385973]
• 16: Daniel Jackson, Alloy: a lightweight object modelling notation, ACM Transactions on Software Engineering and Methodology (TOSEM), v.11 n.2, p.256-290, April 2002 [doi>10.1145/505145.505149]
• 17: Gabor Karsai , Janos Sztipanovits, A Model-Based Approach to Self-Adaptive Software, IEEE Intelligent Systems, v.14 n.3, p.46-53, May 1999 [doi>10.1109/5254.769884]
• 18: J. S. Kim and D. Garlan. Automating the analysis of architectural styles. Technical Report CMU-ISRI-06-106, Carnegie Mellon University, 2006.
• 19: Jeff Magee , Jeff Kramer, Concurrency: state models & Java programs, John Wiley & Sons, Inc., New York, NY, 2000
• 20: Nenad Medvidovic , Richard N. Taylor, A Classification and Comparison Framework for Software Architecture Description Languages, IEEE Transactions on Software Engineering, v.26 n.1, p.70-93, January 2000 [doi>10.1109/32.825767]
• 21: S. Microsystems. J2ee information site. URL: http://java.sun.com/javaee/.
• 22: OMG. Unified modeling language. URL: http://www.uml.info/.
• 23: Dewayne E. Perry , Alexander L. Wolf, Foundations for the study of software architecture, ACM SIGSOFT Software Engineering Notes, v.17 n.4, p.40-52, Oct. 1992 [doi>10.1145/141874.141884]
• 24: Understanding Tradeoffs among Different Architectural Modeling Approaches, Proceedings of the Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA'04), p.47, June 12-15, 2004
• 25: SAE. Sae aadl information site. URL: http://www.aadl.info/.
• 26: Bradley Schmerl , David Garlan, AcmeStudio: Supporting Style-Centered Architecture Development, Proceedings of the 26th International Conference on Software Engineering, p.704-705, May 23-28, 2004
• 27: Mary Shaw , David Garlan, Software architecture: perspectives on an emerging discipline, Prentice-Hall, Inc., Upper Saddle River, NJ, 1996
• 28: João Pedro Sousa , David Garlan, Formal Modeling of the Enterprise JavaBeansTM Component Integration Framework, Proceedings of the Wold Congress on Formal Methods in the Development of Computing Systems-Volume II, p.1281-1300, September 20-24, 1999
• 29: B. Spitznagel and D. Garlan. Architecture-based performance analysis. In 10th International Conf. on Software Engineering and Knowledge Engineering (SEKE'98), San Francisco, CA, June 1998.
• 30: Bedir Tekinerdogan , Hasan Sozer , Mehmet Aksit, Software Architecture Reliability Analysis Using Failure Scenarios, Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05), p.203-204, November 06-10, 2005 [doi>10.1109/WICSA.2005.65]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Languages (e.g., description, interconnection, definition)

Keywords:
architectural style, software architecture, style analysis