Creating an expert system's knowledge base is the heart of knowledge engineering. This description covers the first 3 steps of the process at a high level. Orientation Knowledge engineers require orientation to the processes and methodologies that will be used to create the knowledge base for the particular system under construction. Subject matter experts also... Continue Reading →
Expert systems rely on computers to deliver non-expert reasoning, support and guidance to non-expert users. To benefit from this expert knowledge, users must have access to the technology, either directly on their own, or with the help of others. Expert systems are machines Expert systems deliver their output through computers. Paper-based "choose your own adventure" versions... Continue Reading →
Intelligent technologies like expert systems are designed to deliver expert knowledge to non-expert users. Finding good subject matter experts and using them the appropriately are critical to success. The importance of expert knowledge The knowledge engineering process will depend on the availability of expert knowledge. At least one subject matter expert with specialized domain knowledge... Continue Reading →
Knowledge engineers work to capture knowledge from a messy, abstract domain and turn it into logic-based rules structured in a very methodical way within a concrete, tangible knowledge base. Managing scope is a key to success. Managing scope of problems While work is under way to define the problem and potential responses, knowledge engineers must define... Continue Reading →
Expert systems can respond to real world problems. It's important for knowledge engineers to decide on the right problem before work begins. Defining the problem and the response Earlier, we talked about 3 key questions a knowledge engineer should consider: Is this a problem for non-experts that wouldn’t be a problem for experts? Is there a... Continue Reading →
A knowledge engineer's job is to mine domain knowledge from human subject matter experts. The domain knowledge is the knowledge in a particular field of expertise. The Ins and Outs of Domains The domain can't just be "everything" or "all knowledge." It would be too difficult to cover everything in the knowledge base. You don't... Continue Reading →
This post is part of my attempt to create a start to finish* or end-to-end knowledge engineering process description for (legal) expert systems. Problem identification is a great place to start. Problem Identification There's no real methodology involved with identifying a problem. Problems just happen. The knowledge engineer's job is to examine the problem and ask 3... Continue Reading →
It takes a lot of humanity to make machines intelligent. At least, that's true for expert systems. An expert system with an empty knowledge base is actually quite dumb. It depends completely on people to collect its knowledge, put it in the right form, load it up and then look after its ongoing care and feeding.... Continue Reading →
In my last post, I explained how courts could make court technology leapfrogs. In short, they can leapfrog from A (pre-industrial revolution) past B (post-industrial revolution) to C (the information and technology revolution). Courts can do the same thing when it comes to usability. Usability and access to justice Access to justice is a big problem... Continue Reading →
In an age accelerating technological transformation, some courts are decidedly stone age. But there's an upside: the most technically backward courts are well-positioned to leapfrog stages of justice's slow technological evolution. The Mobile Phone Leapfrog Mobile phones helped developing countries leapfrog stages of technological evolution. While developed or industrialized countries invested in the expensive and complicated... Continue Reading →
Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.