System Testing Entry and Exit Criteria

1.1 Entry Criteria

The following must be in place prior to the onset of QA System Testing
Business

· The Business Requirements Document is “frozen
· All new Requirements that arise are initiated through Change Control process

QA
· Daily communication plan in place
· Test Cases Reviewed & signed-off
· Cross-functional, dependent teams & resources identified
· QA Data Requirements identified & all necessary passwords/accesses obtained
· Daily Defect Meeting Day/Time/Attendance established in the execution phase
· All appropriate team members have access to Test Director
· Test cases have been linked to test sets in Test Director
1.2 Exit Criteria

The following must be in place prior to the sign-off of QA System Testing:
· No open P1 or P2 defects
· All P3-P5 (enhancements) defects have a documented resolution plan
· A minimum of 2 test cycles (100% execution) is completed.
· 95% Pass Rate of all test cases
· Regression testing of defects fixed during system testing
· All defects logged in Test Director
· QA sign-off on system test
· System test Close-out report Provided
· Documented list of any outstanding (open) defects

Testing Process

Testing Process
1. BRS Review
2. Test Plan Review
3. FRS Review and Reporting
4. Participating in Review Meetings.
5. Identifying the Test scenarios
6. Prioritizing the scenarios
7. Designing the Test cases.
8. Involving in Peer Reviews (Optional)
9. Sending the TCD to Lead for Lead Review
10. Refining the Design based on Peer/Lead comments (optional)
11. Getting the approval for the design from BA. (Baseline)
12. SRN study, understanding the scope.
13. DD study, Deploying the Build into Test Environment
14. Conducting Sanity
15. Proceeding with Functional Testing.
16. Defects Reporting
17. Getting the modified build from Development Team.
18. Re and Regression testing on the modified build.
19. Preparation for System test scenarios and performing System Testing. (Domain Experts)
20. Test Closure.

CMM Levels

CMM:(Capability Maturity Model) SEI : CMM: (Software Engineering Institute): Initially a five level model is developed by the PHD people from Software engineering Istitute located in USA. That is why it is named as SEI CMM. These 5 levels are for IT industries
CMM Level 1: INITIAL : It is used for startup companies but here one thing is considered team should be very strong technically strong, more experienced people so definitely the product will be quality product. If at all the team strong they wont ask any guidelines. ( with Strong Team and well defined guidelines )
CMM Level 2: REPEATABLE: Once we entered into it two guidelines are given one is well defined guidelines another they should focus on reusability. Team should very strong in Technical. (with Strong Team , well defined guidelines and Focus on Reusability )
CMM Level 3: DEFINED :It means Documented. At CMM Level 3 it should focus on Documentation. (with Strong Team , well defined guidelines ,Focus on Reusability and focus on Documents)
CMM Level 4: MANAGED Each and every work in the organization must be measured ( Metrics). It should focus on metrics apart from level 1 + level 2 + level 3.(with Strong Team , well defined guidelines ,Focus on Reusability, focus on Documents and focus on Marketing )
CMM Level 5: Research and development & as well as continual growth. level 1 + level 2 + level 3 + level 4 as well as Research and development & continual growth. There is a great demand for CMM Level 5 . These 5 levels are for IT industries(with Strong Team , well defined guidelines ,Focus on Reusability, focus on Documents, focus on Marketing and focus on Research and Development)
CMM I (Integrated): It is introduced for both non IT & IT integration
CMM P 0r PCMM: P stands for People capability & maturity of people. It focus on People.