Version of the model

[[email protected]]

Hello all,
we managed db model in EA with our supplier. The supplier deliver us an application which use this DB in standard versions scheme (X.Y.Z - major.minor.build). Due to track changes in DB we want to keep version of application in EA model of the database. What is the best practices to do it? Is there some recommendation to keep "release notes of DB" in EA model?
Thank a lot
MiSu

[PeterHeintz]

I am not sure if I understand you right.
One way you could manage that, is creating a component representing your supplier delivered application having an attribute representing the version of the application.
Either you regard this component as an abstract component and you derive your concrete application version/Components by setting the version attribute of the derived component or you create instances of your application component.

[qwerty]

I also don't understand the question. What is the DB you mention? The repository itself or a DB you manage in a repository?

q.

[[email protected]]

Hello,
sorry that the description wasn't very precise - I try to give more detail:

• we have 3-tier architecture of application
• the database tier (DB) is designed in EA model
• when supplier deliver new version of application - they deliver us new version of EA model as well
• we want to keep changes of database structure only in EA model
• so if we upgrade application from version 2.0 to version 2.1 we need identified in model of database structure which element was changed.
• it is possible to have information on each object about its version - but we need to know some "global" information about the version of whole model (eg. maximum of element versions)
• the best solution for us is to create report of changes in each version

now i'm not sure that it is clearer :-)

[qwerty]

I think it's clearer now. However, there's no simple answer. You can use the version property per element, but that's not practical in use. What I would do is using a shadow branch in the repository for the external delivery. You could freeze them with individual version numbers in the import name (strip GUIDs) and engineer the deltas manually in the production branch. Alternatively you could keep the external branch floating with imports not using strip GUIDs and make baselines you number accordingly. Using VC can also be a good idea. So you can use the XMI from the VC to communicate with your external supplier.

In short: to find a good solution you have to sit down with your config manager and the external supplier and try a couple of scenarios. It's a good idea to hire a consultant who had done that before.

q.

[Uffe]

I agree, there's no simple answer. EA is not able to keep two versions of the same thing in a model at the same time. Baselines allow you to see changes between versions, but you can't retrieve any information on those changes, you can only see them visually.

I know that LieberLieber GmbH, a third-party add-on supplier (with which I am not affiliated), has done some work in this area so they might be the right people to call.

Or me. Call me!

/Uffe

[qwerty]

You just want some Czech beer, right?

q.

[Uffe]

Damn - rumbled.