I have the following question , I am writing  a use cases document were each use case consists of the following sections (pre-condition, detailed description, alternative flow, exception flow , post-condition)

I need to write use case/s for the approval process, where in my system a request will be send to the manager to either approve or reject a registration request , so  I wrote the one use case were in the detailed description section I wrote the flow for approving the registration request and in the exception section I wrote the reject the registration request and in the alternative flow I wrote approving the registration request through the email,, so is this right or I should have wrote two use cases one for approving the request and another use case for rejecting the use case.

thanks

John:

You want to know how you should partition (i.e., divide up) your system.   Only data flow diagrams actually guide you through a proper partitioning.   Lack of partitioning guidance is a  big hole in the UML (which includes Use Cases).

Tony

John-123,

Use cases need actors. I like to write the usecases from the actors perspective. Doing your requirement requires at least two actors (requestor, manager) each with a "goal" (seek registration and approve registration). Now Browncraig suggests that a process diagram (activity or BPMN diagram) with swimlanes could assists to give the reader (developer, manager) a context. Why? Because usecases are disjoint; and unless they are linked by some context (activity diagrams etc), they are hard to follow. I'd do a context and write two use cases.

warm regards,

K