Evaluation of the Applicability of CM3: Emergency Problem Management within the Industry

Software has become one of the main villains of many organizational problems, emergencies and crises. Despite this, there is only one process model defining how to manage emergency software problems. It is CM 3 : Emergency Problem Management. In this paper, we evaluate the applicability of the CM 3 : Emergency Problem Management model within five companies. Our results show that the model correctly manages the real-life emergency and crisis situations that are dependent on malfunctioning software. This evaluation shows that all the five companies have emergency processes that reflect CM 3 model's architecture, however, to different degrees. Additionally all the five companies have also designated roles that act as focal points of information and decision making during emergencies. Finally, only one company has identified the organizations and systems, which should be affected by the emergency process

[1]  Mira Kajko-Mattsson,et al.  Eliciting CM3: Emergency Problem Management at Scandinavian Airline Systems , 2006, J. Res. Pract. Inf. Technol..

[2]  M. Kajko-Mattsson,et al.  An outline of CM/sup 3/: emergency problem management , 2005, 31st EUROMICRO Conference on Software Engineering and Advanced Applications.

[3]  Joakim Snygg,et al.  Comparing two software emergency process models , 2012, 2012 International Conference on Software and System Process (ICSSP).

[4]  David A. Patterson,et al.  Embracing Failure: A Case for Recovery-Oriented Computing (ROC) , 2001 .

[5]  Mira Kajko-Mattsson,et al.  Motivating the corrective maintenance maturity model (CM/sup 3/) , 2001, Proceedings Seventh IEEE International Conference on Engineering of Complex Computer Systems.

[6]  Mira Kajko-Mattsson.  Corrective Maintenance Maturity Model: Problem Management , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[7]  Thierry C. Pauchant,et al.  Recent research in crisis management: a study of 24 authors' publications from 1986 to 1991 , 1993 .

[8]  David Lorge Parnas,et al.  Evaluation of safety-critical software , 1990, CACM.

[9]  Anne H. Reilly.  Preparing for the worst: the process of effective crisis management , 1993 .

[10]  Denis D. Smith,et al.  Beyond contingency planning: towards a model of crisis management , 1990 .

[11]  Mira Kajko-Mattsson,et al.  Common concept apparatus within corrective software maintenance , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).

[12]  Mira Kajko-Mattsson,et al.  An Outline of CM3: Emergency Problem Management , 2005, EUROMICRO-SEAA.

[13]  Christine M. Pearson,et al.  Reframing Crisis Management , 1998 .

[14]  E. Quarantelli.  DISASTER CRISIS MANAGEMENT: A SUMMARY OF RESEARCH FINDINGS , 1988 .

[15]  M. Kajko-Mattsson,et al.  CM3: Emergency problem management - A scenario-based evaluation , 2012, 2012 8th International Conference on Information Science and Digital Content Technology (ICIDT2012).