Artifact-based software process improvement and management: a method proposal

When it comes to software process improvement (SPI), process engineers look for SPI methods to support process analysis, design, realization, deployment, and management. Although a number of different SPI methods and models exist, process engineers tend to view these as too generic, too large, or a poor fit for the organization in which SPI is conducted. A strategy to overcome these shortcomings is to concentrate on the artifacts, which precisely define the desired outcomes, rather than on specific methods. In this paper, we present the Artifact-based Software Process Improvement & Management (ArSPI) model that provides a unified perspective on SPI and company-wide software process management (SPM), the required key artifacts, and the life cycle models. ArSPI is shown to be of practical support to industry who called for a practical way to define the interfaces between SPI projects. This paper concludes with an example of how ArSPI paved the way for several organizations through applying the model in real-world SPI-projects.

[1]  Marco Kuhrmann,et al.  The Process Enactment Tool Framework - Transformation of software process models to prepare enactment , 2014, Sci. Comput. Program..

[2]  Jürgen Münch,et al.  Experiences and results from tailoring and deploying a large process standard in a company , 2008, Softw. Process. Improv. Pract..

[3]  Marco Kuhrmann,et al.  A Survey on the Application of the V-Modell XT in German Government Agencies , 2011, EuroSPI.

[4]  Cmmi Product Team.  CMMI for Development, Version 1.2 , 2010 .

[5]  Marco Kuhrmann,et al.  Who Cares About Software Process Modelling? A First Investigation About the Perceived Value of Process Engineering and Process Consumption , 2013, PROFES.

[6]  Mario Piattini,et al.  Software Process Improvement: The Competisoft Project , 2007, Computer.

[7]  Ivan Rozman,et al.  Managing the complexity of SPI in small companies , 2000 .

[8]  Manfred Broy,et al.  A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering , 2010, MODELS'10.

[9]  Onur Demirörs,et al.  A Detailed Software Process Improvement Methodology: BG-SPI , 2011, EuroSPI.

[10]  Marco Kuhrmann.  ArSPI: An Artifact Model for Software Process Improvement and Management , 2013 .

[11]  D. Ross Jeffery,et al.  An exploratory study of why organizations do not adopt CMMI , 2007, J. Syst. Softw..

[12]  Rory O'Connor,et al.  Investigating software process in practice: A grounded theory perspective , 2008, J. Syst. Softw..

[13]  J. L. Boria.  A framework for understanding software process improvement's return on investment , 1997, Innovation in Technology Management. The Key to Global Leadership. PICMET '97.

[14]  Jarmo J. Ahonen,et al.  LAPPI: A light‐weight technique to practical process modeling and improvement target identification , 2013, J. Softw. Evol. Process..