Requirement gathering is a process of collecting the user needs to solve a problem or issues and achieve an objective.
It is basically a software capability needed by the user to solve a problem or achieve an objective.
This is really an important phase/milestone in a project lifecycle. Because if the requirement gathering is not done properly/completely, all below hierarchy phases get incomplete. No matter how best the design, until unless requirements are incomplete.
It is not quite accurate to say that requirements are in the minds of clients; it would be more accurate to say that they are in the social system of client organization. They have to be invented, not captured or elicited and that invention has to be a cooperative venture involving the clients, the users and developers. The difficulties are mainly social, political and cultural and not technical.
No comments:
Post a Comment