WHAT IS AN ASPECT IN REQUIREMENTS ENGINEERING?

Hermann Kaindl

Abstract

Addressing the issue of crosscutting concerns within a software system, the notion of an aspect has been introduced, first for so-called Aspect-Oriented Programming (AOP) and then, more generally, for Aspect-Oriented Software Development (AOSD). Unfortunately, this notion is used with two different meanings: one as a synonym for “crosscutting concern”, and the other as a means to deal with a crosscutting concern within the software. Later, this notion has been carried over to so-called Aspect-Oriented Requirements Engineering (AORE). This raises questions about the meaning(s) of an aspect in this context, and about the relationship of this notion in AORE and the same notion in AOP. We try to answer these questions and argue to define an aspect as a means to deal with crosscutting concerns, and not as a synonym of “crosscutting concern”. Most importantly, an aspect in AORE is not necessarily related to an aspect within the software.

References

  1. Arnautovic, E., Kaindl, H., 2004. Aspects for crosscutting concerns in systems architectures?, In Proc. of the Second Annual Conference on Systems Engineering Research (CSER-04), pp. 1-10.
  2. Baniassad, E., Clarke, S., 2004. Theme: An Approach for Aspect-Oriented Analysis and Design. In Proc. of the 26th International Conference on Software Engineering (ICSE'04), pp. 158-167.
  3. Baniassad; E., Clements, P.C., Araujo, J., Moreira, A., Rashid, A., Tekinerdogan, B., 2006. Discovering early aspects, IEEE Software, 23(1): 61-70.
  4. Elrad, T., Filman, E.R., Bader, A., 2001. Aspect-oriented programming: Introduction. Communications of the ACM, 44(10):29-32.
  5. Kaindl, H., 1999. Difficulties in the Transition from OO Analysis to Design, IEEE Software, 16(5):94-102.
  6. Katara, M., Katz, S., 2003. Architectural Views of Aspects. In Proc. of the Second International Conference on Aspect-Oriented Software Development (AOSD 2003), ACM Press, pp. 1-10.
  7. Katz, S., Rashid, A., 2004. From aspectual requirements to proof obligations for aspect-oriented systems. In Proc. of the 12th IEEE International Requirements Engineering Conference (RE'04), pp. 48-57.
  8. Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J.-M., Irwin, J., 1997. AspectOriented Programming. In Proc. ECOOP 7897, LNCS 1241, Springer-Verlag, pp. 220-242.
  9. Rashid, A., Sawyer, P., Moreira, A., Araujo, J., 2002. Early aspects: a model for aspect-oriented requirements engineering. In Proc. of the IEEE Joint International Conference on Requirements Engineering (RE'02), pp. 199-202.
  10. Xu, D., Vivek G., Nygard, K., 2006. An Aspect-Oriented Approach to Security Requirements Analysis. In Proc. of the 30th Annual International Computer Software and Applications Conference (COMPSAC'06), pp. 79- 82.
  11. Yu, Y., Leite, J.C.S.P., Mylopoulos, J., 2004. From goals to aspects: discovering aspects from requirements goal models. In Proc. of the 12th IEEE International Requirements Engineering Conference (RE'04), pp. 38-47.
Download


Paper Citation


in Harvard Style

Kaindl H. (2009). WHAT IS AN ASPECT IN REQUIREMENTS ENGINEERING? . In Proceedings of the 4th International Conference on Software and Data Technologies - Volume 1: ICSOFT, ISBN 978-989-674-009-2, pages 354-357. DOI: 10.5220/0002280603540357


in Bibtex Style

@conference{icsoft09,
author={Hermann Kaindl},
title={WHAT IS AN ASPECT IN REQUIREMENTS ENGINEERING?},
booktitle={Proceedings of the 4th International Conference on Software and Data Technologies - Volume 1: ICSOFT,},
year={2009},
pages={354-357},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0002280603540357},
isbn={978-989-674-009-2},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 4th International Conference on Software and Data Technologies - Volume 1: ICSOFT,
TI - WHAT IS AN ASPECT IN REQUIREMENTS ENGINEERING?
SN - 978-989-674-009-2
AU - Kaindl H.
PY - 2009
SP - 354
EP - 357
DO - 10.5220/0002280603540357