Let us discuss in detail.
The output of Unit Testing stage will be the input for this Integration Testing stage as shown in Fig. 3.5. here we will have Unit Test Modules, Detailed Design Document, Integration Test Cases, Software Project Plan, Software Configuration Management Plan, Software Measurements/Metrics Plan and SQA Plan as the inputs for this stage. The main task of this stage is Integrate all modules after that perform Integration Testing against Integration Test Cases and report and track the bugs. The final output of this stage is Integrated and baselined product, Integration Test Reports and Updated Project Data Collection Sheet. This testing done by Developers and sometimes by White-box Testers (based on the Organization).
It is pure black-box testing. As shown in the Fig. 3.6. System Test Plan, System Test Cases, Software Project Plan, Software Configuration Management Plan, Software Measurements/Metrics Plan and SQA Plan are the inputs for this stage here testing is performed as per the schedule and different tests depend upon the client requirement. After testing report and track the bugs. The final output of this System Testing is Integration Test Reports and Updated Data collection Sheet. Different type of tests like Compatibility testing, documentation Testing, Facility Testing, Installability Testing, Performance Testing, Procedure Testing, Recovery Testing, Security Testing, Serviceability Testing, Storage Testing, Functional Testing, Regression Testing, Load Testing, Stress Testing, Usability Testing, Link Testing and Volume Testing.
After completion of System Testing, we will have Software Requirement Specification Document, Detailed Design Document, Professional Service Agreement, System Tested Software Product and Software Project Plan documents as input for this phase. And in this stage the Information system will go live into production. Testing team installs the application in Production Environment and they will do some Client Acceptance Testing against User Requirements. Generally Alpha Testing and Beta Testing comes under Acceptance Test. The client in the presence of Developer at Developer Site will do alpha Testing. But beta Testing is done at the User end Client will distribute the application to the end-users and he will collect the feedback and bug reports from them. The final output of this stage gives a full-fledged User Manual, Installation Instructions, Release Notes and Updated Project Data Collection Sheet.
Once the application has been deployed successfully it needs 24 X 7 support provided to the customer so that the customer does not come across major problems in operating the system. It depends on the Organization to decide the strength of the support team. Generally supporting is done in three levels:
1. First Level Support (FLS)
2. Second Level Support (SLS)
3. Third Level Support (TLS)
First Level Support deals with logging of complaints that are explained by the Customers, it is the primary duty of the FLS professionals to keep track of the timing that has been taken to solve the issue. FLS professionals log the tickets and store it in an Open Server accessed by Second Level Support Professionals.
Second Level Support deals with the solving of the issue in an accurate way and also in a very short span of time. Once the SLS professionals find the issue complex and not solvable, it will be escalated to the Third Level Support.
Third Level Support is generally the high level professionals, who are well versed of the technology that has been used in the product and they are the professionals who take care of all complex issues. TLS Professionals would be concentrating on the time that required solving the issues.
In case the issue is a bug and has to be escalated to the Development Team then it is the duty of the TLS Unit to decide whether the bug has to be addressed early or not
vyoma.net | About | Contact | Site Map | Copyright © 2015. etestinghub