DEV ITPL adheres to the global norms as speicifed under ISO certifications for the software development service industry applicable world wide. We have software development quality check flexible processes's such as that the prominent best practices shared by Microsoft and Oracle to ensure the quality of solutions being developed on its platform is imbibed by our quality check processes's based on specific solution requirement.
The QC hierarchy has been shown in the QC team structure attached to the organization and staffing chart.
The roles and responsibilities for conducting inspections are as under:
| Inspection Item | Author |
| URS | Systems Analysts |
| SRS | Systems Analysts |
| Code | Jr./Sr. Developers |
The roles and responsibilities for conducting reviews are as under:
Phase | QC Item | QC Activities |
User Requirement Study | URS document, Test Matrix document |
Team Inspection |
Systems Analysis | SRS Document, Test Matrix document |
Team Inspection |
Systems Design |
SDD, Test Matrix document |
Team Inspection |
Coding |
Application Code, Test Matrix document |
Individual Inspection |
Testing |
Test Results Document, Test Matrix document |
Review |
Implementation |
Alpha Test Results document |
Review |
Training |
Feedback Forms, Test Matrix document |
Review |
Service and Maintenance |
Change Requirement document, Test Matrix document |
Reviews/Inspections |
CONFIGURATION MANAGEMENT
• Version Control
• Change Control
• Trace Matrix
• Backup procedures
MODULE WISE TEST AND IMPLEMENTATION PLANS
The test plan consists of the following phases
Unit Test
Each module is tested using the procedural design description as a guide. Important control paths are tested to uncover errors within the boundary of the module. This is a white box oriented test and will be conducted by the developers themselves. For each module relevant log reports will be made (if necessary) so as to perform this test.
Integration Test
The integration test performed by DEV ITPL will be Bottom-up Integration. As modules are integrated from the upwards from the bottom, end stubs can be avoided and hence reduce coding overheads. As we move upwards the requirement for drivers is also eliminated. If, in case, the upper modules are through with unit testing, upper drivers can also be eliminated.
Finally regression testing can be performed as per design requirements.
Validation Test
Validation test will check if the specifications in the SRS are met. This will be a black box test, where a test plan will be outlined to uncover errors in conformity with requirements. It will check if all the performance requirements are achieved, documentation is correct and human-engineered and other requirements like error recovery, maintainability are met.
System Test
This final test phase will consist of Recovery Test: To check whether the system can recover within a pre-specified time from faults. It will also test the level of fault tolerance.
Security Test
This test will check the level of unauthorized penetration of the system.
Stress Test
To check how the system performs in certain abnormal conditions.
Performance Test
Here the overall performance of the system is tested with the context of the integrated system.
During and after the test phase the debugging phase will commence. Here the following approaches will be adopted, as per requirements:
• Backtracking.
• Cause Elimination.
Related Links >> Application Development : Methodology | Projects