Skip to main content

Modeling Early Availability Requirements Using Aspect-Oriented Use Case Maps

  • Conference paper
SDL 2013: Model-Driven Dependability Engineering (SDL 2013)

Part of the book series: Lecture Notes in Computer Science ((LNCCN,volume 7916))

Included in the following conference series:

Abstract

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.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  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 

  3. Hassine, J., Gherbi, A.: Exploring Early Availability Requirements Using Use Case Maps. In: Ober, I., Ober, I. (eds.) SDL 2011. LNCS, vol. 7083, pp. 54–68. Springer, Heidelberg (2011)

    Chapter  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

  6. Avizienis, A., et al.: Basic Concepts and Taxonomy of Dependable and Secure Computing. IEEE Transactions on Dependable and Secure Computing 1(1), 11–33 (2004)

    Article  Google Scholar 

  7. Hatebur, D., Heisel, M.: A Foundation for Requirements Analysis of Dependable Software. In: Buth, B., Rabe, G., Seyfarth, T. (eds.) SAFECOMP 2009. LNCS, vol. 5775, pp. 311–325. Springer, Heidelberg (2009)

    Chapter  Google Scholar 

  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

  12. Mussbacher, G., Amyot, D.: Extending the user requirements notation with aspect-oriented concepts. In: Reed, R., Bilgic, A., Gotzhein, R. (eds.) SDL 2009. LNCS, vol. 5719, pp. 115–132. Springer, Heidelberg (2009)

    Chapter  Google Scholar 

  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

    Chapter  Google Scholar 

  14. Mussbacher, G., et al.: AoURN-based modeling and analysis of software product lines. Software Quality Journal 20(3-4), 645–687 (2012), http://dx.doi.org/10.1007/s11219-011-9153-8

    Article  Google Scholar 

  15. jUCMNav v5.2.0: jUCMNav Project (tool, documentation, and meta-model) (2013), http://jucmnav.softwareengineering.ca/jucmnav

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Hassine, J., Mussbacher, G., Braun, E., Alhaj, M. (2013). Modeling Early Availability Requirements Using Aspect-Oriented Use Case Maps. In: Khendek, F., Toeroe, M., Gherbi, A., Reed, R. (eds) SDL 2013: Model-Driven Dependability Engineering. SDL 2013. Lecture Notes in Computer Science, vol 7916. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-38911-5_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-38911-5_4

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-38910-8

  • Online ISBN: 978-3-642-38911-5

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics