Monterey Phoenix, or how to make software architecture executable

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Monterey Phoenix, or how to make software architecture executable

Full text

Pdf (526 KB)

Source

Conference on Object Oriented Programming Systems Languages and Applications archive
Proceeding of the 24th ACM SIGPLAN conference companion on Object oriented programming systems languages and applications table of contents

Orlando, Florida, USA

SESSION: Onward! short papers session 5: the enchanted tiki room table of contents

Pages 1031-1040

Year of Publication: 2009

ISBN:978-1-60558-768-4

Author

Mikhail Auguston

Naval Postgraduate School, Monterey, CA, USA

Sponsor

SIGPLAN: ACM Special Interest Group on Programming Languages

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 13, Downloads (12 Months): 13, Citation Count: 0

Additional Information:

abstract references index terms

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1639950.1640075 What is a DOI?

ABSTRACT

This paper suggests an approach to formal software system architecture specification based on behavior models. The behavior of the system is defined as a set of events (event trace) with two basic relations: precedence and inclusion. The structure of event trace is specified using event grammars and other constraints organized into schemas. The schema framework is amenable to stepwise architecture refinement up to executable design and implementation models, reuse, composition, visualization, and application of automated tools for consistency checks.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Gregory Abowd, Robert Allen, and David Garlan, Formalizing Style to Understand Descriptions of Software Architecture, ACM Transactions on Software Engineering and Methodology 4(4):319--364, October 1995.
	2	Robert Allen and David Garlan. A Formal Basis for Architectural Connection. In ACM Transactions on Software Engineering and Methodology, Vol. 6(3): 213--249, July 1997.
	3	"Alloy Analyzer 4.1.10" MIT, Accessed May 8, 2009 http://alloy.mit.edu/community/software
	4	M. Auguston, "Program Behavior Model Based on Event Grammar and its Application for Debugging Automation", in Proceedings of the 2nd International Workshop on Automated and Algorithmic Debugging, Saint-Malo, France, May 1995.
	5	M.Auguston, C.Jeffery, S.Underwood, A Framework for Automatic Debugging, in Proceedings of the 17th IEEE International Conference on Automated Software Engineering, September 23--27, 2002, Edinburgh, UK, IEEE Computer Society Press, pp.217--222.
	6	M.Auguston, B.Michael, M.Shing, Environment Behavior Models for Automation of Testing and Assessment of System Safety, Information and Software Technology, Elsevier, Vol. 48, Issue 10 , October 2006, pp. 971--980
	7	Robert Allen and David Garlan. A formal basis for architectural connection. ACM Transactions on Software Engineering and Methodology, July 1997.
	8	Bass, Len; Paul Clements, Rick Kazman, Software Architecture In Practice, Second Edition, Boston: Addison-Wesley, 2003
	9	Grady Booch, Ivar Jacobson & Jim Rumbaugh (2000) OMG Unified Modeling Language Specification, http://www.omg.org/docs/formal/00-03-01.pdf
	10	B. Bruegge, P. Hibbard, "Generalized Path Expressions: A High-Level Debugging Mechanism", The Journal of Systems and Software 3, 1983, pp. 265--276.
	11	R.H. Campbell and A.N. Habermann, The Specification of Process Synchronization by Path Expressions, Lecture Notes in Computer Science, No. 16, Apr. 1974, pp. 89--102. Vol. 14, No. 3, May 1989, pp. 147--150.
	12	P.Clements, M.Shaw, "The Golden Age of Software Architecture" Revisited, IEEE Software, Vol. 26, No 4, 2009, pp. 70--72
	13	Peter H. Feiler, David P. Gluch, John J. Hudak, The Architecture Analysis & Design Language (AADL): An Introduction, Technical Note CMU/SEI-2006-TN-011, http://www.sei.cmu.edu/publications/documents/06.reports/06tn011.html (accessed June 2009)
	14	C. A. R. Hoare. Communicating Sequential Processes. Prentice-Hall, 1985.
	15	Jackson, Daniel. 2006. Software Abstractions: Logic, Language, and Analysis. Cambridge, Massachusetts: The MIT Press.
	16	Jackson, Daniel, "A Direct Path to Dependable Software: Who could fault an approach that offers greater credibility at reduced cost?, Communications of the ACM, Vol. 52 No. 4, 2009, Pages 78--88,
	17	Donald E. Knuth. "Literate Programming". The Computer Journal, 27(2):97--111, May 1984
	18	David C Luckham, Lary M. Augustin, John J. Kenney, James Vera, Doug Bryan, and Walter Mann. Specification and analysis of system architecture using Rapide. IEEE Transactions on Software Engineering, Special Issue on Software Architecture, 21(4):336--355, April 1995.
	19	Pelliccione, Patrizio; Inverardi, Paola; Muccini, Henry, CHARMY: A Framework for Designing and Verifying Architectural Specifications, IEEE Transactions on Software Engineering, Vol. 35, No 3, 2009, pp.325--346
	20	Dewayne E. Perry and Alexander L. Wolf. "Foundations for the Study of Software Architecture", ACM SIGSOFT Software Engineering Notes, 17:4 (1992), pp. 40--52.
	21	Shaw, M. and Clements, P., A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems, COMPSAC97, 21st Int'l Computer Software and Applications Conference, 1997, pp. 6--13.
	22	Shaw, M. and Clements, P., The Golden Age of Software Architecture, IEEE Software, Vol. 23, No 2, 2006, pp.31--39
	23	Shaw, M. and Garlan, D. 1996. Software Architecture: Perspectives on an Emerging Discipline. Prentice-Hall, Englewood Cliffs, New Jersey.
	24	J.M.Spivey, The Z Notation: A reference manual, Prentice Hall International Series in Computer Science, 1989. (2nd ed., 1992)