Legends, Colour and Requirements

[Guy Manning]

Hi
As a relative EA newbie, just received v12 and have lots of questions

FIRST:
If we use MoSCoW for our Requirement Priority and want each requirement to have a visible different colour to differentiate MUST from SHOULD etc,,,I have so far used the Requirement Element Status Field (and created the 4 MoSCoW values) which allows me to set 4 colours and to show these visibly in the Catalogue

a) Is this the best way of doing this and add colour?
b) I created a LEGEND to show the 4 colours against MoSCoW. Is there a way of this defined LEGEND becoming a part of EVERY Requirement Diagram (as a matter of course) or do I have to cut 'n paste it in from another diagram every time
c) I also created 2 Tagged Values of 1. MoSCow and 2. Req Owner for each requirement element. Is there a way of using the MoSCoW Tag to effect colour instead of the STATUS field?

SECOND:
Anyone used TFS and EA together and can give me some simple overview of how it all works?

Ta for any help
Guy

[qwerty]

You can create your own MDG. This way you can color requirements based on the status field via a shape script. This also allows for adding default tagged values (see here). To create a legend automatically you need to write an add-in. Else you can (IIRC) copy paste the legend from one diagram to another and it will be a single element (so if you change one it will change everywhere). Not sure about this since it's long ago I last used a legend (you might give it a try, though).

No idea about TFS but I guess it's not different to other version control systems. There's a good read from Sparx about using version control. (Well, I have my own thoughts about using VC and I recommend to think twice / have a good config manager.)

q.

[Guy Manning]

Thanks for the info

The MDG looks a bit complicated when I tried to read about it...may need a lot more exposure to the whole EA thing before trying that out

Cheers
 

[Geert Bellekens]

You might want to try the template package.
It is quite possible that if you put the legend on the diagram in the template package that it gets copied to new diagrams. (to be tested, I'm not sure)

As for TFS, I use TFS version control in EA.
You just basically follow the instructions in the help file to set it up, and off you go.
Works fairly well, but the whole version control in EA has its limits.

You must know that VC is done using XMI export of packages in your model. It's the xmi file that is stored in the VC system.

Geert

[Guy Manning]

Added the MoSCoW legend to the Templates package and now when  you select the Legend Common element it appears as this config.

with regard to TFS I just wanted to understand the actual Process needed to use it effectively i.e. ...Start in TFS and create X then go to the EA model and it shows Y etc...
How to map TFS Tasks/Stories, to EA Requirements etc

A dummies guide as to how they both work together I guess

[Geert Bellekens]

The help file actually contains most of what you need to know about setting up version control. Start here: Version Control

Geert

[Guy Manning]

Hi Geert

Thanks for that but I need to know less about putting Version Control in place around models etc (i.e,. Model Check in/Out) and understand more about how we will use TFS here for organising work

We currently use TFS here to organise Projects and Tasks..so when a new Business idea comes through which we plan to develop in IT, we create a Project and associated Stories to support that in TFS.
So to associate EA Requirements and Analysis with TFS how will it all work?
Not sure whether I am explaining myself adequately tbh!  

[Geert Bellekens]

Ha, now I understand.
I'm not quite sure in fact. I've never tried any of the TFS/Visual Studio integrations as we already have our own system in place to track the changes on elements using the TFS workitem number.


Geert