A rule-based approach for evolution of AADL models based on changes in functional requirements

Göknil, Arda; Kurtev, Ivan; Berg, Klaas van den

doi:10.1145/2993412.3004846

Cited by 4 publications

(2 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Changes to specifications have a significant effect on software release schedules, defect rates, budget, and project performance. The degree to which software project schedules, defect counts, costs, and performance are all negatively correlated with the number of requirements change [27]. The software development life cycle consists of a number of processes, such as the design, development, and testing of the software.…”

Section: D) Change Impact Analysismentioning

confidence: 99%

Exploring Software Development Change Analysis with an Emphasis on Requirements

Syed Adnan Afaq

2023

IJRITCC

View full text Add to dashboard Cite

Most software requirements are not definitive of the development process. Rapid changes in user expectations, market conditions, and company practises all need regular updates to software. Requirement change management is a crucial and difficult component of every software development project. Project failure or cancellation often occurs because of requirements changes. Requirements Change refers to requirements that are added, removed, or amended during the system development life cycle. Requirements Change requires additional work in the design phase, which boosts the cost of developing the system, lengthens the time required, and reduces system quality. The paper investigates research efforts in the topic of requirement change and helps in determining the study's purpose. Various Requirement Change Management concepts and approaches are provided, and numerous activities are conducted to mitigate the effects of requirement changes. The study emphasizes on causes, attributes, prioritization of changed requirement, framework for RCM and Change Impact Analysis. This study briefly describes all the possible fact and figure about requirement change. The study includes various phases of requirement change management such as Requirement Elicitation, Requirement Change Identification in Requirement Document using Two Phase Requirement Document Comparison Algorithm, Prioritization of Changed Requirement using Fuzzy approach, Interdependency analysis and change impact analysis on various software project parameters such as time, cost and human resources.

show abstract

Section: D) Change Impact Analysismentioning

confidence: 99%

Exploring Software Development Change Analysis with an Emphasis on Requirements

Syed Adnan Afaq

2023

IJRITCC

View full text Add to dashboard Cite

show abstract

“…The approach described in Goknil et al [11] acts on AADL software architecture and is based on verifying functional requirements and uses Maude model checker. Blouin et al [2] defines a way to link requirement and AADL element and ALISA also has the similar meta-model with this tool.…”

Section: Related Workmentioning

confidence: 99%

Automatic Generation of the AADL ALISA Verification Plan with ATL

Wu¹,

Huang²,

Yang³

et al. 2017

IJPE

View full text Add to dashboard Cite

Architecture Led Incremental System Assurance short for ALISA presents a method to check if a system implementation meets its requirements. This method helps find errors in the early phase of system integration. ALISA provides four notations-requirements specifications, architecture models, verification techniques and assurance cases. The verification plan, which is designed by extracting information from requirement specification and architecture model, can be executed on the system and the result is significant metrics to judge the system quality. There are problems when generating a verification plan. As for the hierarchical architecture model with increasing complexity, the system may be divided into several parts and it is difficult to accomplish the assurance manually for each tier of the architecture. The approach also needs to respond to the ever-changing demands rapidly. New faults may be introduced artificially when designing requirement specifications and verification plans. In the paper, we propose an approach which uses ATL, whose full name is ATLAS transformation language, to help automatically generate verification plans. The meta-model of the verification plan and of requirement specification are given. Thus, designing the transformation rules from the verification part to the requirement part is easy. A lightweight template described in ATL is used to generate the verification plan for critical requirement and quality property.

show abstract