How use-oriented development can take place

Abstract Usability is still a problem for software development. As the introduced software changes the use context, use qualities cannot be fully anticipated. Close co-operation between users and developers during development has been proposed as a remedy. Others fear such involvement of users as it might jeopardize planning and control. Based on the observation of an industrial project, we show how user participation and control can be achieved at the same time. The present article discusses the specific measures that allowed for co-operation between users and developers in an industrial context. It indicates measures to improve software development by focusing on use-orientation, i.e. allowing for user–developer co-operation.

[1]  Marcus Banks,et al.  Visual Research Methods , 2002 .

[2]  David Hakken.  Work‐Oriented Design of Computer Artifacts , 1989 .

[3]  Christiane Floyd,et al.  Software Development and Reality Construction , 1992 .

[4]  L. Suchman.  Plans and situated actions , 1987 .

[5]  S. Bodker,et al.  Computer Applications as Mediators of Design and Use-A Developmental Perspective , 1999 .

[6]  L. Wittgenstein.  Philosophical investigations = Philosophische Untersuchungen , 1958 .

[7]  Olav W. Bertelsen,et al.  Elements of a theory of design artefacts - a contribution to critical systems development research , 1998, DAIMI PB.

[8]  Gerhard Schmidt,et al.  STEPS to Software Development with Users , 1989, ESEC.

[9]  M. Grant,et al.  Communities of practice. , 2020, Health progress.

[10]  David D. McDonald,et al.  Programs , 1984, CL.

[11]  L. Wittgenstein.  Tractatus Logico-Philosophicus , 2021, Nordic Wittgenstein Review.

[12]  Etienne Wenger,et al.  Communities of Practice: Learning, Meaning, and Identity , 1998 .

[13]  Tom Rodden,et al.  Probing the Probes , 2002 .

[14]  Philip Kraft,et al.  Software Practice Is Social Practice , 2002, Social Thinking - Software Practice.

[15]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[16]  Yvonne Dittrich,et al.  Doing Empirical Research on Software Development: Finding a Path between Understanding, Intervention, and Method Development , 2002, Social Thinking - Software Practice.

[17]  Mark C. Paulk,et al.  Capability Maturity Model for Software, Version 1.1 , 1993 .

[18]  Lucy Suchman.  Plans and situated actions: the problem of human-machine communication , 1987 .

[19]  Susan Leigh Star,et al.  The Structure of Ill-Structured Solutions: Boundary Objects and Heterogeneous Distributed Problem Solving , 1989, Distributed Artificial Intelligence.

[20]  Martina Hammel.  Partizipative Softwareentwicklung im Kontext der Geschlechterhierarchie , 2003 .

[21]  Dave Randall,et al.  The development is driven by our users not by ourselves-including users in the development of off-the-shelf software , 2003 .

[22]  Alan H. Bond,et al.  Distributed Artificial Intelligence , 1988 .

[23]  Reinhard Keil-Slawik.  Artifacts in Software Design , 1992 .

[24]  Finn Kensing,et al.  Participatory Design: Issues and Concerns , 2004, Computer Supported Cooperative Work (CSCW).

[25]  Yvonne Dittrich,et al.  Social Thinking - Software Practice , 2002, Social Thinking - Software Practice.

[26]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[27]  Yvonne Dittrich,et al.  'Bad practice' or 'Bad methods' are software engineering and ethnographic discourses incompatible? , 2002, Proceedings International Symposium on Empirical Software Engineering.

[28]  Victor R. Basili,et al.  Software process evolution at the SEL , 1994, IEEE Software.

[29]  Yvonne Dittrich,et al.  Designing for changing work and business practices , 2003 .

[30]  Yvonne Dittrich,et al.  PD in the Wild; Evolving Practices of Design in Use , 2002 .

[31]  Tone Bratteteig,et al.  User Participation and Democracy: A Discussion of Scandinavian Research on System Development , 1995, Scand. J. Inf. Syst..

[32]  Meir M. Lehman.  Programs, life cycles, and laws of software evolution , 1980 .