I've googled & searched doco's forums etc. but can't find anything that helps me on this one... assuming I'm searching for the right stuff.
Basic scenario is we have a bunch of use cases & we're trying to generate a detailed use case spec via an RTF doc. All works like a charm; normal course, conditions etc. look beautiful; but we're having trouble including
just the actors.
We're trying to include the actors by finding elements
connected to our use case. Thus we're using the "Connector"->"Source"->"Element" sections (& target->element) to try to get a dump of all the actors that "Use" each use case. Which works... but we also get all other connected elements such as other use cases which invoke or are invoked, extend etc.
This is what we're getting:
| Use Case | UC001: Make Coffee |
| Preconditions | Victim is experiencing stage 2 caffeine withdrawals |
| Scenarios | 1. Victim desperately grabs coffee beans from cupboard
2. ... |
| Post conditions | Meltdown averted |
| Actors | Victim
UC002: Fervently Steam Milk
UC003: Add too much sugar
UC004: Attend Coffee Addicts Anonymous
|
What we're trying to get rid of are the
struck through items which we're retrieving using the aforementioned connectors approach. We want the
Actors section to only include the
Victim, not all connected elements.
Does anyone have any words of wisdom to impart?
I was hoping we could do something like:
a) Add filters to child elements / sections ... eg. add a filter on the "Connector" section so it only retrieves connectors that are of the "Uses" type, or where the source element type is an actor or something?
b) Nest a template?? eg. create a template which is designed only to handle connectors, so we can add appropriate filters in the document properties of that child template; then drop that template into the "Actors" portion of our parent template in between the "Connector" section tags??
Either method will open up a new world of power & flexibility...
Surely this has come up before? *Fingers crossed*
Cheers,
Bandit
