Briony J. Oates

New frontiers for information systems research: computer art as an information system

This paper proposes extending the frontiers of information systems (IS) research by seeing computer art as a kind of information system. It explores some research questions that arise if we take such a view. A new agenda for IS research is developed, based upon six themes in computer art and related work in previous IS research. The link between IS and computer art is bi-directional: our theories of information systems could inform the study of computer art, and computer art could inform our information systems theories, possibly leading to modification or even abandonment of them. Twelve research questions are suggested, and potential barriers to IS researchers studying computer art are also discussed. The paper offers possibilities, not solutions, and makes an important contribution by suggesting new opportunities for innovative research in IS and by signposting some of the topics which could be addressed.

Multi‐metaphor method: organizational metaphors in information systems development

Abstract.  Conventional methods have been criticized for their positivist philosophy and for either ignoring the organizational context of information systems development (ISD) or using only a simplistic, machine‐based conceptual model of organizations. We have developed an approach to enable systems developers to use a richer view of organizations and a more interpretive approach. Multi‐Metaphor Method (MMM) supports developers via a range of metaphors as cognitive structuring devices to understand an organization so that developers can learn to move between different ways of ‘reading’ the social context in which ISD occurs. We explain the rationale and theoretical underpinnings of MMM and then discuss our action research to investigate the viability and relevance of MMM during ISD practice. We show how the developers’ use of organizational metaphors via MMM did not just enable rich conceptualizations of the client organizations but also influenced the ISD process and final product. We review the learning outcomes and discuss the implications for systems development practice of our research.

Empirical methodologies in software engineering

The collection and use of evidence in software engineering practice and research are essential elements in the development of the discipline. This paper discusses the need for evidence-based software engineering, the nature of evidence in its various forms and some of the research methodologies used in other disciplines for the collection of evidence, which are also relevant to software engineering. Two frameworks or models are proposed which illustrate the relationships between the methodologies discussed. In particular, the paper highlights the importance and roles of both positivist and interpretivist methods of investigation.

Action research: Time to take a turn?

Following the linguistic turn of social sciences in the 20 th century, some researchers are now taking a turn to action.They use action research but give it a broader meaning than that currently understood by many researchers in IS. This paper discusses the newer meaning of action research and indicates how it contrasts with some uses of action research reported in the IS literature. Five quality issues for the new action research are discussed: relational praxis, reflexive-practical outcome, plurality of knowing, significant work, and new and enduring consequences or infrastructure.The paper then gives a reflexive account of an IS research study that attempted to address these five issues. Finally, the paper discusses some of the broader implications for IS research of a turn to action.

Lecture-free Teaching for Systems Analysis: An Action Research Study

This paper discusses experiences in moving to lecture-free teaching for a systems analysis module taught on-campus. It describes the action research approach and the context for the module. It discusses the lea rning materials provided as an alternative to lectures, including the description of a website in some detail. The initial lecture- free teaching approach is explained and how changes to that practice were made during the operation of the module. Student feedback by questionnaire is analysed, concentrating on the learning materials, the teaching approach and the advantages and disadvantages. Staff reflections and lessons learnt are considered under the same headings. Conclusions are drawn and further work proposed.

Widening the scope of evidence gathering in software engineering

This paper argues that the empirical evaluation of software engineering requires a wider range of strategies and data generation methods than has been used until now. It can learn from its sister discipline of information systems (IS). The paper summarises a range of strategies and methods that could be used. However, adoption of some of the additional strategies and methods would require software engineers to examine their assumptions about the nature of evidence and how it should be evaluated. The paper therefore explains the scientific, positivist paradigm and the interpretive paradigm. It argues for including qualitative methods and the interpretive paradigm in the empirical evaluation of software engineering. Finally the paper reflects on the implications for research and practice of having a range of available strategies and methods and two contrasting underlying philosophies.

Empirical Methodologies for Web Engineering

We review a range of data generation methods and empirical research strategies of potential usefulness to web engineering research. The various strategies do not all share the same underlying philosophy about knowledge and how it can be acquired. We therefore explain two contrasting philosophical paradigms: positivism and interpretivism. We suggest that empirical web engineering should use a plurality of research strategies and data generation methods, and recognise the potential usefulness of both positivism and interpretivism. Finally we discuss the implications of such a plurality.

Participation in Information Systems Research

This paper summarises the arguments given in the IS research literature in favour of participation in IS development, and suggests that similar arguments can be made for the participation of all the stakeholders in IS research. It invites readers to consider how much involvement they ‘allow’ stakeholders to have in their IS research. The paper concentrates on action research, and discusses the difficulties of evaluating action research and achieving authentic collaboration. It summarises the nature of ‘co-operative inquiry’ and proposes that the research literature of cooperative inquiry can help us 1) to examine critically the extent of participation achieved in IS research and 2) to develop further and understand the nature of action research.

On Systematic Reviews for Evidence-Based Practice

Boell and Cecez-Kecmanovic’s paper has two parts: it compares systematic literature reviews (SLRs, often shortened to ‘systematic reviews’) with ‘traditional narrative literary reviews’, and then critically evaluates some IS papers whose authors claim they had undertaken an SLR or systematic review.

Endless Bad Projects or Evidence-Based Practice? An Agenda for Action

This short position paper promotes the need for more evidence based practice to underpin the successful execution of information systems (IS) projects. This research responds to the high numbers of IS projects that are seen to have failed in terms of either one or many success criteria such as: not meeting original objectives, running over budget, negatively impacting on people, processes or organizations, to name but a few. We advocate the need for the development of a more rigorous evidence base for IS research similar to those used in medicine or more recently in social studies and software engineering. For example, Systematic Literature Reviews (SLRs) and also Meta-Analysis of empirical research studies could be used more extensively within IS to compile more coherent, consistent and referable bodies of evidence and knowledge. We conclude with a 7 point action plan and suggestions for further research.