Advice on Requirements Gathering/Analysis

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have come mainly from a Development background.

I have now to get involved in some Requirements Gathering / Analysis.

My Customer is going to give me a brief Requirements document of what they
want.

I am then going to write a Functional Specification document and get him to
sign this off. This Functional Spec will detail how the system will work from
a business point of view.

Once the functional spec is signed off we then start development.

Am I approaching this in the correct way?

Thanks in Advance.
 
Sure, don't be surprised though if the customer then doesn't realize
something, and want something changed. Or if your document misses one of the
'exception' cases or neglects to figure out what happens if there is a
certain combination of conditions, etc.

Basically, this might be a general spec, but it's all the little details
that end up coming that always require going back and forth to settle those.

But in general, the more thought out the requirements are, the smoother it
will go. And from my experience customers are generally not capable of
providing that, so a lot of it will be up to you.
 
Thanks Marina.

Marina Levit said:
Sure, don't be surprised though if the customer then doesn't realize
something, and want something changed. Or if your document misses one of the
'exception' cases or neglects to figure out what happens if there is a
certain combination of conditions, etc.

Basically, this might be a general spec, but it's all the little details
that end up coming that always require going back and forth to settle those.

But in general, the more thought out the requirements are, the smoother it
will go. And from my experience customers are generally not capable of
providing that, so a lot of it will be up to you.
Click to expand...
 
Back
Top