Requirements Capture Process

Summary

The requirements capture process at Stylus begins with client communication and the definition of initial requirements and ends with the creation of the software requirements specification document. The documents generated in the RC process should tell the client how the solution offered is the best solution and how it would do what it promised to accomplish.

The benefits of having a solid RC process are that vague client requirements are clearly defined. This helps communication between user and developer with different backgrounds. Also, risks and costs are reduced during development.

The RC team analyses the client's problem to arrive at a Vision document. The Vision document looks out into the future and aims to describe all that will happen on a project until the delivery stage. This is a document outlines a high-level client view of the system to be built. The Business objective, the overall vision for the solution proposed, assumption and dependencies, scope of releases, limitations and assumptions are proposed here.

The SRS or the software requirements specifications document
A requirements specification is the definition of the requirements and provides a basis for estimation and helps define costs accurately. The SRS also helps the design and project implementation team begin their work in an easy manner.

Use case diagrams
Use case diagrams show the possible scenarios in the project - they are information models that help convey the concepts of the application being developed.

Functional specifications
Functional specifications are blue prints for how a particular web project or application looks and works. It details what the finished product will do and how a user will interact with it. Functional requirements describe a service of a function that the solution must provide. A non-functional requirement describes a constraint placed in the solution or on the development process. Once those specifications are created, they are validated and a feasibility study is done.

At the end of the RC process, the client signs of the SRS and the project is passed on to the Project manager who allocates a project leader for the project.

7 important points to keep in mind for successful requirements capture

Related Links - Client Care

How to Reduce Outsourcing Risk 6 Ways to Effectively Manage Your Software Development Risk Getting Started Quick Start Pilot Our Processes Web Development Process Sample Agreement International Payment Details Global Clients Project Tracking Code Of Ethics Enterprise Project Management Objectives Management System Pools: Our specialists