Messages

1

Uml Process / Re: When to nest requirements vs when to aggregate

« on: August 11, 2009, 12:38:24 pm »

I agree Fred. This does seem inconsistent and the ability to specify a default relationship / pick at relationship creation would seem to be useful.

2

Uml Process / Re: When to nest requirements vs when to aggregate

« on: July 24, 2009, 12:56:32 pm »

Thanks for the feedback. Specifically I am trying to determine the best way to document business requirements such as "minimise the time to identify errors in historical FooBaa data" along with the implied technical requirements for the system that will realise the requirement and the user interactions with the system.

My current thinking is that...

The aggregated technical requirements for the above include a wizard that reviews the imported data and employs a heuristic learning algorithm. So the technical requirements specify the capabilities of the system.

The use cases then define how the user interacts with the wizard and algorithm. So they specify the requirements fo the interfaces and state machine.

Does that seem correct from a UML documentation perspective?

3

Uml Process / Re: When to nest requirements vs when to aggregate

« on: July 23, 2009, 04:09:08 pm »

Thanks Paolo, you've confirmed my suspicion that this isn't black and white and your approach seems logical. In practice, is there any risk to mandating aggregation only?

4

Uml Process / When to nest requirements vs when to aggregate

« on: July 23, 2009, 01:30:55 pm »

Are there rules/guidelines on when to nest requirements (creating an owned by relationship) versus when to create an aggregation relationship?