How to version model objects

[J Mussi]

I'm currently working on a project where we will be modelling current and future state "generations" for application and information architecture. What is the best way to manage the creation of these models and their respective objects (e.g. components) from one "generation" to another.

For example, how can I show that the component "C1" that exists in the current state will exist with changes in G1 and G2. Ideally I would like to see a version trace that would show each object linked together.

Do I have to create these relationships for every object or is there a way to have automatic inheritance of the objects. I only know how this would work with classes, but not with other UML objects.

thanks

[Matt Thomas]

There are baselines, and their's version control, both of which work well and allow use of the compare facility.
I'm curious about the term "state generations" that you use. Is there something particular about this that introduces additional challenges that baselines and version control don't help with?

[OpenIT Solutions]

As well as baselines and version control you may also want to look at "diagram filters". You could then add the G1, G2 to the phase attribute for elements that apply to both releases and G1 to first and G2 for just the second. You can then create filters that hide appropriate elements on your diagrams - this is useful when you want to show whats happening overtime in your model.

Regards,

Jon.