BlackBoards

Rule-based systems

But

Need Modularity - tasks/subtasks (generic tasks)

problems: how know which tasks, how do they communicate, how 'connected' ?

Agendas
(use of modules)

Agenda: a list of tasks a system could perform

- with each task

  1. a list of reasons why the task is being proposed (justifications)

  2. a rating representing the overall weight of evidence suggesting that the task would be useful

Operation...

  1. Choose the most promising task from the agenda (task rep ? ADT's... any rep.)

  2. Execute the task by devoting to it the number of resources determined by its importance.

For each task generated from (2) - How does one find the most promising task on each cycle?

(low level control methodology: Best-first search)

Blackboards

HEARSAY - 1980 - Speech Understanding

Entire system consists of a set of independent modules (knowledge sources KS's)
that contain domain-specific knowledge and a blackboard - a shared data structure to which all the KS's have access. (like demons - triggers)

Mechanisms that affect a message (speech):

eg. or one that happened to me

eg. script

Interpretations: higher level interpretations incorporate lower level ones

Hypotheses on the blackboard are arranged along two diminsions:

level - (from small, low-level hyp. about individual sounds to large, high-level hyp. about the meaning of the entire sentence)

time - time periods of the utterance being analyzed

Associated with each KS is a set of triggers for activation

When a trigger fires, it creates an activation record describing (1) the KS that should be activated and (2) the specific event that fired the trigger.

The determination of which KS should be activated next is done by a special KS called the Scheduler. (like Executive in Hayes-Roth)

Main Points:

Modularity with respect to task

Communication

HEARSAY III

Blackboards - Hayes-Roth (Stanford)

BB1 blackboard control architecture

Hierarchical family of tools used to modify the

global data structure called the blackboard:

Top level:

Knowledge structures for representing all actions, states, events, and facts in a system.

Wide range of problem classes, methods, and domains. This level is control of overall system.

A system may have 3 classes of know. sources.

  1. domain knowledge sources

  2. control knowledge sources

  3. learning knowledge sources (modify KSs and facts in knowledge base)

Next level:

Knowledge structures for representing all actions, states, events, and facts involved in addressing a particular class of problems with a particular problem-solving method.

(Generic Tasks)

Lowest level:

Individual applications for particular classes of problems with particular problem-solving methods in particular subject-matter domains

(Domain knowledge)

Boeing Blackboard System

derived from BB1

In problem-solving ... use of "domain-specific problem solving strategies". not well said

significance of user-interface

note term: event-driven system