Why gather requirements?
You may wish to gather requirements: • To define an architecture, application or component • To purchase software, and discover beforehand what it must do • To aid your choice between writing or buying and customizing software • To gather your thoughts • To gather someone else’s thoughts • To give the testers something to base their tests on, other than an all out bug hunt You may also wish to avoid gathering requirements. Gathering requirements blindly can limit you to getting what you think you want, or limit your sponsors to getting what they think they want. When you do not gather requirements, you do not begin to formulate a solution. This may be the best way to go about purchasing a piece of software. If you gather requirements, then fit each potential suitor to your requirements, you may well filter out the best suitor for your enterprise. You may also not gather requirements initially in the hope of creating an insightful solution to a problem before becoming lost in, or guided
