Book a Demo

Author Topic: Feature versus Requirement in generated RTF doc?  (Read 5384 times)

kents

  • EA Novice
  • *
  • Posts: 16
  • Karma: +1/-0
    • View Profile
Feature versus Requirement in generated RTF doc?
« on: March 04, 2013, 09:45:55 pm »
Hi,

I am using EA for requirements management, and have created a model containing Feature elements and Requirement elements (from EA's built-in Requirements toolbox. When I generate an RTF report for this model, there is nothing in the document to indicate which elements are Features and which are Requirements. How can I get the report to distinguish between them? Something like prefixing each Feature with the text 'Feature' and prefixing each Requirement with 'Requirement' would do.

By the way, I know that in diagrams, Features have a blue bar at the left hand side of the rectangle, whereas Requirements have a brown bar. But I am not including the diagrams in my RTF report, because I just want the names and notes text of the Features and Requirements, and some of their attributes.

Thanks in advance for any help you can provide.

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: Feature versus Requirement in generated RTF do
« Reply #1 on: March 05, 2013, 02:58:56 am »
You could use the Alias or the Elementname for it.

Predefine the aliases or elementname with the prefix you want to use.

The Definition can be done in "Settings->Auto names and Counters"


Since Enterprise Architecdt version 10 you can also RE-Generate ethe Counters to existing packages with "Rightclick to the package and select "Apply auto names and counters""

Regards

Stefan
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

kents

  • EA Novice
  • *
  • Posts: 16
  • Karma: +1/-0
    • View Profile
Re: Feature versus Requirement in generated RTF do
« Reply #2 on: March 05, 2013, 03:02:20 am »
Yes, I could do that. But EA clearly already knows which is a Feature and which is a Requirement, so it seems wrong to have to put in that information again.

Thanks for your response anyway.

Stefan Bolleininger

  • EA User
  • **
  • Posts: 308
  • Karma: +0/-0
    • View Profile
Re: Feature versus Requirement in generated RTF do
« Reply #3 on: March 05, 2013, 03:06:40 am »
Than you may use Element.Type within your Reports.
Enterprise Architect in "safetycritical development" like medical device industry. My free Add-in at my Website

kents

  • EA Novice
  • *
  • Posts: 16
  • Karma: +1/-0
    • View Profile
Re: Feature versus Requirement in generated RTF do
« Reply #4 on: March 05, 2013, 03:18:28 am »
Yes, that does what I want.

Thank you.