Software Quality Assurance (SQA) and Independent Verification and Validation (IV&V) is all about ass
essing and managing risk. Unissant has extensive experience conducting independent Validation and Verification of vendor / client implementations, as well as evaluating and refining client Quality Assurance (QA) processes. In addition, our experts understand that not all gaps and defects are created equal, and that driving the prioritized testing of solutions and issue remediation is as important as the mechanical exercise of conducting manual and automated validations and tests.
A Validation exercise aims to confirm that the solution specifications meet user(s) expectations. Our consultants combine standard quality testing expertise with business process and operations experience, both of which enable them to anticipate and effectively communicate with users and proactively identify gaps or defects with requirements and system specifications.
A Verification exercise aims to confirm that the solution was built according to the specifications. This is where our testing practices come into play.
Unissant consultants are skilled in multitudes of testing services, which include:
-
Build Verification Tests
-
Functionality Testing
-
User Interface Testing
-
Usability Testing
-
System Integration and end-to-end testing
-
Error Handling / Negative Testing
-
System Platform
-
Stress Testing
-
Performance Testing
-
Installation Testing
-
Security / Controls Testing
-
Print Testing
-
Localization Testing
-
Regression testing
Unissant’s Software Quality Assurance practices are embedded throughout a project’s life cycle, aiming to identify risks and issues early in the process in order to allow for more time to prioritize and address those items. Our SQA process follows a default workflow over the course of a typical iteration, release, project, or program in an enterprise environment.
Phased Approach to SQA
We have a documented process for conducting quality assurance. The steps involved are listed below.
Requirements Analysis: Validation begins in the requirements phase of the software development life cycle and involves reviews by stakeholders, implementers, and QA consultants. This also results in the initial version of one of the key artifacts produced by any solutions team: a Requirements Traceability Matrix (RTM).
Design Analysis: During the design phase, testers work with designers and developers in determining what aspects of a design are testable and under what parameters those tests work.
Development Verification: During the development phase, our QA experts confirm that proper unit testing is occurring within the development team and also to identify potentially complex or high-risk areas to concentrate on more deeply during the testing phases.
Test Planning: Test Strategy, Test Plan(s), Test Bed creation. Testing strategy and planning begins at the onset of a project and considers testing environments, scope, test data, priorities, and timing of user involvement.
Test Development: This is where the rubber meets the road and includes Test Procedures, Test Scenarios, Test Cases, and Test Scripts to use in testing software.
Test Execution: Testers execute the software based on the plans and test cases and track, report, and follow through upon resolution of any errors found.
Test Reporting: As test execution progresses, the team generates metrics and reports on test execution progress, defects by phase and cause, and overall risk and quality assessment.
