There are many schools of thought on how best to gather requirements.
On one hand, there are those that don't document anything and get straight into code, there are others that cover absolutely everything in detail at the start. Both have their problems. The smaller the project, the less risk there is in not capturing requirements. In larger projects, the risk is increases dramatically.
However, develompent is not an exact science and often requirements, even if written well can change due to unknown or unforeseen circumstances which makes you wonder why you bother in the first place! This is where common sense has to prevail. The amount of detail put into the requirements will depend on the scale and nature of the project.
Essentials in Requirement Gathering:
a) Focus and Clarity
b) A Format for Specifying Requirements
c) The Author of the Requirements Document
d) The Language of Requirements
e) Accuracy is Critical
f) Minimize the Risk of Errant Interpretation
Peddi.R.Akurati
::::::::::::::::::::::: www.mindmapinfo.net ::::::::::::::::::::::::::::::::