Abstract
Software process improvement and software process assessment have received special attention since the 1980s. Some models have been created, but these models rest on a normative approach, where the decision-maker's participation in a software organization is limited to understanding which process is more relevant to each organization. The proposal of this work is to present the MCDA-C as a constructivist methodology for software process improvement and assessment. The methodology makes it possible to visualize the criteria that must be taken into account according to the decision-makers' values in the process improvement actions, making it possible to rank actions in the light of specific organizational needs. This process helped the manager of the company studied to focus on and prioritize process improvement actions. This paper offers an empirical understanding of the application of performance evaluation to software process improvement and identifies complementary tools to the normative models presented today.
Highlights
Software process improvement (SPI) and software process assessment (SPA) have received special attention from government, researchers and industries (Staples et al, 2007; Coleman et al, 2008; Habra et al, 2008; Niazi et al, 2010)
Despite the importance and the interest, when we looked for statistics about the number of software organizations that have adopted one of the models, we have noticed that few have done so
This article summed up the components and assessment methods of two CMMI and SPICE models, the most used by software organizations
Summary
Software process improvement (SPI) and software process assessment (SPA) have received special attention from government, researchers and industries (Staples et al, 2007; Coleman et al, 2008; Habra et al, 2008; Niazi et al, 2010). Published works certify the economy provided by the improvement in software quality (Pitterman, 2000). Since the 1980s several models have been developed with this intention. The most used by software organizations are CMMI and SPICE (Kuilboer et al, 2000). The CMM and CMMI models were developed by the Software Engineering Institute (SEI) of Canergie Mellon University and SPICE by the International Organization for Standardization (ISO). Despite the importance and the interest, when we looked for statistics about the number of software organizations that have adopted one of the models, we have noticed that few have done so. Lack of adoption can be seen by examining the SEI CMMI appraisal data for the years 2002–2006, in which period just 1581 CMMI appraisals were reported to the SEI (Coleman et al, 2008)
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Journal of Information Systems and Technology Management
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
