Author Topic: Make reporting much more flexible  (Read 2949 times)

marcelloh

  • EA User
  • **
  • Posts: 192
  • Karma: +0/-0
    • View Profile
Make reporting much more flexible
« on: December 23, 2009, 08:22:59 pm »
I suggest to make the reporting part much more flexible.
if my template could do stuff like this like the XML below.

ExampleExample with infoOutput
<section what="A">
<section.attribute="B"/>
</section>
<section what="scenario">
<section.attribute="name"/>
</section>
MyNormalScenario
MyAlternateScenario1
MyAlternateScenario2

And then we could use this for every part of object that could be documented.

And there is more:
ExampleExample with infoOutput
<section what="A" type="C">
<section.attribute="B"/>
</section>
<section what="scenario" type="Basic Path">
<section.attribute="name"/>
</section>
MyNormalScenario

And then we could use this for every part of object that could be documented.

But there is still more, because we could actually do stuff like this:

ExampleExample with infoOutput
<section what="A" type="C">
<section.attribute="B"/>
</section>
<section what="D" type="F">
<section.attribute="E"/>
</section>
<section what="G" type="I">
<section.attribute="H"/>
</section>
<section what="scenario" type="Basic Path">
<section.attribute="name"/>
</section>
<section what="diagram">
<section.attribute="name"/>
</section>
<section what="scenario" type="Alternate">
<section.attribute="name"/>
</section>
MyNormalScenario
MyImageName
MyAlternateScenario1
MyAlternateScenario2

This sytem is far more flexible, and I think we can actually generate a lot more of the documents we need to have sometimes.

And there is more.... Think of nesting and stuf. We could so much more.