Book a Demo
« previous next »
Pages: [1]

Author Topic: Requirements Traceability  (Read 2882 times)

ngong

  • EA User
  • **
  • Posts: 275
  • Karma: +2/-2
    • View Profile
Requirements Traceability
« on: June 20, 2011, 10:40:14 pm »
 I have got two models behaving different and I like to know why:

 It is about Reruirements, Use-Cases, and Components.

 In a diagram I have connected a Use-Case to some Requirements using a Realization association. In another diagram I connected a Component with a Use-Case also using a Realization association.

 In one model I can find the Requirements in the Tagged Values properties of the component, what is a needed service to me. It tells me, that the component is affected by this requirements.

 I did the same in another model but it does not have that trick. Could you think of, what could be different that hinders this Traceability service?

 Kind Regards

 Rolf

p.s. I am using EA 8.0.864
« Last Edit: June 20, 2011, 10:45:55 pm by ngong »
Logged
Rolf

Dave_Bullet

  • EA User
  • **
  • Posts: 295
  • Karma: +0/-0
    • View Profile
Re: Requirements Traceability
« Reply #1 on: June 24, 2011, 01:43:15 pm »
Strict UML syntax turned on?  Not sure if this is at the tool (EA) level or per repository?
Logged
"I know I'm close to a good design, but it's like the balloon animals, squeeze in one spot and the problem moves down the line"

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Requirements Traceability
« Reply #2 on: June 24, 2011, 05:45:48 pm »
Probably an MDG setup issue when tagged values behave different.

q.
Logged
Pages: [1]
« previous next »