Book a Demo

Author Topic: Report requirements  (Read 4872 times)

cfoe

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Report requirements
« on: November 08, 2016, 10:03:45 pm »
Hello,

I would like to extract only requirement elements and the note linked to the requirement.
It could be displayed in the diagram but is not shown as an element in the treeview.

How can i extract the data to include it in the report ?

Best Regards,
CFOE

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Report requirements
« Reply #1 on: November 08, 2016, 10:55:28 pm »
What have you tried so far?
I think you can report on notes just like any other type of element.

Geert

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Report requirements
« Reply #2 on: November 08, 2016, 10:57:11 pm »
From the document generation perspective, notes and other so-called "diagram objects" are actually elements the same as any other, even though they're not shown in the project browser.

So assuming your note links run from the note to the requirement, simply tick Element -> Connector -> Source -> Element in the template designer and insert the Notes field.

HTH,


/Uffe
My theories are always correct, just apply them to the right reality.

cfoe

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Report requirements
« Reply #3 on: November 09, 2016, 03:19:35 am »
I tryed selecting elements from the Diagram and I can have the Note.

Below the code:

package >
{Pkg.Name}

diagram >
{Diagram.DiagramImg}
element >

Name: {Element.FullName}
Notes: {Element.Notes}
{Element.ParentPackage}
{Element.Type}
< element
< diagram
< package


The issue is that i don't know the way to get the link between the note and the requirements and display it in the report.

Best Regards

CFOE

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
Re: Report requirements
« Reply #4 on: November 10, 2016, 08:46:38 pm »
In general, it's a bad idea to generate documentation based on diagram content.

This is a case in point: in a diagram-based template, you can report on the elements displayed and the connectors displayed, but you can't get connectors by element.

/Uffe
My theories are always correct, just apply them to the right reality.

cfoe

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Report requirements
« Reply #5 on: November 10, 2016, 09:12:21 pm »
Of course Uffe !

It's a bad idea to generate documentation based on diagram content.
So we changed the way to do this. We changed the notes to set it as risks although it's not a risk.
Using the different templates and customizing it, we can now extract the risks.

It's not so easy to customize the report.

For now I would like to know how to only display the packages that contain risks in order to avoid too many pages in the Word document.

Thanks for your information.

CFOE