Derived Object

The concept of derived object comes from base ClearCase, in which it is quite essential. UCM doesn't nearly accord it as much of importance.

It is obviously generalizable from this context.

A full derived object is produced by clearmake or clearaudit as a view private object with a config record, the result of a build audition.

Derived objects may be promoted to the shared status, either explicitly or implicitly by winkin. They remain however site local i.e. are not as such replicated by MultiSite. One may however check them in i.e. make versioned derived objects out of them, which has various consequences, and introduces various tradeoffs.

Config records may be used to apply labels, in a way which soon competes with UCM.

-- MarcGirod - 27 Feb 2005