Search

Software engineering focuses on producing quality software products through quality processes. The attention to processes dates back to the early 1970s, when software engineers realized that the desired qualities (such as reliability, efficiency, evolvability, ease of use, etc.) could only be injected in the products by following a disciplined flow of activities. Such a discipline would also make the production process more predictable and economical. Most of the software process work, however, remained in an informal stage until the late 1980s. From then on, the software process was recognized by researchers as a specific subject that deserved special attention and dedicated scientific investigation, the goal being to understand its foundations, develop useful models, identify methods, provide tool support, and help manage its progress. This paper will try to characterize the main approaches to software processes that were followed historically by software engineering, to identify the strengths and weaknesses, the motivations and the misconceptions that led to the continuous evolution of the field. This will lead us to an understanding of where we are now and will be the basis for a discussion of a research agenda for the future. Copyright © 1998 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

Component-based software reuse has been generally regarded as a promising approach to improving software productivity and quality within software development. However, progress in component-based software reuse has been slower than expected. Much of the software reuse literature points to the lack of software components that can maximize users' benefits as the most important source of the slow progress. Considering that the underlying processes behind component-based software reuse are strikingly similar to commercial software marketing, this paper attempts to identify the aspects of software components that consumers value and to establish relationships between the identified aspects and consumer behavior in the software component market. More specifically, this paper focuses on the perceived subjective features of software components. This study was conducted in a web-based artificial market environment called "SofTrade." [ABSTRACT FROM AUTHOR]

The international SPICE (Software Process Improvement and Capability dEtermination) project was set up to support the development of the ISO/IEC 15504 standard for software process assessment (SPA). The project mounted a set of trials to validate the emerging standard against the goals and requirements defined at the start of the SPICE project and to verify the consistency and usability of its component parts. A considerable number of empirical evaluation studies have been conducted during the Phase 2 SPICE Trials based on ISO/IEC PDTR 15504 (between September 1996 and June 1998). Such an exercise is unprecedented in the software engineering standards community and it provides a unique opportunity for empirical validation. The purpose of this paper is to present major parts of the findings of the empirical studies conducted as part of the SPICE Project during Phase 2 of the SPICE Trials. The topics covered in this paper include (i) investigation into reasons for performing SPAs, (ii) evaluation of the internal consistency of the capability dimension, (iii) use of interrater agreement as a measure of the reliability of assessments, (iv) evaluation of the predictive validity of process capability, (v) evaluation of an exemplar model (Part 5), (vi) identification of factors influencing assessor effort, and (vii) empirical comparison between ISO/IEC PDTR 15504 and ISO 9001. Major lessons learned as well as future research directions are summarized on the strengths and weaknesses of ISO/IEC 15505. Copyright © 2001 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

Two complementary standards are compared, both of which are concerned with the production of quality software. One, IEC 61508, is concerned with the safety of software intensive systems and the other, ISO/IEC TR 15504, takes a process view of software capability assessment. The standards are independent, though both standards build on ISO/IEC 12207. The paper proposes a correspondence between the safety integrity levels (SILs) of 61508 and the capability levels (CLs) of 15504, and considers the appropriateness of the 15504 reference model as a framework for assessing safety critical software processes. Empirical work from the SPICE trials and COCOMO II is used to support the arguments of the paper as well as to investigate their consequences. The development of a 15504 compatible assessment model for software in safety critical systems is proposed. Copyright © 2001 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

This paper provides a practical experience-based approach to managing change in software process improvement initiatives. The contents presented in this paper are based on author’s experience in leading software process improvement initiatives and deploying quality processes in hi-tech organizations involved in large-scale software development, and also based on some years of research and consulting. The paper emphasizes the critical role of processes for the success of software development organizations and provides a practical insight into the process of change for achieving software excellence. Importance of a strategic and structured approach to change management is discussed. An analysis of the problems and difficulties associated with change management in software process improvement initiatives is presented. A simple and pragmatic approach for successfully managing change for software process improvement is provided. A matrix identifying the skills, attitude and characteristics essential for a successful change agent is also presented. Copyright © 1998 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

This paper aims at: (1) improvement of the specification verification capability of SDI, without losing its advantages, i.e., transparency and descriptive power; and (2) realization of translation between specifications described by SDL and LOTOS. A method is proposed which gives a LOTOS interpretation of the specification by SDL. First, the mapping of the object system structure indicated by SDL specification to the LOTOS description is discussed. Then the description of the processing definition of SDL specification is described. Using the method proposed in this paper, a LOTOS interpretation is presented as an example for the SDL specification for the switching service. The result of interpretation is evaluated and the flexibility of the verification process is discussed. [ABSTRACT FROM AUTHOR]

The temporal logic model checking method is very useful for verification of concurrent programs that can be expressed by finite state transition systems. However, a major drawback to using this method is that as the scale of the programs increases, the computation costs for verification increase exponentially. An effective solution for this problem is compositional verification. Compositional verification is a method in which the bisimulation equivalence of concurrent programs is used to extract from each construction element (subprocess) only that abstract information necessary to verify each query, thereby avoiding an explosion in cost. In this paper, PQL (Process Query Language) is proposed as an improved method in the solution of this problem. PQL is based on modal logic which is the union of temporal and process logic. Also in this paper, the compositional verification method is proposed by using PQL with consideration of the ‘divergence by internal transition’. [ABSTRACT FROM AUTHOR]

This paper describes the evolution of the structure and representation of Capability Maturity Modelssm and various components of the ISO/IEC 15504 (PDTR) product set, formerly known as ‘SPICE’ (Software Process Improvement and Capability dEtermination). ‘15504’ will be used as shorthand for the product set encompassed by the 15504 project. The paper focuses on historical, structural, and conceptual evolution of the two product types. © 1997 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

This paper presents a design-based software cycle time reduction model that can be easily implemented without replacement of existing development paradigms or design methodologies. The research results suggest that there are many cycle time factors that are influenced by design decisions. If manipulated carefully it appears that an organization can reduce cycle time and improve quality simultaneously. The preliminary results look promising and it is expected that further experimentation will support the use of this model. This paper will analyze the basis for the model proposed here, describe the model's details, and summarize the preliminary results of the model. [ABSTRACT FROM AUTHOR]

In this paper we describe a metamodel to the system dynamics language that allows the development of software process models based on high-level constructors instead of mathematical equations. These constructors represent software process domain concepts such as developers, activities, resources and artifacts. A domain model allows the translation of these concepts to traditional stock-and-flow diagrams, which can be simulated to evaluate the behavior of software process models. The proposed approach helps inexperienced modelers to build process models by reducing the semantic gap between system dynamics and the software process domain. Thus, resulting models are more readable, easier to understand and maintain. We provide an example of a process model built with the proposed approach presenting its translation and simulation processes. Copyright © 2003 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

In this paper we present empirical findings from our study of software practitioners. We used the repertory grid technique to collect data from nearly 200 developers, project managers and senior managers in 13 companies. The aim of this study is to investigate the perceptions that different staff groups have regarding their role in SPI. Our results allow improved understanding of the SPI concerns and needs that different staff groups have. We suggest that this improved understanding will enable SPI managers to develop multi-strand SPI implementation strategies which deliver benefit to all staff groups. Delivering SPI benefit to all staff groups increases buy-in at all levels and means that SPI can be more successful in the long term. Our main findings are that all staff groups are in close agreement about their roles in SPI. However software developers often have a limited view of SPI and are unable to perceive themselves in some of the roles that successful case studies on SPI recommend. For example, developers do not see themselves assuming ownership of processes. Copyright © 2002 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

In this paper we present survey data characterizing the implementation of SPI in 85 UK companies. We aim to provide SPI managers with more understanding of the critical success factors of implementing SPI. We present an analysis of the critical implementation factors identified in published case studies. We use a questionnaire to measure the use of these factors in ‘typical’ software companies. We found that many companies use SPI but the effectiveness of SPI implementation is variable. Many companies inadequately resource SPI and fail to evaluate the impact of SPI. On the other hand, companies show a good appreciation of the human factors associated with implementing SPI. Copyright © 2002 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

This paper discusses how and under which circumstances software process improvement can be rewarding for small software companies. It describes the course of a process improvement project which was jointly carried out by three small companies. Based on the experience gathered in the project four critical success factors – (1) a flexible, tailored assessment and improvement approach, (2) a functioning network of small enterprises and their environment, (3) external technical help by mentors for change and (4) external financial support coupled to some conditions for performance – have been identified. Together they support a fifth factor, namely the ability to utilize not anticipated side-effects of a project. All factors as well as the problems experienced and the lessons learned are explained in detail and are reflected in relation to current knowledge about the diffusion and adoption of software technologies and with regard to quality management techniques. Copyright © 1998 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

One of the more important steps in starting a process improvement initiative is to determine the appropriate tasking and the scope of the process improvement program. There is great temptation for an organization to attempt to take on too much too fast, especially if it feels that it must catch up with its competition. For example, an organization will assess its capability against all of the key process areas (KPAs) of the Capability Maturity Model (CMM) and try to set up working groups and action plans in a broadly based approach to implement multiple levels of KPAs at the same time. While it is natural to want to initiate a program quickly, it is important for an organization trying to get a process improvement initiative started to be as realistic as possible in these beginning stages. It might not be appropriate for an organization to conduct an assessment right away, yet another organization might want to focus on only a few areas to get its process improvement initiative started, show positive results and then expand. This paper will identify critical factors to consider and discuss process improvement entry strategies that the authors have helped their clients to achieve over the past five years. Copyright © 1998 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

This paper examines the efficiency and effectiveness of a prescriptive systems development methodology in practice. The UK government’s mandatory Structured Systems Analysis and Design Method (SSADM) was examined to determine its value to software projects. The evidence was collected from interviews with 17 project managers, discussions with participants on three large software projects and from observing 90 end users in training. The conclusions are that prescriptive information systems methodologies are unlikely to cope well with strategic uncertainty, user communication or staff development. The recommendations are to focus more on soft organizational issues and to use approaches tailored to each project. © 1997 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

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 visualize the results of SPICE conformant assessments. The tools, which are equally useful to software producers and to software procurers, also have a valuable research role and have been used to summarize the results of the world-wide trials of the SPICE reference model. This work has itself led to the enhancement of the tools based partly on experience of their use and partly on revisions to the SPICE model. © 1997 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

This paper provides brief summaries of the main features of the principal methods and approaches for software process improvement. © 1997 John Wiley & Sons Ltd [ABSTRACT FROM AUTHOR]

Introduces papers compiled in issue 8:3 about large and small scale software process improvement efforts.