Selecting a research method for empirical software engineering research is problematic because the benefits and challenges to using each method are not yet well catalogued. Therefore, this chapter describes a number of empirical methods available. It examines the goals of each and analyzes the types of questions each best addresses. Theoretical stances behind the methods, practical considerations in the application of the methods and data collection are also briefly reviewed. Taken together, this information provides a suitable basis for both understanding and selecting from the variety of methods applicable to empirical software engineering. Despite widespread interest in empirical software engineering, there is little guidance on which research methods are suitable to which research problems, and how to choose amongst them. Many researchers select inappropriate methods because they do not understand the goals underlying a method or possess little knowledge about alternatives. As a first step in helping

This paper introduces a framework for conducting and writing an effective literature review. The target audience for the framework includes information systems (IS) doctoral students, novice IS researchers, and other IS researchers who are constantly struggling with the development of an effective literature-based foundation for a proposed research. The proposed framework follows the systematic data processing approach comprised of three major stages: 1) inputs (literature gathering and screening), 2) processing (following Bloom’s Taxonomy), and 3) outputs (writing the literature review). This paper provides the rationale for developing a solid literature review including detailed instructions on how to conduct each stage of the process proposed. The paper concludes by providing arguments for the value of an effective literature review to IS research.

Based on the critical success factors for offshore software development projects which could be identified within an already completed research project, the paper at hand describes a research-in-progress project that aims to analyze the relevance, the specificity, and the implications of these success factors. By focusing on the viewpoint of German clients, the project is expected to contribute with new insights into managing offshore development projects successfully.

The prevailing approach to free/open source software and licenses has been that each system is developed, distributed, and used under the terms of a single license. But it is increasingly common for information systems and other software to be composed with components from a variety of sources, and with a diversity of licenses. This may result in possible license conflicts and organizational liability for failure to fulfill license obligations. Research and practice to date have not kept up with this sea-change in software licensing arising from free/open source software development. System consumers and users consequently rely on ad hoc heuristics (or costly legal advice) to determine which license rights and obligations are in effect, often with less than optimal results; consulting services are offered to identify unknowing unauthorized use of licensed software in information systems; and researchers have shown how the choice of a (single) specific license for a product affects project success and system adoption. Legal scholars have examined how pairs of software licenses conflict but only in simple contexts. We present an approach for understanding and modeling software licenses, as well as for analyzing conflicts among groups of licenses in realistic system contexts, and for guiding the acquisition, integration, or development of systems with free/open source components in such an environment. This work is based on an empirical analysis of representative software licenses and of heterogeneously-licensed systems. Our approach provides guidance for achieving a “best-of-breed ” component strategy while obtaining desired license rights in exchange for acceptable obligations.

The semantic web envisions the Internet as a globally linked database, one that supports data interoperability and machine readable semantics. The “back-bone ” of the semantic web is structural representations of domains of knowledge in the form of ontologies. A critical prerequisite to supporting this global information exchange is that mappings must exist between domain related ontologies. The process of mapping one ontology to another is far from a fully automated task. Generally, it is necessary for a human to verify and fine-tune the mappings generated by ontology mapping tools. The research focus has been primarily on the automation of this process and has largely ignored the user. We believe that in order for mapping tools to move beyond research labs we need to begin focusing on the user’s needs during the mapping process. In this project, we discuss the first step towards reaching this goal, a pilot user study where we investigate the human decision making process during an ontology mapping task. Based on the data collected, our goal is to gain a detailed understanding of the aforementioned process and develop design requirements that if implemented, will help reduce the cognitive load of the mapping users.

Qualitative case study methodology provides tools for researchers to study complex phenomena within their contexts. When the approach is applied correctly, it becomes a valuable method for health science research to develop theory, evaluate programs, and develop interventions. The purpose of this paper is to guide the novice researcher in identifying the key elements for designing and implementing qualitative case study research projects. An overview of the types of case study designs is provided along with general recommendations for writing the research questions, developing propositions, determining the “case ” under study, binding the case and a discussion of data sources and triangulation. To facilitate application of these principles, clear examples of research questions, study propositions and the different types of case study designs are provided. Key Words: Case Study and Qualitative Methods

Abstract not found

ter verkrijging van de graad van doctor Op gezag van de rector magnificus van Wageningen Universiteit,

In 1993 Couger et al. stated in an MIS Quarterly article on creativity in information systems (IS) organizations that the topic of creativity is under-researched in the IS discipline. Is the subject of creativity—despite its undisputable importance for individuals, organizations, and societies—still a neglected area in IS research? In what contexts, with what methods, and with what results have IS researchers studied the phenomenon of creativity? And what creativity-related themes warrant further investigation? In this article we analyze, based on six analytical dimensions, IS studies on creativity published in the eight top-ranked IS journals as recommended by the Association for Information Systems. The analysis provides a detailed picture of how the concept of creativity has been treated in our discipline‘s arguably most influential publication outlets. It becomes apparent that IS researchers have been

We studied the clarity of three requirements forms, operationalized as ease of problem detection, freedom from obstructions to understanding, and understandability by a variety of stakeholders. A set of use cases for an industrial system was translated into ScenarioML scenarios and into sequence diagrams; problems identified during each translation were noted; and all three forms were presented to a range of system stakeholders, who were interviewed before and after performing tasks using the forms. The data was analyzed, and convergent results were triangulated across data sources and methods. The data indicated that ScenarioML scenarios best support requirements clarity, then sequence diagrams but only for stakeholders experienced with them, and finally use cases as the least clear form. That I require a clearness... To leave no rubs nor botches in the work...