| Abstract: | There is consensus among the members of the HCI community as well as among software developers that work tasks and user characteristics (i.e. context) should play a leading role in the course of system development. There seems to be less consensus on how the information about users and work tasks should be acquired and subsequently moved to the design process of a development project. Due to the use of unifying methods and concepts--such as object-orientation-- that might be used for analysis, design and implementation, this transition seems to be facilitated. However, few inputs have been provided to guide developers on how to shift knowledge from analysis to design when task- and user knowledge are considered to be inherent parts of the development knowledge. This paper details the interface between analysis and design, reviews existing concepts to bridge the gap between the two phases of development, and enriches these findings with some empirical results from a survey with respect to practical experiences. From these findings, requirements to successfully shift knowledge in the early phases of software development have been derived. |
