Documenting relationships

[Gusztav Janvari]

Hello again,

I’m trying to develop a class profile which would, apart from other things, document the associations the class contributes to. I’m however stucked with a horizontal table in which is way too narrow even for the most imporant relationship information (say: name, description, role, contributing item name and path).

I hoped to see a profile for relationships, but I could not find any. Is this a real limitation that relationship info can only be printed in horizontal tables?

Thanks for your efforts.
eM

[eadocX Support]

Try documenting the Class as Inline, then you can have sub-tables for the associated classes, or hyperlinks to them, or inline tables. Try inporting the ‘Class, Dat and State’ build-in profile: that’s a good start.

[Gusztav Janvari]

Hi again,

I have attached a screenshot of my class defition, which is inline. You can see some Relationships items on the lower pane.

I expected the Inline table checkbox to be available for the Relationships items, but it is not the case. Did you think of this solution, or some other?

(What I have also tried is to add a RelationshipItems item, but it only listed the class names, and I had no option to add information to render.)

eM

[Gusztav Janvari]

Hi, any update on this?

[eadocX Support]

Sorry I missed your last update.
I’m still not clear what you want your document to look like.
Can you say (1) what is the structure of this part of your model and (2) what do you want your document to look like.
Thanks

[Gusztav Janvari]

Hi,

It seems it has been quite a long since the issue arised and now I can’t remember all the details (and I would need to buy eaDocX, since trial has expired, but it would great to know first if I can do what I want with it), but most likely I wanted to see a structure similar to that in the attached document (generated content in [] placeholders). What to focus on is that relationships use inline tables: the longer contents like relationship notes are formatted as paragraphs, but a list of attributes like multiplicity render as tables to save space and improve look. I think this is close to what I originally wanted.

Does it help finding out what the exact question is? 🙂

eM

[Author]

Posts