Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Use cases document
Previous Previous
 
Next Next
New Post 1/16/2010 5:51 PM
User is offline Marc Thibault
7 posts
10th Level Poster


Re: Use cases document 

You have three use cases:

  1. Someone prepares a request. What the system does with it is a design, not requirement issue.
  2. The manager selects a pending request and either approves or rejects it. These are two natural flows; alternatives, not main and exception.
  3. The original someone checks their email to see whether the request has been approved or not.

It doesn't seem like it, but the last needs coding. Generating the email is a precondition, and without this use case, there's no need to generate the email.


 
New Post 1/21/2010 5:10 AM
User is offline Peter Herring
13 posts
10th Level Poster


Re: Use cases document 

 john123 wrote
 

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

 

 

Hi John,

Here's my suggestion.

Taking it back to basics you need to decide what the goal is of the actor in this situaiton. So,the manager is receiving registration requests and ultimately wants to approve them. So it seems to me your use case is clear;  he is managing registration requests.  You could call your use case "Manage registration requests." Now, your main flow covers the happy day scenario which is for approving those requests. I would cover rejecting in an alternative flow. It isn't really an exception, because an exception is unexpected behaviour, whereas rejecting a request is something that you would expect to do. Approving via email as an alternative flow seems fine, it depends on if the system behaviour is significantly different or it is optional. It may well be that you dont need an alternative flow for this.

I highly recommend two books on the subject of uses cases:

Use Case modelling - by kurt bittner and ian spence

Writing effective use cases - by Alistair Cockburn

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Use cases document

Community Blog - Latest Posts

In today's dynamic business environment, mastering effective business analysis techniques is crucial for organizations aiming to achieve sustainable growth and competitive advantage. Business analysis involves the systematic evaluation of business processes, requirements, and strategies to uncover insights that drive informed decision-making. T...
For many years now, a lot of people have found it difficult to identify the difference between Sankey diagrams and parallel sets. The two have made headlines, given that most people find it challenging to note what makes them different from each other. What remains to be undeniable is the fact that the Sankey diagram is among the top data visualiza...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Architecture and AI In our recent conversation with Joseph Edward, we explored the transformative power of business architecture (BA) and technology as tools for uplifting communities. Joseph, with his rich background spanning from education to IT leadership, shared...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC