Book a Demo

Author Topic: External Requirements with RTF-generator  (Read 2957 times)

h.neumann

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
External Requirements with RTF-generator
« on: June 08, 2005, 12:54:43 am »
We upgraded our Enterprise Architect software to release 5.0 a fortnight ago.
However, I have difficulty in generating a print of the Use Cases External Requirements using the RTF generator since the upgrade.  
Is it at all possible in the new release?  
Please advise.

Hessel Neumann
[email protected]  ???
« Last Edit: June 08, 2005, 12:55:09 am by h.neumann »

thomaskilian

  • Guest
Re: External Requirements with RTF-generator
« Reply #1 on: June 08, 2005, 04:23:33 am »
What is the exact problem? I could create a Requirements report without problems.

h.neumann

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: External Requirements with RTF-generator
« Reply #2 on: June 08, 2005, 06:59:42 am »
Quote
What is the exact problem? I could create a Requirements report without problems.

It is possible to link requirements to a use case. External requirements.
If i create a use case report, then i wil also printing the linked requirements with the use cases.
Is this possible in the new RTF-generator.

thomaskilian

  • Guest
Re: External Requirements with RTF-generator
« Reply #3 on: June 09, 2005, 09:34:06 am »
You could place the external requirements in either the same package as the use cases or one "nearby" so it is included with the RTF report. I haven't played much with the new RTF yet, but it has a Child Element section. The easiest was: give it a try (one use case, one requirement, basic template) and see what happens...

mjtapp

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Re: External Requirements with RTF-generator
« Reply #4 on: June 09, 2005, 04:49:35 pm »
I posted the same question previously but at that time no one replied :'(. However it seemed fairly clear to me that this was a bug and I raised a bug request for Sparx.

They have since come back to me and said that this is a problem and is going to be fixed in a future release. It is unfortunate because if you use this feature of EA, not being able to generate this documentation is a pain (to say the least).

One work around that I have found is to use the 'Connector' and 'Target Element', the main problem with this is that any other connections apart from realisations also get picked up, but I guess it is better than nothing...