Specifying User Interfaces in DisCo Kari Syst i Abstract behaviors. In particular, we do not concentrate on internal issues or on interfaces to other software components. Based on literature, Booth [3] gives two different uses for the term f~rmal methods in human-computer interface engineering. One type of method attempts to cognitively model the user. The purpose of these methods is to show how complex tasks are in cognitive terms. In the other type of formal method, the behavior of a computer system is described in a formal notation. In this case general purpose specification methods are used instead of special user interface methods. When used for interface specification, their purpose is to expose logical inconsistencies within a system and its user interface. Our aim also falls in this category. Compared to most other specification methods, our notation of joint actions looks like a programming language instead of mathematical formulas, but the purpose is the same: to express logical properties and to expose logical inconsistencies. In the design phase, a formal description of system behavior can expose inconsistencies and errors in the design. A formal description also gives a rigorous basis for the implementation. When an existing user interface
/lp/association-for-computing-machinery/specifying-user-interfaces-in-disco-7yVj8mOu9M