Form Template - requirement gathering
-
Hi, 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. Thanks in advance Shaan
-
Hi, 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. Thanks in advance Shaan
-
Hi, 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. Thanks in advance Shaan
Why do you think the client will know that they want radio buttons, etc? This isn't the way most users think. What you need to do, instead, is get the requirements from the user about what they are actually trying to do. Then, you may want to draw up some use cases to map the process from the users point of view.
Deja View - the feeling that you've seen this post before.
-
Why do you think the client will know that they want radio buttons, etc? This isn't the way most users think. What you need to do, instead, is get the requirements from the user about what they are actually trying to do. Then, you may want to draw up some use cases to map the process from the users point of view.
Deja View - the feeling that you've seen this post before.
This particular thread makes me wonder if there should be an article done here on requirements gathering.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
This particular thread makes me wonder if there should be an article done here on requirements gathering.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
CP's Matt Gullett in 2003 did a series (here is part 1) The Life of a Project[^].
That's a nice find, Richard. It looks like one to definitely bookmark for reading later tonight :)
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham