Requirement Management

Jump to Comments

Requirement Management

 

Purpose

1.      To establish a common acceptance criteria between the Customer and the Project Team on the features and functionalities that are been developed and delivered.

2.      To translating the customer requirements into documented Software Requirements Specification.

 

Process Requirements:

The following are the process of the requirement management:

 

1. Elicitation - Identify the Requirements:

 

Entry Criteria: Business Proposal

 

Procedures:

• Activity or Task: On approval of business proposal, the team will have to transform the client needs and expectations captured into formal System/ Software requirements

 

Mode of Contact:

 

By Direct Customer Interaction

Record the Customer requirements

Collect necessary materials from the customer

Get clarification on doubts

 

Customer provided requirement document

Analysis the Customer requirement

Comfortable with the requirement

 

Requirement against existing Project / Product

Arrange a demo and record the gaps

Feasibility Study

Prepare Gap Analysis document

• Record Retention: Draft version of SRS

 

Exit Criteria: Established Requirement

 

2. Analysis

 

Entry Criteria: Established Requirement

 

Procedure:

• Activities or Task: To identify the requirements in a complete, accurate, consistent, and unambiguous manner.
• Record Retention: Revised version of SRS

 

Exit Criteria: Analyzed requirements

 

3. Prepare Software Requirement Specification (SRS)

 

Entry Criteria: Analyzed requirements

 

Procedure:

• Activity or Task: Documentation of the software requirements specification using SRS Template
• (Refer: http://en.wikipedia.org/wiki/Software_Requirements_Specification)
• Record Retention: Requirements Checklist

 

Exit Criteria: Software Requirement Specification

 

4. Validation:

 

Entry Criteria: Software Requirement Specification

 

Procedure:

• Activity or Task

1.      The completed SRS document shall be reviewed. The details of the review shall be recorded in the Review Report-Work Product

2.      On closing all the review comments, SRS shall be approved.

• Record Retention: Review Report (Software Requirement Review (SRR) - Work product

 

Exit Criteria: Approved Software Requirements Specification

 

2 Comments

Filed under Process Life Cycle, Requirement Management, Software Development Life Cycle, Software Quality Assurance

Tags: Activities, Process, Requirement Engg, Requirement Management, SDLC, SQA, Validation, Verification