Abstract
It is argued that the human factors-oriented system developer is armed with an inadequate set of tools for describing future designs and user requirements in terms compatible with a system analyst's needs. Task analysis and function allocation procedures are not entirely adequate. A method for procedure description that creates a syntactically formal specification using actions and objects which may or may not be formally definable is described as a partial solution to the problem. The ultimate solution is described as the use of a knowledge representation language to specify both the user's model and the implementer's specifications in order to make possible direct comparisons and promote communication across the design interface.
Get full access to this article
View all access options for this article.