Aspect-oriented requirements engineering

Alshareef, Sohil F.; Maatuk, Abdelsalam M.; Abdelaziz, Tawfig M.

doi:10.1145/3279996.3280009

Cited by 9 publications

(2 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…AOSD is a technology that is centered on the parting of concern principle and the crosscutting concerns are encapsulated in two aspects. The identification of the crosscutting concerns at the requirement level is necessary, so they can be handled efficiently at the early stages and provide earlier support for the identification of the functional and non-functional concerns [9]. The traditional requirement approaches cannot have identified the aspects at the requirement phase and this increases complexity in the further phases.…”

Section: Literature Reviewmentioning

confidence: 99%

Complexity in the adaptation of aspect-oriented software Development

Abid¹,

Khan²

2022

ijisct

View full text Add to dashboard Cite

The software products are an integral part of the modern era and this encourages the developers to explore new techniques for the development. As the software products are becoming more complex, this demands a new technique to deal with the complexity. Aspect-Oriented Software Development is an example of a technique that deals with modern complex systems. As the structure of the new technique is also complex for the new developers, they want to change their way of development according to the new demands and there is no model for the new developers. This paper purposed a model using the basic phases of software development. This model educates and encourages the new developers to adopt the new software development technique. The Paper also discusses the common tools and techniques regarding the different phases of aspect-oriented software development (AOSD) to deal with the complexity of the system more efficiently.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Complexity in the adaptation of aspect-oriented software Development

Abid¹,

Khan²

2022

ijisct

View full text Add to dashboard Cite

show abstract

“…Through the investigation described in [3], it is noticed that almost all the approaches focus on identifying crosscutting concerns as well as representing them either using graphical models, XML schema, templates or text-based representation. Therefore, the resulting artefacts from the requirements phase must be validated before moving to other development stages to reduce extra work and effort caused by missing information and unintentionally overlooked inconsistency rules [43].…”

Section: Introductionmentioning

confidence: 99%

A Framework for Aspectual Requirements Validation: an Experimental Study

Maatuk¹,

Alshareef²,

Abdelaziz³

2021

IJSEA

View full text Add to dashboard Cite

Requirements engineering is a discipline of software engineering that is concerned with the identification and handling of user and system requirements. Aspect-Oriented Requirements Engineering (AORE) extends the existing requirements engineering approaches to cope with the issue of tangling and scattering resulted from crosscutting concerns. Crosscutting concerns are considered as potential aspects and can lead to the phenomena “tyranny of the dominant decomposition”. Requirements-level aspects are responsible for producing scattered and tangled descriptions of requirements in the requirements document. Validation of requirements artefacts is an essential task in software development. This task ensures that requirements are correct and valid in terms of completeness and consistency, hence, reducing the development cost, maintenance and establish an approximately correct estimate of effort and completion time of the project. In this paper, we present a validation framework to validate the aspectual requirements and the crosscutting relationship of concerns that are resulted from the requirements engineering phase. The proposed framework comprises a high-level and low-level validation to implement on software requirements specification (SRS). The high-level validation validates the concerns with stakeholders, whereas the low-level validation validates the aspectual requirement by requirements engineers and analysts using a checklist. The approach has been evaluated using an experimental study on two AORE approaches. The approaches are viewpoint-based called AORE with ArCaDe and lexical analysis based on Theme/Doc approach. The results obtained from the study demonstrate that the proposed framework is an effective validation model for AORE artefacts.

show abstract