testing in the software lifecycle

12
0120 4029000 Testing in the Software Lifecycle Debrief

Upload: apex-tgi

Post on 25-Jun-2015

108 views

Category:

Documents


3 download

DESCRIPTION

In software engineering, a software development methodology (also known as a system development methodology, software development life cycle, software development process, software process) is a division of software development work into distinct phases or activities with the intent of better planning and management.

TRANSCRIPT

Page 1: Testing in the software lifecycle

0120 4029000

Testing in the Software Lifecycle Debrief

Page 2: Testing in the software lifecycle

0120 4029000

Initial Project Planning Period

1.1. Test Planning and Control1.1.1. Create system and system integration test plan (5d)1.1.2. Participate in overall project planning (5d)1.2. Test Analysis and Design1.2.1. Perform quality risk analysis (5 d)1.2.2. Outline test suites needed in each iteration (1 d)

Page 3: Testing in the software lifecycle

0120 4029000

2.1. Test Planning and Control2.1.1. Adjust plan as needed for this iteration (1 d)2.1.2. Guide testing work during this iteration (ongoing)2.2. Test Analysis and Design0 d)2.3. Test Implementation and Execution2.2.1. Adjust quality risk analysis (1 d)2.2.2. Design test suites and cases for this iteration (32.3.1. Implement test suites for this iteration (30 d)2.3.2. Execute test suites for this iteration (duration 6 weeks)2.4. Evaluating Exit Criteria and Reporting2.4.1. Check test results against exit criteria in test plan (ongoing)2.4.2. Report test results to project management team (ongoing)

Iteration One (Very High Priority Features)

Page 4: Testing in the software lifecycle

0120 4029000

Iteration Two (High Priority Features)

3.1. Test Planning and Control3.1.1. Adjust plan as needed for this iteration (1 d)3.1.2. Guide testing work during this iteration (ongoing)3.2. Test Analysis and Design3.2.1. Adjust quality risk analysis (1 d)3.2.2. Design test suites and cases for this iteration (30 d)3.3. Test Implementation and Execution3.3.1. Implement test suites for this iteration (30 d)3.3.2. Execute test suites for this iteration (duration 6 weeks)3.4. Evaluating Exit Criteria and Reporting3.4.1. Check test results against exit criteria in test plan (ongoing)3.4.2. Report test results to project management team (ongoing)

Page 5: Testing in the software lifecycle

0120 4029000

Iteration Three (Medium Priority Features)4.1. Test Planning and Control4.1.1. Adjust plan as needed for this iteration (1 d)4.1.2. Guide testing work during this iteration (ongoing)4.2. Test Analysis and Design4.2.1. Adjust quality risk analysis (1 d)4.2.2. Design test suites and cases for this iteration (30 d)

Page 6: Testing in the software lifecycle

0120 4029000

Iteration Four (Low Priority Features)5.1. Test Planning and Control5.1.1. Adjust plan as needed for this iteration (1 d)5.1.2. Guide testing work during this iteration (ongoing)5.2. Test Analysis and Design5.2.1. Adjust quality risk analysis (1 d)5.2.2. Design test suites and cases for this iteration (30 d)5.3. Test Implementation and Execution5.3.1. Implement test suites for this iteration (30 d)5.3.2. Execute test suites for this iteration (duration 6 weeks)5.4. Evaluating Exit Criteria and Reporting5.4.1. Check test results against exit criteria in test plan (ongoing)5.4.2. Report test results to project management team (ongoing)

Page 7: Testing in the software lifecycle

0120 4029000

Iteration Five (Very Low Priority Features)

6.1. Test Planning and Control6.1.1. Adjust plan as needed for this iteration (1 d)6.1.2. Guide testing work during this iteration (ongoing)6.2. Test Analysis and Design6.2.1. Adjust quality risk analysis (1 d)6.2.2. Design test suites and cases for this iteration (30 d)6.3. Test Implementation and Execution6.3.1. Implement test suites for this iteration (30 d)6.3.2. Execute test suites for this iteration (duration 6 weeks)6.4. Evaluating Exit Criteria and Reporting6.4.1. Check test results against exit criteria in test plan (ongoing)6.4.2. Report test results to project management team (ongoing)

Page 8: Testing in the software lifecycle

0120 4029000

Post Project Period

7.1. Test Planning and Control7.1.1. Document variances from plan (5 d)7.1.2. Participate in project retrospective (1 d)7.2. Test Closure Activities7.2.1. Finalize testware for archiving or hand-off (20 d)7.2.2. Document test environment configuration (10 d)

Page 9: Testing in the software lifecycle

0120 4029000

Test case summary

Page 10: Testing in the software lifecycle

0120 4029000

Test suite summary

Page 11: Testing in the software lifecycle

0120 4029000

Test case completion

Page 12: Testing in the software lifecycle