An evolutionary model of requirements correctness with early aspects

ABSTRACT

The achievement of building evolvable systems depends on how efficiently the changeable requirements are elicited and structured by software engineers. In current requirements approaches changing requirements are not dealt with satisfactorily. Partially, this is due to the crosscutting nature of some of these requirements. Aspect-Oriented Requirements Engineering tackles the problem of crosscutting requirements, and its concepts can be used to address this problem. This work describes how early aspects, i.e. aspects identified at early stages of software development, could be integrated to an evolutionary requirements model.

REFERENCES

• 1: Joao Araujo , Joao Carlos Ribeiro, Towards an Aspect-Oriented Agile Requirements Approach, Proceedings of the Eighth International Workshop on Principles of Software Evolution, p.140-143, September 05-06, 2005 [doi>10.1109/IWPSE.2005.31]
• 2: Elisa Baniassad , Siobhan Clarke, Theme: An Approach for Aspect-Oriented Analysis and Design, Proceedings of the 26th International Conference on Software Engineering, p.158-167, May 23-28, 2004
• 3: I. Brito, F. Vieira, A. Moreira, R. Ribeiro, "Handling Conflicts in Aspectual Requirements Compositions", Transactions on AOSD, 2007, to appear.
• 4: M. Cibran and M. D'Hondt, High-Level Specification of Business Rules and Their Crosscutting Connections. 8th International Workshop on Aspect-Oriented Modeling at the International Conference on Aspect-Oriented Programming (AOSD'06), March 2006.
• 5: M. Cibran, and M. D'Hondt, Towards Automatic Integration of High-Level Business Rules Using Aspect-Oriented Programming. Workshop on Models and Aspects - Handling Crosscutting Concerns in MDSD, ECOOP 2005, Glasgow, United Kingdom, July 2005.
• 6: R. Filman, T. Elrad, S Clarke and M. Aksit (eds.), Aspect-Oriented Software Development, Addison-Wesley, 2004.
• 7: Ivar Jacobson , Pan-Wei Ng, Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series), Addison-Wesley Professional, 2004
• 8: G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J. Loingtier and J. Irwin. "Aspect-Oriented Programming", ECOOP'97, Vol. 1231, 1997.
• 9: A. Moreira, J. Araujo, J. Whittle, "Modeling Volatile Concerns as Aspects", CAiSE 2006, Luxembourg, LNCS, Springer, June 2006.
• 10: A. Moreira, J. Araujo. "Handling Unanticipated Requirements Change with Aspects", Software Engineering and Knowledge Engineering Conference (SEKE'04), Banff, Canada, June 2004.
• 11: Ana Moreira , Awais Rashid , Joao Araujo, Multi-Dimensional Separation of Concerns in Requirements Engineering, Proceedings of the 13th IEEE International Conference on Requirements Engineering, p.285-296, August 29-September 02, 2005 [doi>10.1109/RE.2005.46]
• 12: Awais Rashid , Ana Moreira , Joāo Araújo, Modularisation and composition of aspectual requirements, Proceedings of the 2nd international conference on Aspect-oriented software development, p.11-20, March 17-21, 2003, Boston, Massachusetts [doi>10.1145/643603.643605]
• 13: Ian Sommerville , Pete Sawyer, Requirements Engineering: A Good Practice Guide, John Wiley & Sons, Inc., New York, NY, 1997
• 14: J. Whittle and J. Araujo, "Scenario Modeling with Aspects", IEE Proceedings Software, August 2004.
• 15: D. Zowghi and V. Gervasi, Erratum to "On the interplay between consistency, completeness, and correctness in requirements evolution", Journal of Information and Software Technology 46 (11), Elsevier, pp. 763--779, 2004.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications

General Terms:
Design, Documentation, Theory, Verification

Keywords:
aspect-oriented software development, early aspects, requirements correctness