A Review on Software Quality Models

Singh, Brijendra; Kannojia, Suresh Prasad

doi:10.1109/csnt.2013.171

Cited by 14 publications

(17 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is called an FCM (factor criteria metric) model [25]; its structure is hierarchical, and it defines quality attributes (quality factors, quality criteria and quality metrics) [17]. The model bridges the gap between users and software developers, concentrating on a collection of factors that express users' views and developers' priorities [10] [26]. McCall's has three main viewpoints for defining and identifying software quality: product operation, product revision and product transition.…”

Section: Mccall's Software Quality Modelmentioning

confidence: 99%

“…McCall's has three main viewpoints for defining and identifying software quality: product operation, product revision and product transition. These viewpoints contain 11 quality factors [25] [26].…”

Section: Mccall's Software Quality Modelmentioning

confidence: 99%

“…In 1978, Boehm presented his quality prediction model [25] [26], which was the result of a study conducted by Boehm and two of his colleagues [10]. Boehm and his colleagues identified 23 nonfunctional requirements, or software quality characteristics, [10].…”

Section: Boehm's Software Quality Modelmentioning

confidence: 99%

“…There is increased emphasis on the needs of stakeholders within Boehm, including users, developers, testers and maintainers [25]. According to [28], Boehm addressed defects within existing quality models, which provided a quantitative evaluation of software quality [26]. [28]…”

Section: Boehm's Software Quality Modelmentioning

confidence: 99%

See 3 more Smart Citations

A Comparison of Software Quality Characteristics and Software Sustainability Characteristics

Aljarallah

Lock

2019

Proceedings of the 2019 3rd International Symposium on Computer Science and Intelligent Control

View full text Add to dashboard Cite

Software sustainability has generated much interest in the software engineering field in recent times, and has been widely investigated across different fields and from different standpoints. The relationship between software quality and software sustainability is still an open question. In this study, a literature survey and comparison was conducted using three-phases, having as a starting point the comparison of basic models for software quality. A follow-up study, conducted at a more comprehensive level to cover both basic models and the most cited tailored models. , Software sustainability literature is investigated to find the most frequent characteristics. Finally, data gathered from these studies and a comparison shows a similarity in the top level of these characteristics between software sustainability and software quality, and the emphasis on sustainability, maintainability and portability. The study suggests that ISO 25010 can be utilised by software sustainability. As a future work, the findings will be investigated empirically to support designing software sustainability framework identifying the most important criteria in the technical dimension.

show abstract

Section: Mccall's Software Quality Modelmentioning

confidence: 99%

Section: Mccall's Software Quality Modelmentioning

confidence: 99%

Section: Boehm's Software Quality Modelmentioning

confidence: 99%

Section: Boehm's Software Quality Modelmentioning

confidence: 99%

See 2 more Smart Citations

A Comparison of Software Quality Characteristics and Software Sustainability Characteristics

Aljarallah

Lock

2019

Proceedings of the 2019 3rd International Symposium on Computer Science and Intelligent Control

View full text Add to dashboard Cite

show abstract

“…The FURPS quality model [8], which was proposed by Robert Grady from Hewlett Packard in 1992, takes into account the following five characteristics: Functionality, Usability, Reliability, Performance, and Supportability. A main drawback of this model is that it does not consider some important characteristics such as portability, which may be an important criterion for application development [9]. In 1995 Robert Dromey proposed a product based quality model [10] based on the idea that a more dynamic way of modelling process was needed.…”

Section: Related Workmentioning

confidence: 99%

Evaluation of a Dependability Mechanism for Cyber Physical Systems

Regan

McCaffery

Reich

et al. 2019

Communications in Computer and Information Science

View full text Add to dashboard Cite

Cyber-Physical-Systems (CPS) are systems of collaborating computational entities. Concepts such as autonomous cars, smart electric grid, implanted medical devices and smart manufacturing are some practical examples of CPS. However, the open and cooperative nature of CPS poses a significant new challenge in assuring dependability. The DEIS project addresses this important and unsolved challenge by developing technologies that facilitate the efficient synthesis of components and systems based on their dependability information. The key innovation that is the aim of DEIS is the corresponding concept of a Digital Dependability Identity (DDI). A DDI contains all the information that uniquely describes the dependability characteristics of a CPS or CPS component. DDIs are synthesised at development time and are the basis for the (semi-)automated integration of components into systems during development, as well as for the fully automated dynamic integration of systems into systems of systems in the field. In this paper we present an overview of the DDI. Additionally, we provide metrics for evaluating the DDI's impact on CPS dependability, and the results of an evaluation of the DDI's impact on dependability in four CPS industrial systems. These results demonstrate the positive impact of the DDI on the dependability of CPS.

show abstract

Software smell detection techniques: A systematic literature review

AbuHassan

Alshayeb

Ghouti

2020

J Software Evolu Process

View full text Add to dashboard Cite

Software smells indicate design or code issues that might degrade the evolution and maintenance of software systems. Detecting and identifying these issues are challenging tasks. This paper explores, identifies, and analyzes the existing software smell detection techniques at design and code levels. We carried out a systematic literature review (SLR) to identify and collect 145 primary studies related to smell detection in software design and code. Based on these studies, we address several questions related to the analysis of the existing smell detection techniques in terms of abstraction level (design or code), targeted smells, used metrics, implementation, and validation. Our analysis identified several detection techniques categories. We observed that 57% of the studies did not use any performance measures, 41% of them omitted details on the targeted programing language, and the detection techniques were not validated in 14% of these studies. With respect to the abstraction level, only 18% of the studies addressed bad smell detection at the design level. This low coverage urges for more focus on bad smell detection at the design level to handle them at early stages. Finally, our SLR brings to the attention of the research community several opportunities for future research.

show abstract

A Review on Software Quality Models

Cited by 14 publications

References 22 publications

A Comparison of Software Quality Characteristics and Software Sustainability Characteristics

A Comparison of Software Quality Characteristics and Software Sustainability Characteristics

Evaluation of a Dependability Mechanism for Cyber Physical Systems

Software smell detection techniques: A systematic literature review

Contact Info

Product

Resources

About