Abstract
During the last few years, many Software Process Improvement methods (SPI) have been presented to increase the quality of products and services provided by a software organization. Current Software Process Improvement (SPI) methods (i.e. ISO 15504, CBA-IPI,...), are difficult to apply to Small and Medium-sized Enterprises (SMES) due to the costs (financial, time, and resource) associated with their application. Also, these methods are principally focused on the assessment stage. This paper presents a new SPI method, called MESOPYME, which main focus is to reduce effort and time on the SPI implementation. This method focuses on the improvement implementation stage, which is based on a concept called Action Package, whose components are described (in Section 2.1.). The results obtained in the application of a Requirements Engineering Action Package in three organizations are also presented.
Similar content being viewed by others
References
Burwick, Diane M. 1999. How to Implement the CMM, Fredericksburg, BPS Publications.
Byrnes, Paul and Philips, Mike. 1996. Software Capability Evaluation Version 3.0: Method Description, Technical Report: CMU/SEI-96-TR-002, Carnegie Mellon University, Software Engineering Institute, Pittsburgh.
Calvo-Manzano, J.A., Cervera, J., San Feliu, T. 1997. Software process improvement: MESOPYME model, Journal of Computing and Information Technology (CIT), 43: 159-165.
Dunaway, D.K. and Masters, S. 1996. CMM-Based Appraisal for Internal Process Improvement (CBA IPI): Method Description, Technical Report: CMU/SEI-96-TR-007, Carnegie Mellon University, Software Engineering Institute, Pittsburgh.
ESSI. 1993. European Software and System Initiative, http://www.cordis.lu/ESPRIT/src/stessi.htm.
ESSI, IBERIA, LAE. 1994. SPIE: Software Process Improvement and Experimentation, ESSI Project: No 10344, February.
ESSI, EROSKI, SCOOP. 1997a. SYMQUAD: System Requirements and Quality Assurance in a Distribution Company, ESSI Project: No 23947, March.
ESSI, Lantik S.A. 1997b. LANHOBEK: Client Relationships and Requirement Management Improvement, ESSI Project: No 24155, March.
ESSI, G.O.C., 1997c. HOSPUR: User Requirements and Reuse in Health Management Systems, ESSI Project: No 24181, March.
Fowler, P. and Patrick, M. 1998. Transition Packages for Expediting Technology Adoption: The Prototype Requirements Management Transition Package, Technical Report: CMU/SEI-98-TR-004, September. Pittsburgh.
Herbsleb, J., Carleton, A., Rozum, J., Siegel, J., and Zubrow, D. 1994. Benefits of CMM-Based Software Process Improvement: Initial Results, Technical Report: CMU/SEI-94-TR-013, August. Pittsburgh.
ISO/IEC. 1998. ISO/IEC Software Process Assessment Information Technology—Version 3.3, JTC1/SC7/ WG10, TR 15504: 1998.
McFeeley, Bob. 1996. IDEALSM: a user'2 guide for software process improvement, Handbook CMU/SEI-96-HB-001, Software Engineering Institute, Carnegie Mellon University, February.
SPIRE. 1997. Software Process Improvement in Regions of Europe, ESSI Project: No. 23873, http://www.cse.dcu.ie/spire.
SPIRE. 1999. Software Process Improvement in Regions of Europe, European Analysis Report v2.0, ESSI Project: No. 23873, Dissemination action, http://www.cse.dcu.ie/spire April.
VASIE. 1994. VASIE: Value Added Software Information for Europe, ESSI Project: No. 24119, http://www.esi.es/VASIE/.
Wieggers, K.E., Sturzenberger, D. C. 2000. A Modular Software Process Mini-Assessment Method, IEEE Software, 171: 62-69.
Zahran, S. 1998. Software Process Improvement: Practical Guidelines for Business Success, Addison-Wesley.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Calvo-Manzano Villalón, J.A., Cuevas Agustín, G., San Feliu Gilabert, T. et al. Experiences in the Application of Software Process Improvement in SMES. Software Quality Journal 10, 261–273 (2002). https://doi.org/10.1023/A:1021638523413
Issue Date:
DOI: https://doi.org/10.1023/A:1021638523413