This document discusses measuring external product attributes of software quality. It covers topics like software quality models, basic software quality metrics, and quality management models. The key points are: - Software quality can be measured internally during development and externally after release based on ISO and IEEE definitions. Common models include McCall, Boehm, and ISO 9126. - Basic metrics include external metrics measured after release, internal metrics measured during development, and quality in use metrics like effectiveness and user satisfaction. - Software quality assurance aims to ensure the process and product meet standards through techniques like inspections, static analysis, and testing. Quality management models like total quality management link quality to customer satisfaction.

1. MEASURING EXTERNAL
PRODUCT ATTRIBUTES : QUALITY
COURSE CODE : COMP9018
COURSE NAME : SOFTWARE METRIC AND QUALITY
PERIODE : SEPTEMBER 2023
DR.IR. YULYANI ARIFIN,S.KOM., MM.
SESSION 08

2. LEARNING OUTCOME
• LO4 : INVESTIGATE THE MEASURING SOFTWARE
RELIABILITY

3. OUTLINE
• Software Quality
• Software Quality Models
• Basic Software Quality Metrics
• Software Quality Assurance (SQA)
• Quality Management Models

4. SOFTWARE QUALITY
• SOFTWARE QUALITY (ISO / IEC TR 9126) :
• The totallity of features and characteristics of a
software product that bear on its ability to satisfy
stated or implied needs
• SOFTWARE QUALITY ( IEEE 610.12 ) :
• Is a set of attributes of a software system and is
defined as :
• The degree to which a system, component, or process
meets specified requirements
• The degree to which a system, component, or process
meets customer or user needs or expectations
• Quality also comprises of the factors leading to the
satisfaction of its requirements
DEFINITION

5. SOFTWARE QUALITY
• The classification software quality by perspective
(Challa et al, 2011)
CLASSIFICATION

6. SOFTWARE QUALITY
• The classification software quality by perspective
(Challa et al, 2011)
CLASSIFICATION

7. SOFTWARE QUALITY
• The classification software quality by perspective
(Challa et al, 2011) (con’t)
CLASSIFICATION

8. SOFTWARE QUALITY
• The classification software quality by perspective
(Challa et al, 2011) (con’t)
CLASSIFICATION

9. SOFTWARE QUALITY
• The classification software quality by perspective
(Challa et al, 2011) (con’t)
CLASSIFICATION

10. SOFTWARE QUALITY
• Software Quality Classification :
• By Observation
• Internal quality ( quality while the product
is being produced , including process and
checks)
• External quality (final product quality)
• By Process
• Design quality
• Implementation quality
• Test quality
• Maintenance quality
CLASSIFICATION

11. SOFTWARE QUALITY MODELS
• TO MAKE THE CONCEPT “QUALITY” OPERATIONAL VIA
REFINEMENT AND MEASUREMENT
• SELECTING SOME ATTRIBUTES (OR FACTORS)
• PLOTTING RELATIONSHIP AMONG ATTRIBUTES (
MANY TO MANY RELATIONSHIP)
• SELECTING SOME CRITERIA (OR INTERMEDIATE AND
PRIMITIVE CONSTRUCTS ) TO REPRESENT THE
ATTRIBUTES
• MAPPING CRITERIA (OR PRIMITIVE CONSTRUCTS) TO
METRICS.
THE PURPOSE

12. SOFTWARE QUALITY MODELS
• CUPRIMDA MODELS ( BY IBM, 1990)
MODELS

13. SOFTWARE QUALITY MODELS
• BOEHM MODELS (1978)
MODELS

14. SOFTWARE QUALITY MODELS
• McCalls MODELS (1977)
MODELS

15. SOFTWARE QUALITY MODELS
• McCalls MODELS (1977)
MODELS

16. SOFTWARE QUALITY MODELS
• Dromey’s MODELS (1995)
MODELS

17. SOFTWARE QUALITY MODELS
• SATC (SOFTWARE
ASSURANCE
TECHNOLOGY
CENTER) MODELS
(1996)
MODELS

18. SOFTWARE QUALITY MODELS
• ISO 9126 MODELS
MODELS

19. BASIC SOFTWARE QUALITY
METRICS
ACCORDING TO PRODUCT QUALITY IN ISO / IEC 9126
CONSISTS OF :
1. QUALITY MODEL
2. EXTERNAL METRICS
3. INTERNAL METRICS
4. QUALITY IN USE METRICS
ISO / IEC TR 9126

20. BASIC SOFTWARE QUALITY
METRICS
QUALITY MODEL : ISO 9126

21. BASIC SOFTWARE QUALITY
METRICS
QUALITY MODEL : ISO 9126

22. BASIC SOFTWARE QUALITY
METRICS
• AN EXTERNAL METRICS IS A QUANTITATIVE SCALE
AND MEASUREMENT METHOD WHICH CAN BE USED
FOR MEASURING AN ATTRIBUTE OR
CHARACTERISTICS OF A SOFTWARE PRODUCT ,
DERIVED FROM THE BEHAVIOURS OF THE SYSTEM OF
WHICH IT IS A PART.
• EXTERNAL METRICS ARE APPLICABLE TO AN
EXECUTABLE SOFTWARE PRODUCT DURING TESTING
OR OPERATING IN LATER STAGE OF DEVELOPMENT
AND AFTER ENTERING TO OPERATION PROCESS.
EXTERNAL METRICS

23. BASIC SOFTWARE QUALITY
METRICS
• AN INTERNAL METRICS IS A QUANTITATIVE SCALE
AND MEASUREMENT METHODS, WHICH CAN BE
USED FOR MEASURING AN ATTRIBUTE OR
CHARACTERISTICS OF A SOFTWARE PRODUCT ,
DERIVED FROM THE PRODUCT IT SELF , EITHER
DIRECT OR INDIRECT.
• INTERNAL METRICS ARE APPLICABLE TO A NON-
EXECUTABLE SOFTWARE PRODUCT DURING
DESIGNING AND CODING IN EARLY STAGE OF
DEVELOPMENT PROCESS
INTERNAL METRICS

24. BASIC SOFTWARE QUALITY
METRICS
• EFFECTIVENESS
• THE CAPABILITY OF THE SOFTWARE PRODUCT
TO ENABLE USERS TO ACHIEVE SPECIFIC GOALS
WITH ACCURACY AND COMPLETENESS IN A
SPECIFIED CONTEXT OF USE.
• PRODUCTIVITY
• THE CAPABILITY OF THE SOFTWARE PRODUCT
TO ENABLE USERS TO EXPEND APPROPRIATE
AMOUNTS OF RESOURCES IN RELATION TO THE
EFFECTIVENESS ACHIEVED IN A SPECIFIED
CONTEXT OF USE
QUALITY IN USE METRICS

25. BASIC SOFTWARE QUALITY
METRICS
• SAFETY
• THE CAPABILITY OF THE SOFTWARE PRODUCT
TO ACHIEVE ACCEPTABLE LEVELS OF RISK OF
HARM PEOPLE , BUSINESS, SOFTWARE ,
PROPERTY OR THE ENVIRONMENTS IN A
SPECIFIED CONTEXT OF USE
• SATISFACTION
• THE CAPABILITY OF THE SOFTWARE PRODUCT
TO SATISFY USERS IN A SPECIFIED CONTEXT OF
USE.
QUALITY IN USE METRICS

26. BASIC SOFTWARE QUALITY
METRICS
QUALITY IN USE METRICS

27. BASIC SOFTWARE QUALITY
METRICS
ISO 9126 : FUTURE
• A NEW SERIES OF STANDARDS THAT WILL
REPLACE ISO 9126 :
• SOFTWARE PRODUCT QUALITY REQUIREMENTS
AND EVALUATIONS (SQuaRE - ISO 25000)

28. SOFTWARE QUALITY
ASSURANCE
• DEVELOPING DEPENDABLE SOFTWARE USUALLY
REQUIRES :
1. DEVISING SOFTWARE QUALITY ASSURANCE (
SQA)
2. ESTABLISHING SOFTWARE RELIABILITY
ENGINEERING (SRE) PROCESS
DEPENDABLE SOFTWARE

29. SOFTWARE QUALITY
ASSURANCE
• ACCORDING TO ISO 12207 :
• ALL THE PLANNED AND SYSTEMATICS
ACTIVITIES IMPLEMENTED WITHIN THE
QUALITY SYSTEM AND DEMONSTRATED AS
NEEDED, TO PROVIDE ADEQUATE
CONFIDENCE THAT AN ENTITY WITH FULFILL
REQUIREMENTS FOR QUALITY
QUALITY ASSURANCE DEFINITION

30. SOFTWARE QUALITY
ASSURANCE
• SOFTWARE QUALITY ASSURANCE (SQA) IS :
• A PLANNED AND SYSTEMATICS APPROACH
TO ENSURE THAT BOTH SOFTWARE PROCESS
AND SOFTWARE PRODUCT CONFORM TO
THE ESTABLISHED STANDARDS , PROCESSES,
AND PROCEDURES.
• THE GOALS OF SQA ARE TO IMPROVE SOFTWARE
QUALITY BY MONITORING BOTH SOFTWARE AND
THE DEVELOPMENT PROCESS TO ENSURE FULL
COMPLIANCE WITH THE ESTABLISHED
STANDARDS AND PROCEDURES.
DEFINITION

31. SOFTWARE QUALITY
ASSURANCE
• CONSTRUCTIVE QA :
• CREATION OF SOFTWARE QUALITY
• AVOIDANCE OF QUALITY-RELEVANT RISKS
• DESIGN OF SOFTWARE SUCH THAT IT BECOMES
TESTABLE ( BUILT IN TESTING)
• ANALYTICAL QA :
• CHECKING / ASSESSING SOFTWARE QUALITY (
INSPECTION AND TESTS)
• MITIGATIONS OF QUALITY-RELEVANT RISKS
• CORRECTION OF SOFTWARE AS SOON AS
POSSIBLE
QUALITY ASSURANCES TYPES :

32. SOFTWARE QUALITY
ASSURANCE
HOW TO DO CONSTRUCTIVE QA ?
• SELECTION AND IMPLEMENTATION OF SOFTWARE
PROCESS MODELS ( INCLUDING THE PLANNING OF ALL QA
RELEVANT ACTIVITIES
• APPLICATION OF SOFTWARE ENGINEERING PRINCIPLES IN
ALL DEVELOPMENT STEPS : ABSTRACTION,
HIERARCHISATION, MODULARIZATION, FORMALIZATION,
AUTOMATIZATION.
• REQUIREMENTS : EXPLICIT DOCUMENTATIONS OF
REQUIREMENTS ( USE CASE)
• DESIGN : LOW COUPLING , HIGH COHESIONS
• IMPLEMENTATIONS : LOW STRUCTURAL COMPLEXITY
, PROGRAMMING GUIDELINES.
CONSTRUCTIVE QUALITY ASSURANCES

33. SOFTWARE QUALITY
ASSURANCE
HOW TO DO ANALITICS QA ?
• STATIC ANALYSES ( COMPLEXITY , NESTING
LEVELS, STRUCTUREDNESS, ETC)
• VERIFICATION ( INSPECTION, TEST (
DEVELOPMENT PERSPECTIVE)
• VALIDATIONS ( TESTS ( USER PERSPECTIVE)
ANALYTICS QUALITY ASSURANCES

34. QUALITY MANAGEMENT
MODELS
• TQM IS A STYLE OF
MANAGEMENT
AIMING AT ACHIVING
“LONG TERM”
SUCCESS BY LINKING
QUALITY WITH
CUSTOMER
SATISFACTION.
TOTAL QUALITY MANAGEMENT ( TQM)

35. QUALITY MANAGEMENT
MODELS
• PRACTICE OF TQM :
1. FOCUS ON QUALITY
2. COOPERATE WITH CUSTOMERS
3. CONTINUOSLY IMPROVE
DEVELOPMENT PROCESS
4. ENCOURAGE CONSTRUCTIVE CRITICS
AND EMPOWER EMPLOYEES
5. USE THE PROBLEM SOLVING /
PROBLEM PREVENTION CYCLE
6. USE MEASUREMENT TO BACK
DECISIONS
TOTAL QUALITY MANAGEMENT ( TQM)

36. ASSIGNMENT
• SOFTWARE QUALITY MODEL HAS SOME
MODEL LIKE MCCALL,, BOEHM, ISO 1926 ETC.
• CHOOSE WHICH ONE SOFTWARE QUALITY
MODEL THAT SUITABLE FOR YOUR
DISSERTATION TOPIC OR FOR YOUR
INDUSTRY
• WRITE YOUR OPINION WITH REASONS
• SUPPORTING PAPER :
• IMPORTANCE OF SOFTWARE QUALITY
MODELS IN SOFTWARE ENGINEERING (
RAMULU & MURHTYR,2018)
ANALYSE SOFTWARE QUALITY MODEL

37. REFERENCES
Challa, Jagat & Paul, Arindam & Dada, Yogesh & Nerella, Venkatesh &
Srivastava, Dr. Praveen & Singh, Ajit Pratap. (2011). Integrated
Software Quality Evaluation: A Fuzzy Multi-Criteria Approach. Journal
of Information Processing Systems. 77473. 10.3745/JIPS.2011.7.3.473.