Wednesday 15 August 2012

Functional and Performance Testing


1.0          Introduction

Project Process - Delivery Management & Testing Stages Mapping


NOTE:
1)     The above chart depicts how delivery management and testing activates complement each other.
2)       Delivery Management and testing stages happen in parallel.

1.1      Purpose

<This sub-section provides the following information:
§  An overview of the contents and organization of the document
§  Target audience. >

1.2      Scope of the Project

<This sub-section provides the following information:
§  The line of business / solution offering is to be specified
§  Scope of work (in terms of stages in the software development life cycle)
§  The operational model chosen (based on the scope of work)
§  List of processes applicable to the project >

1.3      Definitions and Acronyms

<This sub-section defines all terms, acronyms and abbreviations used in the project.

1.4      References

<This sub-section provides a complete list of all documents referred to in the Process Handbook or those on which the Process Handbook is based on.>

1.5      Assumptions

<This sub-section state the assumptions based on which the Project’s Software Process Handbook has been prepared. >

1.6      Stage Definition

<The stages/processes chosen for the project are:
Please mark applicability of stages in the tabular provided below. IF A PARTICULAR STAGE IS NOT APPLICABLE, and if the PSPH is being tailored to arrive at a Project Specific Process Handbook, ensure that the stage is removed to actually indicate that the stage is not available for the project. >
Stages / Process
Applicable / Not Applicable
Proposal

Test Requirements Study

Requirement Analysis

Knowledge Transition

Formalization

Startup

Execution and control

Test Planning               

Test Design                  

Test Development       

Test Execution            

Delivery                        

Acceptance testing

Project Closure

1.7      Customer Profile

Customer Type: <Mention if it is internal or external>
For internal projects: All processes / activities for the scope of work of the project are mandatory.
For external projects: The activities in the process can be tailored based on the customer’s Quality System and new activities can be included