Understanding the State of Quality of Software

Introduction

This research work suggests a new mathematical model to understand the state of quality of software by calculating parameters such as the time gap and quality gap with relation to some predefined standard software quality or in relation to some chalked out software quality plan. The chapter also suggests methods to calculate the difference in the quality of the software being developed and the model software which has been decided upon as the criteria for comparison (Rashid, Patnaik, & Bhattacherjee, 2013).

Quality is not an absolute term. Rather, just like other scientific parameters, it should be viewed as something relative, precise and concrete. Even the measurement of quality has to be contemplated with the correct approach, which is on the basis of comparison with some specific standard. For instance, what do we mean when I say that something is five meters long. Obviously, I have some standard length, which we call one meter, and when compared to that, my object in discussion is five times that standard lengths. Similar is the case of measuring other scientific parameters. The comparisons are made with some specific standards which are globally recognized. However, in the case of software engineering, quality measures do not have globally recognized concrete values. There are sets of standards defined by the IEEE as to how a software quality should be estimated. Only when some concrete software has been identified as the measuring standard, can I precisely calculate the quality of any software by comparing it to that given standard. This chapter outlines the possible comparison parameters to understand the state of quality of software on the basis of such a comparison. The parameters that have been used are novel ideas and have not been previously used in the realm of software engineering. Moreover, an attempt has been made to chalk out a mathematical model, and a concrete strategy so as to precisely determine the quality of the software being developed. As elucidated earlier, the basis of quality determination is chiefly by drawing out an analogy between what is being developed and what is already developed. Although the author considers that an international standard has to be established, regarding this quality, unless that is achieved, I can define my own standards in my own institutes and organizations and use the methods given herewith to determine concretely the state of quality of the software being developed. The mathematical methods employed are very basic and can be used by any ordinary person. The parameters and terms may be enriched and advanced to form newer concepts and ideas. On the whole after the required comparisons have been made and the particular understanding of the quality has been achieved, decisions can be taken suitably to augment the proper and rapid quality software development.