Aspect Frames: Describing Cross-Cutting Concerns in Aspect-Oriented Requirements Engineering

ABSTRACT

Cross-cutting concerns often arise when non-functional requirements are operationalized, because non-functional requirements are themselves cross-cutting. In the field of aspect-oriented requirements engineering (AORE), functional requirements that cross-cut multiple other functional requirements are called aspects. An aspect describes in most cases a solution for a non-functional requirement and how this solution can be integrated into the realization of the functional requirements it cross-cuts. Examples for cross-cutting concerns are logging, encryption, and access control. We observed that aspects often share a basic structure, behavior, and the way of how they have to be integrated into the realization of the functional requirements they cross-cut. We propose in this paper aspect frames. An aspect frame is a kind of pattern for aspects that share a common concern, behavior, and way how they are integrated into the realization of the functional requirements they cross-cut. These aspect frames support requirements engineers to describe concrete aspects that fit to an aspect frame.

References

1. Azadeh Alebrahim, Thein Than Tun, Yijun Yu, Maritta Heisel, and Bashar Nuseibeh. 2012. An Aspect-Oriented Approach to Relating Security Requirements and Access Control. InProceedings of the CAiSE'12 Forum at the 24th International Conference on Advanced Information Systems Engineering (CAiSE) (CEUR Workshop Proceedings), Vol. 855. CEUR-WS.org, 15--22. http://ceur-ws.org/Vol-855/paper2.pdf
2. Siobhán Clarke and Robert J. Walker. 2001. Composition Patterns: An Approach to Designing Reusable Aspects. In Proceedings of the 23rd International Conference on Software Engineering, ICSE 2001, 12-19 May 2001, Toronto, Ontario, Canada, Hausi A. Müller, Mary Jean Harrold, and Wilhelm Schäfer (Eds.). IEEE Computer Society, 5--14.
3. Stephan Faßbender, Maritta Heisel, and Rene Meis. 2014. Aspect-oriented Requirements Engineering with Problem Frames. In ICSOFT-PT 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends. SciTePress, 145--156.
4. Stephan Faßbender, Maritta Heisel, and Rene Meis. 2015. A Problem-, Quality-, and Aspect-Oriented Requirements Engineering Method. In Software Technologies - 9th International Joint Conference, ICSOFT 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers (Communications in Computer and Information Science), Vol. 555. Springer, 291--310.
5. Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. 1995. Design Patterns: Elements of Reusable Object-oriented Software. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.
6. Alessandro Garcia, Cláudio Sant'Anna, Eduardo Figueiredo, Uirá Kulesza, Carlos Lucena, and Arndt von Staa. 2006.Modularizing Design Patterns with Aspects: A Quantitative Study. Springer Berlin Heidelberg, Berlin, Heidelberg, 36--74.
7. Michael Jackson. 2001. Problem Frames. Analyzing and structuring software development problems. Addison-Wesley.
8. Gregor Kiczales, John Lamping, Anurag Mendhekar, Chris Maeda, Cristina Videira Lopes, Jean-Marc Loingtier, and John Irwin. 1997. Aspect-Oriented Programming. In ECOOP. Springer, 220--242.
9. Maria Lencastre, Ana Moreira, João Araźjo, and Jaelson Castro. 2008. Aspects Composition in Problem Frames. In Proceedings of the 16th IEEE International Requirements Engineering Conference. IEEE Computer Society, 343--344.
10. Rene Meis and Maritta Heisel. 2017. Pattern-based Representation of Privacy Enhancing Technologies as Early Aspects. In Trust, Privacy, and Security in Digital Business (LNCS), Vol. 10442. Springer International Publishing, Cham, 49--65.
11. Ana Moreira, Ruzanna Chitchyan, Joo Arajo, and Awais Rashid. 2013. Aspect-Oriented Requirements Engineering. Springer Publishing Company.
12. Narender Singh and Nasib Singh Gill. 2011. Aspect-Oriented Requirements Engineering for Advanced Separation of Concerns: A Review. IJCSI International Journal of Computer Science Issues 8, 5 (September 2011), 288--297.
13. Tim Wellhausen and Andreas Fießer. 2011. How to write a pattern?: a rough guide for first-time pattern authors. In 16th European Conference on Pattern Languages of Programs, EuroPLoP 2011. ACM, 5.

Index Terms

• Software and its engineering

  • Software creation and management

    • Designing software

  • Software notations and tools

    • General programming languages

      • Language features

        • Patterns