Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Use case description
Previous Previous
 
Next Next
New Post 4/22/2009 4:59 PM
User is offline Kimbo
454 posts
5th Level Poster


Re: Use case description  

Rogs & K,

My old mate kmajoos makes the classic mistake of people using use cases to design a solution i.e. screens etc. If you have design e.g. UI screens, fields etc in your use case, then when these change you have to go and change your use case. If you want to design screens, then use a UI specification. e.g. line 2 of the main flow above - The system displays the request screen (see GUI-001).

This approach means your use case is tied to your solution and use cases are by definition solution independent. To continue the example, if the company decides to allow mobile access using say a PDA, then having defined a particular screen in your use case, your use case is invalid and must be revisited. But if you've just defined the function, no change is required.

Understanding this is crucial to writing good use cases.

Another thing about use cases, don't assume one use case equals one screen. The relationship is many to many. In the above example, if another screen was required to enter parameters or something, then the use case must again be changed.

I suggest these artefacts in your case Rogs

  • functional definition - including use cases that defines the functions (and process or whatever else fits) in the system and is solution independent
  • UI definitions
  • Report definitions

Kimbo

 
New Post 4/22/2009 11:26 PM
User is offline KJ
243 posts
6th Level Poster


Re: Use case description  

Kimbo,

Good to hear from you. We seem to be saying the same thing.

Note my introduction, first sentence, mate

"there are 2 componets to your issue. 1) the report request (use case) and 2) the report GUI/Layout (display). The latter is normally in another specification.

You need to tie your use-case to some of the GUI/Reports. A reference or note to that effect is sufficient.

warm regards,

K

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Use case description

Community Blog - Latest Posts

Salesforce has established itself as one of the most reputable CRM platforms, providing important customer data to assist businesses in effectively managing their operations. Salesforce is the world's best CRM platform that helps businesses to keep up the data in an arranged or structured manner. Salesforce is the world's most popular...
There are big differences between data exploration versus data presentation. And you need to be aware of these differences as you're creating data stories and data presentations. Let’s start by defining our terms: Data exploration means the deep-dive analysis of data in search of new insights. Data presentation means...
Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC