Supporting Systems Development by Capturing Deliberations During Requirements Engineering
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Quantifying the closeness between program components and features
Journal of Systems and Software - Special issue on software maintenance
Computer
An Object-Oriented Tool for Tracing Requirements
IEEE Software
OCL: Syntax, Semantics, and Tools
Object Modeling with the OCL, The Rationale behind the Object Constraint Language
ATL: A model transformation tool
Science of Computer Programming
A Petri Net Based Debugging Environment for QVT Relations
ASE '09 Proceedings of the 2009 IEEE/ACM International Conference on Automated Software Engineering
Analysis of crosscutting in early software development phases based on traceability
Transactions on aspect-oriented software development III
Estimating footprints of model operations
Proceedings of the 33rd International Conference on Software Engineering
Tractable model transformation testing
ECMFA'11 Proceedings of the 7th European conference on Modelling foundations and applications
Dynamic Backward Slicing of Model Transformations
ICST '12 Proceedings of the 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation
Formal specification and testing of model transformations
SFM'12 Proceedings of the 12th international conference on Formal Methods for the Design of Computer, Communication, and Software Systems: formal methods for model-driven engineering
| Hi-index | 0.00 |
Several approaches for specifying the requirements for model transformations have been proposed. Most of them define constraints on source and target models as well as on the relationships between them. A major advantage of these approaches is their independence from transformation implementation languages and transformation implementations. However, when these constraints are used for testing, identifying the model transformation rules that violate the constraints is not possible. In this paper we present an approach for automatically aligning specifications of model transformations and their implementations. Matching functions establish these alignments based on the used metamodel elements in the constraints and rules. We present our first results and outline further use cases where an alignment between constraints and rules is beneficial.