The Quest for Know-How, Know-Why, Know-What and Know-Who: Using KAOS for Enterprise Modelling

Abstract

While the field of information systems engineering is largely focussed on developing methods for complex problems and larger enterprises, less is done to specifically address the needs of smaller organizations like small and medium sized enterprises (SMEs), although they are important drivers of economy. These needs include a better understanding of the processes (knowhow), why things are done (know-why), what concepts are used (know-what) and who is responsible (know-who). In this paper, the KAOS approach is evaluated as not only useful for developing software projects, but with the potential to be used for developing a business architecture or enterprise model. An example of KAOS is given, by way of illustration, and KAOS was applied in a case study by an SME's CEO, which resulted in a set of questions for further research.

Enterprise Architecture for Small and Medium-Sized Enterprises: A Starting Point for Bringing EA to SMEs, Based on Adoption Models

“…To get a holistic overview, these four dimensions should be interrelated. An example of this proposed business architecture layer (Bernaert and Poels 2011b) is given in Fig. 15.…”

Prevention through design: conceptual models for the assessment of a principal designer’s skills, knowledge and experience

“…Declarative knowledge is the factual information that a person knows and can be reported on (Anderson and Schunn, 2000; Hefter et al , 2018). This is often termed as “know what” (Miller, 1990; Baartman and de Bruijn, 2011; Bernaert and Poels, 2011; Śliwa and Kosicka, 2017). On the other hand, procedural knowledge is the connection or use of pieces of declarative knowledge and are usually knowledge that cannot be easily communicated (Baartman and de Bruijn, 2011) and often considered as “know-how” (Miller, 1990; Baartman and de Bruijn, 2011; Bernaert and Poels, 2011; Śliwa and Kosicka, 2017).…”

“…This is often termed as “know what” (Miller, 1990; Baartman and de Bruijn, 2011; Bernaert and Poels, 2011; Śliwa and Kosicka, 2017). On the other hand, procedural knowledge is the connection or use of pieces of declarative knowledge and are usually knowledge that cannot be easily communicated (Baartman and de Bruijn, 2011) and often considered as “know-how” (Miller, 1990; Baartman and de Bruijn, 2011; Bernaert and Poels, 2011; Śliwa and Kosicka, 2017). Tacit knowledge (Polanyi, 1958; Grant, 2007; Ferrari et al , 2016) is a critical part of this knowledge type.…”

A Model of Knowledge Acquisition in the Maintenance Department of a Production Company

“…According to Bernaert and Poels (Bernaert & Poels, 2011), we can distinguish four types of knowledge depending on the identification of acquired information: know what (structural knowledge based on models), know why (interpretation of collected information), know how (knowledge of activity procedure), know who (identification of individuals who could help in problem solving).…”