Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Chapter
Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Chapter
}
TY - CHAP
T1 - Extending the Design Problem-Solving Process Model: Requirements and Outcomes.
AU - Scrivener, Stephen A. R.
AU - Liang, K. C.
AU - Ball, Linden J.
PY - 2002
Y1 - 2002
N2 - In this paper we extend existing design problem-solving models by the explicit inclusion of requirements and evaluation outcomes. We emphasis 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.
AB - In this paper we extend existing design problem-solving models by the explicit inclusion of requirements and evaluation outcomes. We emphasis 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.
M3 - Chapter
BT - Common Ground: Proceedings of the 2002 International Conference of the Design Research Society
A2 - Durling, D.
A2 - Shackleton, J. P.
PB - Staffordshire University Press
CY - Stoke-On-Trent
ER -