Modeling Early Availability Requirements Using Aspect-Oriented Use Case Maps
Non-functional requirements such as availability, reliability, and security are often crucial in designing and implementing distributed real-time systems. As a result, such non-functional requirements should be addressed as early as possible in the system development life-cycle. The widespread interest in dependability modeling and analysis techniques at the requirements elicitation and analysis stage provides the major motivation for this research. This paper presents a novel approach to describe high-level availability requirements using the Aspect-oriented Use Case Maps (AoUCM) language. AoUCM adds aspects-oriented concepts to the Use Case Maps (UCM) language, part of the ITU-T User Requirements Notation (URN) standard. The proposed approach relies on a mapping of availability architectural tactics to reusable AoUCM models, allowing availability tactics to be encapsulated early in the software development life-cylce. Initial tool support for the resulting availability extensions, is provided by the jUCMNav tool. We demonstrate the applicability of our approach using a case study of Lawful Intercept (LI), an IP router feature.
KeywordsException Handling Fault Recovery Failure Path Line Card Availability Requirement
Unable to display preview. Download preview PDF.
- 1.International Telecommunication Union: Recommendation Z.151 (10/12), User Requirements Notation (URN) – language definition (2012), http://www.itu.int/rec/T-REC-Z.151/en
- 2.Hassine, J.: Early Availability Requirements Modeling using Use Case Maps. In: 8th International Conference on Information Technology – New Generations, ITNG 2011, pp. 754–759. IEEE Computer Society (2011)Google Scholar
- 4.Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley (2003)Google Scholar
- 5.ISO/IEC/IEEE: 24765:2010(E) - Systems and software engineering – vocabulary, pp. 1–418 (2010), http://dx.doi.org/10.1109/IEEESTD.2010.5733835
- 8.International Telecommunication Union: Recommendation E.800 (09/08) Definitions of terms related to quality of service (2008), http://www.itu.int/rec/T-REC-E.800/en
- 9.Laprie, J., Avizienis, A., Kopetz, H.: Dependability: Basic Concepts and Terminology. Springer (1991)Google Scholar
- 10.Scott, J., Kazman, R.: Realizing and refining architectural tactics – Availability. Carnegie Mellon University – Software Engineering Institute (2009), http://www.sei.cmu.edu/library/abstracts/reports/09tr006.cfm
- 11.Mussbacher, G.: Aspect-oriented user requirements notation. Ph.D. thesis, University of Ottawa (2010), http://lotos.csi.uottawa.ca/ucm/pub/UCM/VirLibGunterPhDThesis/Aspect-Oriented_User_Requirements_Notation.pdf
- 13.Mussbacher, G., Amyot, D., Araújo, J., Moreira, A.: Requirements Modeling with the Aspect-oriented User Requirements Notation (AoURN): A Case Study. In: Katz, S., Mezini, M., Kienzle, J. (eds.) Transactions on AOSD VII. LNCS, vol. 6210, pp. 23–68. Springer, Heidelberg (2010), http://dx.doi.org/10.1007/978-3-642-16086-8_2 CrossRefGoogle Scholar
- 15.jUCMNav v5.2.0: jUCMNav Project (tool, documentation, and meta-model) (2013), http://jucmnav.softwareengineering.ca/jucmnav