Higher CMM levels attained by QA certified software developers

[Abstract]: This paper addresses the question: is higher capability maturity associated with adoption of Quality Assurance (QA) certification? To assess the extent of adoption of third-party QA certification by Australian software developers, a survey of 1,000 software developers was recently conducted. The questionnaire also included an assessment of their capability maturity based on the capability maturity model (CMM). Cynics who criticise the value of QA certification may be surprised by the strong association found between adoption of QA certification and capability maturity

NASA Experience with CMM and CMMI

This slide presentation reviews the experience NASA has had in using Capability Maturity Model (CMM) and Capability Maturity Model Integration (CMMI). In particular this presentation reviews the agency's experience within the software engineering discipline and the lessons learned and key impacts from using CMMI

Capability Maturity Model (CMM) for Software Process Improvements

This slide presentation reviews the Avionic Systems Division's implementation of the Capability Maturity Model (CMM) for improvements in the software development process. The presentation reviews the process involved in implementing the model and the benefits of using CMM to improve the software development process

Maturity Model Linkages Between Software Development Teams, Users and Quality

Information Systems literature has shown clear linkages between the selection of software development methodologies, the actions of software development teams, overall product quality, and user satisfaction. Rarely are these linkages emphasized, however, in current research on process improvement. This paper examines the convergence of these areas and discusses current research designed to further explore these linkages within the Capability Maturity Model (CMM) framework

PSP Performance Analysis Report

The Personal Software Process (PSP) is a structured software development process that is intended to help software engineers understand and improve their performance, by using a disciplined, data-driven procedure. The PSP was created by Watts Humphrey to apply the underlying principles of the Software Engineering Institute’s (SEI) Capability Maturity Model (CMM) to the software development practices of a single developer. It gives software engineers the process skills necessary to work on a Team Software Process (TSP) team. PSP training includes eight assignments in two courses – PSP Fundamentals and PSP Advanced. The report includes final analysis of all the data that was gathered during the training

An approach to reconcile the agile and CMMI contexts in product line development

Software product line approaches produce reusable platforms and architectures for products set developed by specific companies. These approaches are strategic in nature requiring coordination, discipline, commonality and communication. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifies "what" we must have into account to achieve the disciplined processes (among others things). On the other hand, the agile context is playing an increasingly important role in current software engineering practices, specifying "how" the software practices must be addressed to obtain agile processes. In this paper, we carry out a preliminary analysis for reconciling agility and maturity models in software product line domain, taking advantage of both.Postprint (published version

Kematangan Industri Perangkat Lunak Indonesia (KIPI v1.0) Dan Capability Maturity Model (CMM)

Persaingan industri perangkat lunak saat ini mulai berkembang. Kemampuan untuk meningkatkan produksi perusahaan mulai menunjukan perubahan yang signifikan. Dalam dunia industri global telah dikenal CMM sebagai model kematangan sebuah perusahaan dalam mengembangkan perangkat lunak. Negara-negara di dunia telah banyak menetapkan CMM sebagai standar dalam pengembangan perangkat lunak. Beberapa perusahaan mulai mensyaratkan suatu perusahaan yang mengikuti tender pengembangan perangkat lunak harus memiliki sertifikat CMM minimal level dua dari lima level. Di Indonesia, pemerintah mulai melakukan terobosan-terobosan baru dengan mengadopsi CMM sebagai standar pengembangan perangkat lunak dalam negeri dan menyesuaikan penerapannya dengan situasi serta kondisi di Indonesia. Penyesuaian yang dilakukan pemerintah dengan memecah level CMM dari level lima menjadi level sepuluh yang dikenal sebagai KIPI v1.0 (Kematangan Industri Perangkat Lunak Indonesia). Pemecahan level ini dengan pertimbangan bahwa pelaku bisnis industri perangkat lunak di Indonesia mayoritas perusahaan-perusahaan kecil, sehingga diharapkan pemetaan dari kematangan industri perangkat lunak dapat lebih mengakomodir kemampuan industri perusahaan-perusahaan industri di Indonesia

Software Team Development in the Capability Maturity Model,

As software development organizations become more process-oriented they usually discover that they must address people and team development in an expanded and more systematic manner. The software Capability Maturity Model (CMM®) developed by the Software Engineering Institute specifies in great detail what needs in the system development life cycle; how it is done is greatly dependent on people and teams. This paper discusses team development issues for organizations to consider as they pursue higher maturity levels

A Case Study of Strategic Metrics Use in a CMM-Based Outsourcing Environment

IT firms that specialize in outsourcing must provide assurances to their customers that they are adding value to that business relationship. The purpose of this paper is to describe a practical set of metrics that are focused on customer satisfaction and that are easily understood by both customer and developer organizations. The metrics established by Keane, Inc., a large US-based IT services firm, are based upon the goals and concepts of the Software Engineering Institute\u27s (SEI) Capability Maturity Model (CMM®) for software

Reconciling agility and discipline in COTS selection processes

Currently, information systems are mainly built by integrating or customizing commercial off-the-shelf (COTS) components acquired or licensed from the marketplace. The processes necessary to steer a suitable acquisition are different from traditional software development processes. Among them, we are interested in the process of selection of COTS components. COTS selection requires discipline to coordinate the selection team and the set of new activities that are necessary to support a successful selection. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifiesPeer ReviewedPostprint (published version