EXPLICIT AS ENABLER FOR UNDERSTANDING THE TACIT

Knowledge that can be expressed in words and numbers (i.e., explicit knowledge) only represents the tip of the iceberg in organizational knowledge. Explicit knowledge may be communicated in formal, systematic language, using standard notations. This paper reviews how explicit knowledge is used within software engineering, and has found that this tip is important to store organizational knowledge, discuss improvements, and communicate competences. We further discuss how the tip can be viewed as a facilitator for understanding tacit knowledge, such as context dependent actions, commitments, and involvement. To support these arguments, we have studied software engineering units within Ericsson AB during the period 2005-2007 to learn more about software engineering process descriptions and notations in practice. Findings indicate that unambiguous process descriptions are dependent oil obvious software process notations and that the explicit nature of described software processes serve as a vital catalyst in initiating discussions of tacit knowledge.