McCall proposed a model in 1977 to measure software quality based on quality factors related to software requirements. The model breaks quality factors into three main categories: product operation factors, product revision factors, and product transition factors. Alternative models by Evans/Marciniak and Deutsch/Willis also use these factors to evaluate software quality.

1. Prepared by Software Quality
Faridl Mughoffar Factors by McCall
5210100117

2. Outline
• SQ Factors Model by McCall
• Breakdown each SQ Factors
Model
• Alternative models of software
quality factors

3. Background
The process of defining the requirements or
needs of the software is a very important part
in the development of software. But its very
difficult to measure the software quality based
n the requirement.

4. Background (Cont.)
At 1977, Mc Call proposed a model of quality
factor to measure software quality. It is the
quality factor of the classified software
requirements or software needs.

5. SQ Factors Model
Software Quality Factors
Product operation factors
Product revision factors
Product transition factors

6. Breakdown SQ Factors

7. Explanations
Product Operation Factors
• Correctness In this passage, there are
factors which are factors
• Reliability related to the requirements
or needs that directly affect
• Efficiency the operation of the
• Integrity software.
• Usability

8. Explanations (Cont.)
Product Operation Factors
Correctness Reliability Efficiency Integrity Usability
• For this factor, • This factor • This factor • Related to the • The need for
required relates to the relates to the security of the this factor
precision, failure to need to run system relates to the
accuracy, provide the system software. Like scope of staff
completeness, services. As hardware how to avoid resources
Recency, and the failure rate resources in illegal access needed to
availability of of the software order to meet and manage train new
information at system the the needs of the access users to use
the output of maximum users rights of each the system
the system allowed user type
software.

9. Explanations (Cont.)
Product Revision Factors
Deals with software
• Maintainability maintenance activities:
• Flexibility corrective maintenance,
• Testability adaptive maintenance,
perfect maintenance.

10. Explanations (Cont.)
Product Revision Factors
This factor
Maintainability
determines
the effort Determine
Flexibility
required to the ability and
identify the effort required
causes of Related to the
to support
Testability
ability of the
the failure of adaptive system to help
software, maintenance the tester to
how to activities that provide special
cope, and include a features to see
how to flexible the results of the
ensure it is requirement tests conducted,
correct. such as log files,
and so on

11. Explanations (Cont.)
Product Transitions Factors
• Portability Refers to adaptation to
other environments and
• Reusability interaction with other
• Interoperability systems.

12. Explanations (Cont.)
Product Transitions Factors
• Related to the ability of the
software system to adapt to
Portability different environments, such
as different hardware,
different operating systems.
• This factor relates to the
ability of the existing
Reusability modules in the software to
be used again in the next
software development
• Focus on how to create an
interface / view that is
Interoperability consistent with the system
software or hardware
related companies

13. Mc Call Tree Models
Quality Software
is supported by 3
main root that
explained before
and the branch
main root. Look at
the picture

14. Mc Call Factor Model
and Alternate Model
Alternative factor models
No. Software quality McCall’s classic Evans and Deutsch and
factor model Marciniak model Willis model
1 Correctness + + +
2 Reliability + + +
3 Efficiency + + +
4 Integrity + + +
5 Usability + + +
6 Maintainability + + +
7 Flexibility + + +
8 Testability +
9 Portability + + +
10 Reusability + + +
11 Interoperability + + +
12 Verifiability + +
13 Expandability + +
14 Safety +
15 Manageability +
16 Survivability +

15. Addition Factors
Verifiability
• Defines design and programming features.
• Refer to modularity and simplicity, and
adherence to documentation and
programming guidelines.
• Improves the design reviews and software
tests.

16. Addition Factors (Cont.)
Expandability
• Refers to future efforts that will be needed
to serve larger populations.
Safety
• To eliminate conditions hazardous to
operations of equipment as a result of
errors, including providing alarm signals.

17. Addition Factors (Cont.)
Manageability
• Refers to the administrative tools that
supports software modification, such as
CM.