Scenarios or use cases, level of detail

[Markus Skergeth]

Hi!

The "Your Notification Preferences" page differs from role to role.
Should we therefore model it as individual use cases or is it one use
case with different scenarios? And if it's one use case, should we point
out the differences in the brief description?

Another thing we were wondering is if "View Application" is a good use
case or if we should break it down into "View Summary", "View Contact", ...

Thank you for your answers!
Markus

[Pourya Shaker]

Hi Markus,

Post by Markus Skergeth
The "Your Notification Preferences" page differs from role to role.
Should we therefore model it as individual use cases or is it one use
case with different scenarios? And if it's one use case, should we point
out the differences in the brief description?

I would go with making the distinction in the use-case description (the
brief description in the up-coming deliverable, and in the fully-dressed
description in the later deliverable)

Post by Markus Skergeth
Another thing we were wondering is if "View Application" is a good use
case or if we should break it down into "View Summary", "View Contact", ...

The decision of whether to break down a use-case into lower-level
use-cases can be made on the basis of the complexity of the higher-level
use case (is the higher-level use-case description long, complex, or
hard to understand?). Also, consider whether the lower-level use-cases
can be re-used. Either way, the fact that the information pertaining to
an application is made of the several parts (e.g., summary and contacts)
should appear somewhere: either as separate use-cases or in the
description of the higher-level use-case.