Integrity validation for object versions in a co-operative design environment

Configuration management in evolutionary engineering design using versioning and integrity constraints

“…The creation of an executable CVO is transparent to the designer and handled by the system. The details of this model are given in Goonetillake et al (2001).…”

“…However, a set of design constraints will evolve over time with modifications (Dieter, 1991;Thompson et al, 1993;Ramachandran, 1989;Ram et al, 1997), the addition of new constraints and the omission of existing constraints. A constraint management framework for engineering design was described by Goonetillake et al (2001). In essence this framework is based around an object version model in which the constraint categories are value based (e.g.…”

“…We utilised the version model (for primitive versions) described by Goonetillake et al (2001) as the foundation upon which the configuration management model is built. In Section 4 we discussed the drawbacks associated with static binding such as version proliferation and therefore recommended dynamic binding as the more appropriate approach to be used for configurations.…”

“…Different configurations of the same composite object may have to satisfy different sets of inter-dependency constraints at different times. In Goonetillake et al (2001), an integrity validation model for object versions in general was presented, which considered the means of representing and managing evolving design constraints in a collaborative engineering design environment. We have not located in the literature, a version model that deals with the consistency of design configurations, through managing constraint evolution.…”