The precursor to an industrial software metrics program

A common reason for why software metric programs dasiafailpsila is through lack of participant support and commitment. In this paper, we describe the results of a study which examined the knowledge that subjects had and the opinions they had formed of previous metrics initiatives in the same organization. The research was undertaken by one of the authors as a precursor to a planned metrics initiative in the same large, UK-based company. The study attempted to understand the likely issues that would have to be addressed by that planned metrics program. A key theme to emerge from the analysis was the importance of all participants being aware of the program objectives, and the purpose and use of the data being collected. As part of the analysis, the study also draws on the role that "timely" involvement plays within a metrics program and how that can influence its associated practicalities

Brief review of classical Effort Estimation models for Software development projects

A critical synthesis on the most representative models for software development project effort estimation is provided. This work is a basis for a discussion about the methodological and practical challenges which entail the effort estimation field, specially in the mathematical/statistical modelling fundamentals, and its empirical verification in the software industry

Software process quality models: a comparative evaluation

Numerous software processes are implemented by software organisations in the production and maintenance of software products. Varying levels of success are observed in their execution, as processes vary in content and quality. A number of quality models for software processes have been published, each of which is intended to encompass the totality of quality factors and issues relevant to a specific notion of process quality. These quality models may be used to develop a new process, measure the quality of existing processes, or guide improvement of existing processes. It is therefore desirable that mechanisms exist to select the model of highest intrinsic quality and greatest relevance. In this thesis, mechanisms are proposed for the comparative evaluation of software process quality models. Case studies are performed in which existing software process quality models are applied to existing software processes. Case study results are used in empirical evaluation of models to augment theoretical evaluation results. Specific recommendations are made for selection of models against typical selection criteria. Assessment is performed of the assessment procedures against defined success criteria. Theoretical evaluation procedures are developed to measure process quality models against defined quality criteria. Measurements are performed of conformance of models to the requirements set for an ideal process quality model, and the relevance of model content to defined stakeholders in software processes. Comparison is also made of the scope and size of models. Empirical evaluation procedures are developed to assess model performance in the context of application to real software processes. These procedures assess the extent to which the results of process measurement using process quality models are observed to differ, and hence the importance of selecting one model in preference to others. Measurement is also performed of the extent of difference in the software processes evaluated in the case studies

Motivators and de-motivators in software process improvement : an empirical study

Software quality problems are a concern for the software engineering community. Software Process Improvement (SPI) is the most recent and most popular approach adopted to address this problem. SPI focuses on the processes that develop software in order to deliver improvements to the product. Despite this popularity of SPI there is insufficient evidence of its successful impact on software quality. Quality problems in software continue. This has led to some concern in the industry about the effectiveness of SPI in tackling the problem of software quality. There is evidence to suggest that SPI does improve software quality. However, there is also evidence to suggest that SPI is not sufficiently supported by software practitioners. This lack of support may be one of the reasons why SPI appears to be failing at tackling the problem of software quality. In this research it is argued that this lack of support for SPI is caused by companies' inability to manage software practitioners' motivation for SPI properly. Companies may not be managing software practitioners' motivation for SPI properly because they may not understand them. There is therefore a need to better understand what software practitioners'motivations for supporting SPI are. A review of the literature suggests a set of guidelines that can improve software practitioners' support for SPI. The literature also suggests four themes that underpin software practitioners' motivation for SPI. The four themes are SPI managers' perception of the motivators and demotivators for SPI, software practitioners' motivators, software practitioners' de-motivators and the differences in software practitioners' motivators and de-motivators. The basis of this research is that exploring the four themes that underpin software practitioners' motivation for SPI improves understanding of the factors that influence support for SPI. This knowledge of the factors that influence support for SPI can then be used to validate and provide an empirical basis for the literature-suggested guidelines. Thereby improving confidence in the "-IL iidelines. The four themes underpinning software practitioners' motivation for SPI are examined through empirical studies. Findings from these studies suggest that SPI managers perceive senior managers as not supportive of SPI. They also perceive developers as not enthusiastic about SPI. The findings also suggest that the key motivators of software practitioners for SPI are visible support and commitment from senior management and empowerment of practitioners, whereas the key de-motivators are related to constraints on resources and a failure to secure practitioners' buy-in for SPI. There are also differences in what motivates and de-motivates different practitioner groups for SPI and these differences are related to the jobs that practitioners do. Finally, software practitioners have different perceptions of their role in SPI, which are related to their software development roles. This suggests that the objectives of SPI should be tailored to the software development objectives of practitioners in order to improve their support for SPI. Overall, findinas from these studies confirm most of the guidelines suggested by the t:, literature. The confirmed guidelines are offered as insight to improving support for SPI, which can in turn help to improve the impact of SPI on software quality

A requirements-based software process maturity model

The requirements phase of software development is an on-going problem for the software engineering community. The many disparate recommendations and best practices found in the literature make it difficult for software organisations to recognise which practices apply to their individual needs. The aim of this thesis is to pull together key solutions into a framework that allows practitioners to assess where their requirements process needs strengthening and to provide a means in which improvements can be achieved. In this thesis I show how I design, develop and validate a model of requirements engineering processes. This requirements capability maturity model (R-CMM) adheres to the characteristics of the Software Engineering Institute's Software Capability Maturity Model (SW-CMM) and is designed to take practitioners from an immature process capability through to an advanced capability. I contribute to the body of knowledge in both software process improvement and requirements engineering (RE) by providing rigorous detail of how a process maturity framework is developed to support RE practices. The model is generic and should apply to many software development organisations. The R-CMM guides users towards a view of RE that is based on goals and is problem driven. The SW-CMM framework is transformed into a simplified model that relates goals and problems to individual RE practises

The Critical Success Factors of Quality Assurance and Measurement Practice in the Software Industry

In this thesis I analyse how QA and measurement programmes are implemented in the software industry. My thesis is that, contrary to popular belief, how companies implement QA and measurement is as important to the ultimate success of a programme as what QA and measurement tools and techniques are implemented. I have combined input from over 300 software developers and managers in 26 different companies, with the analysis of all the relevant publicly available information on companies’ experiences to produce a definitive study into implementing QA and measurement in the software industry. In this study I: • identify those QA and measurement practices considered to be state-of-the-art; • quantify the penetration of state-of-the-art practices; • report on the state-of-the-practice; • assess the effectiveness of the state-of-the-practice; • present guidelines for improved practice. I tested a variety of hypotheses about implementing QA and measurement programmes. My key findings about these hypotheses include: • Some companies have a large gap between what is officially said to be implemented and what is actually implemented. • Practitioners had a significant impact on the success of programmes. Furthermore, I confirmed my hypotheses about managers and developers having different attitudes to QA and measurement. However, I was unable to find convincing evidence to confirm that the demographics of practitioners affected their attitudes. • Many of my hypotheses about the implementation process were confirmed. In particular I found that doing background research was related to success, but that very few companies did research. However, I was unable to find convincing evidence to confirm the importance of feedback to practitioners. Overall my study reveals that the quality of the implementation process across the software industry is, in practice, very poor. Indeed, I show that the gap between state-of-the-art and state-of-the practice is large. I conclude that until the software industry puts as much effort into developing strategies for implementing QA and measurement as it does into developing tools and techniques, then effective and optimised programmes will remain rare