Quality Assurance

Our SQA objectives are achieved by adhering to a well-defined process and by adhering to certain well-defined Quality Assurance practices. These consist of:

• Project phases - the development life cycle consists of explicit phases with tangible deliverables.
• Procedural standards - provide the project and team with a set of proven, practical tools and practices with guidelines on how to use them.
• Documentation standards - provide the project and team with the means of preparing the identified tangible deliverable.

The existing quality standards of the client, relevant for the engagement, are considered while tailoring specific standards. If the standards are not pre-defined for any area, we define the standards with client's approval and ensure adherence. All standards required for execution are finalized during the initial planning phase.

Quality assurance activities in the engagement are carried out by teams both internal and external to the project. Internal quality assurance (IQA) activities are done on a continual basis while external quality assurance (EQA) activities are carried out by external qualified auditors, for an independent review. A quality assurance team is associated with the engagement, which ensures that the quality assurance activities are followed from beginning till completion. The team comprises of individuals with knowledge in QA procedures, our software development methodologies and the technology environment. This team constantly interacts with the engagement team and the Quality Coordinator, including monitoring software quality at every stage of its life cycle.

Engagement Management Review

Engagement status is reviewed every quarter for long duration projects or monthly for shorter duration projects by senior personnel. The objective of this review is to monitor the implementation of the QMS (Quality Management System), and protect client's interests with respect to risks and schedules. The review reports are discussed with the team and all issues tracked to closure.

Internal Quality Audit

Internal quality system audits are conducted every six months for a longer duration project and at least once for a short duration project to evaluate compliance with and the effectiveness of QMS. NCRs (Non Compliance Reports) are discussed with the respective project team and all issues tracked to closure.

The objective of the review Process is to:

• Facilitate error / fault / problem detection at the earliest
• Enhance software quality in terms of its technical attributes
• Ensure conformance to project standards and guidelines.
• Ensure requirements are addressed
• Ensure adequate testing has been completed

A checklist is prepared up-front containing the list of items to be checked during review.

The following steps are taken to ensure software quality and process compliance:

• Definition of procedural and documentation standards
• Inspection of client inputs
• Walk through of procedures and periodic reviews for verifying compliance to standards and guidelines
• Defect logging, tracking and analysis
• Corrections based on causal analysis
• Tracking of review comments/suggestions to closure
• Final inspection checks for delivery packages