Book a Demo

Author Topic: traceability from requirement to attribute  (Read 3525 times)

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
traceability from requirement to attribute
« on: June 26, 2003, 08:09:25 am »
G'day folks,

How do you go about setting up, either directly or indirectly, a realization between a table attribute and a requirement object?

I've tried linking a note to a table, then linking that note to an "element feature" (a new column attribute), then linking that note to a requirement with a realization link.  The only problem is notes don't show up in the relationship matrix.

Any other ideas?  (I'm using EAv3.51 build 612.)

Thanks in advance.
Cheers and best regards.

DMT

  • EA User
  • **
  • Posts: 93
  • Karma: +0/-0
    • View Profile
Re: traceability from requirement to attribute
« Reply #1 on: June 27, 2003, 01:59:22 pm »
Out of curiosity, why not link the requirement to the table, then add notes to the realization link describing the attribute on the table that actually realizes the requirement?

I know I'm not answering your question directly, but this seems like it may be a solution that's not "perfect," but one that may allow you to move forward with your design without getting hung up.

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: traceability from requirement to attribute
« Reply #2 on: June 30, 2003, 05:13:24 am »
Thanks DMT,

Yup, that's what I've been doing since my original post.

To avoid typing, I've also created a link from the note back to the table, linking that note to an element feature (the attribute).
Cheers and best regards.