Representing structural requirements in software architecture
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.
KeywordsSoftware architecture Requirements design language
- M. Boasson. The artistry of software architecture. IEEE Software, 12(6): 1316, November 1995.Google Scholar
- T.R. Dean. Software characterization using connectivity. Ph.D. dissertation, Dept. of Computing and Information Science, Queen’s University, Kingston, Canada, 1993.Google Scholar
- R. Kazman, L. Bass. Toward deriving software architectures from quality attributes. Technical report CMU/SEI-94-TR-10, August 1994.Google Scholar
- M. Rosestolato. Non functional requirements in the software architecture. Master’s thesis, Dipartimento di Informatica, Pisa, 1996. In Italian.Google Scholar