Difference between needs and requirements

Jump to navigation Jump to search

near the start of article, it says "an <a href="/wiki/Acquirer_(glossary)" class="cat-glossary_of_terms" title="Acquirer (glossary)">acquirer</a> specifies the needs and requirements" - an acquirer is one of several stakeholders - they totally have needs, but they only become requirements when the systems engineer of the solution has integrated these needs with the needs of other stakeholders, analysed then understood and then completed (stakeholders don't know everything they want) and so produced a valid set of requirements for the system of interest. Failure to distinguish between being a stakeholder defining needs, and the process of defining requirements leads to great confusion and difficulty in the practice of SE.