Author Topic: Highlight differences between two different diagram version  (Read 2632 times)

jack89

  • EA User
  • **
  • Posts: 49
  • Karma: +0/-1
    • View Profile
Highlight differences between two different diagram version
« on: November 06, 2020, 03:08:48 am »
Hi all,

I'm writing this topic because I want to ask your advice about an EA capability.
First of all I'm going to explain my model with an example.

I have modeled a control system that is suitable for the application "A".
Now I have to model the same control system for another application called "B".

Since the requirements of application "A" are different from requirements related to the application "B", some parts of my already developed control system for "A" will change a little bit.

So my question is: I was thinking to develop the same control system for "B" inside the project related to "A" maybe highlighting differences between the parts of the control system for "A" vs. "B".
Is there any efficient method in EA that enable me to reach this goal? For example the EA project is called "Control System" and inside it i have two behavioral packages, one for the application "A" and one for "B". How can I highlight differences between behavior A & B?
which are the best practices in this case?

Thank you!

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Highlight differences between two different diagram version
« Reply #1 on: November 06, 2020, 06:59:11 pm »
Hello Jack,


This is an area where EA does not excel. There is no way to compare two diagrams in a project.

Using baselines you can compare the current version of a diagram to an earlier version, but the earlier version only exists in the baseline. In other words, you can't use baselines for development branches because only the current version exists in the model. This is only viable if you never need to work with, or see, the "A" version once you've started working on the "B" version.

The only way to achieve any kind of branching functionality is to work in multiple projects using baselines and reusable assets. It's a lot of work and you have to do almost all of it manually. It's probably not worth the effort compared to foregoing the comparison functionality and working in a single project.

HTH,


/Uffe
My theories are always correct, just apply them to the right reality.