Abstract
In this paper we extend existing design problem-solving models by the explicit inclusion of requirements and evaluation outcomes. We emphasise the importance of the notion of an evaluation outcome, arguing that it is not simply the term ‘negative’ or ‘positive’. Rather it is a relation between a solution and a requirement(s) expressing whether, why, and to what extent the anticipated effect of the proposed solution is positive or negative. Like requirements and solutions, evaluation outcomes function as objects of reasoning (e.g., ideation). We describe an empirical study of four design dyads engaged in a design task, in which designers’ talk provides evidence for the productions and relations posited in the model. The results show that the explicit consideration of requirements figures in 77.6% of utterances coded, that evaluation outcomes represent 42% of all utterances, and that evaluation outcomes are involved in 21.4% of all solutions uttered. We conclude that we need to understand how design reasoning utilises requirements, solution and evaluation outcomes to achieve design goals.
Citation
Scrivener, S., Liang, K., and Ball, L. (2002) Extending the design problem-solving process model: requirements and outcomes, in Durling, D. and Shackleton, J. (eds.), Common Ground - DRS International Conference 2002, 5-7 September, London, United Kingdom. https://dl.designresearchsociety.org/drs-conference-papers/drs2002/researchpapers/72
Extending the design problem-solving process model: requirements and outcomes
In this paper we extend existing design problem-solving models by the explicit inclusion of requirements and evaluation outcomes. We emphasise the importance of the notion of an evaluation outcome, arguing that it is not simply the term ‘negative’ or ‘positive’. Rather it is a relation between a solution and a requirement(s) expressing whether, why, and to what extent the anticipated effect of the proposed solution is positive or negative. Like requirements and solutions, evaluation outcomes function as objects of reasoning (e.g., ideation). We describe an empirical study of four design dyads engaged in a design task, in which designers’ talk provides evidence for the productions and relations posited in the model. The results show that the explicit consideration of requirements figures in 77.6% of utterances coded, that evaluation outcomes represent 42% of all utterances, and that evaluation outcomes are involved in 21.4% of all solutions uttered. We conclude that we need to understand how design reasoning utilises requirements, solution and evaluation outcomes to achieve design goals.