Software Quality Assurance Methodology
Verification implies that the development of the project is meeting our organizations documented procedures incorporating the industries best practices and ethics. While validation covers the basis of meeting the requirements within the products/services intended environment. Both components provide statistical metrics to deliver an accurate report on the quality of the product and service.
Preparation for Verification & Validation
Peer Review & Analysis
Although not a formal method of Testing, Peer Reviews are internationally recognized within the Industries Best Practices and are a proven method of improving productivity and the overall quality of the Product or Service. Initiated and conducted parallel to the development phase of any product or service and divided into two categories, Structured Walkthroughs and Inspections. The first entailing a formal scheduled inspection piloted by any fellow colleague or senior manager with the purpose of ensuring the code or process meets not only the requirements but encompasses our Organizations guidelines. The latter, Inspections are more of an informal review, though also conducted by a fellow colleague or senior manager they are not scheduled and provide essential feedback on the progress thus far.
- Independent Functional Testing
- Functional & Integration Testing
- System Testing
- Release Testing
- User Acceptance Testing
Independent Functional Testing
Ensures all the Functions/Code Objects are developed according to the Design Specifications and all required Functionality is present.
Functional & Integration Testing
Ensures the Integrated Functionality is per Design Specifications and the required Functionality is present. Additionally checking whether the Product works as a Unit and meets the Acceptance Criteria.
Presumably the most comprehensive testing phase, starting from individual module testing and culminating with overall system functionality testing. Additionally, regression testing is conducted within the phase if and when required.
Release Testing phase is initiated once all system bugs and defects are cleared and the Product is ready to be delivered to its intended environment.
User Acceptance Testing
Also known as End-User Testing, concluding the Testing phases and is conducted within the actual environment of the Product ensuring all the requirements and functionality is met according to the requirements of the Customer.
A sub-process of all the Testing phases, producing detailed test results for Management and all possible Stakeholders.