From requirements to code in a model driven way

Authors:
Audris Kalnins;Elina Kalnina;Edgars Celms;Agris Sostaks
Affiliations:
IMCS, University of Latvia, Riga, Latvia;IMCS, University of Latvia, Riga, Latvia;IMCS, University of Latvia, Riga, Latvia;IMCS, University of Latvia, Riga, Latvia
Venue:
ADBIS'09 Proceedings of the 13th East European conference on Advances in Databases and Information Systems
Year:
2009

Citing 5
Cited 2

Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Model transformation language MOLA

MDAFA'03 Proceedings of the 2003 European conference on Model Driven Architecture: foundations and Applications
Natural MDA: controlled natural language for action specifications on model driven development

ODBASE'06/OTM'06 Proceedings of the 2006 Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, DOA, GADA, and ODBASE - Volume Part I
Complementary use case scenario representations based on domain vocabularies

MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems

Improving formal verification practicability through user oriented models and context-awareness

Proceedings of the 8th International Workshop on Model-Driven Engineering, Verification and Validation
Transforming and tracing reused requirements models to home automation models

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Though there is a lot of support for model driven development the support for complete model driven path from requirements to code is limited. The approach proposed in this paper offers such a path which is fully supported by model transformations. The starting point is semiformal requirements containing behaviour description in a controlled natural language. A chain of models is proposed including analysis, platform independent and platform specific models. A particular architecture style is chosen by means of selecting a set of appropriate design patterns for these models. It is shown how to define informally and then implement in model transformation language MOLA the required transformations. By executing these transformations a prototype of the system is obtained.