Journal of Software, Vol 6, No 4 (2011), 574-583, Apr 2011

Reasoning About Quantitative Architectural Attributes (Invited Paper)

Lamia Labed Jilani, Imen Derbel, Khaled Bsaies, Hamdi Nasreddine, Ali Mili


It is widely accepted that software architectures represent non functional attributes of software systems. Yet we know of no Architectural Description Language that provides automated support for reasoning about such attributes. In this paper we discuss our ongoing research in representing and reasoning about non functional properties of software



Software architecture, non functional attributes, ACME, Wright, response time, throughput, reliability, security, availability, maintainability


[1] A. R. and G. D., “A formal basis for architectural connection,” ACM Transactions on Software Engineering and methodology, vol. 6, no. 3, 1997.

[2] B.Schmerl and D.Garlan, “Acmestudio: Supporting style centered architecture development,” in Proceedings, 26th International Conference on Software Engineering, May 2004.

[3] D.Garlan, R.T.Monroe, and D.Wile, “Acme: An architecture description interchange language,” in Proceedings, CASCON’ 97, 1997.

[4] R. AAllen, “A formal approach to software architecture,” Carnegie Mellon University, Pittsburgh, Technical Report CMU-CS-97-144, May 1997.

[5] C.V.Eenoo, O.Hylooz, and K. Khan, “Addressing non functional properties in software architecture using adl,” in Proceedings, Sixth Australian Workshop on Software and System Architecture, 2005.

[6] B. M., C. P., and D. L., “Architecting families of software systems with process algebras,” ACM TOSEM: Transactions on Software Engineering and Methodology, 2002.

[7] A. A. and B. M., “On the usability of process algebra: An architectural view,” Theoretical Computer Science, May 2005.

Full Text: PDF

Journal of Software (JSW, ISSN 1796-217X)

Copyright @ 2006-2014 by ACADEMY PUBLISHER – All rights reserved.