Duration: February 2010 - April 2011
The global competition challenges the competitiveness of the European software industry, requiring increased efficiency and quality of software development, improved management of huge and complex software systems, and customer-tailored software products. Model-driven software development (MDSD) provides means for separating business and implementation aspects of software at different levels of abstraction and is therefore a key to the achievement of these goals. However, even in MDSD there are key questions, such as the validity of models, the relationship between models and code, and properties of model transformations, which cannot be answered by today's technology. Yet, at this point in time, we face a possible opportunity to tackle these problems: ontologies allow for managing, integrating and validating information found in different software models and code, independently of whether they are graphical models, domain-specific languages, model and software transformations or knowledge about steps in the software process.
One major objective of the MOST project Marrying Ontology and Software Technology) is to leverage MDSD and other approaches from software technology with ontology technology. This concerns all involved artifacts (ontology and modeling languages, models, tools), as well as the development processes. For this purpose, the MOST approach will integrate ontologies and software technologies at three different levels. First, integration will be addressed at the level of modeling languages. Second, ontologies and models will be integrated so that ontologies can be used in models, and vice versa. Third, ontology-based queries will be integrated on the level of model transformations.
As a second major objective, the MOST intends to support the software development process with ontology technology, resulting in Ontology-driven software development (ODSD). Here, the development process will be guided by process guidance ontologies that formalize the rules, conditions and actions a software engineer has to conduct at specific process stages. Thus, it is possible to guide developers through the development and to give appropriate, situation-specific guidance information To be able to capture the current state of the process and related artifacts, it is essential to maintain traceability information between individual artifacts and/or models.
The results of MOST will be applied and evaluated in three case studies in the area of product lines for telecommunications software and in the area of supporting software development at SAP.
Please find further information, publications and current work under Focus Group Software Web