A Review of Software Quality Models for the Evaluation of Software Products <s> Model Comparison <s> ￻ Abstract: - Nowadays, software products rapidly increased and it is usage not limited to specific people or corporation. It is now used in the most of human life activities. Therefore, the quality of the software product is increasingly being important and the users demanding higher quality than ever before. However, most of this research is focused on the internal/development view of quality. Hence, in software development, strong attention must be given to the user's satisfaction. Recently, the studies intend to understand the users' perspective of the software quality. In this study, we intend to discuss the characteristics of the software products that influence the users' satisfaction on software quality. Based on the well-known software quality models and the emotion of the software users, a model of software quality evaluation based on users' views is proposed. one of these approaches is a user perceived quality. That it means a combination of product attributes which provide the greatest satisfaction to a specified user. According to Bevan (6), the expectation of software quality in both consumer and professional market is rapidly increased. That is, matching the software product with the real users needs is increasingly demanded. Moreover, he state that it is not enough sufficient to deliver a software product has a technical excellence. Also, it has to be easy to use and suitable for the end users in the work practices and activates, either the users are normal consumer or professionals. However, Chulani (2, 7) presented software product quality from customer's perspective, and the companies can increase the revenue by increase customer's satisfaction and improve the quality of the software product. That is in order to develop any software product, the user's requirements have to be addressed either functional and non-functional (quality of services) (8). <s> BIB001 </s> A Review of Software Quality Models for the Evaluation of Software Products <s> Model Comparison <s> With the objective of presenting qualitative software system most of the software producers have endeavoured and infact this is their main purpose. Software quality is having multi-dimensional content which may be distinguished and measured easily. To be specific, with the idea of determining the multidimensional content in a more exact pattern various qualitative models have been presented by virtue of which different aspects of this matter have been attempted to be investigated properly. Practically as because there are existences of different models which have used different expressions the comprehension of this basic content have become to some extent hard or difficult. Attempts have been made in this particular paper to introduce some models that have been mentioned and more clearly analysis the qualitative characteristics and side-by-side determine the software quality along with the analytical comparison of these models. This paper may serve the purpose of a reference for investigating software quality and its related models. <s> BIB002 </s> A Review of Software Quality Models for the Evaluation of Software Products <s> Model Comparison <s> Siemens Corporate Development Center Asia Australia (CT DC AA) develops and maintains software applications for the Industry, Energy, Healthcare, and Infrastructure & Cities sectors of Siemens. The critical nature of these applications necessitates a high level of software design quality. A survey of software architects indicated a low level of satisfaction with existing design assessment practices in CT DC AA and highlighted several shortcomings of existing practices. To address this, we have developed a design assessment method called MIDAS (Method for Intensive Design ASsessments). MIDAS is an expert-based method wherein manual assessment of design quality by experts is directed by the systematic application of design analysis tools through the use of a three view-model consisting of design principles, project-specific constraints, and an “ility”-based quality model. In this paper, we describe the motivation for MIDAS, its design, and its application to three projects in CT DC AA. We believe that the insights from our MIDAS experience not only provide useful pointers to other organizations and practitioners looking to assess and improve software design quality but also suggest research questions for the software engineering community to explore. <s> BIB003 </s> A Review of Software Quality Models for the Evaluation of Software Products <s> Model Comparison <s> Software quality is the totality of features and characteristics of a product or a service that bears on its ability to satisfy the given needs. Software quality model is the representation of the characteristics of the software that describe the quality. The benefit of quality models is that they are simpler to use and the benefit of quality management is that they probably more to the point capture the idea of quality . So the quality of the project should be maintained at appropriate label. To maintain the quality, there are different quality models. "A high quality product is one which has associated with it a number of quality factors. These could be described in the requirements specification; they could be cultured, in that they are normally associated with the artifact through familiarity of use and through the shared experience of users. In this paper, we will compare all the quality models: McCall’s quality model, Boehm’s quality model, Dromey's quality model, and ISO 9126 quality model and focus on a comparison between these models, and find the key differences between them. <s> BIB004
Al-Baradeen BIB001 BIB004 , Al-Qutaish BIB002 , Samarthyam BIB003 and Ghayathri BIB004 conducted comparative studies of Basics Quality Models, reaching different conclusions depending on the as they consider more important. Table 2 shows a comparison of the basic models regarding the main characteristics according to Table 1 . We include the ISO 25010 in this evaluation because it contains the last standardized terminology. From table 2 we conclude that Model ISO 25010 is the most complete among the Basic Models, because it covers 26 of the 28 features. Flexibility is related to the manufacturing process BIB004 and is considered as an aspect of maintainability. Regarding Human Engineering this is a particular feature considered only in the Boehm model and has close relation with operability, but this last concept is wider. From the table we conclude that reliability is a common feature to all models. The reason is the close relation with the opinion of users and the success of any product will depend on the fact of being used or not. Table 2 was constructed using the sub characteristics of the model. However and because these features are include in larger characteristic, it is possible that the presence of a feature implies that other has to be present. For example the transferability is related with some aspects of portability and adaptability. 