Requirement Gathering & Analysis
Typically, requirements gathering is done through a series of interviews/sessions with the stakeholders to understand the why’s and how’s of the project. These requirements are documented in theBusiness Requirements Specification. We understand that the most difficult part of requirements gathering is not documenting what the users 'want'; it is the effort of helping users figure out what they 'need' that can be successfully provided within the cost and schedule parameters available to the development team. Therefore, we make sure that the Requirements are actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.
The analysis starts in parallel with the Requirement gathering so that any ambiguities/confusions are resolved with the client before moving on to development. This also saves on a lot of time spent on review and rework later on. During the Requirement Analysis the Functional and Non-Functional requirements are identified and clearly stated in theSystem Requirements Specifications document. It also includes a set of use cases that describe all of the interactions that the users will have with the software.
We also emphasize on review of the Analysis thoroughly internally as well as by the customer.