1. د. حنان الداقيز http://itse421.wordpress.com خريف 2016
9/28/2016
Software Quality Assurance ضمان جودة البرمجيات ITSE – The components of the SQA
د. حنان الداقيز
خريف 2016

2. Components of SQA system overview
Pre-project components
Software project life cycle components.
Infrastructure components for error prevention and improvements.
Management SQA components.
SQA standards, system certification and assessment components.
Organizing for SQA – the human components

3. Management SQA components.
SQA management components supports the control of software development projects and maintenance services. Control components include: ■ Project progress control (including maintenance contract control) ■ Software quality metrics ■ Software quality costs.

4. Management SQA components. Project progress control
The main objective of project progress control components is to detect the appearance of any undesirable situations performance. Project control activities focus on: ■ Resource usage ■ Schedules ■ Risk management activities ■ The budget.

5. Management SQA components. Software quality metrics
Software measurement - the process of deriving a numeric value for some attribute of a software product or a software process. Comparison of these values to each other allows drawing conclusions about the quality of software products or the process. • Metrics can be either Control Metrics or Predictor Metrics

6. Management SQA components. Software quality cost
The quality costs experienced by software development and application are, according to the extended quality costs model, the costs of control (prevention costs, assessment costs, and managerial preparation and control costs) combined with the costs of failure (internal failure costs, external failure costs, and managerial failure costs) .Management is interested in the total sum of the quality costs.

7. SQA standards, system certification and assessment components.
External tools offer another avenue for achieving the goals of software quality assurance.
Quality management standards
These standards focus on what is required and leave the decision about how to achieve it to the organization. The most familiar examples of this type of standard are:
■ SEI CMM assessment standard
■ ISO 9001 and ISO standards.

8. SQA standards, system certification and assessment components.
Project process standards
Project process standards are professional standards that provide methodological guidelines (dealing with the question of “how”) for the development team. Well-known examples of this type of standards are:
■ IEEE 1012 standard
■ ISO/IEC standard.

9. Organizing for SQA – the human components
The SQA components cannot be applied in an organizational vacuum: they require an organizational base. This base includes the organization’s management, software testing personnel and professionals. All these form the organizational software quality framework or, in our terms, the SQA organizational base. The main objectives of the SQA organizational base are as follows: ■ To develop and support implementation of SQA components. ■ To detect deviations from SQA procedures and methodology. ■ To suggest improvements to SQA components. Although the entire SQA organizational base shares these objectives, each segment of the organizational base concentrates on specific tasks.

10. Software Quality Planning and Control

11. The quality plan
Quality plan is the Quality goals and activities performed to ensure the satisfaction of these goals.
Quality plan should set out the desired software qualities and describe how these are to be assessed. It therefore defines what 'high quality‘ software actually means.

12. Software Quality Plan elements
1. List of quality goals 2. Review activities 3. Software tests 4. Configuration management plans: tools, procedures and data for version releases

13. Quality Plan Elements: List of quality goals
Quality goals: Refers to the developed software quality requirements. The quality goals should reflect the major acceptance criteria indicated in the customer’s requirement document. As such, quality goals serve as measures of the successful achievement of the customer’s quality requirements.

14. Elements of quality plan Example
A software system to serve the help desk operations of an electrical appliance manufacturer is to be developed. The help desk system (HDS) is intended to operate for 100 hours per week. The software quality assurance team was requested to prepare a list of quantitative quality goals appropriate to certain qualitative requirements. The quality goals should reflect the major acceptance criteria indicated in the customer’s requirement document. As such, quality goals serve as measures of the successful achievement of the customer’s quality requirements.

15. Elements of quality plan ( Example )

16. Quality Plan Elements: 2. Review activities
Planned review activities: A list of all SDLC activities and deliverables to be reviewed to ensure that quality meets requirements. Development plan review such as: software requirements specification review, preliminary design review, detailed design review, database design review, test plan review, software test procedure review, operator manual review, installation plan review, training objectives review.

17. Quality Plan Elements: 3. Planned Software tests
Planned software tests : The quality plan should provide a complete list of planned software tests, using the following for each test: ■ The unit, integration or the complete system to be tested ■ The type of testing activities to be carried out. ■ The planned test schedule

18. Quality Plan Elements: 4. Configuration management plans:
The quality plan should specify configuration management tools and procedures, including those change-control procedures meant to be applied throughout the project.

19. Thanks  …. Any questions?