TY  - BOOK
AU  - White, Morio, 
TI  - Metric and model in software quality engineering / 
SN  - 9789348196798 [hardbound] 
PY  - 2025///
CY  - New Delhi, India : 
PB  - Venus Books Publishers & Distributors, 
KW  - Software
KW  - Engineering.
N1  - Includes bibliographical references and index.; Contents: 1. What is software quality? -- 2. Software development process models -- 3. Software quality metrics overview -- 4. Metrics for software maintenance.; Adult
N2  - "Software quality is defined as a field of study and practice that describes the desirable attributes of software products. There are two main approaches to software quality: defect management and quality attributes. A software defect can be regarded as any failure to address end-user requirements. Common defects include missed or misunderstood requirements and errors in design, functional logic, data relationships, process timing, validity checking, and coding errors. The software defect management approach is based on counting and managing defects. Defects are commonly categorized by severity, and the numbers in each category are used for planning. More mature software development organizations use tools, such as defect leakage matrices (for counting the numbers of defects that pass through development phases prior to detection) and control charts, to measure and improve development process capability. This approach to software quality is best exemplified by fixed quality models, such as ISO/IEC 25010:2011. A measurement is a manifestation of the size, quantity, amount, or dimension of a particular attribute of a product or process. Software measurement is a titrate impute of a characteristic of a software product or the software process. In Software Engineering, Software Measurement is done based on some Software Metrics where these software metrics are referred to as the measure of various characteristics of a Software.

A metric is a measurement of the level at which any impute belongs to a system product or process. Software metrics are a quantifiable or countable assessment of the attributes of a software product. Traditionally, a high-quality product is outlined in terms of its fitness of purpose. That is, a high-quality product will specifically be what the users need to try. For code merchandise, the fitness of purpose is typically taken in terms of satisfaction of the wants arranged down within the SRS document. Though "fitness of purpose" could be a satisfactory definition of quality for some merchandise like an automobile, a table fan, a grinding machine, etc. for code merchandise, "fitness of purpose" isn't a completely satisfactory definition of quality. Software Quality shows how good and reliable a product is. To convey an associate degree example, think about functionally correct software. It performs all functions as laid out in the SRS document. But, it has an associate degree virtually unusable program, even though it should be functionally correct, we tend not to think about it to be a high-quality product. Another example is also that of a product that will have everything that the users need but has an associate degree virtually incomprehensible and not maintainable code. Therefore, the normal construct of quality as "fitness of purpose" for code merchandise isn't satisfactory. The modern read of high-quality associates with software many quality factors. Software quality assurance engineers strive to build quality into their products by engaging in activities like requirements analysis, design, coding, testing, and maintenance.

In addition to the excellent balance of theory, techniques, and examples, this book is highly instructive and practical, covering one of the most important topics in software development-quality engineering." --Preface
ER  -