![]() |
|
| Process Operators |
A-B-C-D-E-F-G-H-I-J-K-L-M-N-O-P-Q-R-S-T-U-V-W-X-Y-Z
Identification
Definitions/Uses| 1998 | |
|---|---|
| Reference | /Huff, 1988/ A Plan-based Intelligent Assistant that Supports the Software Development Process |
| Definition/ Use |
Operators are parameterized templates defining the possible actions of the domain.
Operator definitions follow the state-based, hierarchical planning approach. Each operator has a precondition defining the state that must hold in order for the action to be legal, and a set of effects that defined the state changes that result from performing the action. These core clauses are augmented by a goal clause that defines the principal effects of an action (thus distinguishing them from the side-effects" of the action), and a constraints clause that defines restrictions on parameter values. The unit-check-in operator in the figure above describes the action of checking a new version of a source module into a source code control system. |
Related terms in the glossary
Publications on this areaThis page online GDPA Online Last Updated 16.June.2002 by C. Freericks