SQA Methodology

The testing activities covered in SQA Service are fully compliant with the Independent Verification and Validation (IV&V) Process. The Independent Verification and Validation (IV&V) means that a completely independent entity evaluates the work products generated by the team responsible for design and development of a given project.

The set of activities we use in our IV&V process are:

Peer reviews

Peer reviews are verification technique applied to both documentation and source code. The objective of a peer review is to have a second person – person from our team – reading and understanding a document or the source code.

Joint reviews

within joint review we demonstrate to our customers the test we have developed, in order to obtain understanding that we have a clear vision on the software specifics, and to ensure that we have covered the desired functionality with tests.

Unit testing

Unit testing is verification technique that aims to verify the logic, computations/functionality, and error handling of a software unit. The unit developer normally develops unit tests during the development of the unit itself. What we do is extend the developed unit tests with verification techniques uncommon to the majority of developers.

System testing

System testing is a verification technique that aims to verify that a software satisfies its functional and non-functional(such as performance, security, maintainability, failover and recovery etc.) requirements.

Regression testing

Regression testing is a selective retesting of a system or a component, which is aimed to verify that recent modifications have not caused unintended effects, and that the system or component still works as specified. Regression test scenarios emphasize breadth more than depth and all components of the software system are briefly tested.

Acceptance testing

Acceptance testing is both a verification and validation technique that aims to verify that the product satisfies all contractual requirements and to finally validate that the product fulfills its intended use when placed in its production environment. In verification aspect, acceptance testing is very similar to system testing (usually acceptance tests are subset of system tests) only that it is performed by/with the customer in the production environment. In validation aspect, the acceptance testing is very similar to the software joint reviews only that acceptance testing would typically involve the system end-users operating the system in its production environment using the available user documentation.

After the final acceptance test is completed, a certificate for completion of IV&V is issued by SQA team to the customers