On the Process of Software Design: Sources of Complexity and Reasons for Muddling through

Abstract

Abstract. Software design is a complex undertaking. This study delineates and analyses three major constituents of this complexity: the formative element entailed in articulating and reaching closure on a design, the progress imperative entailed in making estimates and tracking status, and the collaboration challenge entailed in learning within and across projects. Empirical data from two small to medium-size projects illustrate how practicing software designers struggle with the complexity induced by these constituents and suggest implications for user-centred design. These implications concern collaborative grounding, long-loop learning, and the need for a more managed design process while acknowledging that methods are not an alternative to the project knowledge created, negotiated, and refined by designers. Specifically, insufficient collaborative grounding will cause project knowledge to gradually disintegrate, but the activities required to avoid this may be costly in terms of scarce resources such as the time of key designers.

Project Designs for Student Design Projects

“…Such support could be educationally beneficial by providing for progressively more depth in the projects and for more coherence across study activities. In addition, it could be practically beneficial by rearing student designers' awareness of the importance of learning across projects, an activity that is associated with uncertainty in much practical design work (Hertzum, 2008).…”

“…Are its outcomes reliable and valid? At an overall level these questions call for knowledge about the organization of project activities into a linear or iterative process and the dual use of estimates to enforce plans and status information to enforce realism (Hertzum, 2008). At a detail level they call for knowledge about individual project activities, the methods available for performing them, and the pros and cons of these methods.…”