Modeling architectural non functional requirements: From use case to control case

Zou, Joe and Pavlovski, Christopher J. (2006). Modeling architectural non functional requirements: From use case to control case. In: IEEE International Conference on e-Business Engineering, 2006. ICEBE '06. IEEE International Conference on e-Business Engineering 2006, Shanghai, Peoples Republic of China, (315-322). 24-26 October 2006. doi:10.1109/ICEBE.2006.71


Author Zou, Joe
Pavlovski, Christopher J.
Title of paper Modeling architectural non functional requirements: From use case to control case
Conference name IEEE International Conference on e-Business Engineering 2006
Conference location Shanghai, Peoples Republic of China
Conference dates 24-26 October 2006
Proceedings title IEEE International Conference on e-Business Engineering, 2006. ICEBE '06
Journal name Icebe 2006: Ieee International Conference On E-Business Engineering, Proceedings
Place of Publication Piscataway, NJ, United States
Publisher IEEE
Publication Year 2006
Sub-type Fully published paper
DOI 10.1109/ICEBE.2006.71
ISBN 0-7695-2645-4
978-076952645-4
Start page 315
End page 322
Total pages 8
Language eng
Abstract/Summary While the functional requirements of a system can be effectively modeled through the Use Case driven approach, there is no standard or de facto method for modeling non-functional requirements of the system architecture. Often such requirements are dealt with in a reactive manner rather than proactively. Yet increasingly a contributing factor in project difficulty and failure are the non-functional requirements imposed on the solution architecture. This paper proposes a Control Case approach to record and model non-functional requirements. This technique enables the control case to represent the nonfunctional requirements from different perspectives, most typically the various operating conditions. Furthermore, we propose an extension to the “4+1" view model for depicting software architecture by adding the control case view. The combination of both the use case and control case views thus reflects the complete requirements across the collective system life cycle views: design, process, implementation and deployment.
Q-Index Code E1
Q-Index Status Provisional Code
Institutional Status Non-UQ

 
Versions
Version Filter Type
Citation counts: TR Web of Science Citation Count  Cited 8 times in Thomson Reuters Web of Science Article | Citations
Scopus Citation Count Cited 4 times in Scopus Article | Citations
Google Scholar Search Google Scholar
Created: Sat, 10 Sep 2011, 13:15:36 EST by System User on behalf of School of Information Technol and Elec Engineering