Controls must be developed to ensure a quality product. Basically quality assurance defines the objectives of the project and reviews the o...
Controls must be developed to ensure a quality product. Basically quality assurance defines the objectives of the project and reviews the overall activities so that errors are corrected early in the development process. Steps are taken in each phase to ensure that there are no errors in the final software
Quality factors Specification :
Correctness – the extent to which a program meets system specifications and user objectives
Reliability – the degree to which the system performs its intended functions over a time
Efficiency – the amount of computer resources required by a program to perform a function
Usability – the effort required to learn and operate a system
Maintainability – the ease with which program errors are located and corrected.
Testability – the effort required to test a program to ensure its correct performance
Portability – the ease of transporting a program from one hardware configuration to another
Accuracy – the required precision in input editing, computations and output
Error tolerance – error detection and correction versus error avoidance
Expandability – ease of adding or expanding the existing data base
Access control and audit – control of access to the system and the extent to which that access can be audited
Communicativeness – how descriptive or useful the inputs and outputs of the system are
Software requirements Specifications:
The quality assurance goal of this stage is to generate the requirements document that provides the technical specifications for the design and development of the software. This document enhances the system’s quality by improving communication between the system developer and the user and provides the proper information for accurate documentation.
Software Design Specifications:
The software design document defines the overall architecture of the software that provides the functions and features described in the software requirements document. It specifies how it will be done. The document describes the logical subsystems and their respective physical modules. It ensures that all conditions are covered.
Software Testing and Implementation:
The quality assurance goal of the testing phase is to ensure that completeness and accuracy of the system and minimize the retesting process. In the implementation phase, the goal is to provide a logical order for the creation of the modules and in turn the creation of the system.
Maintenance and Support:
This phase provides the necessary software adjustment for the system to continue to comply with the original specifications. The quality assurance goal is to develop a procedure for correcting errors and enhancing software. This procedure improves quality assurance by encouraging complete reporting and logging of problems, ensuring that reported problems are promptly forwarded to the appropriate group for resolution and reducing redundant effort by making known problem reports available to any department that handles complaints.