Norman Dannhoff

[Norman Dannhoff]

Ok, we are currently using 3.3.15. Maybe we need to upgrade. I’ll try to install a test version and keep you posted.

One more thing (maybe I was not clear in the above): I get the hyperlinks in both versions. However, in the noWork version, they point into nirvana. In the Work version, the actually point to the correct requirement.

many thanks,
Norman

[Norman Dannhoff]

Hmm, I think the difference is:
1) I create the requirements
2) Link the requirements to a feature (via trace links, but that probably doesn’t really matter)
3) Link the requirements to a Use Case (via realization link)

From the EA project you may see, that the project contains 2 top level views (Business Analysis and Functional Design). The requirements are placed in the Business Analysis view, the rest goes into the Functional Design.
I trigger the document generation on the Functional Design view (meaning the requirement elements are not part of the package/view). I therefore use the feature element and report the requirements via the “Related Elements” function of EADocX. And here is also the difference between my two solution: Depending on the EADocX profile of the Requirement (table or inline), my hyperlinking works or does not work.

I do also report the requirements via the use cases, and here I actually use the hyperlinking to the requirements (related to the feature).

… complicate to explain, hope I was better this time …

Many thanks for your efforts,
Norman

[Norman Dannhoff]

next try … I renamed the file extension from eap to txt.

[Norman Dannhoff]

Ops, seems like I forgot to attach the example EA project.

[Norman Dannhoff]

Attached find an example. Using the EADocX template ProblemExampleWorks which renders Requirement elements inline, my hyperlinking works fine. However, I want the requirements to show up in a table, so in example ProblemExampleNoWorks. This template renders requirements into table format. Unfortunately my hyperlinking does not work anymore.

It seems like hyperlinking only works, when I specify a heading for a single source element. However, in table representation, thi does not seem to be possible.

Hope, this helps understanding my problem.

Many thanks,
Norman

[Norman Dannhoff]

Many thanks for the fast reply!

Well, to me the hyperlink is the hard part 🙂 It seems like EADocX resolves hyperlinks via bookmarks on document heading formatting.

Within the document, my requirements are rendered into a table (that is, how I defined the profile for my requirement stereotype). When I now generate the document, I see my referenced requirements at the use case documentation … but not as hyperlink (event though, this is the selected format).

I then changed the profile of the requirement and print them as Inline Text with a defined header. Now it works! The references at the use case are hyperlinked.

But I want the requirements to be in a table (since this looks a lot more tidy and saves space).

Any idea?

(I am now using 3.3.15.1. I found an old document which I generated with 3.3.something … and there it worked?! Within that document I have valid hyperlinks from the Use Case to the requirements which are rendered into a table)

Thanks for listening,
Norman

[Author]

Posts