How to filter requirements in RTF generation?

[manfredw]

Hello folks,

I'm generating a doc that should list all use cases in a package.
For each use case I'd like to list the requirements that are connected to it.
So far no problem.

UC1
- REQ001 some technical requirement
- REQ002 some functional requirement
UC2
- REQ003 some functional requirement
- REQ004 some technical requirement

But I'd like to filter some of the requirements.
Let's say I just want the functional requirements to be listed, how can I do that?

UC1
- REQ002 some functional requirement
UC2
- REQ003 some functional requirement

I tried a lot of approaches, template fragments, Element Filters etc. but to no avail  

Any help is much appreciated!

thanks in advance,

regards
Manfred

[marcel_str]

Thing I would think of is the one you already seem to have tried: Element filters in your RTF template.
Could you explain why that didn't work? Could it be you missed out something during the configuration of the filter?!

[manfredw]

Hi Marcel,

I'm trying the following:


element>
  {Element.Name}{Element.Notes} these are the use cases
  connector>
    target>
      element>
         {Element.Name}{Element.Notes}    I want this line only for functional requirements
      <element
    <target
  <connector
<element

here 2 of the filters I have tried:
 - RequirementType    EqualsTo     Functional
 - StereoType           NotEquals    <<Technical>>

The filter seems to be only applied to the outer 'element' scope but not to the connectors elements.

cheers
Manfred

[marcel_str]

Ah, I see.

I think you're correct in this. If you add an element filter to only show some type of requirement, your use cases are also filtered out when using these filters.

I also don't know a way how to do this. Though, I would use the 'external requirement' section for this. That way you don't need filters to exclude dependencies to non-requirement elements:

element>
 {Element.Name}{Element.Notes}
 external requirement>
        {Element.Name}{Element.Notes}
 <external requirement
<element

Sorry I can't help you out, hope you find your solution.
Marcel.

[Ian Mitchell]

Have you looked at eaDocX as an alternative way of creating reports? It doesn't use the same Filtering approach as RTF, but might be able to deliver what you need. Worth a look. Just Google it.

[manfredw]

Hello Marcel,
Thanks anyways for your implication!

Hello Ian,

I had a glimpse at it, eaDocX seems not bad indeed, but I'll have problems to convince my boss to buy it just for that purpose.
Another problem is that we already have a lot of doc generation set up and we cannot afford to rewrite end reconfigure all that.

Isn't there a native way to do that? To me it seems to be a basic need, so I hope Sparx has some tricks in their bag to achieve it, come on...

cheers
Manfred

[Graham_Moir]

Rather than running the generation over a set of packages, would a search work better ?   You could retrieve the population of elements you're interested in and then run the rtf generation over that?

[manfredw]

Hi Graham,

Thank you for your input!

We have a setup with master document and model documents that refer to the packages to be documented. Each model document has its own rtf template. I'm not sure how to include a search in that case?

Could you please give me some advice?

thanks in advance,

cheers
Manfred

[Konrad Wieland]

Since EA v10 document template fragments can be used in combination with e.g. custom SQL queries. With these queries you can easily filter the elements.

Here is video showing the new capabilities:
http://www.youtube.com/watch?v=FdZQ2m-tjIQ&list=UU1IbtSvXDURkqZQf_EpyvgQ&index=1

Cheers
Konrad

[manfredw]

Hello Konrad,

Thank you very much for your input and the link!
I'm using EA now for several years, but I was not aware that Sparx has added this possibility

That opens a whole lot of new options!  

cheers und servus
Manfred