Validation Framework for Aspectual Requirements Engineering (ValFAR)

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

doi:10.1145/3410352.3410777

Cited by 10 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This section describes the proposed solution, i.e., the Validation Framework for Aspectual Requirements (ValFAR) [12]. It validates the AORE artefacts in three main phases, each of which has its activities as shown in Figure 1.…”

Section: The Proposed Approachmentioning

confidence: 99%

“…Some experiments and case studies were conducted in terms of aspects and concerns identification. Therefore, we have proposed a framework, i.e., Validation Framework for Aspectual Requirements (ValFAR) to validates the AORE artefacts in three main phases, each of which has several activities [12]. Phase 1 is for concern handling, Phase 2 is for concern validation, i.e., high-level validation, whereas Phase 3 consists of Aspectual requirement specification and validation, i.e., low-level validation.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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

Section: The Proposed Approachmentioning

confidence: 99%

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

show abstract

“…A well-defined interface enables reasoning about a range of issues in relative isolation. Thus, they become (un)pluggable and customizable via independent development (Alshareef et al, 2020). This article will provide an introduction of aspect-oriented programming and explain the notion of a common set of important terminology.…”

Section: Introductionmentioning

confidence: 99%

Aspect Oriented Programming: Trends and Applications

et al. 2022

View full text Add to dashboard Cite

The competitive advantage of aspect oriented programming (AOP) is that it improves the maintainability and understandability of software systems by modularizing crosscutting concerns. However, some concerns, such as logging or debugging, may be overlooked and should be entangled and distributed across the code base. AOP is a software development paradigm that enables developers to capture crosscutting concerns in split-aspect modes. Additionally, it is a novel notion that has the potential to improve the quality of software programs by removing the complexity involved with the production of code tangles via the usage of separation of concerns. As a result, it provides more modularity. Throughout its early development, some believed that AOP was easier to build and maintain than other implementations since it was based on an existing one. The statements are predicated on the premise that local improvements are easier to implement. Additionally, without appropriate visualization tools for both static and dynamic structures, cross-cutting challenges may be difficult for developers and researchers to appreciate. In recent years, AspectJ has begun to enable the depiction of crosscutting concerns via the release of IDE plugins. This article explains aspect oriented programming and how it may be used to improve the readability and maintainability of software projects. Additionally, it will evaluate the challenges it presents to application developers and academics.

show abstract