Results 1 - 10
of
14
Survey of Traceability Approaches in Model-Driven Engineering
- in Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference
, 2007
"... Models have been used in various engineering fields to help managing complexity and represent information in dif-ferent 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 artefac ..."
Abstract
-
Cited by 14 (1 self)
- Add to MetaCart
(Show Context)
Models have been used in various engineering fields to help managing complexity and represent information in dif-ferent 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 engi-neering 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 verifica-tion of software artefacts and their relationships and depen-dencies with other artefacts during the software life-cycle. In this survey, we discuss the state-of-the-art in traceabil-ity 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. 1
C.: On-Demand Merging of Traceability Links with Models. 3 rd ECMDA Traceability Workshop
, 2006
"... Abstract. Model management operations such as refinement and transformation modify existing or produce new models. To assist both engineers and tools in tracing the path of changes and decisions, maintenance of traceability information is essential. There are two main approaches for storing traceabi ..."
Abstract
-
Cited by 11 (4 self)
- Add to MetaCart
(Show Context)
Abstract. Model management operations such as refinement and transformation modify existing or produce new models. To assist both engineers and tools in tracing the path of changes and decisions, maintenance of traceability information is essential. There are two main approaches for storing traceability; in the first, traceability information is embedded inside the models, while in the second, traces form separate models. The former allows users to inspect traceability information in a visual manner, but pollutes the models, while the latter keeps the models clean, but visualization is troublesome. In this paper, we propose a unification of the two approaches via model merging. We suggest that traceability information should be maintained in separate models, which can be merged with the primary model(s) on demand to produce annotated models for inspection purposes. We present a concrete example that demonstrates the practicality of our approach. 1
Building Model-Driven Engineering Traceability Classifications
"... Abstract. Model-Driven Engineering involves the application of many different model management operations, some automated, some manual. For developers to stay in control of their models and codebase, trace information must be maintained by all model management operations. This leads to a large numbe ..."
Abstract
-
Cited by 7 (3 self)
- Add to MetaCart
Abstract. Model-Driven Engineering involves the application of many different model management operations, some automated, some manual. For developers to stay in control of their models and codebase, trace information must be maintained by all model management operations. This leads to a large number of trace links, which themselves need to be managed, queried, and evaluated. Classifications of traceability and trace links are an essential capability required for understanding and managing trace links. We present a process for building traceability classifications for a variety of widely used and accepted operations (both automated and manual) and show the results of applying the process to a rich traceability context. 1.
Inter-dsl coordination support by combining megamodeling and model
- Eds.), Proceedings of the 2010 ACM Symposium on Applied Computing (SAC
, 2010
"... Model-Driven Engineering (MDE) advocates the use of models at every step of the software development process. Within this context, a team of engineers collectively and collaboratively contribute to a large set of interrelated models. Even if the main focus can be on a single model (e.g. a class diag ..."
Abstract
-
Cited by 7 (0 self)
- Add to MetaCart
(Show Context)
Model-Driven Engineering (MDE) advocates the use of models at every step of the software development process. Within this context, a team of engineers collectively and collaboratively contribute to a large set of interrelated models. Even if the main focus can be on a single model (e.g. a class diagram model), related elements in other models (e.g. a requirement model) often have to be considered and/or accessed. Moreover, all the involved models do not necessarily conform to the same metamodel and thus may have been built using different independent Domain-Specific Languages (DSLs). Such a situation has already been frequently observed in many large-scale industrial deployments of MDE. Manually coordinating all the involved models, i.e. being able to both manage and use the links existing between them, can become a cumbersome and difficult task. As a proposal to solve this inter-DSL coordination issue, we introduce in this paper a generic and extensible inter-model traceability and navigation environment based on the complementary use of megamodeling and model weaving. We illustrate our solution with a concrete working example.
A Traceability Engine Dedicated to Model Transformation for Software Engineering. ECMDA Traceability Workshop
, 2008
"... Abstract. This paper deals with the use of a model transformation traceability engine in a model-driven process. We propose to use traces of model transformations for the visualization and debugging of an example of model refactoring transformation. We start off with the transformation Java code and ..."
Abstract
-
Cited by 5 (0 self)
- Add to MetaCart
(Show Context)
Abstract. This paper deals with the use of a model transformation traceability engine in a model-driven process. We propose to use traces of model transformations for the visualization and debugging of an example of model refactoring transformation. We start off with the transformation Java code and analyse the trace graph generated by the framework during the transformation execution. A short description of the framework and its functionalities is presented. We compare our work with frameworks already proposed to manage traceability in a MDE context. 1
PREDIQT: A Method for Model-based Prediction of Impacts of Architectural Design Changes on System Quality
, 2011
"... ii The increasing criticality of the ICT systems and the steady growth of their mutual collaboration impose new challenges with respect to adapting system architecture to new needs while preserving the required system quality. Architectural adaptions are inevitable for accommodating the systems to t ..."
Abstract
-
Cited by 4 (4 self)
- Add to MetaCart
(Show Context)
ii The increasing criticality of the ICT systems and the steady growth of their mutual collaboration impose new challenges with respect to adapting system architecture to new needs while preserving the required system quality. Architectural adaptions are inevitable for accommodating the systems to the new services, processes, technologies, standards, or users. However, due to criticality of the systems involved, planning, implementation, testing and deployment of changes can not involve downtime or similar degradation of quality of service. Instead, the systems have to quickly and frequently adapt at runtime, while maintaining the required quality of service. Architectural adaptions which realize the new collaborations often also have to provide conditions for compatible quality levels across systems. We argue that quality has to be predictable in order for systems in collaboration to be trustworthy. There are often trade-offs between quality characteristics. Moreover, one quality goal may be possible to achieve through several different architectural designs. Before adapting a system to changes,
Towards a Generic Solution for Traceability in MDD
"... Abstract. Traceability is an important feature in model-driven development. Many research initiatives are currently investigating how to collect, store and utilize traceability information to improve the quality of the MDD process, and there is a need to unify the results from these initiatives. Thi ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
(Show Context)
Abstract. Traceability is an important feature in model-driven development. Many research initiatives are currently investigating how to collect, store and utilize traceability information to improve the quality of the MDD process, and there is a need to unify the results from these initiatives. This paper proposes a generic solution for traceability that offers a set of services that is meant to cover both the specification and appliance of traceability. Our proposed traceability solution is specified as a metamodel with guidelines and templates for use. An example of how the solution can be integrated in a model-driven development project is given.
A Model-Driven Traceability Framework for Software Product Lines
, 2012
"... 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). Ther ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
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
Towards Rigorously Defined Model-to-Model
"... Abstract. A Model Driven Engineering process typically involves models expressed in different modelling languages that capture different views of the system under development. To enhance automation, consistency and coherency, establishing and maintaining semantically rich traceability links between ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. A Model Driven Engineering process typically involves models expressed in different modelling languages that capture different views of the system under development. To enhance automation, consistency and coherency, establishing and maintaining semantically rich traceability links between model elements that belong to different models used throughout the process is of paramount importance. In this paper we propose a rigorous approach to defining such semantically rich traceability links between models expressed in diverse modelling languages using case-specific traceability metamodels and demonstrate the practicality and usefulness of our approach using a concrete example. 1