|
This process is applicable to
all external QA projects irrespective of the SDLC chosen.
QA Testing Phases
• Requirement Analysis.
• Design.
• System Testing.
The four phases Viz., SQA and Review Plan, Configuration Management
Plan, Software Measurement Plan and Software Project Plan
will span across all the phases.
Acronyms & Definitions
• QA: Quality Assurance.
• SEI-CMM: Software Engineering Institute – Capability
Maturity Model.
• SQA: Software QA.
• SE: Software Engineer-QA.
• SSE: Senior Software Engineer-QA.
Operating Process
Operating Process
| Roles |
Responsibility |
| Team Lead |
Preparation of System Test Plan |
| Team Lead / SSE/SE |
Preparation of Test case Index document |
| Review Team |
Review of System Test Plan & Test Case
Index |
| Customer |
Approval of Software Test plan and Test
case Index (if required) |
| Systems / Database Administrator: |
set up the environment. |
Entry Criteria
• Completion of contract review.
• Completion of PIN.
Input
• Software Requirements Specification document.
• Use Cases.
• User Manual.
• Client’s Test Cases.
• Application Software (software to be tested).
• Other project related documents.
TASKS
Task01: Prepare Software Test Plan
• Prepare Software Test Plan.
• Review Software Test Plan.
• Log and fix defects.
Task02: Prepare Test Case Index Document
• Study and analyze the client’s documents and
application.
• Prepare Test Case Index document.
• Review Test Case Index document.
• Log and fix defects.
• Obtain customer approval.
Output
• Test Case Index document.
• Review Logs.
• Software Test Plan.
• Defect Data collection log.
Exit Criteria
i. Software Test Plan Document baseline is established.
ii. Test Case Layout Document baseline is established.
Design
| Roles |
Responsibility |
| TL and SSE /SE |
Design of System Test cases |
| PL/Peer TL |
Review of System Test cases. |
| SQA Group |
System Test case audit |
Entry Criteria
Availability of baseline System Test Plan document.
Test Case Index document.
Input
i. Software Test Plan.
ii. Test Case Index document.
TASKS
Task01: Prepare System Test Cases
i. Prepare System Test Cases.
ii. Review System Test Cases.
iii. Log and fix defects.
iv. Baseline System Test Cases.
Output
• System Test Cases.
• Review Log.
• Defect Data collection log.
Exit Criteria
• System Test Case document is base lined.
The following are the revised documents:
• Software Test Plan.
• System Test Cases.
System Testing
System test planning consists of creation of the environment
required for testing the product. This environment is similar
to the user environment consisting of hardware, software,
communications and any other support tools.
System Testing is to be carried out on the software product
by QA Engineer(s).
Responsibilities
| Roles |
Responsibilities |
| Test Team |
Execution of system test cases / test scripts |
| Client’s Development Team |
Fix defects |
| Systems / Database Administrator |
set up Application Environment |
Entry Criteria
i. System Test Cases design is completed.
Inputs
i. Software Test Plan.
ii. System Test Cases/Test scripts.
iii. Application Software.
TASKS
Task01: Setup Testing Environment
i. Setup System Testing environment.
Task02: Perform System Testing
ii. Execute System Test Cases.
iii. Review defects.
iv. Post and track defects.
v. Send defect documentation to customer.
Task03: Close Defects
vi. Receive new build.
vii. Re-execute System Test Cases.
viii. Close defects.
Output
• Test case/Test script execution summary.
• Defect data collection Log.
• Bug summary report.
• Test summary report.
Exit Criteria
• System Testing is conducted and defects are closed.
Checklists
The following checklists are available to assist reviewers
and SQA auditors in assessing the quality of various work
products produced in the software process.
• Software Test Plan Checklist.
• Test Cases Checklist.
• Software Project Plan Checklist.
• Contract Review Checklist.
Standard Templates
• Software Project Plan Template.
• Statement of Work Template.
• Test Case Index document.
• Software Test Plan Template.
• System Test Cases Format.
• Project Status Report-weekly Format.
• Bug Summary Report Format.
• Project Closure Report Template.
|
