| Franch, X., Botella, P. Putting Non-Functional Requirements into Software Architecture. In, 9th Int l Wksp. on Software Specification & Design. 60-67, 1998. |
....the reliability of a main subroutine styles vs. the performance of an event based style. While these problems can be reasoned about informally, the properties need qualifiers to provide support to a software architecture analysis method. Many research efforts have attempted to remedy this issue [8,12,27]. One suggestion is to include in the architecture definition the information that pertains to composing components, the functional assumptions that relate components, and the answers to desired behavior resulting in a credential with an attribute value property list [27] Another method is to ....
....with an attribute value property list [27] Another method is to describe components and connectors in terms of both their functional and non 3 functional parts. This is achieved by converting detailed requirements into attributes of software such as reliability, performance, accuracy, etc [12]. A third approach endeavors to translate non functional requirements into goals whose conflicts ultimately help shape the design of the system [8] It is proven, nonetheless, that software architecture principles provide the best hope of developing a system that fulfills its requirements, ....
Franch, X., Botella, P. Putting Non-Functional Requirements into Software Architecture. In, 9th Int l Wksp. on Software Specification & Design. 60-67, 1998.
No context found.
Franch X., and Botella P. 1996. Putting Non-Functional Requirements into Software Architecture. Proceedings of the 9th International Workshop on Software Specification and Design, Ise-Shima, Japan, IEEE Computer Society, Los Alamitos, CA, pp. 60-67.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC