A software engineering experiment in software component generation
Proceedings of the 18th international conference on Software engineering
The Impact of Maintainability on Component-based Software Systems
EUROMICRO '03 Proceedings of the 29th Conference on EUROMICRO
Verifying Metamodel Coverage of Model Transformations
ASWEC '06 Proceedings of the Australian Software Engineering Conference
Practical Model-Based Testing: A Tools Approach
Practical Model-Based Testing: A Tools Approach
Domain-Specific Modeling
A Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance
IEEE Transactions on Software Engineering
Process Algebra for Parallel and Distributed Processing
Process Algebra for Parallel and Distributed Processing
Worst Practices for Domain-Specific Modeling
IEEE Software
Test-Driven Development of Model Transformations
MODELS '09 Proceedings of the 12th International Conference on Model Driven Engineering Languages and Systems
Tooling for the full traceability of non-functional requirements within model-driven development
Proceedings of the 6th ECMFA Traceability Workshop
Implementing modular domain specific languages and analyses
Proceedings of the Workshop on Model-Driven Engineering, Verification and Validation
Hi-index | 0.00 |
The utilisation of Domain-Specific Modelling (DSM) in software development has a significant positive impact on productivity. The productivity increase is caused by the utilisation of modelling languages and generators that are especially suitable for a specific problem domain instead of those designed for solution domains. The prerequisite for this significant productivity increase is that the languages and the automation function correctly. To ensure the suitability of the languages and tools, we need to be able to use the verification and validation (V&V) techniques in the context of DSM. In this position paper we study what V&V actually stands for in this particular context and what the current means are for performing V&V. We found that although there are some means available for verification, comprehensive methods still do not exist. For validation, we believe that maintaining a bidirectional trace link between requirements, models and the generated deliverables is a promising approach to significantly facilitate the validation process.