Realization
From IDMPP
(→Build Configuration Resolution Demonstrator) |
|||
| Line 3: | Line 3: | ||
== Build Configuration Resolution Demonstrator == | == Build Configuration Resolution Demonstrator == | ||
| + | The use case aims to show that the MDE technology and the solver technology can be used to solve software engineering problem. The size increase of the software has leaded the computer science to introduce the concept of components. A component is a reusable piece of software which is combined with other components to implement another software component. The use of components by another implies the declaration of a dependency from the using component to the used component. The dependency can be constrained by a version range. For example: the version 1.2 of component A has dependency to the component B having a version upper than 2.3 and lower to 3.1. We meet more and more software products that are composed of huge number components, for example the yearly release of Eclipse (Helios) contains 11974 components and 80080 dependencies. To define a build configuration for such kind of software is a complex problem that cannot be solved in an acceptable time by regular algorithms. | ||
| + | The use case shows the use of MDE and solver technology to generate an Eclipse build configuration conforming to the dependencies constraints and to additional constraints. | ||
== OCL++ == | == OCL++ == | ||
Revision as of 11:55, 15 September 2011
Contents |
Build Configuration Resolution Demonstrator
The use case aims to show that the MDE technology and the solver technology can be used to solve software engineering problem. The size increase of the software has leaded the computer science to introduce the concept of components. A component is a reusable piece of software which is combined with other components to implement another software component. The use of components by another implies the declaration of a dependency from the using component to the used component. The dependency can be constrained by a version range. For example: the version 1.2 of component A has dependency to the component B having a version upper than 2.3 and lower to 3.1. We meet more and more software products that are composed of huge number components, for example the yearly release of Eclipse (Helios) contains 11974 components and 80080 dependencies. To define a build configuration for such kind of software is a complex problem that cannot be solved in an acceptable time by regular algorithms.
The use case shows the use of MDE and solver technology to generate an Eclipse build configuration conforming to the dependencies constraints and to additional constraints.
