Model-driven engineering (MDE) provides us with efficient tools for generating software, re-engineering solutions, and even becoming involved with enterprise wide architectural strategies. 

There are three very different approaches from which MSc theses can scrutinize these tools or tool chains:

• Comparison of the currently available tools and their applicability for large development projects, especially when services and service systems are expected to be the main product. The set of evaluation criteria for this group of desing, development and implementation tools is rigorous, ranging from business needs to use of formal computer science theories in their built, and to the applicability to use in different technological environments.
• An analysis of prerequisites and potential consequences for a company that  considers taking  MDE tools  in use. Gains include increase of efficiency, clarity of large scale systems architecture, automation of reporting and testing, and many others. There is a good amount of cases to provide evidence for this. On the other hand, the transition to methodologies relying on totally new concepts (service-orientation and model-orientation) requires investments and may cause other worries and risks as well. A real company to give a realistic background situation for the evaluation is necessary for this kind of thesis.
• The formalisms that enable the building of model-driven software and architecture management tools is multifaceted. A formally oriented MDE thesis explains the foudations and how they become used in the tools, and what kind of consequences (gains, costs, vulnerabilities, potential for reducing risks) they cause in production processes, for business strategies, and to the users of software-supported services.