Extending element description

[J. Linden]

Hello everybody,

I would like to extend a use case with additional information, such as

• Use case objective: ...
• Possible difficulties: ...
• Relevant patents: ...
• ...

Finally, this information should be included into an automatically generated RTF report in form of a table.

Using tagged values seems not a suitable solution, since no list or other formatting can be used.

I could imagine that one possibility could be adding attributes to the use case. However, I am not sure if this is the right approach to add such additional information towards the automatically generated RTF documents. Is there a need to define sterotypes for this?

Any tips and tricks welcome!

[Geert Bellekens]

J.

We had the same issue here, and we choose to add some sort of xml like structure into our notes.
So the notes for a usecase could be

<Definition>The definition goes here</Definition>
<Description> this is the description content </Description>

Then we built an add-in to easily edit the contents of those different tags.
I guess you could follow that approach, but I'll take a lot of custom development before it is really usable.
Other then that, the only advice I could give you is to use tagged values.

Geert

[J. Linden]

Hello Geert,

Thank you very much for your reply! I will have a look at your proposed solution.
However, I cannot really believe, that there is no easier way. I thought defining custom 'tagged values' as a kind of templates for an element, which are editable as rtf rather than plain text are quite common in use case modelling.

Best regards
Jens