JSEA  Vol.3 No.6 , June 2010
The Exploratory Analysis on Knowledge Creation Effective Factors in Software Requirement Development
Abstract: The knowledge creation effective factors were found in both necessary elements for stimulus of knowledge creation and the key influencing factors of software project success. The research was carried with the specific successful practices of Microsoft Corporation and William Johnson’s analysis of R & D project knowledge creation. The knowledge creation effective factors in requirement development project are clarified through deeply interviewing the software enterprises in Guangdong province as well as other corporate information departments. The effective factors are divided with R & D project knowledge creation model in the view of organizational, team, personal and technical four levels through literature research and interview in enterprises, and the empirical study was done with questionnaire and exploratory analysis.
Cite this paper: nullJ. Wan and R. Wang, "The Exploratory Analysis on Knowledge Creation Effective Factors in Software Requirement Development," Journal of Software Engineering and Applications, Vol. 3 No. 6, 2010, pp. 580-587. doi: 10.4236/jsea.2010.36067.

[1]   X. M. Li, L. Y. Sun and Y. L. Wang, “Research on Software Requirement Management Based on Knowledge Management,” Management of Research and Deve- lopment, Vol. 17, No. 2, February 2005, pp. 28-32, 39.

[2]   Swebok, “Guide to Software the Software Engineering Body of Knowledge,” 2004.

[3]   X. H. Zhang, “Software Development Process and Mana- gement,” Tsinghua University Press, Beijing, 2005.

[4]   M. A. Cusumano and R. W. Selby, “The Secrets of Micro- soft,” Free Press, New York, 1995.

[5]   G. von Krogh, K. Ichijo and I. Nonaka, “Enabling Knowledge Creation: How to Unlock the Mystery of Tacit Knowledge and Release the Power of Innovation,” Oxford University Press, New York and Oxford, 2000.

[6]   J. P. Wan, Q. J. Liu, D. J. Li and H. B. Xu, “Research on Knowledge Transfer Influencing Factors in Software Process Improvement,” Journal of Software Engineering and Applications, Vol. 3, No. 2, February 2010, pp. 134- 140.

[7]   J. P. Wan, H. Zhang, D. Wan and D. Y. Huang, “Research on Knowledge Creation in Software Requirement Deve- lopment,” Journal of Software Engineering and Applica- tions, Vol. 3, No. 5, May 2010, pp. 487-494.

[8]   I. Nonaka and H. Takeuchi, “The Knowledge Creating Company,” Oxford University Press, New York, 1995.

[9]   W. Johnson, “Technological Innovation and Knowledge Creation: A Study of Enabling Condition and Processes of Knowledge Creation in Collaborative R & D Project,” Ph.D. Dissertation, York University, Toronto, 2000.

[10]   H. G. Chen, et al., “The Science and Art of Software De- velopment,” Electronic Industry Press, Beijing, 2002.

[11]   Y. S. Zhang, “The Way of System Analyzer,” Electronic Industry Press, Beijing, 2006.

[12]   W. M. Cohen and D. Levinthal, “Absorptive Capacity: A New Perspective on Learning and Innovation,” Adminis- trative Science Quarterly, Vol. 35, No. 1, 1990, pp. 128- 152.

[13]   Y. H. Ke, “Research on Imparting Knowledge Transfer across Team: Based Information Systems,” Master Thesis, Information Management of Institute, National Sun Yat-sen University, Taiwan, 2005.

[14]   P. Sawyer and G. Kotonya, “Swebok: Software Require- ments Engineering Knowledge Area Description Version 0.5,” IEEE and ACM Project on Software Engineering Body of Knowledge, San Francisco, July 1999.

[15]   J. P. Wan, “Research on Software Product Support Struc- ture,” Journal of Software Engineering and Applications, Vol. 2, No. 3, October 2009, pp.174-194.

[16]   B. Jayatilaka, “The Role of Developer and User Know- ledge Domains and Learning in Systems Development,” AMCIS2000, 2000, pp.1323-1329.

[17]   S. Alshawi and W. Al-Karaghouli, “Managing Know- ledge in Business Requirements Identification,” Logis- tics Information Management, Vol. 16, No. 5, 2003, pp. 341-349.

[18]   H. Barki and J. Hartwick, “User Participation, Conflict and Conflict Resolution,” Information Systems Research, Vol. 5, No. 2, December 1994, pp. 422-440.

[19]   P. J. Guinan, J. G. Cooprider and S. Faraj, “Enabling Software Development Team Performance during Requi- rement Definition: A Behavioral vs. Technical Approach,” Information Systems Research, July 1998, pp. 101-125.

[20]   R. Hirschheim and H. K. Heinz, “Realizing Emancipatory Principles in Information Systems Development: The Case for ETHICS,” Management Information Systems Quar- terly, Vol. 18, No. 1, March 1994, pp. 83-109.

[21]   Standish Group, “Chaos 1994,” The Standish Group International, Massachusetts, 1994.

[22]   Standish Group, “Chaos,” Standish Group Report, 1995.

[23]   Standish Group, “Chaos: A Recipe to Success,” Standish Group Report, 1999.

[24]   W. S. Humphrey, “Managing the Software Process,” Reading, Addison-Wesley, Massachusetts, 1989, pp. 19- 24.

[25]   L. L. Constantine, “Beyond Chaos: The Expert Edge in Managing Software Development,” Addison-Wesley, Boston, 2001.

[26]   I. V. Eriksson and G. W. Dickson, “Knowledge Sharing in High Technology Company,” American Conference on Information System, Vol. 36, No. 2, 2000, pp. 1330-1335.