Requirement Analysis Level

Requirement Analysis

Overview

 

During this phase, test team studies the requirements from a testing point of view and identify the testable requirements. This also includes interaction with various stakeholders involved in the project to understand requirements in detail to define the scope of the work. Automation feasibility analysis (checking the applicability of various test tools to carry out and manage the testing) is also one of the activities done in this phase. Requirements could be classified as

Functional Requirements: These specify the functions that a system or system component must be able to perform.

Non Functional Requirements: Non-functional requirements specify system's quality characteristics/attributes like performance/security/availability etc.

 

Various components of this phase can be found in the below diagram.

 

Entry-criteria

 

1.Requirements Document available (both functional and non functional)

2.Acceptance criteria defined.

3.Application architectural document available.

 

Activities under Analysis Stage:

 

1.Analyse business functionality to know the business modules and module specific functionalities.

2.Identify all transactions in the modules.

3.Identify all the user profiles.

4.Gather user interface/authentication, geographic spread requirements.

5.Identify types of tests to be performed.

6.Gather details about testing priorities and focus.

7.Prepare Requirement Traceability Matrix (RTM). Refer to Test Deliverables (RTM section) for the details of this.

8.Identify test environment details where testing is supposed to be carried out.

9.Automation feasibility analysis (if required).

 

Measures

 

1.Effort spent on

a.   Requirement Analysis to prepare RTM

b.  Review and rework of RTM

c. Automation feasibility analysis (if done)

       2.Defects

                        a. RTM review defects.

Exit-criteria

 

Signed off RTM

Test automation feasibility report signed off by the client