Actually Im a developer, But my Current role is to gathering requirement from user or customer or client .....Because Im working in a small company....
My specific role is to identify the different forms, reports needed for the analysing project.
while analysing forms or reports I need to know what are fields that going to appear on the form or reports...
So I need to interview the clients or user directly. This is the situation
Now my question is like:
1) First I will probe the client for requirement, AFter that I will identify the forms needed for the project.
2) Now I need to capture the forms fields and what are the logic behind each forms rite, how to do that?
For eg: The client ask you to create a form with radio button, text box, tables, option button, label etc..
Radio button: So client saying that I need to select 1 field out of 5 fields, So at this situation you can use radio button, But my question is like how to document it from user, And this document is easy to modify and also understandable by any developer to create.
Tables: So client saying that I need 2 rows 2 columns and this are the heading, So at this situation you can use tables, But my question is like how to document it from user, And this document is easy to modify and also understandable by any developer to create.
So actually I need different kind of template to capture the requirement for Form, reports etc.. from user or clients, or customer....
remember :We are not developing, I just gathering requirement, I need to just document the requirement so any developer can understand and able to create. And also able to understand by client or customer or user to sign off.
First of all you have to find out what the customer needs not what the customer wants or what he think he needs. In practice there might be slightly differences between those.
You should ask the client about the uses cases, to describe exactly how he intends using the software. One those scenarios are identified you might go to identify the attributes of each step, screen, etc.
It's not good if you start focusing on details before having the general picture. Then you have to understand which is the role of each attirbute(field) in the process and make sure the client is on the same wavelength with you.
Previous Topic
