Identifying the Aspectual Requirements: A Theme Based Vector-Orientation Model

‘Separation of Concerns’ in the field of Software Engineering has been an important issue for quite some time. And this issue is very much related to Aspect Oriented Software Development. This is so because Aspects happen to be certain concerns that get interleaved with the Core-Functionalities in such a way that they become nearly inseparable. As a result of which both the designer as well as the programmer, who are supposed to be concerned only with the Core-Functionalities, is bound to take extra burden or botheration regarding the proper and accurate handling of Aspects. The Theme approach is an already established approach for Aspect identification in the requirements-engineering phase. Our approach is a diversification of the Theme approach where we look for Aspectual Requirements instead of Aspectual Themes. This paper proposes a purely mathematical model for RequirementsEngineering for Aspect Identification. The concept is based on N-Dimensional-Vector-Orientation Model, which is used to serve the purpose.

[1]  Stanley M. Sutton,et al.  Modeling of software concerns in Cosmos , 2002, AOSD '02.

[2]  Yves Lespérance,et al.  Agent-Oriented Requirements Engineering Using ConGolog and i* , 2001 .

[3]  João Araújo,et al.  Modularisation and composition of aspectual requirements , 2003, AOSD '03.

[4]  Siobhán Clarke,et al.  Aspect-oriented analysis and design - the theme approach , 2005, Addison Wesley object technology series.

[5]  F. W. Kellaway,et al.  Advanced Engineering Mathematics , 1969, The Mathematical Gazette.

[6]  Siobhán Clarke,et al.  Extending standard UML with model composition semantics , 2002, Sci. Comput. Program..

[7]  Siobhán Clarke,et al.  Composition patterns: an approach to designing reusable aspects , 2001, ICSE 2001.

[8]  Robert J. Walker,et al.  Evaluating Emerging Software Development Technologies: Lessons Learned from Assessing Aspect-Oriented Programming , 1999, IEEE Trans. Software Eng..

[9]  Stanley M. Sutton,et al.  N degrees of separation: multi-dimensional separation of concerns , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[10]  W. Marsden.  I and J , 2012 .

[11]  MylopoulosJohn,et al.  Towards requirements-driven information systems engineering , 2002 .

[12]  Gail C. Murphy,et al.  Design pattern rationale graphs: linking design to source , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[13]  Ian Sommerville,et al.  The viewpoints FAQ , 1996 .

[14]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[15]  Gregor Kiczales,et al.  Aspect-oriented programming , 2001, ESEC/FSE-9.

[16]  Cristina V. Lopes,et al.  Aspect-oriented programming , 1999, ECOOP Workshops.

[17]  Siobhán Clarke,et al.  Towards a standard design language for AOSD , 2002, AOSD '02.

[18]  Dennis Spellman,et al.  Vector analysis and an introduction to tensor analysis , 1980 .

[19]  Axel van Lamsweerde,et al.  Formal refinement patterns for goal-driven requirements elaboration , 1996, SIGSOFT '96.

[20]  John C. Grundy,et al.  Aspect-oriented requirements engineering for component-based software systems , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[21]  Shmuel Katz,et al.  Architectural views of aspects , 2003, AOSD '03.

[22]  Siobhán Clarke,et al.  Theme: an approach for aspect-oriented analysis and design , 2004, Proceedings. 26th International Conference on Software Engineering.

[23]  Marco Furini,et al.  International Journal of Computer and Applications , 2010 .