Enlighten us about Document artifacts

[marcelloh]

I can have a linked document on an Document Artifact.
That should give me a lot of possibilities.

But if I use this, there is no way how to get this into a document.

The manual should give me some info, I suppose.

[fwoolz]

Hi Marcelloh,

I'm not sure I understand what you're getting at. I just tried the following and it worked properly:
1. Add a plain "Artifact" to a diagram.
2. Create and then edit a linked document for that "Artifact".
3. Add a "Document Artifact" to a diagram.
4. Create and then edit a linked document for that "Document Artifact".
5. Generate RTF documentation for the package containing the diagram with "Linked Document" checked under "Element" in the RTF Template Editor.
6. View the generated document and verify that the contents of the linked documents are in fact in the generated document.

[marcelloh]

1. I added a Document Artifact to a package
2. moved it to the use case within that package
    just because I can't create it there in the first place
3. added a Linked Document to the Document Artifact
4. Typed "It would be fine if this shows"
5. saved the Linked Document
6. closed the Linked Document editor
7. checks if it really is there (by opening it again)
     it is there
8. Generate my report from the package
    just to see, that it isn't showing

At step 3, I added a linked document to a Document Artifact that has no notes, and one with notes.
In my report I only get the notes.

[skiwi]

In your document template did you select the appropriate "linked document" checkbox?

http://www.sparxsystems.com/uml_tool_guide/modeling_with_uml/linking_documentation.html

[marcelloh]

appropriate?

I suppose I did, because it shows me the notes of that document artifact.

I've read the info on the hyperlink, and I've done it like this.

The only thing is, I did't add it to a diagram.
(See my steps.)

[skiwi]

Including the notes from an entity is not the same as including the linked document. The linked documents box needs to be checked in the document template as well. (And note there are several places wherer you may need to tick this) - I'd add a picture, but the admins in their wisdom don't allow picture directly on this forum to make it more difficult for us to help each other. S

[marcelloh]

Gheghe, I found out that they where not published via
Embedded Elements, or via Lnked Documents at all....  

They where in my template via Child Elemtents.
And that has absolutely no way of reportinga Linked Document that is hidden inside (as far as I can see).

And I am talking about Document Artifacts that are childs of an Use Case.

My general rule is, if i can put stuff in, I want it in my report ;-)

[Dermot]

The Child Element section by default, if left clear of fields, will replicate the full Element section - which will include Element::Linked Documents if set on.  
So I suggest you set this section on but leave it unpopulated - see the standard (basic template).

[marcelloh]

So, If I do that, I get everything else in my "Child-documentation"?
But what if I don't want that?
Recursiveness is nice, if you want the same, and if the structure is the same. Perhaps I'm still unknown with how to write a perfect Use Case Template recursive, so there must be somebody else who done this?