• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

requirement gathering for User Interfaces

 
Shanmugam nagaraj
Ranch Hand
Posts: 76
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
while gathering requirement how can we capture the logic behind the radio button for user interfaces like forms report etc.

For example :
if you have 50 fields in one form and you need to select one radio button out of 5 radio button if the first radio button has selected then you need to populate the 10 and 20 th fields.

how can we capture the requirements and document it for the purpose of developer.

Any body have any sample template to capture this kind of situation, I struggle a lot for week, but cant find a solution.


Thanks in advance

Shaan
 
raj malhotra
Ranch Hand
Posts: 288
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Shaan
One way can be -whenever you select one radio button ,a javascript method should be called .In that method you can disable/hide all other fields except the required fields.
Now when you submit the form depending upon the radio button value you can validate your form.
[ October 03, 2008: Message edited by: raj malhotra ]
 
Martijn Verburg
author
Bartender
Posts: 3275
5
Eclipse IDE Java Mac OS X
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In terms of capturing your requirements, you should probably look at Use Case diagrams or other UML modeling techniques.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Use Case diagrams are not particularly good for this kind of documentation. And I don't know of anything else in UML that would sound appropriate for me.

At which stage of development are you? As a developer, I would probably prefer to get this requirement in the form of an executable Acceptance Test, but it might be too early to write such a thing if it isn't going to be implemented soon.
 
Martijn Verburg
author
Bartender
Posts: 3275
5
Eclipse IDE Java Mac OS X
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ilja Preuss:
Use Case diagrams are not particularly good for this kind of documentation. And I don't know of anything else in UML that would sound appropriate for me.


Ilja is quite right and my apologies for putting you wrong there. What you might find useful is a simple 2-d matrix (Spreadsheet) with the radio buttons listed down one side and the fields listed along the top, you can then fill in the squares of the fields that should be active when you select a particular radio button.
 
Shanmugam nagaraj
Ranch Hand
Posts: 76
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for response..

At which stage of development are you? As a developer, I would probably prefer to get this requirement in the form of an executable Acceptance Test, but it might be too early to write such a thing if it isn't going to be implemented soon.


My role is system analyst(new to this role...)

It is in analysis stage like gathering the information from user and documenting and finalizing a solution...

what is executable Acceptance Test ? do you have any sample to explain me better..

My template need to be as ready to code condition and it have to be finalized by user, i.e the template is need to cover all the scenario and confirmed by customer or users. I struggling to probe the right questions and also how to prepare the template like forms..reports letter etc...

Is there any url, document, material, etc. any thing.....to answer my questions
 
Shanmugam nagaraj
Ranch Hand
Posts: 76
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any body can help out this???
 
Jimmy Clark
Ranch Hand
Posts: 2187
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
while gathering requirement how can we capture the logic behind the radio button for user interfaces like forms report etc.

how can we capture the requirements and document it for the purpose of developer.


A good option for capturing requirements is Use Case narratives.

A Use Case narrative is a textual explanation of a Use Case. It the text of the narrative, one can describe the logic behind the GUI / form report. Also, one can describe any other presentation/display requirement, such as a specific graphic has to be displayed.

Use Case narratives provide good documentation and are very helpful for developers. The key to writing good Use Case narratives is good spelling, good grammar and punctuation, and a clean writing style.

Good Luck!
 
Lutz Hankewitz
Greenhorn
Posts: 5
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
you can take a look at decision tables to document these kind of rules.
see decision tables

kind regards

Lutz
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic