Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  designing user case
Previous Previous
 
Next Next
New Post 1/9/2009 1:55 PM
User is offline carmelfarrugia
4 posts
No Ranking


designing user case 

Dear All,

I thought that I am confident with writing user cases.  However, I am getting slightly confused with this case scenario:

The customer wants the BA to design a screen form that will comprise a top section that records clients details; together with another two tabs (i.e. two sub screens; tabs as in vb tab screens etc), each one to provide a different function.  Also, the user wants a facility to inport a file and to export a daily output file.

The dilemna is that should the BA define a user case defining issues such as the sequence of events, rules, pre conditions post conditions etc, for the top section that records clients detail, another one to cover the functionality of one tab and another to cover the functionality of the other tab, a user case to cover the import facility and another to cover the export facility??

Should the BA define e.g. RULES SECTION and under neat it  define the rule for the top section that records clients detail, followed by a sub section (still defining rules) that incorporates the rules that fall under one tab; followed by a sub section for the other tab etc.,?  Or should the BA do one case for the top section that records clients details, one section for the functionality covered on one tab and another user case to cover the functionality of the second tab etc?????

I hope that the above is clear and I am pretty sure that you must have covered a lot of experience in cases like this.

Many thanks for you input.

 

Regards,


Carmel

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


Re: designing user case 
Modified By KJ  on 1/10/2009 1:16:57 AM)

Carmel,

No concreting this time, I’m taking Kimbo’s advice!

When confronted with these convoluted requirements, always revert to the basics of a use case. We identify the user and the user’s goal. Secondly, a single screen could map onto multiple use cases and vice versa.

So, given the complex design constraints placed on this requirement how would you 1) identify the users, and 2) identify the goals of each user. At a high-level each of the goals becomes a use case.

Lets say the goals are 1) to capture/record client information (this covers cleint capture and imports); and 2) to make client details available to others (this covers the export functions).

Here is a sample snippet for goal 1:

Goal: capture/record client(s) information

Main Scenario

1.       This use case starts when the clerk is presented with the new client options screen (scr:CLi).

2.       The clerk selects the “Enter Client details“ menu item

3.       The system presents the “Enter Client details“ screen (scr: CLi001-001 with two tabs)

4.       The clerk enters the new client data. Current address at Tab1, and other address at Tab2.

5.       The system records client details and displays “wow another client”

Exception

2.1. The clerk selects the “Import client details” menu item.

2.2. The system presents the “Import client details” screen (scr: CLi002)

2.3. The clerk enters the file location and format(XML, CVS format)

2.4. The system uses the import file at specified location and updates client data.

2.5. The system  displays “wow heaps more clients”. This use case end here.

Post Condition.

       New client(s) established

Sample Screens:

Note: all screens are mock-up VB screen editor/dumps)

CLi – Main Menu

CLi001-001 – Enter Client Screen

Cli002 – Import Client Screen (etc..)

 

All the best,

K

 
New Post 1/12/2009 4:47 AM
User is offline carmelfarrugia
4 posts
No Ranking


Re: designing user case 

Dear knajoos,

Many thanks for your reply which is very clear.  However, this is where the whole matter needs clarification as to the way one would design the U Case.

Let us focus on the case whereby the user will select the form to enter the client details and then the user will select  tab screen 1.

Now at this stage, the use can select class type 1 from a dropdown list (within tab screen 1), so that s/he will enter the corresponding details (that correlate to the option 1 type).  If the user selects class type 2 from the dropdown list, then some of the fields available for class type 1 will not be relevant and the rules that applied for the class type 1 no longer applied - differ.

So, what should the user case show in terms of rules, post conditions etc?

Is it appropriate to define  one user case and  show the data capture entry at top level (for the whole screen), followed by a sub section to cover the  selection of tab 1 screen, etc.,  Under this section then one will define the flow of events, rule, pre-conditions, post-conditions etc to highlihgt the event of tab 1 selection.  This will be followed by class 2 option selection??  See below

 e,g:

MAIN FLOW OF EVENTS

1.0) Enter Client Details

1.1) Select tab1 screen

       1.1.1) e.g. Select class type 1 - define the main flow of events are as follows...

       1.1.2) e.g. Select class type 2 - define the sequence of what should be selected and sequence of events....

1.2) Select tab2 screen

..................

RULES:

1.0) Enter Client Details - the rules are as follows .....

1.1) Select tab1 screen

       1.1.1) e.g. Select class type 1 - define the rules as follows...

       1.1.2) e.g. Select class type 2 - define the rules as follows....

1.2) Select tab2 screen

..................

PRE-CONDITIONS

1.1) Select tab1 screen

       1.1.1) e.g. Select class type 1 - define the pre-conditions are as follows...

       1.1.2) e.g. Select class type 2 - define the pre-conditions are as follows....

1.2) Select tab2 screen

..................

etc.,

I hope that this is clear and I am pretty sure that you must have came across cases like this.

 

Many thanks for your precious ideas.

 

Regards,


Carmel

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  designing user case

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC