Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors' own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.

/pdf/guidelines-for-conducting-and-reporting-case-study-research-q10xdzyou5.pdf

Guidelines for conducting and reporting case study research in software engineering

Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a cookbook when evaluating new methods or techniques before implementing them in their organization.

Experimentation in Software Engineering

Seeking meaning: A process approach to library and information services

Most programs today are written not by professional software developers, but by people with expertise in other domains working towards goals for which they need computational support. For example, a teacher might write a grading spreadsheet to save time grading, or an interaction designer might use an interface builder to test some user interface design ideas. Although these end-user programmers may not have the same goals as professional developers, they do face many of the same software engineering challenges, including understanding their requirements, as well as making decisions about design, reuse, integration, testing, and debugging. This article summarizes and classifies research on these activities, defining the area of End-User Software Engineering (EUSE) and related terminology. The article then discusses empirical research about end-user software engineering activities and the technologies designed to support them. The article also addresses several crosscutting issues in the design of EUSE tools, including the roles of risk, reward, and domain complexity, and self-efficacy in the design of EUSE tools and the potential of educating users about software engineering principles.

/pdf/the-state-of-the-art-in-end-user-software-engineering-4dyszkiskr.pdf

The state of the art in end-user software engineering

In a world that is not predictable, improvisation, evolution, and innovation are more than a luxury: they are a necessity. The challenge of design is not a matter of getting rid of the emergent, but rather of including it and making it an opportunity for more creative and more adequate solutions to problems. Meta-design is an emerging conceptual framework aimed at defining and creating social and technical infrastructures in which new forms of collaborative design can take place. It extends the traditional notion of system design beyond the original development of a system to include a coadaptive process between users and a system, in which the users become co-developers or codesigners. It is grounded in the basic assumption that future uses and problems cannot be completely anticipated at design time, when a system is developed. Users, at use time, will discover mismatches between their needs and the support that an existing system can provide for them. These mismatches will lead to breakdowns that serve as potential sources of new insights, new knowledge, and new understanding. This paper is structured in four parts: conceptual framework, environments, applications, and findings and challenges. Along the structure of the paper, we discuss and explore the following essential components of meta-design, providing requirements, guidelines, and models for the future of end-user development: (1) the relationship of meta-design to other design methodologies; (2) the Seeding, Evolutionary Growth, Reseeding (SER) Model, a process model for large evolving design artifacts; (3) the characteristics of unselfconscious cultures of design, their strengths and their weaknesses, and the necessity for owners of problems to be empowered to engage in end-user development; (4) the possibilities created by meta-design to bring co-creation alive; and (5) the need for an integrated design space that brings together a technical infrastructure that is evolvable, for the design of learning environments and work organizations that allow endusers to become active contributors, and for the design of relational settings in which users can relate, find motivations and rewards, and accumulate social capital.

/pdf/meta-design-a-framework-for-the-future-of-end-user-7xfunnz741.pdf

Meta-Design: A Framework for the Future of End-User Development

The development of methods tools and process improvements is best to be based on the understanding of the development practice to be supported. Qualitative research has been proposed as a method for understanding the social and cooperative aspects of software development. However, qualitative research is not easily combined with the improvement orientation of an engineering discipline. During the last 6 years, we have applied an approach we call `cooperative method development', which combines qualitative social science fieldwork, with problem-oriented method, technique and process improvement. The action research based approach focusing on shop floor software development practices allows an understanding of how contextual contingencies influence the deployment and applicability of methods, processes and techniques. This article summarizes the experiences and discusses the further development of this approach based on several research projects in cooperation with industrial partners.

Cooperative method development

Changes in the use context of computer programs require flexibility and adaptability of the software itself. But, how do you design for change in rapidly changing environments? Based on a case study, the chapter argues that it is not enough to only relate to the use context. Taking also technical and developmental contexts and how they relate to the use context into consideration, allows for light-weight solutions for adaptable special purpose software. The conceptualisation of design as "artful integration" of different contexts provides a starting point for a systematic identification of relevant contexts and evaluation of design alternatives in relation to these contexts.

Designing for changing work and business practices

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.

How use–oriented development can take place

The report summarises the first year of the research project 'Design for Design in Use of Database Applications'. It focuses on end user tailoring and adaptable systems.

Design for Change

Organizational problems in industry have evoked increased interest in empirical methodologies in the broader software engineering community. In this article ethnography and its relation to software engineering is addressed. Until now sociologists have performed the majority of ethnographic studies on software development. But how useful are these studies for software engineering? Ethnography emphasizes the members' point of view in order to understand the social. Studies from the members' perspective can be interpreted, as revealing 'bad methods' that do not work in complex work situations. From a software engineering point of view, they are just as easy point to the opposite as 'bad practice', bad application of existing methods. The objective of this paper is to promote ethnography and its contribution to software engineering by revealing the different research attitudes of ethnographers and software engineers. Possibilities how to combine ethnographic studies with software method improvement are indicated.

Olle Lindeberg

Papers

Cooperative method development

Designing for changing work and business practices

How use–oriented development can take place

Design for Change

'Bad practice' or 'Bad methods' are software engineering and ethnographic discourses incompatible?