Requirements Traceability and Transformation Conformance in Model-Driven Development

Almeida, João Paulo A.; Eck, Pascal van; Iacob, Maria-Eugenia

doi:10.1109/edoc.2006.45

Cited by 12 publications

(12 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…However, requirements on the model-driven design trajectory (so-called application-independent requirements) are addressed by Almeida et al (2006d). According to Almeida et al (2006d), these are to be maintained separately from application-specific requirements, and are relevant only to "suppliers" and their internal organization and are not visible to "customers. "…”

Section: Requirements Engineering and Traceabilitymentioning

confidence: 99%

“…These should be captured Table 4 Requirements traceability matrix with indirect evidence Table 3 Requirements traceability matrix with direct evidence in project requirements which "represent an understanding between the customer and the supplier about contractual matters pertaining to production of software and thus should not be included in the SRS." However, requirements on the model-driven design trajectory (so-called application-independent requirements) are addressed by Almeida et al (2006d). According to Almeida et al (2006d), these are to be maintained separately from application-specific requirements, and are relevant only to "suppliers" and their internal organization and are not visible to "customers.…”

Section: Requirements Engineering and Traceabilitymentioning

confidence: 99%

See 1 more Smart Citation

Requirements traceability in model-driven development: Applying model and transformation conformance

2007

Self Cite

View full text Add to dashboard Cite

The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations.

show abstract

Section: Requirements Engineering and Traceabilitymentioning

confidence: 99%

Section: Requirements Engineering and Traceabilitymentioning

confidence: 99%

Requirements traceability in model-driven development: Applying model and transformation conformance

2007

Self Cite

View full text Add to dashboard Cite

show abstract

“…We reuse the idea that the model must be as simple as possible and the complex logic for analysis shifted to the tool support. There exists a large body of knowledge related to metamodels for traceability [3,4,9,10,16,19,26,28,48,49,55]. A variety of approaches for storing traceability information are proposed: database schema [6], XML schema [26,49] or metamodels [19,28,46].…”

Section: Traceability Framework Metamodelmentioning

confidence: 99%

A model-driven traceability framework for software product lines

et al. 2009

View full text Add to dashboard Cite

Software product line (SPL) engineering is a recent approach to software development where a set of software products are derived for a well defined target application domain, from a common set of core assets using analogous means of production(for instance, through Model Driven Engineering). Therefore, such family of products are built from reuse, instead of developed individually from scratch. Software product lines promise to lower the costs of development, increase the quality of software, give clients more flexibility and reduce time to market. These benefits come with a set of new problems and turn some older problems possibly more complex. One of these problems is traceability management. In the European AMPLE project we are creating a common traceability framework across the various activities of the SPL development. We identified four orthogonal traceability dimensions in SPL development, one of which is an extension of what is often considered as "traceability of variability". This constitutes one of the two contributions of this paper. The second contribution is the specification of a metamodel for a repository of traceability links in the context of SPL and the implementation of a respective traceability framework. This framework enables fundamental traceability management operations, such as trace import and export, modification, query and visualization. The power of our framework is highlighted with an example scenario.

show abstract

“…In [4], Almeida et al aim at simplifying the management of relationships between requirements and various design artefacts. They propose a framework which is a basis for tracing requirements, assessing the quality of model transformation specifications, metamodels, models and realizations.…”

Section: Requirements Traceability and Transformation Conformance (Rttc)mentioning

confidence: 99%

Survey of Traceability Approaches in Model-Driven Engineering

Galvão

Göknil

2007

11th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2007)

View full text Add to dashboard Cite

Models have been used in various engineering fields to help managing complexity and represent information in different abstraction levels, according to specific notations and stakeholder's viewpoints. Model-Driven Engineering (MDE) gives the basic principles for the use of models as primary artefacts throughout the software development phases and presents characteristics that simplify the engineering of software in various domains, such as Enterprise Computing Systems. Hence, for its successful application, MDE processes must consider traceability practices. They help the understanding, capturing, tracking and verification of software artefacts and their relationships and dependencies with other artefacts during the software life-cycle. In this survey, we discuss the state-of-the-art in traceability approaches in MDE and assess them with respect to five general comparison criteria: representation, mapping, scalability, change impact analysis and tool support. As a complementary result, we have identified some open issues that can be better explored by traceability in MDE.

show abstract

Requirements Traceability and Transformation Conformance in Model-Driven Development

Abstract: The variety of design artefacts (models)

Cited by 12 publications

References 17 publications

Requirements traceability in model-driven development: Applying model and transformation conformance

Requirements traceability in model-driven development: Applying model and transformation conformance

A model-driven traceability framework for software product lines

Survey of Traceability Approaches in Model-Driven Engineering

Contact Info

Product

Resources

About