A. Trevor Wood-Harper

Bio: A. Trevor Wood-Harper is an academic researcher from University of Salford. The author has contributed to research in topics: Soft systems methodology & Information system. The author has an hindex of 4, co-authored 7 publications receiving 1307 citations. Previous affiliations of A. Trevor Wood-Harper include University of South Australia.

A critical perspective on action research as a method for information systems research

Abstract: This paper reviews the origins, techniques and roles associated with action research into information systems (IS). Many consider the approach to be the paragon of post-positivist research methods, yet it has a cloudy history among the social sciences. The paper summarizes the rigorous approach to action research and suggests certain domains of ideal use (such as systems development methodology). For those faced with conducting, reviewing or examining action research, the paper discusses various problems, opportunities and strategies.

An Holistic Approach to the Management of Information Systems Development—A View Using a Soft Systems Approach and Multiple Viewpoints

Abstract: This paper argues that only a systems-based approach to information systems development is likely to cover all the recognized problem issues reported in the literature. It is then shown that software development can be characterized by the structure of the Soft Systems Methodology, so that this methodology acts as a metaphor for the process of information systems development. The structure of this methodology can be seen at lower levels of the development process, and so the model generated here is seen as recursive. Further, information systems development is seen as an unstructured business problem that can be characterized by the Multiple Viewpoint approach. The connections between this approach and the methodology are identified. Finally, the unifying link between these approaches and all forms of action research is identified.

Towards user-oriented control of end-user computing in large organizations

Abstract: This paper questions the traditional IT view of end-user computing which stifles the development of new systems by users and imposes technical controls on them. It proposes a new user-oriented view of end-user computing which will be of significant use to IT management and explores the dynamic nature of end-user computing using causal maps.

The soft system methodology as a framework for software process improvement

Abstract: The overall aim of this paper is to argue that only a systems-based approach to information systems development (ISD) and software process improvement (SPI) are likely to cover all the recognised issues. This paper will examine reports in the literature concerning problems associated with ISD and implementation. The characteristics of these problems are identified. It is noted that these problems have been known for many years. The responses to the problems fall into two broad areas which are characterised as paradigms. On the one hand, there is a belief that systems development should be considered to be a form of applied science or engineering (Dijkstra, 1976; Floyd, 1992; Hoare, 1982). This is also the approach behind Software Process Improvement. However, there are weaknesses with this approach which are identified below. These weaknesses are addressed by approaches from within the second paradigm or systems paradigm (Checkland, 1981; Checkland and Scholes, 1990). The systems paradigm has been developed from the traditional paradigm. Consequently, it is argued that fewer problems will be found if methodologies based on the systems paradigm are used. The foundations and nature of this approach are described. Further, it is shown that the Soft Systems Methodology (SSM), which is based on this paradigm, can be used as a metaphor or model of ISD. In this form it is recursive and so this model is characterised as Recursive SSM. SSM is offered as a useful framework for both ISD and software process improvement (SPI). This paper will therefore address the following major activities:

Inquiring Systems in Approaches to Information Systems Development

Abstract: The initial assertion of this paper is that information systems development (ISD) failures can best be addressed through a systems approach. Such an approach is characterised by Linstone’s Multiple Viewpoints or Checkland’s Soft System Methodology (SSM), both of which are supported by Singerian inquiring systems. The paper notes that these approaches are both forms of action research and therefore examines the support given to other forms of action research by Singerian inquiring systems. Organisations which recognise that they are not perfect when it comes to ISD and wish to do something about it can be considered as Learning Organisations. Senge’s approach to Learning Organisations is seen as being generic. In the context of ISD, it is contrasted with SSM. In particular, the support required by these approaches from the classical inquiring systems is being considered. Further, the implications of what any resolution might mean for ISD is also considered. The final focus is to consider the framework of ISD as a social construct and examine the benefits of a non-classical inquiring system, based on the philosophy of Rorty.

Guidelines for conducting and reporting case study research in software engineering

Abstract: 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.

Experimentation in Software Engineering

Abstract: 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.

Action research for operations management

Abstract: A fundamental methodological question guides this paper: How can operations managers and researchers learn from the applied activity that characterises the practice of OM? To address this question, defines and explores the legitimacy of an action‐oriented research approach in OM, and the particular logic and value of applying action research (AR) to the description and understanding of issues in OM. Begins with a review of the role of empirical research in OM and how AR features within the OM research literature. Introduces the theory and practice of AR and outlines the AR cycle and how AR is implemented. Finally, describes the skills required to engage in AR and explores issues in generating theory. Concludes with the assertion that AR is relevant and valid for the discipline of OM in its ability to address the operational realities experienced by practising managers while simultaneously contributing to knowledge.

Investigating information systems with action research

Abstract: Action research is an established research method in use in the social and medical sciences since the mid-twentieth century, and has increased in importance for information systems toward the end of the 1990s. Its particular philosophic context is couched in strongly post-positivist assumptions such as idiographic and interpretive research ideals. Action research has developed a history within information systems that can be explicitly linked to early work by Lewin and the Tavistock Institute. Action research varies in form, and responds to particular problem domains. The most typical form is a participatory method based on a five-step model, which is exemplified by published IS research.

Principles of canonical action research

Abstract: Despite the growing prominence of canonical action research (CAR) in the information systems discipline, a paucity of methodological guidance contin- ues to hamper those conducting and evaluating such studies. This article elicits a set of five principles and associated criteria to help assure both the rigor and the relevance of CAR in information systems. The first principle relates to the devel- opment of an agreement that facilitates collaboration between the action researcher and the client. The second principle is based upon a cyclical process model for action research that consists of five stages: diagnosis, planning, inter- vention, evaluation and reflection. Additional principles highlight the critical roles of theory, change through action, and the specification of learning in terms of impli- cations for both research and practice. The five principles are illustrated through the analysis of one recently published CAR study.