Knowledge Capture
As modern IT projects increase in complexity, and traditional approaches continue to be followed, the problems of accurate requirements capture and the extraction of expert skills become ever more acute.
Those who follow traditional approaches to IT system development find it difficult to manage complex requirements and skills capture because of the limitations inherent with classic documentation (of requirements) and the highly skilled nature of system coding.
The Erudine Behaviour Engine technology was created with precisely these problems in mind.
Tacit knowledge
“Tacit knowledge can be defined as knowledge that is not made explicit, because it is highly personal, not easily visible or expressible, and usually requires joint or shared activities to transmit it”
The isolation of expert skills – tacit knowledge - is such a significant obstacle in traditional system development because the proportion of tacit knowledge required increases with the complexity of the project.
Erudine’s technology does not seek to make explicit a user’s tacit knowledge. Instead, it directly captures knowledge as part of a learning process through its unique Conclusion & Justification system.
With traditional approaches it is also difficult to accurately capture, test, and record system requirements. Here, it is largely the process itself that is the problem. Requirements are described to a system developer by an expert and it is then down to the developer to translate them into the system. This can make it difficult for the developer to ensure that all requirements are met, recorded and tested, and consumes a large amount of time.
The accurate capture, testing, and recording of requirements are completely automated in Erudine's Behaviour Engine technology.