Critiquing systems can examine the custom adjustments, or, alternatively, the tools generated to detect problematic cases. Incorrect metatool implementation. Naturally, there can be bugs in the metatool implementation that result in incorrect knowledge-acquisition tools. Critiquing systems can detect some of these problems, because metatool bugs often result in incomplete target tools. Thus, developers get confused by incorrect metatool input that manifests itself in the target tool.
Developers make inappropriate custom adjustments occasionally.
A run-time system then uses this definition to produce the tool user interface, and to provide the appropriate tool behavior. A critiquing system can examine the textual definition and critique the tool design on the basis of this definition. The developer can run CT once DASH has completed the knowledge-acquisition tool. CT reads the resulting EO file and builds an internal structure of the tool definition. CT then analyzes this structure by applying critiquing rules to it.