| SPP Tool Chain | ![]() |
| 5.2 Output Interface model |
The above class diagram was designed based on the idea that DESERT outputs valid configurations that satisfy the applied constraints. Each configuration will have exactly one Natural member or Custom member assigned to each Variable property, and exactly one node (=Element) for each compound node of type OR in space.
The DesertBackSystem is a class that contains everything. This will be the type of the root object of the output data network. DesertBackSystem contains values, elements, and configurations that are objects of type value, element, and configuration, respectively. Further, the elements contain Variable properties. Elements and Variable properties have exactly the same semantics as in the input interface model.
A Configuration object identifies a particular configuration in the design space. The valid configurations are numbered, beginning from 1, and these are the values of their id attribute. The name attribute value will be set to "Conf. no. x", where x is the id of the configuration. A configuration contains assignments, which can be of two kinds: Alternative Assignment and Property Assignment . Alternative assignments assign a compound OR node (alternative_of) to a child node (alternative). Property assignments assign a Value to a Variable Property. However, if there are multiple Assigned value objects in the input data network assigning the same member to the same Variable property, for each such Assigned value object there will be a Property Assignment object in the output data network.
The Value objects, and it's derivates, Custom member and Natural member correspond to the member, custom member and natural member objects, respectively, defined in the input interface model.
The values of the id, externalID attributes of the objects in the output data network are equal to the values of the id and externalID attributes of the corresponding objects defined in the input interface model.
Next Up: 6 Tutorial