Originally posted by Tomi Tuomainen:
The pricing model may be very simple at the moment, but the analyst may have thought that this is very important part of the system that could be very complicated in the future: so pricing should be separated as it's own use case.
This way the other use cases can include the pricing use case, so there's no need to duplicate the logic in use case stories. And perhaps it also makes use case diagram clearer.
Even if there wouldn't be any user interaction in the use case story (read and believe it :roll: ) this may change if more complicated pricing model will take place.
Tomi
[ August 02, 2004: Message edited by: Tomi Tuomainen ]
Originally posted by Ian Roberts:
I'm not sure what the issue is here because (to me) the business analyst was simply identifying a common piece of functionality that is used by two use cases. The Price Itinerary use case has an includes stereotype that concludes that it is a piece of functionality that has been identified as a potential reusable component and separated as such.
A use case is a kind of classifier representing a coherent unit of functionality provided by a system, a subsystem, or a class as manifested by sequences of messages exchanged among the system (subsystem, class) and one or more outside interactors (called actors) together with actions performed by the system (subsystem, class)."
The uses relationship occurs when you have common behavior that exists in multiple use cases that can be factored out into a separate use case (e.g., login use case). Note that actors have relationships to use cases that are being extended whereas there is often no actor associated with a common use case.
Originally posted by Frank Silbermann:
Perhaps, but he's mixing requirements with design.
On the one hand, it is relevant for him to point out that the business rules for initial pricing are the same as those for re-pricing, and it's not immediately clear to me where else he would record this.
On the other hand, I cannot recall ever seeing a use case realization that did not include a user!!! Has any of you seen one?