Organisation of design activities: opportunistic, with hierarchical episodes

The organisation of actual design activities, even by experts involved in routine tasks, is not appropriately characterised by the retrieval of pre-existing plans, but is opportunistic (possibly with hierarchical episodes at a local level, but not globally hierarchical). Actually executed design actions depend, at each moment t, on the evaluation of actions proposed at t-1. These proposals can be made by pre-established plans, but also by other action-proposal knowledge structures. This position is supported by results from diverse empirical design studies. A major reason why design activities are organised opportunistically is that, even if designers possess plans which they may retrieve and use, the designers very often deviate from these plans so that their activity satisfy action-management constraints, of which the most important is "cognitive economy". Two types of variables underlying this opportunism are discussed: "situational" and "processing". If design is opportunistically organised, a support system which imposes a hierarchically structured design process will probably handicap designers. Suggestions for systems offering "real" support are formulated.

[1]  Richard E. Mayer,et al.  Human Nonadversary Problem Solving , 1989 .

[2]  John M. Carroll,et al.  Introduction to This Special issue on Design Rationale , 1991, Hum. Comput. Interact..

[3]  Kate Ehrlich,et al.  NOVICE-EXPERT DIFFERENCES IN SOFTWARE DESIGN. , 1985 .

[4]  Willemien Visser Strategies in programming programmable controllers: a field study on a professional programmer , 1987 .

[5]  Barbara Hayes-Roth,et al.  A Cognitive Model of Planning , 1979, Cogn. Sci..

[6]  B. Adelson,et al.  The Role of Domain Expenence in Software Design , 1985, IEEE Transactions on Software Engineering.

[7]  Elaine Kant,et al.  Understanding and Automating Algorithm Design , 1985, IEEE Transactions on Software Engineering.

[8]  Robin Jeffries,et al.  The Processes Involved in Designing Software. , 1980 .

[9]  John M. Carroll,et al.  Aspects of Solution Structure in Design Problem Solving. , 1980 .

[10]  G. Miller,et al.  Plans and the structure of behavior , 1960 .

[11]  S. Kay On the Nature of Expertise. , 1992 .

[12]  David Chapman,et al.  Planning for Conjunctive Goals , 1987, Artif. Intell..

[13]  G. Miller,et al.  Plans and the structure of behavior , 1960 .

[14]  Simon P. Davies,et al.  Characterizing the program design activity : neither strictly top-down nor globally opportunistic , 1991 .

[15]  Timothy A. Post,et al.  Problem-Solving Skill in the Social Sciences , 1983 .

[16]  James A. Hendler,et al.  Readings in Planning , 1994 .

[17]  David J. Gilmore,et al.  Towards a cognitive browser for OOPS , 1992, Int. J. Hum. Comput. Interact..

[18]  Pierre Falzon,et al.  Catégorisation et types d'expertise. Une étude empirique dans le domaine de la conception industrielle , 1992 .

[19]  Willemien Visser,et al.  Variations in expertise: implications for the design of assistance systems , 1989 .

[20]  Andy Whitefield,et al.  AN ANALYSIS AND COMPARISON OF KNOWLEDGE USE IN DESIGNING WITH AND WITHOUT CAD , 1986 .

[21]  D. Navinchandra Exploration and Innovation in Design: Towards a Computational Model , 1990 .

[22]  Elliot Soloway,et al.  A model of software design , 1986, Int. J. Intell. Syst..

[23]  David J. Gilmore,et al.  Expert Programming Knowledge: A Strategic Approach , 1990 .

[24]  Robert S. Rist Variability in Program Design: The Interaction of Process with Knowledge , 1990, Int. J. Man Mach. Stud..

[25]  K. Holyoak Symbolic connectionism: Toward third-generation theories of expertise. , 1991 .

[26]  A. Bisseret Towards computer-aided text production , 1990 .

[27]  Willemien Visser Design organization : there is more to expert knowledge than is dreamed of in the planner's philosophy , 1992 .

[28]  Willemien Visser Designers' activities examined at three levels: organization, strategies and problem-solving processes , 1992, Knowl. Based Syst..

[29]  Simon P. Davies Skill levels and strategic differences in plan comprehension and implementation in programming , 1990 .

[30]  Barbara Hayes-Roth,et al.  Modeling Planning as an Incremental, Opportunistic Process , 1979, IJCAI.

[31]  R. Byrne Planning meals: Problem-solving on a real data-base , 1977, Cognition.

[32]  L. Suchman Plans and situated actions , 1987 .

[33]  Willemien Visser L'activité de comparaison de représentations dans la mise au point de programmes , 1988 .

[34]  Jane Darke,et al.  The primary Generator and the Design Process , 1979 .

[35]  David C. Brown,et al.  Design Problem Solving: Knowledge Structures and Control Strategies , 1989 .

[36]  T. Ormerod Human Cognition and Programming , 1990 .

[37]  Timothy A. Post,et al.  On the solving of ill-structured problems. , 1988 .

[38]  John C. Thomas,et al.  Cognitive Processes in Design. , 1980 .

[39]  Nancy Pennington,et al.  The Tasks of Programming , 1990 .

[40]  Bill Curtis,et al.  Breakdowns and processes during the early activities of software design by professionals , 1987 .

[41]  Raymonde Guindon Designing the design process: exploiting opportunistic thoughts , 1990 .

[42]  Willemien Visser,et al.  More or Less Following a Plan During Design: Opportunistic Deviations in Specification , 1990, Int. J. Man Mach. Stud..

[43]  Willemien Visser,et al.  Expert Software Design Strategies , 1990 .

[44]  Earl D. Sacerdoti,et al.  Planning in a Hierarchy of Abstraction Spaces , 1974, IJCAI.

[45]  Raymonde Guindon,et al.  Requirements and design of DesignVision and object-oriented graphical interface to an intelligent software design assistant , 1992, CHI.

[46]  Thomas G. Dietterich,et al.  A model of the mechanical design process based on empirical data , 1988, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.

[47]  J. Hoc,et al.  Cognitive psychology of planning , 1988 .