Table conditional formatting from 2nd stereotype

[Mark Elson]

Hi,
I have a table of requirements. Some of those requirements have a second stereotype called SafetyRelated. I would like to be able to highlight those SafetyRelated requirements without necessarily having the Stereotype as a column in the table. Is there any way to do that?
Thanks,
Mark

[eadocX Support]

I think you can get the StereotypesEX attribute from eaDocX: have you tried to create conditional formatting on that?
Personally, I’m not a fan of multiple-stereotypes. Seems like but a short step away from multiple inheritance, and that’s the top of a steep, slippery slope down to deep badness…..

[Mark Elson]

I’ll give StereotypesEX a go. I guess the more unusual aspect of what I was asking was to format one attribute (the Requirement alias) that is a column in a table based on the state of another (stereotype): as Excel can do.
What I can do is just have the extra column with StereoTypesEx, call it “Safety Critical?” and conditional format it as Y if StereoTypesEx contains “Safety Critical” and N otherwise. Thank you for the help.
(BTW, I don’t see a problem with MI if parent classes are orthogonal concepts and you avoid a common ancestor – but that’s a whole other discussion …).

[eadocX Support]

I was once fortunate enough to be the ‘bag carrier’ for Tom Love, inventor of Objective C. He did a pitch on “the 7 deadly sins of OO”. One of them was Multiple Inheritance. His suggestion was that, if you want to know why it’s a bad idea, just spend a while debugging some code which uses MI.

[David Rains]

Might consider using a tag value to represent a type of a stereotyped requirement (think taxonomy and metadata vs. a stereotype?) my two pence worth… 🙂

[eadocX Support]

Would you are to elaborate? (aka “I’m not sure I understand….:-) “)

[Author]

Posts