André Gil
ABSTRACT
In KAOS, a goal-oriented requirements engineering approach, requirements are obtained from the goals a system must accomplish. When modeling goals some of them will be tangled and scattered all over the system. This will increase the complexity of the system, thus diminishing the understandability of it. Identification of cross-cutting concerns at requirements enables us to separate those concerns from the very beginning and provide a simpler and enhanced design of the system so it will have a better evolution. By combining goals and aspects we will improve the system's maintainability, reusability and evolution over time.
- A. Anton, "Goal-Based Requirements Analysis", Proceedings of the 2nd IEEE International Conference on Requirements Engineering, April 1996, Colorado Springs, USA, pp. 136--144. Google Scholar
Digital Library
- A. Dardenne, A. Lamsweerde, S. Fickas, "Goal-Directed Requirements Acquisition", Science of Computer Programming, April 1993, Volume 20(1-2), Elsevier North-Holland, Inc, pp. 3--50. Google ScholarDigital Library
- A. Lamsweerde, "Divergent Views in Goal-Driven Requirements Engineering", Proceedings of the Workshop on Viewpoints in Software Development, October 1996, San Francisco, USA, pp. 252--256. Google ScholarDigital Library
- A. Lamsweerde, "Elaborating Security Requirements by Construction of Intentional Anti-Models", Proceedings of the 26th International Conference on Software Engineering, May 2004, Edinburgh, UK, pp. 148--157. Google ScholarDigital Library
- A. Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", Proceedings of the 5th IEEE International Symposium on Requirements Engineering, August 2001, Toronto, Canada, pp. 249--263. Google ScholarDigital Library
- A. Lamsweerde, "KAOS Tutorial", Cediti, September 5, 2003, http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf.Google Scholar
- A. Lamsweerde, A. Dardenne, B. Delcourt, F. Dubisy, "The KAOS Project: Knowledge Acquisition in Automated Specification of Software", Proceedings of AAAI Spring Symposium Series, March 1991, Stanford University, USA, pp. 59--62.Google Scholar
- A. Rashid, A. Moreira, J. Araújo, "Modularisation and Composition of Aspectual Requirements", Proceedings of the 2nd International Conference on Aspect-Oriented Software Development, March 2003, Boston, Massachusetts, pp. 11--20. Google ScholarDigital Library
- D. Kim, R. France, S. Ghosh, E. Song, "A UML-Based Metamodeling Language to Specify Design Patterns", Workshop in Software Model Engineering, October 2003, San Francisco, USA.Google Scholar
- D. Stein, S. Hanenberg, R. Unland, "Modeling Pointcuts", Workshop Proceedings of Early Aspects 2004, March 2004, Lancaster, UK, pp. 108--115.Google Scholar
- E. Yu, "Modeling Organizations for Information Systems Requirements Engineering", Proceedings of the 1st IEEE Symposium on Requirements Engineering, January 1993, San Diego, California, pp. 34--41.Google Scholar
- F. Alencar, C. Silva, A. Moreira, J. Araújo, J. Castro, "Identifying Candidate Aspects with I-star Approach", Workshop on Early Aspects in 5th International Conference on Aspect--Oriented Software Development, March 2006, Bonn, Germany.Google Scholar
- G. Mussbacher, D. Amyot, J. Araújo, A. Moreira, M. Weiss, "Visualizing Aspect-Oriented Goal Models with AoGRL", 2nd International Workshop on Requirements Engineering Visualization, October 2007, New Delhi, India. Google ScholarDigital Library
- Y. Yu, J. Leite, J. Mylopoulos, "From goals to aspects: Discovering aspects from requirements goal models", 12th Intl. Conf. on Requirements Engineering, IEEE Computer Society, Japan, 2004, pp. 38--47. Google ScholarDigital Library
Index Terms
- AspectKAOS: integrating early-aspects into KAOS
Recommendations
Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models
Models in Software EngineeringTechnologies based on aspects and applied at the early stages of software development allow requirements engineers to better encapsulate crosscutting concerns in requirements models. The Aspect-oriented User Requirements Notation (AoURN) extends the ...
A Review on Approaches for Identifying Crosscutting Concerns
ICACTE '08: Proceedings of the 2008 International Conference on Advanced Computer Theory and EngineeringBrito argued that there are certain properties that the existing software development approaches are not able to modularize. Brito claimed, these properties cut across a large number of artefacts that compose the system. Therefore it is difficult to ...
3CI: A Tool for Crosscutting Concern Identification
CIMCA '08: Proceedings of the 2008 International Conference on Computational Intelligence for Modelling Control & AutomationCertain requirements in requirements document are scattered and tangled. Often software developers neglect these requirements during implementation or repeat the same functionality throughout the codes. These requirements are called crosscutting ...
Comments