|
The most difficult part of requirements gathering is not the act of
recording what the users want - it is the exploratory,
developmental activity of helping users figure out what they
want. During requirements development, the software concept becomes
tangible through the creation of several versions of a user
interface prototype and a user manual. This approach facilitates
gathering the best possible set of requirements, lays a
foundation for excellent architecture work, streamlines the
project by eliminating the time-consuming detailed requirements
document, and keeps user documentation off the critical path.
Software requirements development is the part of the project
during which the needs of the customer are gathered and
translated into a specification of what the system must do.
Requirement Overview of the Product Development:
-
Identify the target market, end-users, potential
competitors.
-
Understanding user requirements and expectations.
-
Building an interactive user interface prototype.
-
Going through iterative process of enhancing the prototype.
-
And then building a complete functional prototype leading
through the entire process flow of the product.
-
Develop the entire product revolving around the actual
prototype.
-
Continuous user observation - and implementing user centric
approach based on the feedback and suggestions.
These activities are often referred to as "specification,"
"analysis," or "gathering". Users’ minds are fertile sources of
requirements, but the project team must plant the seeds and
cultivate them before the requirements can be harvested. |
