Compare BPMNs, compare Requirements

[NicoP]

Hi

I have a need to compare two sets of busines processes and requirements for the same activities. the two sets of documentation have been produced with a couple of years difference and I must document gaps and changes, missing and undocumented features.

Currently both sets are available under different packages (BPMN and Requirements 'as was' and 'as is').

What would be the best approach to

• map matches?
• highlight gaps?

Many thanks
Nico

[Geert Bellekens]

I've had a similar task just a few weeks ago.
From what you describe there is already a major drawback:
since you say that both packages are in the same model this must mean that they have a different GUID.
Unfortunately the build-in Compare utitility will only compare those elements that have the same id.

I solved this by writing a little add-on program to give each element the correct id again.
Then I was able to compare the two version using the build-in utitility.

The steps you would have to take:

• take a copy of your model and work on that
• export the 'as was' package to xmi
• run your little tool on the 'as is' package, looping each element, finding its counterpart in the 'as was', copy the guid of the as was element to the as is element and delete the as was element.
• delete the rest of the as was package
• compare the as is package to the xmi file of the as was package

Geert

[NicoP]

Hi Geert

Thanks so much for your explanation. In some ways, it makes sense if the As Is was an evolution of the As Was, but in my case it is not.

The As Was was documented as a msWord document whilst the As Is is documented in EA and is considered by the customer as a new project. i need to map them both as there are some commercials that need resolving.

So I documented the As Was in EA in the hope there would be a way to relate elements together using EA interface features rather than the compare utility.

I will look at the feasibility of your method nevertheless.

Thanks
Nico