Definition of knowledge domain, sources and tools

The next few steps are very similar to those required in any software project. One of the first stages is the clear definition of the knowledge domain. It must be clear which problems the expert system must solve. It is at this stage not the intention to define how this can be done. Clarity and specificity must be the major guides here. Fuzziness at this stage will, more than in classical software projects, have to be paid for later when different interpretations cause misunderstandings. Equally important is the clear definition of the end user(s). An expert system set up as decision support tool for professionals is totally different from an expert system that can be used as a training support for less professional people. 

After the knowledge domain, the end users and the experts have been defined, a choice must be made for the software environment for the development of the expert system. In addition, the hardware for the development process as well as for the delivery system must be identified. Real application expert systems always require at least a mid-sized tool (see Section 43.7). 

If possible, the best procedure for selecting a tool is to implement a smaller test knowledge base similar to the final knowledge base in a few different tools. This test knowledge base should be small enough to be implemented quickly in different tools. On the other hand, it must be specific enough to highlight the differences between the tools. 

---