For tip 1 – there are 30 or so ‘big packages’ in the model, but each document is per each big package, so using this method I would need a different stereotype for each big package. Then for each analyst that is generating for their ‘big package’ they would need to re-configure the element report so that it picks up their packages not someone else’s. I would prefer not to go down this route.
Tip 2 – I don’t understand how a table of contents will help me create a table of names and notes.
Is there any reason why it won’t list child packages like this? It has no problem listing other child elements (use cases, objects, requirements) in exactly the same way (a simple table with the name and the description).
