Software quality management: an Australian experience

1992 ◽  
Vol 1 (2) ◽  
pp. 75-80
Author(s):  
John G. Phippen
Keyword(s):  
Quality Management ◽  
Software Quality ◽  
Software Quality Management ◽  
Australian Experience

scholarly journals Application of multistage process control methodology for software quality management

2016 ◽  
pp. 55-66 ◽  
Author(s):  
Boby John ◽  
R. S. Kadadevaramath ◽  
I. A. Edinbarough
Keyword(s):  
Quality Management ◽  
Process Control ◽  
Software Quality ◽  
Multistage Process ◽  
Software Quality Management ◽  
Control Methodology

Relating Software Quality Models and Process Methods to User Value

2013 ◽  
Vol 4 (2) ◽  
pp. 27-42 ◽  
Author(s):  
Mohamed A Sheriff ◽  
Elli Georgiadou
Keyword(s):  
Risk Management ◽  
Quality Management ◽  
Software Development ◽  
Software Quality ◽  
Process Models ◽  
Quality Model ◽  
Quality Models ◽  
Software Quality Management ◽  
Risk Management Process ◽  
User Value

The ultimate object of software development should be to deliver value to all stakeholders. The traditional approach to delivering this value is to ensure that the software developed is of the highest quality. A number of quality models have been proposed to specify or describe what constitutes high quality software. The ISO9126 is one such model and perhaps the most comprehensive. Similarly, there are several methods, frameworks and guidelines for ensuring software quality in either the development or use process or both. Software Quality Management and Risk Management are probably the two most popular methods employed by developers during software development and implementation to deliver quality. In this paper the authors examine whether, and to what extent, the implied value propositions of software products as portrayed by the ISO9126 quality model and the prescribed processes in Software Quality Management and Risk Management, map onto user value perceptions and experiences. An ontology of value, in the form of a value tree, is developed and used to identify and analyse the key value dimensions of the ISO9126 quality model and the Software Quality Management and Risk Management process methods. These are then mapped onto contextualised user value characterisations derived from the extant literature. Differences identified are analysed and discussed and the authors suggest approaches that could narrow the perennial gap between idealised quality product and process models and stakeholder perceptions and actualisations of software value.

Design process of software quality management

2017 ◽  
Author(s):  
Elena N. Desyatirikova ◽  
Vadim E. Belousov ◽  
Viktor N. Zolotarev ◽  
Oksana Yu. Lavlinskaia
Keyword(s):  
Quality Management ◽  
Design Process ◽  
Software Quality ◽  
Software Quality Management

Software Engineering and Software Quality Management

2014 ◽  
Vol 926-930 ◽  
pp. 2642-2645
Author(s):  
Wen Hong Liu ◽  
Chun Yan Wang ◽  
Li Ge
Keyword(s):  
Software Engineering ◽  
Quality Management ◽  
Software Quality ◽  
Software Reliability ◽  
Rapid Development ◽  
High Quality ◽  
Software Products ◽  
Software Quality Management ◽  
Management Method

As the rapid development of social informatization, software reliability and security are highly required. Only applying high-quality software products can increase work efficiency. Quality is the life of software. How to enhance the quality of software products and how to use effective quality management method is an urgent need. This paper discuss the key point of software engineering and software quality management, and this is the basis of software quality ensurance model.

Sign in / Sign up

Export Citation Format

Share Document