Book a Demo

Author Topic: RequirementID in UseCase title?  (Read 4234 times)

jberntx

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
RequirementID in UseCase title?
« on: October 07, 2015, 12:58:19 am »
Hi All

Is it possible to automatically add properties to the title of an element? In example, we would like to append the requirementID to the general headline for a UseCase when shown in a diagram.

Thanks for any help, JB

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: RequirementID in UseCase title?
« Reply #1 on: October 07, 2015, 01:23:52 am »
Can you please elaborate on this. Do you have only a single requirement per use case?? How are use case and req. related?

q.

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 591
  • Karma: +7/-0
    • View Profile
Re: RequirementID in UseCase title?
« Reply #2 on: October 07, 2015, 10:24:08 am »

jberntx

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: RequirementID in UseCase title?
« Reply #3 on: October 07, 2015, 06:37:17 pm »
Hi

I will try to explain this a bit further. We use RaQuest to generate unique IDs for both requirements, test cases etc.

I would like this ID to be displayed as part of the text for each element in a diagram.

Thus in the example below:
https://dl.dropboxusercontent.com/u/10489827/UseCase.PNG

I would like the text on the TestCase to state "Load door - 3315". So the "Load door" comes from the General properties while the 3315 is the RequirementID.

Thanks for helping, JB

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: RequirementID in UseCase title?
« Reply #4 on: October 07, 2015, 08:02:58 pm »
The only way to do that is to write a MDG where you define your own use case. By assigning a stereotype to such a use case you can define a shape script. And this shape script can read and print tagged values like the one you like to show. It's a bit of work but in the end it pays off. See here for an intro.

q.