manu/mldr-zoomed-100char-total-queries-documents

chunk_id stringlengths 3 9	chunk stringlengths 1 100
9839_67	CISQ reports on the cost of poor quality estimates an impact of: $2.08 trillion in 2020
9839_68	$2.84 trillion in 2018
9839_69	IBM's Cost of a Data Breach Report 2020 estimates that the average global costs of a data breach:
9839_70	$3.86 million
9839_71	Definitions
9839_72	ISO
9839_73	Software quality is "capability of a software product to conform to requirements." while for others
9839_74	it can be synonymous with customer- or value-creation or even defect level.
9839_75	ASQ
9839_76	ASQ uses the following definition: Software quality describes the desirable attributes of software
9839_77	products. There are two main approaches exist: defect management and quality attributes.
9839_78	NIST Software Assurance (SA) covers both the property and the process to achieve it:
9839_79	[Justifiable] confidence that software is free from vulnerabilities, either intentionally designed
9839_80	into the software or accidentally inserted at any time during its life cycle and that the software
9839_81	functions in the intended manner
9839_82	The planned and systematic set of activities that ensure that software life cycle processes and
9839_83	products conform to requirements, standards, and procedures
9839_84	PMI
9839_85	The Project Management Institute's PMBOK Guide "Software Extension" defines not "Software quality"
9839_86	itself, but Software Quality Assurance (SQA) as "a continuous process that audits other software
9839_87	processes to ensure that those processes are being followed (includes for example a software
9839_88	quality management plan)." whereas Software Quality Control (SCQ) means "taking care of applying
9839_89	methods, tools, techniques to ensure satisfaction of the work products towards quality requirements
9839_90	for a software under development or modification."
9839_91	Other general and historic
9839_92	The first definition of quality history remembers is from Shewhart in the beginning of 20th
9839_93	century: "There are two common aspects of quality: one of them has to do with the consideration of
9839_94	the quality of a thing as an objective reality independent of the existence of man. The other has
9839_95	to do with what we think, feel or sense as a result of the objective reality. In other words, there
9839_96	is a subjective side of quality."
9839_97	Kitchenham and Pfleeger, further reporting the teachings of David Garvin, identify five different
9839_98	perspectives on quality:
9839_99	The transcendental perspective deals with the metaphysical aspect of quality. In this view of
9839_100	quality, it is "something toward which we strive as an ideal, but may never implement completely".
9839_101	It can hardly be defined, but is similar to what a federal judge once commented about obscenity: "I
9839_102	know it when I see it".
9839_103	The user perspective is concerned with the appropriateness of the product for a given context of
9839_104	use. Whereas the transcendental view is ethereal, the user view is more concrete, grounded in the
9839_105	product characteristics that meet user's needs.
9839_106	The manufacturing perspective represents quality as conformance to requirements. This aspect of
9839_107	quality is stressed by standards such as ISO 9001, which defines quality as "the degree to which a
9839_108	set of inherent characteristics fulfills requirements" (ISO/IEC 9001).
9839_109	The product perspective implies that quality can be appreciated by measuring the inherent
9839_110	characteristics of the product.
9839_111	The final perspective of quality is value-based. This perspective recognizes that the different
9839_112	perspectives of quality may have different importance, or value, to various stakeholders.
9839_113	Tom DeMarco has proposed that "a product's quality is a function of how much it changes the world
9839_114	for the better." This can be interpreted as meaning that functional quality and user satisfaction
9839_115	are more important than structural quality in determining software quality.
9839_116	Another definition, coined by Gerald Weinberg in Quality Software Management: Systems Thinking, is
9839_117	"Quality is value to some person." This definition stresses that quality is inherently
9839_118	subjective—different people will experience the quality of the same software differently. One
9839_119	strength of this definition is the questions it invites software teams to consider, such as "Who
9839_120	are the people we want to value our software?" and "What will be valuable to them?".
9839_121	Other meanings and controversies
9839_122	One of the challenges in defining quality is that "everyone feels they understand it" and other
9839_123	definitions of software quality could be based on extending the various descriptions of the concept
9839_124	of quality used in business.
9839_125	Software quality also often gets mixed-up with Quality Assurance or Problem Resolution Management
9839_126	or Quality Control or DevOps. It does over-lap with before mentioned areas (see also PMI
9839_127	definitions), but is distinctive as it does not solely focus on testing but also on processes,
9839_128	management, improvements, assessments, etc.
9839_129	Measurement
9839_130	Although the concepts presented in this section are applicable to both structural and functional
9839_131	software quality, measurement of the latter is essentially performed through testing [see main
9839_132	article: Software testing]. However, testing isn't enough: According to a study, individual
9839_133	programmers are less than 50% efficient at finding bugs in their own software. And most forms of
9839_134	testing are only 35% efficient. This makes it difficult to determine [software] quality.
9839_135	Introduction
9839_136	Software quality measurement is about quantifying to what extent a system or software possesses
9839_137	desirable characteristics. This can be performed through qualitative or quantitative means or a mix
9839_138	of both. In both cases, for each desirable characteristic, there are a set of measurable attributes
9839_139	the existence of which in a piece of software or system tend to be correlated and associated with
9839_140	this characteristic. For example, an attribute associated with portability is the number of
9839_141	target-dependent statements in a program. More precisely, using the Quality Function Deployment
9839_142	approach, these measurable attributes are the "hows" that need to be enforced to enable the "whats"
9839_143	in the Software Quality definition above.
9839_144	The structure, classification and terminology of attributes and metrics applicable to software
9839_145	quality management have been derived or extracted from the ISO 9126-3 and the subsequent ISO/IEC
9839_146	25000:2005 quality model. The main focus is on internal structural quality. Subcategories have been
9839_147	created to handle specific areas like business application architecture and technical
9839_148	characteristics such as data access and manipulation or the notion of transactions.
9839_149	The dependence tree between software quality characteristics and their measurable attributes is
9839_150	represented in the diagram on the right, where each of the 5 characteristics that matter for the
9839_151	user (right) or owner of the business system depends on measurable attributes (left):
9839_152	Application Architecture Practices Coding Practices Application Complexity Documentation
9839_153	Portability Technical and Functional Volume
9839_154	Correlations between programming errors and production defects unveil that basic code errors
9839_155	account for 92 percent of the total errors in the source code. These numerous code-level issues
9839_156	eventually count for only 10 percent of the defects in production. Bad software engineering
9839_157	practices at the architecture levels account for only 8 percent of total defects, but consume over
9839_158	half the effort spent on fixing problems, and lead to 90 percent of the serious reliability,
9839_159	security, and efficiency issues in production.
9839_160	Code-based analysis
9839_161	Many of the existing software measures count structural elements of the application that result
9839_162	from parsing the source code for such individual instructions tokens control structures
9839_163	(Complexity), and objects.
9839_164	Software quality measurement is about quantifying to what extent a system or software rates along
9839_165	these dimensions. The analysis can be performed using a qualitative or quantitative approach or a
9839_166	mix of both to provide an aggregate view [using for example weighted average(s) that reflect

9839_67

CISQ reports on the cost of poor quality estimates an impact of: $2.08 trillion in 2020

9839_68

$2.84 trillion in 2018

9839_69

IBM's Cost of a Data Breach Report 2020 estimates that the average global costs of a data breach:

9839_70

$3.86 million

9839_71

Definitions

9839_72

ISO

9839_73

Software quality is "capability of a software product to conform to requirements." while for others

9839_74

it can be synonymous with customer- or value-creation or even defect level.

9839_75

ASQ

9839_76

ASQ uses the following definition: Software quality describes the desirable attributes of software

9839_77

products. There are two main approaches exist: defect management and quality attributes.

9839_78

NIST Software Assurance (SA) covers both the property and the process to achieve it:

9839_79

[Justifiable] confidence that software is free from vulnerabilities, either intentionally designed

9839_80

into the software or accidentally inserted at any time during its life cycle and that the software

9839_81

functions in the intended manner

9839_82

The planned and systematic set of activities that ensure that software life cycle processes and

9839_83

products conform to requirements, standards, and procedures

9839_84

PMI

9839_85

The Project Management Institute's PMBOK Guide "Software Extension" defines not "Software quality"

9839_86

itself, but Software Quality Assurance (SQA) as "a continuous process that audits other software

9839_87

processes to ensure that those processes are being followed (includes for example a software

9839_88

quality management plan)." whereas Software Quality Control (SCQ) means "taking care of applying

9839_89

methods, tools, techniques to ensure satisfaction of the work products towards quality requirements

9839_90

for a software under development or modification."

9839_91

Other general and historic

9839_92

The first definition of quality history remembers is from Shewhart in the beginning of 20th

9839_93

century: "There are two common aspects of quality: one of them has to do with the consideration of

9839_94

the quality of a thing as an objective reality independent of the existence of man. The other has

9839_95

to do with what we think, feel or sense as a result of the objective reality. In other words, there

9839_96

is a subjective side of quality."

9839_97

Kitchenham and Pfleeger, further reporting the teachings of David Garvin, identify five different

9839_98

perspectives on quality:

9839_99

The transcendental perspective deals with the metaphysical aspect of quality. In this view of

9839_100

quality, it is "something toward which we strive as an ideal, but may never implement completely".

9839_101

It can hardly be defined, but is similar to what a federal judge once commented about obscenity: "I

9839_102

know it when I see it".

9839_103

The user perspective is concerned with the appropriateness of the product for a given context of

9839_104

use. Whereas the transcendental view is ethereal, the user view is more concrete, grounded in the

9839_105

product characteristics that meet user's needs.

9839_106

The manufacturing perspective represents quality as conformance to requirements. This aspect of

9839_107

quality is stressed by standards such as ISO 9001, which defines quality as "the degree to which a

9839_108

set of inherent characteristics fulfills requirements" (ISO/IEC 9001).

9839_109

The product perspective implies that quality can be appreciated by measuring the inherent

9839_110

characteristics of the product.

9839_111

The final perspective of quality is value-based. This perspective recognizes that the different

9839_112

perspectives of quality may have different importance, or value, to various stakeholders.

9839_113

Tom DeMarco has proposed that "a product's quality is a function of how much it changes the world

9839_114

for the better." This can be interpreted as meaning that functional quality and user satisfaction

9839_115

are more important than structural quality in determining software quality.

9839_116

Another definition, coined by Gerald Weinberg in Quality Software Management: Systems Thinking, is

9839_117

"Quality is value to some person." This definition stresses that quality is inherently

9839_118

subjective—different people will experience the quality of the same software differently. One

9839_119

strength of this definition is the questions it invites software teams to consider, such as "Who

9839_120

are the people we want to value our software?" and "What will be valuable to them?".

9839_121

Other meanings and controversies

9839_122

One of the challenges in defining quality is that "everyone feels they understand it" and other

9839_123

definitions of software quality could be based on extending the various descriptions of the concept

9839_124

of quality used in business.

9839_125

Software quality also often gets mixed-up with Quality Assurance or Problem Resolution Management

9839_126

or Quality Control or DevOps. It does over-lap with before mentioned areas (see also PMI

9839_127

definitions), but is distinctive as it does not solely focus on testing but also on processes,

9839_128

management, improvements, assessments, etc.

9839_129

Measurement

9839_130

Although the concepts presented in this section are applicable to both structural and functional

9839_131

software quality, measurement of the latter is essentially performed through testing [see main

9839_132

article: Software testing]. However, testing isn't enough: According to a study, individual

9839_133

programmers are less than 50% efficient at finding bugs in their own software. And most forms of

9839_134

testing are only 35% efficient. This makes it difficult to determine [software] quality.

9839_135

Introduction

9839_136

Software quality measurement is about quantifying to what extent a system or software possesses

9839_137

desirable characteristics. This can be performed through qualitative or quantitative means or a mix

9839_138

of both. In both cases, for each desirable characteristic, there are a set of measurable attributes

9839_139

the existence of which in a piece of software or system tend to be correlated and associated with

9839_140

this characteristic. For example, an attribute associated with portability is the number of

9839_141

target-dependent statements in a program. More precisely, using the Quality Function Deployment

9839_142

approach, these measurable attributes are the "hows" that need to be enforced to enable the "whats"

9839_143

in the Software Quality definition above.

9839_144

The structure, classification and terminology of attributes and metrics applicable to software

9839_145

quality management have been derived or extracted from the ISO 9126-3 and the subsequent ISO/IEC

9839_146

25000:2005 quality model. The main focus is on internal structural quality. Subcategories have been

9839_147

created to handle specific areas like business application architecture and technical

9839_148

characteristics such as data access and manipulation or the notion of transactions.

9839_149

The dependence tree between software quality characteristics and their measurable attributes is

9839_150

represented in the diagram on the right, where each of the 5 characteristics that matter for the

9839_151

user (right) or owner of the business system depends on measurable attributes (left):

9839_152

Application Architecture Practices Coding Practices Application Complexity Documentation

9839_153

Portability Technical and Functional Volume

9839_154

Correlations between programming errors and production defects unveil that basic code errors

9839_155

account for 92 percent of the total errors in the source code. These numerous code-level issues

9839_156

eventually count for only 10 percent of the defects in production. Bad software engineering

9839_157

practices at the architecture levels account for only 8 percent of total defects, but consume over

9839_158

half the effort spent on fixing problems, and lead to 90 percent of the serious reliability,

9839_159

security, and efficiency issues in production.

9839_160

Code-based analysis

9839_161

Many of the existing software measures count structural elements of the application that result

9839_162

from parsing the source code for such individual instructions tokens control structures

9839_163

(Complexity), and objects.

9839_164

Software quality measurement is about quantifying to what extent a system or software rates along

9839_165

these dimensions. The analysis can be performed using a qualitative or quantitative approach or a

9839_166

mix of both to provide an aggregate view [using for example weighted average(s) that reflect