software testing

Mobile-D for Mobile Software : How to Use Agile Approaches for the Efficient Development of Mobile Applications

Software Process Improvement - EuroSPI 2005 Conference

A Case Study on Naked Objects in Agile Software Development

The Use of Architectural Patterns in the Agile Software Development of Mobile Applications

Software Process Improvement: 12th European Conference, EuroSPI 2005, Budapest, Hungary, November 9-11, 2005, Proceedings (Lecture Notes in Computer Science)

Keynote: Mobile software development - the business opportunity of today

Integrating agile software development and software process improvement: a longitudinal case study

Developing Software Products for Mobile Markets: Need for Rethinking Development Models and Practices

Providing test quality feedback using static source code and automatic test suite metrics

Commitment to Software Process Improvement—Development of Diagnostic Tool to Facilitate Improvement1

This paper suggests that by operationalizing the concept of commitment in the shape of a model, a new insight is provided in improving software processes—a more human centered approach as opposed to various technical approaches available. In doing so the SPI managers/change agents are able to plan better the software process improvement initiative and benchmark successful projects (as well as failed ones). Results from five interviews with SPI professionals on the proposed Behavior-based Commitment Model are reported, together with early results from the empirical test in 14 software process improvement projects. Early results suggest that the behaviors introduced in the model are relevant in SPI initiatives, the use of model raises the awareness about the people issues in improving processes, and the model could be used aside with CMM, SPICE or other process improvement models.

The personal software process: experiences from Denmark

The focus of the research and practice in software process improvement (SPI) is shifting from traditional large-scale assessment based improvement initiatives to smaller sized, tailored initiatives where the emphasis is on the development personnel and their personal abilities. Personal software process (PSP/sup SM/) is a method designed for improving the personal capabilities of the individual software engineer. This paper contributes to the body of knowledge within this area by reporting experiences from Denmark. The findings indicate an improvement in effort estimation skills and an increase in the resulting product quality in terms of reduced total defect density. The data shows that even with a relatively small effort (i.e., 10%) used in defect prevention activities (i.e., design and code reviews) almost one third of all defects could be removed and, consequently, the time required for the testing was reduced by 50%. On the basis of this data, the use of the PSP method in the software industry is discussed.

Commitment Nets in Software Process Improvement

Several studies have revealed the fact that nearly two-thirds of all software process improvement (SPI) efforts have failed or have at least fallen short of expectations. Literature and practice have shown that commitment to SPI at all organizational levels is essential for the success of any SPI endeavor. A research model for studying the existence, development and interplay of SPI-related commitment is introduced in this paper. This study suggests that software organizations operate through strategic, operational and personal commitment nets. These nets consist of actors, drivers, concerns, actions, commitment, and outcomes. The commitment nets model is applied in a study of four industrial SPI initiatives. The results from two of these cases are reported here. The results show that SPI is driven through the formation and reformation of commitment nets. The contents of strategic, operational and personal commitment nets are laid out and implications are discussed.