With the progress of society and the development of scientific and technological information, people's lives have become inseparable Website production The economic value of software quality is not well covered in the existing software engineering literature. There are many reasons for this. The main reason is that the software quality measurement methods in the field of software engineering are quite poor. Many cost factors such as unpaid overtime are often ignored. In addition, there are frequent sulfur omissions and omissions in software cost data, such as the omission of project management costs, and the omission of part-time experts (such as technical document writers). In fact, only the cost of coding work has reasonably good data available. Any other work, such as data on requirements, design, review, testing, quality assurance, project office and documentation, is often underreported or simply ignored. 
The software engineering literature is too dependent on the definition of quality that is not traceable and unpredictable, such as "software products meet user needs" or meet a series of "characteristics". These unscientific quality definitions slow down the research on the most economical price of software quality. The use of the other two invalid economic metrics also affects the research on the most economic value of software quality, namely, average defect cost and code lines. Average defect cost is bad for quality, but the software with the lowest defect cost is often full of holes. The line of code is disadvantageous to the high-level programming language. It covers up the value of high-level programming language in software quality and productivity research.
In this part, the author will try to use research cases to show the economic advantages of software quality crab. Since the economic value of software quality address is closely related to the application scale, four discrete scales are used to illustrate: 100 function points, 1000 function points, 10000 function points and 100000 function points. The application software with 100 function points is usually a small function module of a large system rather than an independent application software. However, this magnitude is also the most common scale range of larger application software prototypes. Some small independent applications may also be on this scale, such as currency converters or small applications on handheld devices (such as iPhones).
Application software with 10000 function points is usually an important system in all aspects of business control, such as insurance claim processing, motor vehicle registration, child support application software and other software systems. The application software with 100000 function points is usually a major system such as the large international telephone switching system, an operating system such as Vista or IBM MVS, and an associated and collaborative application suite such as Microsoft Office. Some ERP applications are also software of this scale, and may even reach 300000 function points. Similarly, large-scale defense applications such as the Global Military Command and Control System (WWMCCS) may also have up to 100000 function points.
To reduce the number of variables, all examples assume that the code is written in C language, and each function node contains about 125 code statements. Since all application examples assume that they are written in the same programming language, productivity and quality can be represented by undistorted code line indicators. Note that it is invalid to use code line indicators for comparison between different programming languages.
