1. QUALITY ASSURANCE PRACTICES

2. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – – Google Project - ISS2011S7 – Location - https://iss2011s7.googlecode.com/svn/trunk/Documentshttps://iss2011s7.googlecode.com/svn/trunk/Documents Document s MGMT Communi cation PlansQualityReportsTech Specificati on UserWorkSCM

3. Document Review Procedure Review of documents done as per the schedule in the project plan. Review Forms used to capture the defects found in the documentation. Approval to the document given after the changes requested in the review form were made and verified by an assigned reviewer.

4. Software Configuration Management Simple Configuration Management system for code implementation was selected. Main Features – – All development changes done on main trunk. – Feature by feature tagged and released for system testing – Last test run done on fully integrated system. Tag VersionFeatures 0.1Air Documents Processing 0.2Sea Documents Processing 0.3Customer Profile Management 0.4Agent Profile Management + User Administration 0.5Shipment Tracking Management 0.6Full integrated system 1.0Initial Release

5. Testing Strategy and Practices Test plan and cases created and approved after internal review. Issues found during system testing logged using Issue Tracker (corrective actions). – Issues notified to the developer automatically – Issue fixes notified to tester on change of status by developer so that retesting can be done.

6. Testing Strategy and Practices (cont’d) Feature Based Testing Raise corrective actions Developer fixes bugs Fully Integrated System Testing Retesting Test Case Reference no indicated in the issue raised, so that developer can recreate the steps to duplicate the issue.

7. Testing Metrics Test Coverage = 75% Test Run (V0.1 – 0.5) Test Coverage = 95% Test Run (V0.6)

8. Acceptance Procedure User invited to do the multiple round of acceptance testing. – First Round focus on functionality testing (completed) – Second Round focus on non-functionality requirements (ongoing) Feedbacks given in the first round of acceptance testing gave us following metrics – Based on the functionality handled, user has accepted the new software, and the system will be deployed and supported by us for the next 2 months. SeverityNo of Open Points Critical / Severe0 High / Major0 Medium / Minor8 Low / Very Minor13 Total22