Ming‐Chang Lee · British Journal of Applied Science & Technology · 2014
Aims: Software quality assurance is a formal process for evaluating and documenting the quality of the work products during each stage of the software development lifecycle.The practice of applying software metrics to operational factors and to maintain factors is a complex task.Successful software quality assurance is highly dependent on software metrics.It needs linkage the software quality model and software metrics through quality factors in order to offer measure method for software quality assurance.The contributions of this paper build an appropriate method of Software quality metrics application in quality life cycle with software quality assurance.Design: The purpose approach defines some software metrics in the factors and discussed several software quality assurance model and some quality factors measure method.Methodology: This paper solves customer value evaluation problem are: Build a framework of combination of software quality criteria.Describes software metrics.Build Software quality metrics application in quality life cycle with software quality assurance.Results: From the appropriate method of Software quality metrics application in quality life cycle with software quality assurance, each activity in the software life cycle, there is one or more QA quality measure metrics focus on ensuring the quality of the process and the resulting product.Future research is need to extend and improve the methodology to extend metrics that have been validated on one project, using our criteria, valid measures of quality on future software project.
Cited by 57Open access
B.S. Dhillon · 2022
Cited by 0
D. J. Asher · Apress eBooks · 2024
There is plenty of great source material to understand software testing per se, but from a Software Manager’s perspective it’s helpful to think about the quality of human–computer interactions and the meaning of bugs through real experiences. In this chapter, we’ll take a very expansive view of quality, especially relating to the kinds of fuzzy problems that are more recently being tackled with Artificial Intelligence.
Cited by 0
James E. McDonough · Apress eBooks · 2021
Every software component has a quality; it may be low quality, high quality, or somewhere in between. Its level of quality will reflect how well the software component meets the needs of the organization using it. This chapter covers software quality and how it can be evaluated.
Cited by 1
April, Alain, Tockey, Steve, Schwarm, Steve · Espace ÉTS (ETS) · 2024
Cited by 0
Lauritsch, Nadja · TUGraz OPEN Library (Graz University of Technology) · 2022
Cited by 0Open access
Sukhvir Kaur · INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY · 2012
In the given paper I present the information regarding quality metrics. Different quality factors can be imposing with relation to cost, schedule and rework. It’s very important to make quality assurance plans. For that you have to cover many milestones which can be represented in time sheets. The main characteristics of the quality models have covered in this paper
Cited by 0Open access
Kshirasagar Naik, Priyadarshi Tripathy · 2008
This chapter contains sections titled: Five Views of Software Quality McCall's Quality Factors and Criteria ISO 9126 Quality Characteristics ISO 9000:2000 Software Quality Standard Summary Literature Review References Exercises
Cited by 0
paula andrea · Bulletin of Miscellaneous Information (Royal Gardens Kew)
Cited by 0
David J. Asher · RePEc: Research Papers in Economics
Abstract There is plenty of great source material to understand software testing per se, but from a Software Manager’s perspective it’s helpful to think about the quality of human–computer interactions and the meaning of bugs through real experiences. In this chapter, we’ll take a very expansive view of quality, especially relating to the kinds of fuzzy problems that are more recently being tackled with Artificial Intelligence.
Cited by 0
Cleve, Anthony, Vinju, Jurgen · HAL (Le Centre pour la Communication Scientifique Directe) · 2014
International audience
Cited by 0
James E. McDonough · RePEc: Research Papers in Economics
Abstract Every software component has a quality; it may be low quality, high quality, or somewhere in between. Its level of quality will reflect how well the software component meets the needs of the organization using it. This chapter covers software quality and how it can be evaluated.
Cited by 0
Kurt F. Fischer · 1980
The FAA's computerized Enroute System for controlling in-flight commercial aircraft crashes during a peak holiday period due to overloading. The DoD Early Warning System, a computerized air defense system, mistakes the rising moon for a barrage of incoming enemy missiles and shock waves travel all the way to the White House. A single erroneous statement in a small computer on-board a French weather satellite causes 71 of 142 weather balloons to self-destruct. These experiences would not have happened if there had been better software quality.
Cited by 0Open access
Dietmar Winkler, Stefan Biffl, Daniel Méndez et al. · Lecture notes in business information processing · 2021
Cited by 16
Marc-alexis Côté M. Ing, Witold Suryn Phd, Elli Georgiadou · 2008
Software Quality Engineering is an emerging discipline that is concerned with improving the approach to software quality. It is important that this discipline be firmly rooted in a quality model satisfying its needs. In order to define the needs of this discipline, the meaning of quality is broadly defined by reviewing the literature on the subject. Software Quality Engineering needs a quality model that is usable throughout the software lifecycle and that it embraces all the perspectives of quality. The goal of this paper is to propose a quality model suitable for such a purpose, through the comparative evaluation of existing quality models and their respective support for Software Quality Engineering.
Cited by 0
Michal Žemlička, Jaroslav Král · Lecture notes in computer science · 2016
Cited by 5
Daniel Mendez, Dietmar Winkler, Johannes Kross et al. · Lecture notes in business information processing · 2023
Cited by 0Open access
Software Quality Days 2020 Wien, Dietmar Winkler, Stefan Biffl et al. · Lecture notes in business information processing · 2020
Cited by 6
Elsevier eBooks · 2016
Cited by 6
J. Chris Gibson · 2008
The information contained within this document has been gathered from a variety of sources and practices observed by the development team at Protera Software Corporation. Quality Properties of a Software Requirement A high quality software requirement is: • Complete. Completeness with respect to a single requirement means that the requirement completely describes what is needed. A requirement is complete if 1) the requirement description represents everything that the software is supposed to do, and 2) software responses to all possible classes of input in all possible situations is described. • Design Independent. A software requirement is free of design and implementation decisions except in the form of a constraint (i.e. operating system constraint). A software requirement is design independent if it describes an aspect of a problem space without describing any implementation details of a solution to the problem space or aspect of the problem space (the old what, not how paradigm). • Unambiguous. A requirement is unambiguous if it has only one possible interpretation. Much of this quality has to do with the use of terminology. Agreement on the definition
Cited by 0