Chapter 17 I.Omaima Al-Matrafi

Slides:



Advertisements
Similar presentations
Software Quality Seung Yang CS 525 Software Engineering II Dr. Sheldon X. Liang.
Advertisements

Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Risk Analysis for Testing Based on Chapter 9 of Text Based on the article “ A Test Manager’s Guide to Risks Analysis and Management” by Rex Black published.
Overview Lesson 10,11 - Software Quality Assurance
Software project management (intro) Quality assurance.
SE 555 Software Requirements & Specification Requirements Quality Attributes.
COMP2002 Lecturecopyright DMU 2001 COMP2002 Quality Basics.
Chapter#7.  Part 1: Quality Management ◦ ƒ Understand the definition of quality and the different methodologies to provide quality ◦ ƒ Know quality management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
Non-functional requirements
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 17 Software Quality
THE PRINCIPLES OF QUALITY MANAGEMENT. DEFINING QUALITY Good Appearance? High Price? The Best? Particular Specification? Not necessarily, but always: Fitness.
Chapter 24 - Quality Management
Fundamentals of ISO.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 17 Software Quality
Software Quality SEII-Lecture 15
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
Chapter 11: Strategic Leadership Chapter 8 Production and operations management.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Software Quality Engineering Chapters 1-3 Overview, Software Quality and Quality Assurance.
1 Software quality - Definition IEEE 1. The degree to which a system, component, or process meets specified requirements. 2. The degree to which a system,
Software Quality Assurance SE Software Quality Assurance What is “quality”?
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
This chapter is extracted from Sommerville’s slides. Text book chapter
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Software Quality : The Elusive Target
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
1 SYSC Software Project Management: Software Quality1 Software Quality & Metrics Software Quality & Metrics Sources: 1.Roger S. Pressman, Software.
Jump to first page (C) 1998, Arun Lakhotia 1 Quality Assurance: Reviews and Walkthroughs Arun Lakhotia University of Southwestern Louisiana Po Box
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
About Quality Pre paired By: Muhammad Azhar. Scope What is Quality Quality Attributes Conclusion on software Quality Quality Concepts Quality Costs.
Quality Management Managing the quality of the software process and products.
Quality Models in Software Engineering Literature: An Analytical and Comparative Study Rafa E. Al-Qutaish, PhD Al Ain University of Science and Technology.
Quality Factors Chapter Three. Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Prepared by: Hussein Alhashimi.  This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
Chapter 13: Software Quality Project Management Afnan Albahli.
SEN 460 Software Quality Assurance
CSE 303 – Software Design and Architecture
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Quality Prepared By: Rooshabh Kothari Assistant Professor T & P Co-ordinator CSE/IT Department 1.
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
SOFTWARE QUALITY ASSURANCE LECTURE # 2 SOFTWARE QUALITY.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
TOTAL QUALITY MANAGEMENT
Software Quality Control and Quality Assurance: Introduction
Software Quality Management
Quality Management chapter 27.
SEVERITY & PRIORITY RELATIONSHIP
Source & Courtesy: Doc. S. Dapkūnas
Software Quality Assurance Software Quality Factor
McCall’s Quality Factors
Software Quality Assurance
Software Testing and Quality Assurance
Fundamentals of ISO.
Software engineering.
مقدمه اي بر مهندسي نيازمنديها
Software Quality Engineering CS- 449
Charakteristiky kvality
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Software Quality Assurance Lecture 3
Chapter 13 Quality Management
الزامات استاندارد 2008 : ISO 9001
Software Quality Assurance 2015
ISO/IEC Systems and software Quality Requirements and Evaluation
Software Verification and Validation
Presentation transcript:

Chapter 17 I.Omaima Al-Matrafi Software Quality Chapter 17 I.Omaima Al-Matrafi

Exercises 1. Briefly explain the five different views of software quality. 2. Briefly explain how one can measure the user’s view of software quality. 3. Briefly explain how one can measure the manufacturer’s view of software quality. 4. Briefly explain McCall’s quality factors and quality criteria. 5. Briefly explain McCall’s categorization of quality factors into three quality criteria. 6. Briefly explain the ISO 9126 quality characteristics. 7. Compare McCall’s quality model with the ISO 9126 quality model. 8. State some difficulties in applying the McCall and ISO 9126 quality models. 9. Briefly explain the ISO 9000:2000 (Fundamental) document for quality assurance. 10. Briefly explain the ISO 9001:2000 (Requirements) document for quality assurance.

1. Briefly explain the five different views of software quality.

The five views of software quality are Transcendental view, SQ is something that can be perceived through experience alone. A good quality object clearly stands out. The user view of quality concerns the extent to which user needs and expectations have been fulfilled. In the manufacturing view, quality is something conforming to requirements. The concept of a process plays a key role in manufacturing. Products must be manufactured by following process standards. In the product view,. The central idea in the product view is internal qualities are thought to affect external qualities. Value based view is how much a customer is willing to pay for a certain level of quality. (tradeoff between quality and cost).

2. Briefly explain how one can measure the user’s view of software quality.

To measure the user view of SQ Identify the external quality attributes of a system. Examples: functionality, Usability and reliabilty. Functionality : can be computed as the ratio of the number of pass test cases to the total number of test cases. Reliability : measured by counting the number of faults or the failure rate of a system. OR apply Gilb’s technique :broken down into component parts until each can be stated in terms of directly measurable attributes

3. Briefly explain how one can measure the manufacturer’s view of software quality.

Manufacturers count two things as a measure of SQ Defect count: The total number of defects detected during development and operation. It is a measure of the quality of the work produced. Rework cost: that is how much it costs to fix the defects. pre-release (development) rework cost: is a measure of development efficiency post-release (oparation) rework cost: is a measure of delivered quality.

4. Briefly explain McCall’s quality factors and quality criteria. A quality factor: represents a behavioral characteristic of a system. McCall’s 11 quality factors are: correctness, reliability, efficiency, integrity, usability, maintainability, testability, flexibility, portability, reusability, and interoperability. A quality Criterion: is an attribute of a quality factor that is related to software development. McCall suggested 23 quality criteria. Ex: modularity  maintainability

5. Briefly explain McCall’s categorization of quality factors into three quality criteria.

McCall’s quality factors relate more to the quality of delivered products, rather than products in development or development processes themselves.

6. Briefly explain the ISO 9126 quality characteristics

7. Compare McCall’s quality model with the ISO 9126 quality model. ISO 9126 model (quality characteristic) McCall model (quality factor) High-level factors/characteristics in both models are: reliability, usability, efficiency, maintainability, and portability. Similarity External characteristic (visible to user) Internal characteristic Differences 1 Q subcharacteristic impact 1 Q characteristic 1 Q attribute can impact several Q factors Testability: is a low level (subcharacteristic) of maintainability Testability : is a high level factor

8. State some difficulties in applying the McCall and ISO 9126 quality models. No consensus about what high level quality factors are important. (McCall 11,ISO 6) No consensus about what is a top level quality characteristic and what is a more concrete quality sub- characteristic (or attribute). Interoperability. An absence of rationale in both the quality models. Hence, it is difficult to follow a prescribed model

9. Briefly explain the ISO 9000:2000 (Fundamental) document for quality assurance. This is based on eight principles. Customer focus Leadership Involvement of people Process approach System approach to management Continual improvement Factual approach to decision making Mutually beneficial supplier relationships

10. Briefly explain the ISO 9001:2000 (Requirements) document for quality assurance. The five major parts of this document are as follows. Part 4. Systemic requirements Part 5. Management requirements Part 6. Resource requirements Part 7. Realization requirements Part 8. Remedial requirements