We postulate that these perspectives in combination inuence the eectiveness of design activities. Design eectiveness is dened in terms of requirements coverage and design time utilization. at is, given a certain amount of design time, how can one team address more requirements? Does one team solve a design problem more quickly than another team because of their design decision-making activities? In this study, we carry out protocol encodings of the transcripts. We label each part of the designer conversations to identify the decision-making and reasoning activities that went on during the design. e encoded protocols are analyzed to create visual decision maps. We evaluate the results to investigate the factors that inuence the eectiveness of so ware design. We have found that the ways that decisions are made impact on the eective use of design time and, consequently, the derived solutions.
|Title of host publication||Software Designers in Action|
|Subtitle of host publication||A Human-Centric Look at Design Work|
|Number of pages||26|
|Publication status||Published - 1 Jan 2013|