I'm a beginner in systems and would want to understand more about the SDLC before I plan for an upcoming project.
I'm trying to understand the "readiness" of the testing phase of the SDLC including SIT, UAT, ORT and Production. I was wondering for each phase, what are the different "readinesses" (i.e. the different tasks that is required for me to say, for example, to complete SIT before I move onto UAT, and then UAT to ORT and ORT to Production)?
Re: Before planning, require some knowledge in SDL
Below are some of the items or tasks that come to mind at the moment. I hope they will be of assistance to your testing processes and methodology.
SIT - System Integration Testing
-> Enter criteria;
1. All requirements or use cases have been locked down and approved
2. Test plan completed and approved
3. All identified test cases have been written and reviewed
4. All functionality code has been completed
5. Unit testing has been completed
6. Code review has been conducted
7. Code has been delivered to QA
8. Test environment has been set up
9. Testing schedules has been established (included in the Test Plan)
10. Resources have been identified and allocated for the project (included in the Test Plan)
-> SIT Exit criteria;
1. All test cases have been executed (100% coverage)
2. At least 80% of the test cases have passed (this could be higher or lower depending on your methodology)
3. All Critical or Major defects have been addressed (P1 and P2)
4. SIT Summary report has been created
UAT - User Acceptance Testing
-> UAT Enter criteria;
1. Customer business scenarios have been identified
2. Test environment has been set up
3. UAT Test Plan has been created and approved
4. Testing schedules has been established (included in the Test Plan)
5. Resources have been identified and allocated for the project (included in the Test Plan)
-> UAT Exit Criteria
1. All customer business scenarios have been executed (100% coverage)
2. All customer business scenarios have passed (100% pass coverage)or deferred to future release
3. All (100%) of the defects have been closed or resolved (deferred to future release)
4. UAT Summary report has bee completed
3. End user signs off on UAT Summary Report
Note: Performance testing should be conducted throughout the process, during SIT and UAT. All performance defects should be address prior to moving the code to production.
Additionally it would be important to note that all documentation should be ready prior to UAT and finalized prior to production.
Code is now ready for production :-)
A postmortem should be conducted at the end of each cycle in order to identify improvements areas and waste processes to be included/excluded in future SDLCs.