Incorporating Behavioral Techniques Into the Systems Development Life Cycle

The gathering of a variety of human-oriented information is vital in the development stages of a software system. This information can be applied at a given stage to improve the human-computer interface of the software product. To reflect this, new categories of design and/or development effort need to be added tot he traditional systems development stages. These efforts, termed user factor stages, differ from the traditional feasibility studies, requirements analyses, and tests that are currently conducted. The stages offer a flexible series of techniques, which can be compared and contrasted in terms of their expected information benefit, cost, and reliability of data obtained. As a concrete example, the development of a forms interface to a relational database management system illustrates these techniques.

[1]  N. Walker,et al.  Designing keybindings to be easy to learn and resistant to forgetting even when the set of commands is large , 1988, CHI '88.

[2]  Susan F. Ehrlich,et al.  Social and psychological factors influencing the design of office communications systems , 1986, CHI '87.

[3]  Marilyn Tremaine,et al.  Skilled financial planning: the cost of translating ideas into action , 1989, CHI '89.

[4]  J. Nielsen,et al.  Integrated software usage in the professional work environment: evidence from questionnaires and interviews , 1986, CHI '86.

[5]  John L. Bennett,et al.  Usability Engineering: Our Experience and Evolution , 1988 .

[6]  R. M. Young,et al.  Choosing between methods: analysing the user's decision space in terms of schemas and linear models , 1988, CHI '88.

[7]  David Volk Beard.  Automatically-generated form screens as a database interface language (human factors, information systems) , 1985 .

[8]  Phyllis Reisner,et al.  Human Factors Studies of Database Query Languages: A Survey and Assessment , 1981, CSUR.

[9]  David E. Kieras,et al.  DEVELOPING A USER INTERFACE TECHNOLOGY FOR USE IN INDUSTRY , 1987 .

[10]  Steve Draper,et al.  Questionnaires as a software evaluation tool , 1983, CHI '83.

[11]  K. A. Ericsson,et al.  Protocol Analysis: Verbal Reports as Data , 1984 .

[12]  Tony J. Simon,et al.  Analyzing the Scope of Cognitive Models in Human-Computer Interaction: A Trade-Off Approach , 1988, BCS HCI.

[13]  Michael Good.  The use of logging data in the design of a new text editor , 1985, CHI '85.

[14]  Bernard H. Boar,et al.  Application prototyping: a requirements definition strategy for the 80s , 1984 .

[15]  M. E. J. Masson,et al.  Misconceived misconceptions? , 1988, CHI '88.

[16]  Wayne A. Bailey,et al.  Directed dialogue protocols: verbal data for user interface design , 1989, CHI '89.

[17]  C Runciman,et al.  User programs: a way to match computer systems and human cognition , 1986 .

[18]  Niklaus Wirth,et al.  Program development by stepwise refinement , 1971, CACM.

[19]  Toby J. Teorey,et al.  Metaform: updatable form screens and their application to the use of office metaphors in query language instruction , 1987 .

[20]  John M. Carroll,et al.  Artifact as theory-nexus: hermeneutics meets theory-based design , 1989, CHI '89.

[21]  Takashi Kato,et al.  What "Question-Asking Protocols" Can Say about the User Interface , 1986, Int. J. Man Mach. Stud..

[22]  Jerry M. Manheimer,et al.  A case study of user interface management system development and application , 1989, CHI '89.

[23]  Fred D. Davis.  A technology acceptance model for empirically testing new end-user information systems : theory and results , 1985 .

[24]  Austin Henderson,et al.  A multiple, virtual-workspace interface to support user task switching , 1986, CHI '87.

[25]  Allen Newell,et al.  The keystroke-level model for user performance time with interactive systems , 1980, CACM.

[26]  Richard M. Young,et al.  Programmable user models for predictive evaluation of interface designs , 1989, CHI '89.

[27]  R. Budde,et al.  Approaches to Prototyping , 1984, Springer Berlin Heidelberg.