Which eaDocX Version are you using?
What you are doing is correct. There are two ways to print the Internal Requirements of a Use Case:
1 – Add a sub-element called ‘Element Requirements’. If you have not already defined some a Profile for Element Requirements, then eaDocX will privide some initial defaults (a table with the name & description)
2 – Add an attribute of ‘Element Requirements Summary’, and this will print a single comma-delimited list of the Internal requirements.
I’ve just re-run the test cases for this using eaDocX 3.0.5, and it looks OK.
Are these Internal Requirements, or requirements whih are connected to the Use Case via relationships? If the latter, then I suggest you create a ‘Quick Document’ using the package which contains the Use Cases, and Quick Document will find all the relationship types which exist in your model, and print hyperlinks to them.
