Creating Software Process Capability/Maturity Models

The customization of software process capability/maturity models (SPCMMs) to specific domains/sectors or development methodologies represents one of the most discussed and applied trends in ICT organizations. Nonetheless, little research appears to have been performed on how theoretically sound and widely accepted SPCMMs should be developed to high quality. The aim of this paper is therefore to elicit the state-of-the-art regarding the processes adopted to develop such models and to propose a systematic approach to support the customization of SPCMMs. Such an approach is developed based on ISO/IEEE standard development processes integrating Knowledge Engineering techniques and experiences about how such models are currently developed in practice. Initial feedback from an expert panel indicates the usefulness and adequacy of the proposed method.

2010

Software process improvement and assessment guided by a maturity level or a process capability profile based on a capability/maturity model is now well established in practice as a successful means for improving software intensive organizations. Therefore, a wide range of software process capability/maturity models have been developed evolved and adapted over the past years. In this paper, we present the results of a systematic literature review on this type of models. Our results show that there exist a large variety of models with a trend to the specialization of those models for specific domains. We also identified that most of those models are concentrated around the CMM/CMMI framework and the standard ISO/IEC 15504 (SPICE).

2011

A complicated and time-consuming phase in the development of Maturity/Capability Models (MCMs) is the identification of existing relevant source models as, currently, information on existing MCMs is provided in very different forms and levels of detail on diverse web sites, publications etc. In this paper, we present our ongoing research on developing a web-based repository to store and provide overview information on MCMs as a continuous knowledge management effort maintained within the Software Process Improvement (SPI) community. Such a centralized repository containing metadata on MCMs is expected to facilitate the identification of relevant models (as well as parts) and provide a systematic basis for the development/evolution or customization of MCMs.

Process Improvement with CMMI® v1.2 and ISO Standards, 2008

CMMI (Capability Maturity Model Integration) is a process improvement maturity model for the development of products and services. It consists of best practices that address development and maintenance activities that cover the product lifecycle from inception through delivery and maintenance. The purpose of CMMI for software development is to help organizations improve their development and maintenance processes for both products and services. In this paper, we have tried to focus on the importance of process improvement in a software organization by discussing the various aspects of Capability Maturity Model's different process areas.

2001

This document presents a metamodel for the "Capability Maturity Model for Software". This Metamodel embodies seven fundamental concepts (common types), which are neither new nor unique to the SW-CMM and which occur across all key process areas in the same relationship to each other. It can be (and has been) used to build a model for each of the 18 key process areas in the SW-CMM and an idealized model for the entire SW-CMM. It represents an orthogonal view of the SW-CMM and can be used to define the fundamental skills an organization must instantiate across all 18 key process areas.

Software: Practice and Experience, 2006

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 measurement models in an integrated way. Modelling and measurement are two key factors to promote continuous process improvement. As a result, important benefits were obtained. The company improved the maturity of its processes which allowed it to obtain the ISO 9000 certification. From a research point of view, are Capability Maturity Model for Software (SW-CMM) [1], Capability Maturity Model Integration (CMMI) and Software Process Improvement and Capability Determination (SPICE), which has been standardized as ISO 15504 .

—In order to have a competitive software industry, it is essential to adopt standards and reference models of software processes quality. However, despite the growing adoption of standards and models, the number of organizations that adopt these is a small portion of the total population of software organizations. This paper presents a set of support tools to enactment of modeled processes in the Software Process Engineering Metamodel (SPEM). This set of support tools, called Spider-PE (Process Enactment), aims to assist software organizations in the implementation of the Capability Maturity Model Integration for Development (CMMI-DEV) and Reference Model of Software Process Improvement to Software (MR-MPS-SW) models. We expect Spider-PE to be more easily adopted by software organizations because it is based on models and standards largely accepted. Furthermore, this set of support tools adopts free technologies (non-proprietary) in order to reduce costs.

Proceedings of the International Conference on Software and System Processes and International Conference on Global Software Engineering

Model-based systems engineering (MBSE) can address many challenges of modern systems development. However, due to its comprehensive coverage, process maturity improvement can take many directions, potentially leading to sub-optimal solutions. Therefore, selecting disciplines most aligned to the development team context and goal is key to higher returns on investment. This research aims to relate goals driving MBSE process maturity improvement and candidate capabilities, thus, providing recommendations that highest yield the expected benefits. For this means, we propose a goal-benefit model and respective operationalization method. The model relates MBSE capabilities with benefits generated upon implementation and process improvement goals. Our approach results in a list of MBSE capabilities prioritized according to the improvement goal. The approach was applied to eight development teams located in Germany and Brazil. We also provide a sensitivity analysis to validate the model. The approach was assessed positively by the case study participants, who stated that it provides a starting ground for process maturity improvement efforts. CCS CONCEPTS • Software and its engineering → Capability Maturity Model; Software design engineering.