TACIT KNOWLEDGE EXTRACTION FOR SOFTWARE REQUIREMENT SPECIFICATION

Öz

Knowledge extraction is becoming an important research area for the organizations in order to get and share the knowledge. Most important and useful part of the knowledge extraction is dedicated to tacit knowledge extraction. There are already known methods to acquire the tacit knowledge. Yet, these methods are mostly general approaches applicable to all the areas in need of tacit knowledge extraction and become too abstract when applied to a specific domain. One such specific domain is the requirement specification process for the software project development. Our own experiences in the area as well as the scientific researches have shown that Software Requirement Specification (SRS) process has field-specific problems that need to be eliminated by using the suitable tacit knowledge extraction techniques. For example, the experts and/or users may not have a clear idea of their requirements. They may also be technically unsophisticated or have different vocabularies than the software developers. Benefiting from the existing body of academic literature in the related fields, as well as co-authors’ experience from their domains of practice, this paper aims to find the concrete methods for extracting the tacit knowledge in the area of software project development with specific implications for these academic fields and practice domains, as well as more general suggestions for all related or concerned

Anahtar Kelimeler

• Tacit Knowledge extraction, Expert Knowledge, Software Requirement Specification (SRS), Knowledge Engineer (KE)

Kaynakça

1. Gourlay, Stephen (2002), “Tacit knowledge, tacit knowing or behaving?”, Kingston Business
2. School, Kingston upon Thames,UK Nonaka, Ikujiro; Takeuchi, Hirotaka (1995), The knowledge creating company: how Japanese companies create the dynamics of innovation, New York: Oxford University Press
3. Tagger, Ben, An Enquiry into the Extraction of Tacit Knowledge, http://www.cs.ucl.ac.uk/staff/B.Tagger/FinalIMR.pdf [Accessed 7.01.2011]
4. Wikipedia (2011), Requirement Analysis, http://en.wikipedia.org/wiki/Requirements_analysis [Accessed 7.01.2011]
5. Epistemics (2003), Knowledge Acquisition, http://www.epistemics.co.uk/Notes/63-0-0.htm [Accessed 7.01.2011]
6. Irick, Michael L. (2007), “Managing Tacit Knowledge In Organizations”, Journal of Knowledge
7. Management Practice, Vol. 8, No. 3, pp.1-5. Memon, Nasrullah , Knowledge Elicitation – Converting Tacit Knowledge to Explicit, http://www.mip.sdu.dk/~memon/10-2.pdf [Accessed 7.01.2011]
8. Usability Body of Knowledge (2007), Card Sorting, http://www.usabilitybok.org/methods/card-sorting [Accessed 12.02.2011]

9. Wikipedia (2011),Use case diagram, http://en.wikipedia.org/wiki/Use_case_diagram [Accessed 07.01.2011]
10. Institute for Human and Machine Cognition (2006), The Theory Underlying Concept Maps and How to Construct and Use Them, http://cmap.ihmc.us/publications/researchpapers/theorycmaps/theoryunderlyingconceptmaps.htm Accessed 23.02.2011]
11. Becerra-Fernandez, et al (2004), Dekai Wu (2007), Knowledge Management www.cs.ust.hk/~dekai/600G/notes/KM_Slides_Ch10.pdf [Accessed 12.02.2011]
12. Gravity Freedom (2011), Card Sorting Your Way to an Improved User Experience http://gravityfreedom.com/2007/06/14/card-sorting-your-way-to-an-improved-user-experience/ Accessed 12.02.2011]
13. Study Habits (2011), How To Mind Map http://www.study-habits.com/how-to-mind-map [Accessed 12.02.2011]