Improving the Software Problem Management Process: A Case Study

1. ISO/IEC 12207: Information Technology Software Life-Cycle Processes. ISO/IEC Copyright Office (1995)

   Google Scholar 

2. Office of Government Commerce: ITIL Service Delivery. The Stationary Office, UK (2002)

   Google Scholar 

3. Jackson, A.L., Lyon, G., Eaton, J.: Documentation meets a knowledge base: blurring the distinction between writing and consulting (a case study). In: SIGDOC 1998: Proceedings of the 16th Annual International Conference on Computer Documentation, pp. 5–13. ACM Press, New York (1998)

   Chapter  Google Scholar 

4. Saunders, A.: Online solutions: looking to the future of knowledgebase management. In: SIGUCCS 2004: Proceedings of the 32nd Annual ACM SIGUCCS Conference on User Services, pp. 194–197. ACM Press, New York (2004)

   Chapter  Google Scholar 

5. Mays, R.G., Jones, C.L., Holloway, G.J., Studinski, D.P.: Experiences with defect prevention. IBM Syst. J. 29(1), 4–32 (1990)

   Article  Google Scholar 

6. Office of Government Commerce: ITIL Service Support. The Stationary Office, UK (2002)

   Google Scholar 

7. Florac, W.: Software quality measurement a framework for counting problems and defects. Technical Report CMU/SEI-92-TR-22 (1992)

   Google Scholar 

8. Hirmanpour, I., Schofield, J.: Defect management through the personal software process. Crosstalk, The Journal of Defense Software Engineering (2003)

   Google Scholar 

9. Leszak, M., Perry, D.E., Stoll, D.: A case study in root cause defect analysis. In: ICSE 2000: Proceedings of the 22nd International Conference on Software Engineering, pp. 428–437. ACM Press, New York (2000)

   Chapter  Google Scholar 

10. Zhen, J.: It needs help finding root causes. Computerworld 39(33), 26 ID: EBSCO Academic Search Elite (2005)

    Google Scholar 

11. Jalote, P.: CMM in Practice, Processes for Executing Software Projects at Infosys. Addison-Wesley, Reading (2000)

    Google Scholar 

12. Sandusky, R.J., Gasser, L.: Negotiation and the coordination of information and activity in distributed software problem management. In: GROUP 2005: Proceedings of the 2005 International ACM SIGGROUP Conference on Supporting Group Work, pp. 187–196. ACM Press, New York (2005)

    Chapter  Google Scholar 

13. Kajko-Mattsson, M.: Problem management maturity within corrective maintenance. Journal of Software Maintenance and Evolution - research and practise 14(3), 197–227 (2002), Article; English; ID: Web of Science (ISI)

    Google Scholar 

14. Kajko-Mattsson, M., Forssander, S., Olsson, U.: Corrective maintenance maturity model (cm3): maintainer’s education and training. In: ICSE 2001: Proceedings of the 23rd International Conference on Software Engineering, Washington, DC, USA, pp. 610–619. IEEE Computer Society, Los Alamitos (2001)

    Chapter  Google Scholar 

15. Kajko-Mattsson, M., Ahnlund, C., Lundberg, E.: Cm3: Service level agreement. In: ICSM 2004: Proceedings of the 20th IEEE International Conference on Software Maintenance, Washington, DC, USA, pp. 432–436. IEEE Computer Society, Los Alamitos (2004)

    Chapter  Google Scholar 

16. Jäntti, M., Toroi, T.: Uml-based testing: A case study. In: Proceedings of NWUML 2004. 2nd Nordic Workshop on the Unified Modeling Language, pp. 33–44. Turku Centre for Computer Science, Turku (2004)

    Google Scholar 

17. Kruchten, P.: The Rational Unified Process: An Introduction. Addison-Wesley, Reading (2001)

    Google Scholar 

18. Yin, R.: Case Study Research: Design and Methods. Sage Publishing, Beverly Hills (1994)

    Google Scholar 

19. Eisenhardt, K.: Building theories from case study research. Academy of Management Review 14, 532–550 (1989)

    Article  Google Scholar 

20. Garvin, D.A.: Building a learning organization. Harward Business Review, 78–91 (1993)

    Google Scholar 

21. Gasston, J., Halloran, P.: Continuous software process improvement requires organisational learning: An australian case study. Software Quality Control 8(1), 37–51 (1999)

    Google Scholar 

Download references