PDFPrintE-mail

Model-Driven Software Development

Last Updated (Wednesday, 16 June 2010 19:16) Written by Thomas Schütz Monday, 05 April 2010 19:42

In the first place the development of model driven tools and applications requires a sound knowledge of the application domain. Protos gathered experiences over many years from development projects in the domains of industrial automation, telecom and automotive. Protos develops the requirements in a dialog form together with the customer's domain experts. Thus the customer's excellent domain knowledge is complemented by Protos' expertise in finding meaningful abstractions.

In a second step a metamodel is created from the abstractions chosen which serves as a backbone for the whole application.

Textual, graphical or form based editors allow context dependent views of the model and always provide fast editing of the models and a good overview.

This way a tool is created which is tailored to suit the user's needs and provides the best means to support his work.

For Embedded Systems frequently not only static structure but also behaviour is modelled. So the job isn't done just by modelling. The tooling to produce executable code is also required. This is achieved by code generators developed for this special purpose.

It is quite common that this code runs on top of a middleware which implements part of the abstract concepts of the modelling language.