Quality Assurance is defined as the auditing and reporting procedures used to provide the stakeholders with data needed to make well-informed decisions.
It is the Degree to which a system meets specified requirements and customer expectations. It is also monitoring the processes and products throughout the SDLC.
Below are the Quality assurance criteria against which the software would be evaluated against:
Quality control is a set of methods used by organizations to achieve quality parameters or quality goals and continually improve the organization's ability to ensure that a software product will meet quality goals.
The three class parameters that control software quality are:
The total quality control process consists of:
Requirements-based testing is a testing approach in which test cases, conditions and data are derived from requirements. It includes functional tests and also non-functional attributes such as performance, reliability or usability.
Release Candidate (RC) is the build released internally to check if any critical problems have gone undetected into the code during the previous development period. Release candidates are NOT for production deployment, but they are for testing purposes only. However, in most of the cases, there are no differences between the final build and the last release candidate.
Software reliability testing a testing technique that relates to testing a software's ability to function given environmental conditions consistently that helps uncover issues in the software design and functionality.
Dependent elements of reliability Testing:
Key Parameters that are measured as part of reliability are given below:
The requirements are the high-level descriptions about a particular system services, constraints or to a detailed specification that are generated during the requirements gathering process.
User Requirements - It is a detailed description in natural language along with diagrams of the services the system provides and its operational constraints. It is usually developed by end users.
System requirements - It is a structured document detailing the descriptions of the system's functions, services and operational constraints.
Functional Requirements - It describes the services of the system, how the system should react to particular inputs and how the system should behave in definite situations.
Non-functional Requirements - It describes the attributes of the system.
Domain Requirements - Requirements that arises from the domain of the application and that reflect characteristics of that domain. It can be either functional or non-functional specifications.