OSDM definition
Examples of OSDM in a sentence
An initial function called the Optimization Space Definition Module (OSDM) will take this model and determine the possible design space.
Unlike the other elements, which are used in each optimisation iteration, the OSDM is only required once, at the beginning of the optimisation.
The OSDM is necessary to ensure that the optimisation engine itself does not need to know anything about the semantics of the models it deals with other than what variability is present in the original model and how it can be encoded.
However, for pragmatic implementation reasons a different form of encoding might be required to simplify the implementation of the OSDM and/or the optimisation engine or to enable the reuse of existing implementations (to be investigated).
Apart from the OSDM, the optimisation process therefore consists of a loop - from engine to VRM, to analysis tools, and back to engine - which is iterated continuously until the optimisation is complete.
Unlike the other elements, which are used in each optimisation iteration, the OSDM is only required once, at the beginning of the optimisation, not iteratively in each optimisation cycle as the other elements.
The OSDM could also have a mode in which it strips out or hides any irrelevant variability, e.g. allowing optimisation to take place on only one product line variant.
In parallel (and afterwards), development of a prototype optimisation architecture should take place, i.e. the OSDM, VRM, ▇▇▇, and a few analysis wrappers (all implemented as Papyrus-compatible plugins in Java).
The optimisation space definition module (OSDM) takes a model with variability and derives from that an abstract definition of the optimisation space, i.e. a structure which can be manipulated to obtain the set of all valid design candidates – the Master Encoding Hierarchy (MEH).
It implements both the OSDM and VRM as part of the existing CVM plugin and also includes a new prototype ▇▇▇.