Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Use cases document
Previous Previous
 
Next Next
New Post 10/5/2009 2:57 PM
User is offline john123
4 posts
No Ranking


Use cases document 

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

 
New Post 10/5/2009 9:46 PM
User is offline Adrian M.
755 posts
3rd Level Poster




Re: Use cases document 

From your description, it sounds like one use case is the way to go since the registration process/activity is one process with multiple outcomes.

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 10/6/2009 7:57 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Use cases document 

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

 
New Post 10/7/2009 4:45 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: Use cases document 

John

One use case is the right way to go here, however, is a use cas sufficient or even the best way to go?  Would it be nicely augmented with a little swim lane diagram?  Would a context diagram show the flow better?

Who is your audience? Developers? A system designer?  What do they say works best for them?

I recently saw a similar case where the two outcomes of pass or fail were described as two separate reqirements statements.  It doesn't make sense, not becasue it's one scenario with two outcomes, but because when it's implemented it will be one developer piece of work. 

 
New Post 10/17/2009 1:13 AM
User is offline KJ
243 posts
6th Level Poster


Re: Use cases document 

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

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

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC