Although we will seperate these into smaller related packages soon...I wanted to see if we could colour code the links so e.g. Associations were Blue, Trace were Red etc to be able to see at a glance what type of relationship they were.
I wanted to apply this across the Prioject as Standard
Does that make sense? 
Guy
Hi Guy,
Well, it does and it doesn't.
Telling an association apart from a trace is already simple -- associations are solid lines, and traces are dashed. Realization, another common relationship in requirement models, is also dashed but has a triangular arrow head instead of the open, plain V shape of trace and (directed) association.
So if that's all you're after, the colour won't add any information. Fundamentally, colour is not an information carrier in UML. The entire standard works in monochrome.
That said, there's nothing keeping you from adding colour to denote certain things in your own models. What triggered this response is really the last thing you said, about wanting to apply this colour-coding as a standard.
If you want that, you probably want any new or changed connectors to display the right colour automatically. The way to do that in EA is to create a UML profile where you define your own stereotypes for your connectors. In those stereotypes you specify the appearance of the connector, including its colour, by writing a shape script. You may also wish to create your own custom diagram type (with related toolbox pages) to facilitate creating these new connectors.
If you write an in-EA script, you have to run it manually every time you change something. For anything but a trivial model, this is unmanageable. Going the stereotype-and-shape-script route means EA runs the shape script for you whenever necessary (every refresh of the diagram).
Put another way, creating a profile is the proper UML way of doing it. If you want to create UML models, rather than draw pictures, that's the way to go.
Cheers,
/Uffe
