Design Science Methodology for Information Systems and Software Engineering

Abstract

The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein.

A Study on Tangible Participative Enterprise Modelling

“…Given available data, this study employs generalization by analogy: "If an observation is explained by a general theory, then this observation may also occur in other cases where this general theory is applicable" [27]. Since social or psychological mechanisms can explain the observed phenomena using constructs such as synchronicity, cognitive load, cognitive fit, gamification, and constructive learning (see Sect.…”

“…This section describes our research design following the checklist provided by Wieringa [27]. We translate our research goal in the following research question:…”

OSSAP – A Situational Method for Defining Open Source Software Adoption Processes

“…Still, the work done while designing the DKE-approach has been crucial to generate OSSAP. We may sense that the formulation of OSSAP starts a second cycle in a design science approach [15] after the validation done in practice of the former DKE-approach. …”

LightCDD: Application of a Capability-Driven Development Method for Start-ups Development

“…To shape our research, we conduct a design science project [6]. We perform the first iteration of a design cycle from the problem investigation to the treatment validation (see Figure 2).…”