CPIS 357 Software Quality & Testing

1. CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010

2. Lecture2:Quality Assurance Framework • Lecture Objectives • Quality Definition • Prevention versus Detection • Verification versus Validation • Software Quality Assurance (SQA) Definition • Components of Quality Assurance • Software Quality Assurance Plan Definition • Steps to Develop and Implement Software Quality Assurance Plan

3. Quality Definition • Quality is the essential character of something, an inherent or distinguishing character, degree or grade of excellence. • There are two meanings of quality: • 1- Producer Points • 2- Customer Points • Requirement specification is a specification for a software product, program or application that performs function in a specific environment organized by feature.

4. Quality Definition • Some of Confusing Ideas about Quality Commitment • Quality requires a commitment from top management. • Many individuals believe that defect-free product and services are impossible. • Quality demands requirement specifications in sufficient detail which many organization may not capable or willing to expend the effort to produce specification at the level required. • Technical person often believe that standard stifle their creativity. • Quality is frequently associated with cost.

5. Prevention versus Detection • The aim of the quality is to prevent quality defect or deficiencies in the first place and to make the product assessable by quality assurance measures. • The total cost of effective quality management is the sum of four components: • 1- Prevention • 2- inspection • 3- Internal Failure • 4- External Failure • The greatest payback is with prevention. Increasing the emphasis on prevention costs reduces the number of defects that go to the customer undetected, improved product quality, and reduces the cost of production and maintenance.

6. Verification versus Validation • Verification • The product meet the requirement specified during previous activities • Carried out correctly throughout the development life cycle. • * Building the product correctly * • Validation • Confirm that the system meets the customers requirements at the end of • the life cycle . Proof that the product meet the expectation of the users • And ensures that the executable system perform as specified. • Building correct Product* • It is good to combine between verification and validation through development cycle start from the requirement to coding stage. • Verification process produce product with less number of error

7. Software Quality Assurance • Software Quality Assurance (SQA) is the systematic activities providing Evidence of the fitness for use of the total software product, and it is achieved through the use of guidelines for quality control to ensure the integrity and long life of software.

8. Software Quality Assurance • Software Quality Assurance (SQA) is a strategy for a risk management. • Examples of Poor Software Quality • Delivered software frequently fails. • Consequences of system failure are unacceptable, from financial to • life threatening scenario. • System are often not available for their future purpose. • System enhancement are often very costly. • Costs of detecting and removing defects are too much.

9. Component of Quality Assurance Software Configuration Management Software Testing Quality Control

10. Components of Quality Assurance • 1- Software Testing (Verification/Validation) • Is a popular risk management strategy and it is used to verify that the functional requirements were met. • The verification effort takes less time and is less complex when conducted throughout the development process • 2- Quality Control • Is defined as a processes and methods used to monitor work and observe whether requirements are met. • Focuses on reviews and removal of defects before shipment of the products. • Responsible of the of the group who build the product. • Designed to detect and correct defects in all program life cycle.

11. Components of Quality Assurance • 3- Software Configuration Management • Is concerned with labeling, tracking, and controlling changes in the software elements of a system. It controls the evolution of a software system by managing versions of its software components and their relationships. • Elements of Software Configuration Management Version Control Component Identification Configuration Building Change Control Software Testing Quality Control

12. Software Quality Assurance Plane • Is an outline of quality measures to ensure quality levels within a software development effort. • Steps to Develop and Implement a SQA Plan • Step1: Document the Plan • Step2:Obtain Management Acceptance • Step3: Obtain Development Acceptance • Step4: Plan for Implementation of the SQA Plan • Step5: Execute the SQA Plan