Representing structural requirements in software architecture

  • V. Ambriola
  • V. Gervasi
Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT)


Software architecture is often intended as a synonym of functional decomposition. Recently, the growing interest in quality factors is pushing software architects to explicitly address issues such as reliability, robustness, and efficiency in the early phases of the software process. Also, an effective software process emphasizes the need for requirement traceability in all phases of development. This paper is a first step in the direction of representing and tracking structural requirements (i.e., non functional requirements) in the software architecture. A graphical language, based on the Dean and Cordy proposal, is extended to cope with this new issue, and an example of its use is given.


Software architecture Requirements design language 


  1. M. Boasson. The artistry of software architecture. IEEE Software, 12(6): 1316, November 1995.Google Scholar
  2. T.R. Dean. Software characterization using connectivity. Ph.D. dissertation, Dept. of Computing and Information Science, Queen’s University, Kingston, Canada, 1993.Google Scholar
  3. T.R. Dean, J.R. Cordy. A syntactic theory of software architecture. IEEE Transactions on Software Engineering, 21(4): 302–313, April 1995.CrossRefGoogle Scholar
  4. D.L. Parnas. On the criteria to be used in decomposing system into modules. Communications of the ACM, 15(12): 1053–1058, December 1972.CrossRefGoogle Scholar
  5. D.E. Perry, A.L. Wolf. Foundations for the study of software architecture. ACM Sigsoft Software Engineering Notes, 17(4): 40–52, October 1992.CrossRefGoogle Scholar
  6. R. Kazman, L. Bass. Toward deriving software architectures from quality attributes. Technical report CMU/SEI-94-TR-10, August 1994.Google Scholar
  7. M. Shaw, R. DeLine, D.V. Klein, T.L. Ross, D.M. Young, G. Zelesnik. Abstractions for software architecture and tools to support them. IEEE Transactions on Software Engineering, 21(4): 314–335, April 1995.CrossRefGoogle Scholar
  8. M. Rosestolato. Non functional requirements in the software architecture. Master’s thesis, Dipartimento di Informatica, Pisa, 1996. In Italian.Google Scholar
  9. I. Tervonen. Support quality-based design and inspection. IEEE Software, 13(1): 44–54, January 1996.CrossRefGoogle Scholar

Copyright information

© IFIP 1998

Authors and Affiliations

  • V. Ambriola
    • 1
  • V. Gervasi
    • 1
  1. 1.Dipartimento di Informatica CorsoUniversità di PisaPisaItaly

Personalised recommendations