This article presents the results and lessons learned in the application of the Framework for the Modelling and Measurement of Software Processes (FMESP) in a software company dedicated to the development and maintenance of software for information systems. The aim of FMESP is to provide companies with a conceptual and technological framework for the management of their process models and measu...

This paper highlights the need for greater agility and flexibility in the process improvement activity. The ideas presented here relate to aspects that have arisen from a case study of a global software product organisation. A model of how software process improvement can be agile in nature is proposed. This model is intended as indicative of the issues that need consideration by IS management....

In this paper we present findings from our empirical study of software process improvement (SPI) implementation. We aim to provide SPI practitioners with insight into designing appropriate SPI implementation initiatives in order to achieve better results. Thirty-four interviews were conducted with Australian practitioners. Three SPI implementation issues were investigated: reasons for embarking...

The crisis in developing software has been known for over thirty years. Problems that existed in developing software in the early days of computing still exist today. These problems include the delivery of low-quality products, actual development costs that exceed expected development costs, and actual development time that exceeds expected development time. Several solutions have been offered ...

The objective of this research paper is to study about the software reliability metrics. Reliability is one of the important aspects of any software that cannot be ignored and hard to measure. According to ANSI, “Software Reliability is defined as the probability of failure-free software operation for a specified period of time in a specified environment”. Software Reliability is different from...

How do these steps differ from other popular methods for analyzing processes? One popular method is process assessments, for example, SEI (Software Engineering Institute) process assessments.1 Most assessments document peoples’ answers to subjective questions that are designed around somebody’s model of ideal software development practices. If such models are accurate and if peoples’ answers re...

This paper addresses the issue of technology transfer in software development organizations. Common problems for the software industry are still software failures, project overruns, and unfinished projects. To remedy these, knowledge-intensive technologies like quality management and software process improvement (SPI) have been promoted. The organizational implementation of such approaches is a...

Software processes improvement (SPI) is a challenging task, as many different stakeholders, project settings, and contexts and goals need to be considered. SPI projects are often operated in a complex and volatile environment and, thus, require a sound management that is resource-intensive requiring many stakeholders to contribute to the process assessment, analysis, design, realisation, and de...

..............................................................................................................ix

Many software process assessment models have been developed based on, or inspired by, the Software Engineering Institute’s Capability Maturity Model (CMM). The outputs arising from such models can be voluminous and complex, requiring tool support to comprehend and analyse them. The paper describes some tools developed in order to visualise the results of SPICE conformant assessments. The tools,...