On the use of model transformation for requirements trace models generation

Haidrar, Saida; Anwar, Adil; Roudiès, Ounsa

doi:10.1109/wits.2017.7934625

Cited by 3 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Considering the assessment methodology criteria, we note that in most works, the authors show the feasibility of their approaches [13] , [15] , [18] , [20] , [22], [23] , [24] , [25], [26] and [28] through simple case studies or very simple examples. Only few works [27], [12] , [14] , [17], [21], [29], [1] propose a practical assessment methodology. In our method, we have developed a prototype for the transformation approach and an Eclipse plug-in for the traceability approach.…”

Section: Evaluation Results 71 Comparison Of Our Traceability Methods...mentioning

confidence: 99%

“…In the second category explicit traceability models are defined through two methodologies: (i) defining a separate external traceability models basing on transformation models that consists of storing all trace links as an external traceability model that conforms to traceability meta-model [21] , [22], [23] , [24] , or (ii) defining external traceability manually that consists of creating traceability links in the form of a separate trace model [4], [25] , [26] , [25] , [27]. , [28] , [29] and [1].…”

Section: Related Workmentioning

confidence: 99%

“…Related works of the first methodology (i) include a study in [21] that introduces a profile to capture traceability information from the requirement model before performing the generation of a design model. Another traceability approach [22] provides a meta-model that contains a set of concepts for traceability of model elements and their locations in the code artifacts.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Explicit traceability model for aligning a conception sequence diagram and a BPMN diagram

Bouzidi

Haddar

2023

Preprint

View full text Add to dashboard Cite

In modern software engineering process methodologies, business process models (BPM) tend to occupy an increasingly important role in the development and ongoing management of information systems (IS). However, only few information systems are developed according to the business processes they support. This separation leads to differences between the economic model and the model of IS. Thus, this work aims to bridge the gap between business and software modeling. To achieve this goal, we introduce an explicit traceability methodology that extends a previous requirements traceability methodology to address alignment and the coevolution of the dynamic viewpoint of the software models and business process models (BPM). Indeed, we first define a unified trace metamodel that includes all Business Process and Model Notation (BPMN) and Unified Modeling Language (UML) elements (use cases, conception sequence diagrams) and traceability links between interconnected elements. Next, we instantiate the built-in metamodels in the form of new diagrams called BPMNTraceISM (BPMN Traces Information System Models). Finally, we define a set of bi-directional transformation models between the BPMN, UML, and the new BPMNTraceISM diagrams. To prove the feasibility of our traceability method, we implemented a full graphic editor to design and visualize BPMNTraceISM diagrams, and ATL (ATLAS Transformation Language) rules to support the bi-directional transformation models. We have also test traceability methods with a case study.

show abstract

Section: Evaluation Results 71 Comparison Of Our Traceability Methods...mentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Explicit traceability model for aligning a conception sequence diagram and a BPMN diagram

Bouzidi

Haddar

2023

Preprint

View full text Add to dashboard Cite

show abstract

“…Many approaches define relation types, mostly as part of their specific meta-model, e.g., [5,10,11,14,29,42,[65][66][67], or [12], but despite similarities there is no common terminology or semantics, as already criticized by Espinoza et al [14,68] and listed as traceability challenge by Winkler and Pilgrim [69]. Spanoudakis and Zisman [2] identify commonalities and describe eight main relation types, complemented by Espinoza et al [14] with two additional from Letelier [66] In the following exemplary those types, which we later explicitly use in our model and case study excerpts, are shortly described with examples from EagleEye.…”

Section: Traceability Relation Typesmentioning

confidence: 99%

Requirements document relations

2022

View full text Add to dashboard Cite

Relations between requirements are part of nearly every requirements engineering approach. Yet, relations of views, such as requirements documents, are scarcely considered. This is remarkable as requirements documents and their structure are a key factor in requirements reuse, which is still challenging. Explicit formalized relations between documents can help to ensure consistency, improve completeness, and facilitate review activities in general. For example, this is relevant in space engineering, where many challenges related to complex document dependencies occur: 1. Several contractors contribute to a project. 2. Requirements from standards have to be applied in several projects. 3. Requirements from previous phases have to be reused. We exploit the concept of “layered traceability”, explicitly considering documents as views on sets of individual requirements and specific traceability relations on and between all of these representation layers. Different types of relations and their dependencies are investigated with a special focus on requirement reuse through standards and formalized in an Object-Role Modelling (ORM) conceptual model. Automated analyses of requirement graphs based on this model are able to reveal document inconsistencies. We show examples of such queries in Neo4J/Cypher for the EagleEye case study. This work aims to be a step toward a better support to handle highly complex requirement document dependencies in large projects with a special focus on requirements reuse and to enable automated quality checks on dependent documents to facilitate requirements reviews.

show abstract

“…However, this approach is unable to customize the traceability of all the initial metamodel elements; only the transformed elements are traced. Several approaches use this method such as Haidrar et al [16], which proposes a profile that helps to capture traceability information from the requirement model before performing the transformation to a design model. Generally, model transformation provides the ability to link model elements, but it is unable to manage the traceability of all existing heterogeneous metamodel elements.…”

Section: Related Workmentioning

confidence: 99%

Traceability and Synchronization Between BPMN and UML Use Case Models

Bouzidi¹,

Haddar²,

Haddar³

2019

ISI

View full text Add to dashboard Cite

The purpose of this paper is to ensure and maintain the alignment between business modeling and requirement elicitation. To do this, we propose an approach that combines the strengths of traceability and model transformations to bridge the gap between BPMN model and the UML use Case models in particular, we propose an intermediate integrated model (BPSUC), and bidirectional transformation rules between the use case and BPMN models into the BPSUC and vice versa. We have implemented an editor to design and visualize BPSUC, and ATL transformation rules to carry out transformation and have successfully tested our approach on a case study, and evaluation criteria. The engineers and the business design can use BPSUC to work together in a single integrated diagram as well as they can synchronize their initial model through the bidirectional model transformations.

show abstract

On the use of model transformation for requirements trace models generation

Cited by 3 publications

References 6 publications

Explicit traceability model for aligning a conception sequence diagram and a BPMN diagram

Explicit traceability model for aligning a conception sequence diagram and a BPMN diagram

Requirements document relations

Traceability and Synchronization Between BPMN and UML Use Case Models

Contact Info

Product

Resources

About