JSEA  Vol.3 No.5 , May 2010
Research on Knowledge Creation in Software Requirement Development
ABSTRACT
After field survey and literature review, we found that software requirement development (SRD) is a knowledge creation process, and knowledge creation theory of Nonaka is appropriate for analyzing knowledge creating of SRD. The characteristics of knowledge in requirement elicitation process are analyzed, and dissymmetric knowledge of SRD is discussed. Experts on requirement are introduced into SRD process as a third knowledge entity. In addition, a knowledge creation model of SRD is put forward and the knowledge flow and the relationship of entities of this model are illustrated. Case study findings are illustrated in the following: 1) The necessary diversity of the project team can facilitate the implementation of the SRD. 2) The introduction of experts on requirement can achieve the transformation of knowledge effectively, thus helping to carry out the SRD. 3) Methodology and related technologies are important for carrying out the SRD.

Cite this paper
nullJ. Wan, H. Zhang, D. Wan and D. Huang, "Research on Knowledge Creation in Software Requirement Development," Journal of Software Engineering and Applications, Vol. 3 No. 5, 2010, pp. 487-494. doi: 10.4236/jsea.2010.35055.
References
[1]   M. Polanyi, “Personal knowledge,” University of Chicago Press, Chicago, 1958.

[2]   V. Allee, “The Knowledge Evolution: Expanding Organi- zational Intelligence,” Butterworth Heinemann, Boston, 1997.

[3]   I. Nonaka, “The Knowledge Creating Company,” Harvard Business Review, Vol. 69, No. 6, 1991, pp. 96-104.

[4]   X. M. Li, et al. “Research on Software Requirement Management based on Knowledge Management,” R&D Management, Vol. 2, 2005, pp. 28-39.

[5]   J. P. Wan, “Research on Software Product Support Structure,” Journal of Software Engineering and Appli- cations, Vol. 2, No. 3, 2009, pp. 174-194.

[6]   J. P. Wan et al., “Research on Knowledge Transfer Influencing Factors in Software Process Improvement,” Journal of Software Engineering and Applications, 2010, Vol. 3, No. 2, 2010, pp. 134-140.

[7]   I. Nonaka, “A Dynamic Theory of Organizational Kno- wledge Creation,” Organization Science, Vol. 5, No. 1, 1994, pp.14-37.

[8]   I. Nonaka and V. K. Georg, “Perspective—Tacit Knowledge and Knowledge Conversion: Controversy and Advancement in Organizational Knowledge Creation Theory,” Organization Science, Vol. 20, No. 3, 2009, pp. 635-652.

[9]   V. K. Georg, et al. “Enabling Knowledge Creation: How to Unlock the Mystery of Tacit Knowledge and Release the Power of Innovation,” Oxford University Press, New York, 2000.

[10]   P. Zave, “Classification of Research Efforts in Requi- rements Engineering,” ACM Computing Surveys, Vol. 29, No. 4, 1997, pp. 315-321.

[11]   D. C. Gause and G. M. Weinberg, “Exploring Requi- rements: Quality before Design,” Dorset House Publishing Co., Inc, Vancouver, 1989.

[12]   S. L. Pfleeger, “Software Engineering: Theory and Practice,” 2nd Edition, Higher Education Press, Beijing, 2002.

[13]   S. Alshawi and W. A. Karaghouli, “Managing Know- ledge in Business Requirements Identification,” Logistics Information Management, Vol. 16, No. 3, 2003, pp. 341- 349.

[14]   Q. F. Shi, et al. “Characteristics and Modal Analysis of Implicit Knowledge Transfer,” Studies in Dialectics of Nature, Vol. 20, No. 2, 2004, pp. 62-68.

[15]   X. J. Xv, “On the Transmission of Knowledge,” Studies in Science of Science, Vol. 23, No. 3, 2005, pp. 298-303.

[16]   N. Maiden, et al. “Provoking Creativity: Imagine What Your Requirements Could be Like,” IEEE Software, Vol. 21, No. 5, 2004, pp. 68-75.

 
 
Top