Browse > Article
http://dx.doi.org/10.9708/jksci.2014.19.2.209

Evaluation the Relationship of Software Engineering Level and Project Performance by Organization Change Management  

Kim, Seung-Gweon (SW Engineering Center of National IT Promotion Agency)
Yoon, Jong-Soo (School of Business Administration, Kangnam University)
Cho, Kwun-Ik (School of Information Sciences, Dongduk Women's University)
Abstract
With rapid convergence of information technology and expending role of software, many organizations have taken interested in We explore the relationship between the level of change awareness and deployment of software process improvement (SPI) approaches using a competing values framework. To measure awareness level of organization's change, DICE framework which provides means for predicting the outcome of change management initiatives is used. The four factors for organizaton's change: duration, integrity, commitment, and effort are evaluated and a score is calculated. In this paper, we apply the DICE(R) score as an independent variable to predict the outcome of a software process improvement. Our results indicated that the Organization have a higher chance of success have the better outcome in software process improvement.
Keywords
Software Process Improvement; DICE(R) framework; Software Engineering Level; Bootstrap; Oneway ANOVA;
Citations & Related Records
연도 인용수 순위
  • Reference
1 Ravichandran, T. and Rai, A., "Total Quality management in information systems development: key constructs and relationships," Journal of Management Information Systems, Vol. 24, No. 3, Winter 1999-2000, pp. 81-415.   DOI   ScienceOn
2 SEI. "Maturity Profile Reports: CMMI v1.2/V1.3 Class A Appraisal Results." SEI.Caregie Mellon Univ, March, 2013.
3 SEC, "Software Engineering White Book : Korea 2013, Software Engineering Center, p. 6, 2013.
4 SEI, Process Maturity Profile: Software CMM 2004, Mid-year Update, SEI., Caregie Mellon Univ., 2004.
5 Aaen, I., Arendt, J. Mathiassen, L., and Ngwenyama, O., "A conceptual MAP of software process improvement," Scandinavian Journal of Information Systems, Vol. 13, 2001, pp.79-99.
6 Hansen, B., Rose, J. and Tjornehoj, G., "Prescription, description, reflection: the shape of the software process improvement field," International Journal of Information Management, Vol. 24, No. 6, 2004, pp. 457-472.   DOI   ScienceOn
7 Nielsen, P.A. and Norbjerg J., "Software process maturity and organizational politics," in: Proceedings of the IFIP TC8/WG8.2 Working Conference on Realigning Research and Practice in Information Systems Development: The Social and Organizational Perspective, 2001, pp. 221- 240.
8 Harold L. Sirkin, Perry Keenan, and Alan Jackson, "The Hard Side of Change Management," Harvard Business Review Online, april 2005.
9 SEI, "CMMI for Development, Version 1.3" Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 2010.
10 Bartlomiej, Z. and Geoffrey, D., "Rolling the DICE for Agile Software Projects," XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in Software Engineering, 2006, pp. 114-122
11 Madeyski, L. and Biela W., "Capable Leader and Skilled and Motivated Team Practices to Introduce eXtreme Programming," CEE-SET, 2007, pp. 96-102.
12 El Emam, Khaled, and Andreas Birk. "Validating the ISO/IEC 15504 measures of software development process capability." Journal of Systems and Software 51.2 (2000): 119-149.
13 Dennis R. Goldenson, Herbsleb, D. James, "After the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success", Technical report CMU/SEI-95- TR-009, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 1995.
14 Humphrey, W. S., Snyder, T. R., & Willis, R. R. (1991). Software process improvement at Hughes Aircraft. Software, IEEE, 8(4), 11-23.
15 Lawlis, P., Flowe, R. and Thordahl, J. (1995), A Correlational Study of the CMM and Software Development Performance, Crosstalk, Vol. 8, No. 9, September, 1995, pp 21-25
16 Clark, B. K. (1997). The effects of software process maturity on software development effort.
17 Diaz, M., & Sligo, J. (1997). How software process improvement helped Motorola. Software, IEEE, 14(5), 75-81.
18 Brodman, J. G., & Johnson, D. L. (1995). Return on investment (ROI) from software process improvement as measured by US industry. Software Process: Improvement and Practice, 1(1), 35-47.
19 Mathiassen, L., Ngwenyama, O. K., & Aaen, I. (2005). Managing change in software process improvement. Software, IEEE, 22(6), 84-91.   DOI   ScienceOn