Quality Management

 

PaxoSoft has always taken an uncompromising position in respect to quality. PaxoSoft’s Quality Management is a complex set of engineering and managerial activities that ensures the high quality of delivered software through the entire workflow.

 

PaxoSoft Quality Management Tasks and Objectives:

Elaboration and implementation of procedures and regulations for software development process based on the industry best practices and standards Product life-cycle monitoring to ensure compliance with established processes and guidelines Product quality verification and validation to ensure its correspondence with the client needs and expectations Establishment of an effective collaboration of all production participants

 

Independent QA Phase


PaxoSoft’s QA department is an independent structural subdivision. Our QA team consists of skilled QA engineers and experienced testers that are involved into the projects on a dedicated or as-needed basis. QA engineers’ allocation depends on the project size and complexity. If it is required they can be easily switched from one project to another. Such flexibility let us optimize project efforts and correspondingly the overall project budget. The QA team is not accountable to the project manager allowing them to provide the best input to the development process.

 

Key Processes:

  • Full-cycle QA Testing
  • Document and Code Reviews
  • Defect Tracking
  • Configuration Management Process
  • Monitoring Risk Management

 

Simultaneous Development and QA


PaxoSoft conducts quality assurance procedures throughout the full software lifecycle. QA team members are involved at all project iterations. Lead QA specialist is allocated from the initial stage of the project and involved into initial business analysis and requirements specification. This simultaneous interaction of the development and QA teams ensures a better understanding of the project scope and the client’s business objectives. Typical QA lifecycle includes the following phases:

Initiation and Planning

The responsible QA person studies the project specification, starts test plan elaboration and plan assignment of the QA team members for specific tasks

 

First Review

Initial testing of first development deliverables. The project test plan and test items refining (if necessary)

 

Iteration Audits

On-going testing of intermediate iterations builds

 

Final Verification and Validation

The final product thorough testing to ensure the final quality and readiness for deployment

 

QA process may include different test types to ensure increased QA depth:

  • Functional and Regression Testing
  • GUI and Usability Testing
  • Accessibility Testing
  • Compatibility Testing
  • Performance Testing
  • Installation/Configuration Testing
  • System/Integration Testing
  • Security Testing Internationalization/Localization Testing
  • User Acceptance Testing (UAT)

 

What Is High Quality?

We define software quality as to the measure of how well the software is designed (quality of design), and how well the software conforms to that design (quality of conformance).

We designed our quality assuance at each of the critical points that ensure the high quality software.