Software quality program and establishiment cocepts
- 1. SOFTWARE QUALITY PROGRAM K GURU KRISHNA TEJA
- 2. SOFTWARE QUALITY PROGRAM CONCEPTS SQP stands for Software Quality program. Software Quality Program is a framework for building quality into the software and for the actions necessary to verify that the required functionality and performance have been achieved. The Software Quality program is more than "traditional" quality assurance, It goes beyond what is normally performed by "traditional" quality assurance functions and defines the enterprise wide actions necessary for achieving quality in software development, such as:
- 3. Establishing the quality requirements for the software product. Defining, implementing, and evaluating processes and methodologies for the development, operation, and maintenance of the software. Defining and using productivity, process quality, and product quality measures. Defining documentation requirements for the software. Performing evaluations of the software development processes and products. Planning, implementing, and managing a Software Quality Program.
- 4. Objective: The objective of the software quality program is to assure the quality of: Deliverables software and its documentation. The process used to produce deliverable software. Non deliverable software.
- 5. Responsibility for the software quality program The persons conducting the evaluation of a product or activity shall not be the persons who developed the product, performed the activity, or are responsible for the product or activity. This does not prevent members of the development team from participating in these evaluations, The contractor shall assign responsibility for the fulfillment of, and for ensuring compliance with, the software quality program requirements.
- 6. Documentation for the software quality program The software quality program, including procedures, processes, and products, shall be documented in contractor format and shall provide implementing instructions for each of the requirements in standard. The software quality program is subject to review by the contracting agency and may be disapproved by the contracting agency whenever the program does not meet the requirements of the contract.
- 7. Software quality program planning The contractor shall conduct a complete review of the contract to identify and make timely provision for acquiring or developing the resources and skills required for implementing the software quality program. Objective: The objective of the Software Quality Program Plan is to ensure that developing software is evaluated to determine that the desired quality has been achieved. Scope: The scope shall identify the specific ,program or project, state the purpose and provide an introduction to the document. Referenced Documents: This section shall identify all the applicable and referenced documents which are required for the specific program or project.
- 8. Software quality program procedure, tools and records: procedures used by SQP arc as follows: Product reviews (internal, end-of-phase),in-process reviews (peer reviews),management review, process audits (internal),Code walkthrough, Static code analysis (Risk Class 1),FEMA (Risk Class1),etc. Tools to be used in the SQP are: Name, the identification number, version, and development status of the tools necessary to complete the Software Quality Program.
- 9. ESTABLISHMENT OF A SOFTWARE QUALITY PROGRAM Tasks: • Swift and accurate collection of data. • Develop a plan for quality.
- 10. Scope: Planning for and conducting assessments of the quality of the software. Planning for and conducting assessments of the quality of workmanship of all contractors for the software. Planning for and conducting assessments of the quality of all work which will need to be performed for the on-going maintain of the software. All deliverable and non-deliverable items which are to be purchased as the part of the project need to be clearly identified and labeled. Systems boundaries need to be clearly defined.
- 11. Minimal quality Assurance Effort: Concentrate efforts for greatest effect. Most major system failures have been caused by interface problems. Search for risk function. Encourage developers cooperation.
- 12. Quality plan The quality plan helps you schedule all of the tasks needed to make sure that your project needs of your customer. It comprises of two parts: The Quality Assurance Plan lists the independent reviews needed. The Quality Control Plan lists the internal reviews needed to meet your quality targets.
- 13. Purpose: The purpose of this Software Quality Plan is to define the techniques, procedures, and methodologies that will be used to assure timely delivery of the software and that the development system meets the specified requirements within project resources. Barrier: • Top management must understand the direct relationship of improved quality to productivity and from there to lowering of costs and expenses • Top management must understand that it controls the system and subsystems that determine the performance of the people in the organization
- 14. Technical Definitions: The technical definition consists of the following three parts: Requirements: The organization must develop, manufacture and distribute consistently low-cost products and services. The products must be what customers believe they want. Confidence: The products must be supplied at the level of reliability which matches the client's needs. Constant improvement: Constant improvements od all products and all process must be made as an integral part of the corporate culture for the client to continue a supplier as a quality procedure.