A Semi-Automated Approach for the Co-Refinement of Requirements and Architecture Models

Blouin, Dominique; Barkowski, Matthias; Schneider, Melanie; Giese, Holger; Dyck, Johannes; Borde, Étienne; Tamzalit, Dalila; Noppen, Joost

doi:10.1109/rew.2017.52

Cited by 2 publications

(2 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [72], a coevolution of use cases models and feature model configurations is proposed and implemented with a bidirectional transformation language. In [73], Blouin et al present a semiautomated approach to evolve nonfunctional requirements and their trace links following system's architecture refinement in the context of design space exploration and automated code generation. The approach has been prototyped for AADL models refined with the RAMSES tool and model transformations implemented as story diagrams.…”

Section: Model Refinementmentioning

confidence: 99%

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

Wang¹,

Yang²,

Huang³

et al. 2020

IEEE Trans. Rel.

View full text Add to dashboard Cite

Requirements traceability is broadly recognized as a critical element of any rigorous software development process, especially for building safety-critical software (SCS) systems. Modeldriven development (MDD) is increasingly used to develop SCS in many domains, such as automotive and aerospace. MDD provides new opportunities for establishing traceability links through modeling and model transformations. Architecture Analysis and Design Language (AADL) is a standardized architecture description language for embedded systems, which is widely used in avionics and aerospace industries to model safety-critical applications. However, there is a big challenge to automatically establish the traceability links between requirements and AADL models in the context of MDD, because requirements are mostly written as free natural language texts, which are often ambiguous and difficult to be processed automatically. To bridge the gap between natural language requirements (NLRs) and AADL models, we propose an approach to generate the traceability links between NLRs and AADL models. First, we propose a requirement modeling method based on the restricted natural language, which is named as RM-RNL. The RM-RNL can eliminate the ambiguity of NLRs and barely change engineers' habits of requirement specification. Second, we present a method to automatically generate the initial AADL models from the RM-RNLs and to automatically establish traceability links between the elements of the RM-RNL and the generated AADL models. Third, we refine the initial AADL models through patterns to achieve the change of requirements and traceability links. Finally, we demonstrate the effectiveness of our approach with industrial case studies and evaluation experiments.

show abstract

Section: Model Refinementmentioning

confidence: 99%

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

Wang¹,

Yang²,

Huang³

et al. 2020

IEEE Trans. Rel.

View full text Add to dashboard Cite

show abstract

“…In Blouin et al (2017) describe an approach in which affected link impact detection for linked requirements and architectural models is automated. Impact detection rules are based on the linked model elements' hierarchy and model element types to detect architectural refinements.…”

Section: Rq11: Which Tm Approaches Do Existmentioning

confidence: 99%

Interaction-based creation and maintenance of continuously usable trace links between requirements and source code

Hübner

Paech

2020

Empir Software Eng

View full text Add to dashboard Cite

Trace links between requirements and code are beneficial for many software engineering tasks such as maintenance, program comprehension, and re-engineering. If trace links are created and used continuously during a project, they need to have high precision and recall to be useful. However, manual trace link creation is cumbersome and existing automatic trace link creation methods are typically only applied retrospectively and to structured requirements. Therefore, they focus on recall and accept manual effort to cope with low precision. Such manual effort is not acceptable continuously. Furthermore, the maintenance of existing links along with changing artefacts in a project is neglected in most automatic trace link creation approaches. Therefore, we developed and evaluated an interaction log-based trace link creation approach IL to continuously provide correct trace links during a project. IL links unstructured requirements specified in an issue tracker and source code managed in a version control system. In the latest version, I L Com , our approach uses the interactions of developers with files in an integrated development environment and issue identifiers provided in commit messages to create trace links continuously after each commit. In this paper, we present I L Com , its most recent evaluation study, and a systematic literature review (SLR) about trace link maintenance (TM). We also present a TM process for I L Com based on two approaches from our SLR. In the evaluation study, we show that precision of I L Com created links is above 90% and recall almost at 80%. In the SLR, we discuss 16 approaches. Our approach is the first trace link creation approach with very good precision and recall and integrated trace maintenance.

show abstract

A Semi-Automated Approach for the Co-Refinement of Requirements and Architecture Models

Cited by 2 publications

References 16 publications

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

Interaction-based creation and maintenance of continuously usable trace links between requirements and source code

Contact Info

Product

Resources

About