zbMATH — the first resource for mathematics

Using a qualitative research method for building a software maintenance methodology. (English) Zbl 1009.68930
Summary: This article explains our experience of using Action Research to develop a software maintenance methodology involving two organizations: a group of university researchers and a software services organization. The concept of ‘methodology’ comprises a wide set of elements whose identification, definition and integration is not a trivial task, due to the magnitude of the project and to the different nature of the organizations. The use of Action Research was a key factor in the progress of the research and has been essential in the adoption of the methodology within the software services organization.
68U99 Computing methodologies and applications
68N01 General topics in the theory of software
68N15 Theory of programming languages
68P30 Coding and information theory (compaction, compression, models of communication, encoding schemes, etc.) (aspects in computer science)
Full Text: DOI
[1] Practical Software Maintenance. Best Practices for Managing your Investment. Wiley: New York, 1997.
[2] Practices of software maintenance. Proceedings International Conference on Software Maintenance. IEEE Computer Society Press: Los Alamitos, CA, 1998; 139-245. · doi:10.1109/ICSM.1998.738502
[3] Sourcing. World Class IT Service Management Guide, (ed.). ten Hagem & Stam Publishers: The Hague, The Netherlands, 2000.
[4] Schach, Journal of Software Maintenance: Research and Practice 12 pp 24– (2000)
[5] Understanding and predicting the process of software maintenance releases. Proceedings International Conference on Software Engineering. IEEE Computer Society Press: Los Alamitos, CA, 1996; 464-474.
[6] Niessink, Journal of Software Maintenance: Research and Practice 12 pp 103– (2000)
[7] Managing the software maintenance process. World Class IT Service Management Guide. (ed.). ten Hagem & Stam Publishers: The Hague, The Netherlands, 2000.
[8] Organizational Development: Behavioral Science Interventions for Organization Improvement. Prentice-Hall: London, 1996.
[9] Avison, Communications of the ACM 42 pp 94– (1999)
[10] Seaman, IEEE Transactions on Software Engineering 25 pp 557– (1999)
[11] Kock, Information Technology and People 14 pp 6– (2001) · doi:10.1108/itp.2001.16114aaa.001
[12] What is Participatory Action Research? Action Research International. http://www.scu.edu.au/schools/sawd/ari/ari-wadsworth.html [12 June 2002].
[13] Guidelines for Planning Action Research Projects. http://archon.educ.kent.edu/Oasis/Pubs/0200-08.html [12 June 2002].
[14] The OPEN Process Specification. ACM Press and Addison-Wesley: Essex, UK, 1997.
[15] European Commission. Employment in Europe 2001?Recent trends and prospects. Office for Official Publications of the European Communities, Luxembourg. http://europa.eu.int/comm/employment_social/empl&esf/docs/empleurope2001_en.pdf [12 June 2002].
[16] IEEE. Standard for Software Maintenance, IEEE Std. 1219-1992. The Institute of Electrical and Electronics Engineers, Inc.: New York, 1992.
[17] ISO/IEC. Information Technology-Software Life Cycle Processes, ISO/IEC 12207. Swiss, 1995.
[18] Software Engineering Guides. Prentice-Hall: London, 1996. · Zbl 0874.68027
[19] Radatz, Crosstalk, the Journal of Defense Software Engineering 8 pp 2– (1995)
[20] Ministerio de Administraciones Públicas. Métrica 3: guía de referencia. Tecnos: Madrid, 2001. http://www.map.es/csi/metrica3 [12 February 2002].
[21] Mantema: A complete rigorous methodology for supporting maintenance based on the ISO/IEC 12207 standard. Proceedings Third European Conference on Software Maintenance and Reengineering. IEEE Computer Society Press: Los Alamitos, CA, 1999; 205-210.
[22] Software Engineering: a Practitioner’s Approach (3rd edn). McGraw-Hill, 1993.
[23] Mantenimiento del Software. Modelos, técnicas y métodos para la gestión del cambio. Ra-Ma: Madrid, 2000.
[24] Polo, ACM Software Engineering Notes 24 pp 84– (1999)
[25] Cuestionario para la identificación de riesgos en proyectos de mantenimiento. Actas de las V Jornadas de Ingeniería del Software y Bases de Datos, Universidad de Extremadura, Cáceres, Spain, 2000; 30-35.
[26] Euromethod project. Euromethod ver 1. http://projekte.fast.de/Euromethod/ [12 June 2002].
[27] Planning the non-plannable maintenance. Project Control: the Human Factor, Proceedings of the Combined 11th European Software Control and Metrics Conference and the 3rd SCOPE Conference on Software Product Quality (ESCOM-SCOPE 2000). Shaker Publishing: Maastricht, The Netherlands, 2000; 49-57.
[28] Piattini, Software Quality Journal 9 pp 79– (2000)
[29] An empirical study with object-relational databases metrics. 4th International Workshop on Quantitative Approaches in Object-Oriented Software Engineering (in ECOOP’2000), Centre de recherche informatique de Montreal, Montreal, Québec, 2000; 39-46.
[30] Díaz, Information Systems Journal 26 pp 15– (2001)
[31] Postgraduate programs using action research. Action learning, action research and process management: theory, practice, praxis, Zuber-Skerritt (ed.), Faculty of Education, Griffith University, Brisbany, Australia, 2000.
[32] Polo, Journal of Software Maintenance and Evolution: Research and Practice 13 pp 77– (2001)
[33] Audit of software maintenance process. Auditing Information Systems, (ed.). Idea Group Publishing: Hershey, PA, 2001.
[34] Assessment of maintenance maturity in IT departments of public entities: Two case studies. Proceedings of the 3rd International Conference on Product Focused Software Process Improvement (Lecture Notes in Computer Science, vol. 2188). Springer: Berlin, 2001; 86-97. · Zbl 1029.68860
This reference list is based on information provided by the publisher or from digital mathematics libraries. Its items are heuristically matched to zbMATH identifiers and may contain data conversion errors. It attempts to reflect the references listed in the original paper as accurately as possible without claiming the completeness or perfect precision of the matching.