Abstract
Requirements engineering techniques that explicitly recognize the importance of clearly identifying and treating crosscutting concerns are called Aspect-oriented Requirements Engineering Approaches (AORE approaches). The emergence of aspect-oriented programming languages has raised the explicit need to identify crosscutting concerns already during the analysis phase. Besides this observation, the modular representation of crosscutting requirements is a first step to ensure traceability of crosscutting concerns through all other artifacts of the software lifecycle (architecture, design and implementation).Aspect-oriented requirements engineering approaches improve existing requirements engineering approaches through an explicit representation (and modularization) of concerns that were otherwise spread throughout other requirements artifacts (such as use cases, goal models, viewpoints, etc.).AORE approaches adopt the principle of separation of concerns at the analysis phase (the early separation of concerns). In other words, AORE approaches provide a representation of crosscutting concerns in requirements artifacts.
Highlights
Summarizing, aspect-oriented requirements engineering (AORE) approaches focus on systematically and modularly treating, reasoning about, composing and subsequently tracing crosscutting concerns via suitable abstraction, representation and composition mechanisms tailored to the requirements engineering domain
Requirements engineers and developers feel most comfortable when a requirement for a system property can confidently be allocated to a particular software component that assumes responsibility for satisfying the requirement
Performance is a factor of the system architecture and its operational environment; one cannot develop a performance module independent of other parts of a software system
Summary
Requirements are always derived from some business problem whether it is, for example, processing passport applications, improving automotive safety systems or adding features to cell phones An effective RE process which minimizes the occurrence of requirements errors and mitigates the impact of requirements change is critical to the success of any development project When such allocation is possible, the resulting software is well modularized, the modules have good communication with each other and all requirements are clearly separated. AORE Arcade provides the notion of crosscutting concern next to viewpoints in a requirements artifact Besides this fact, these approaches focus on the composition principle: it should be possible to compose each concern/requirement with the rest of the concerns/requirements of the system under construction to understand interactions and trade-offs among concerns. Summarizing, AORE approaches focus on systematically and modularly treating, reasoning about, composing and subsequently tracing crosscutting concerns via suitable abstraction, representation and composition mechanisms tailored to the requirements engineering domain.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
