scholarly journals Software Quality Management supported by Software Agent

10.28945/858 ◽  
2005 ◽  
Vol 2 ◽  
pp. 659-669
Author(s):  
Rita C Nienaber ◽  
Andries Barnard
10.28945/2924 ◽  
2005 ◽  
Author(s):  
R. C Nienaber ◽  
A. Barnard

Software technology and computing resources have evolved and developed considerably over the past years and may be considered as the backbone of many business ventures today. However, the software project management environment has also changed and is continuously evolving. Currently software projects are developed and deployed in distributed, pervasive and collaborative environments. This means that traditional software project management methods cannot, and do not, address the added complexities found in a pervasive, distributed global environment. Projects thus have a high rate of failure. More specifically, software projects often do not comply with the traditional standard measurements of success, namely time, cost and specifications. There is thus a need for new methods and measures to support software project management. In this paper, software agent technology is explored as a potential tool for enhancing software project management practices in general. We propose and discuss a software agent framework, specifically to support software quality management. Although still in its initial phases, research indicates some promise in enabling software developers to meet market expectations and produce projects timeously, within budget and to users’ satisfaction.


Author(s):  
Mohamed A Sheriff ◽  
Elli Georgiadou

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.


Sign in / Sign up

Export Citation Format

Share Document