'It's lots of bits of paper and ticks and post-it notes and things . . .': a case study of a rapid application development project

The retationship between information technology IT and productivity is widely discussed but little understood. Delivered computing power in the U.S. economy has increased by more than two orders of magnitude since 1970 (Figure 1) yet productivity, especially in the service sector, seems to have stagnated (Figure 2). Given the enormous promise of IT to usher in «the biggest technological revolution men have known» [29], disillusionment and even frustration with the technology is increasingly evident in statements like «No, computers do not boost productivity, at least not most of the time» [13]. The increased interest in the «productivity paradox,» as it has become known, has engendered a significant amount of research, but thus far, this has only deepened the mystery

This paper discusses long-term change In organizations In relation to information systems. It reviews causes of social Inertia, resistance and counterimplementatlon. Itstresses the pluralistic nature of organizations. Tactics for managing change rely on Incremental, facilitative approaches. These limit strategic change which requires coalition-building and careful attention to political mechanisms.

Rapid application development (RAD) is an approach to information systems (IS) development which is much discussed in the practitioner literature. However, there is comparatively little research data on this topic. This paper forms a report of the results of a multi-disciplinary research project which has been studying this development approach for the last three years. The paper discusses seven case studies of RAD projects and compares each to issues relating to a number of RAD principles as represented in methodologies such as the recent open standard known as dynamic systems development method. We conclude with a discussion of a number of important questions relating to further research on RAD.

Abstract The paper presents the results of a survey carried out in the latter part of 1987 to assess the use of SSADM (Structured Systems Analysis and Design Methodology) and its variants in both the commercial sector and government departments in the United Kingdom. The survey was designed to identify the background of the organizations using SSADM, the use made of SSADM and other methodologies within these organizations, the value placed by the respondents on SSADM and its constituent stages, and any problems encountered in the implementation of SSADM-designed systems. The information obtained from analysis of the survey data is presented and conclusions are drawn as to the current state of the art regarding the use of the SSADM methodology and the impact that SSADM is having on systems analysis in general. In particular, the paper discusses the problems inherent within the SSADM process and makes recommendations about how the methodology should be applied and extended, to increase the efficiency and effectiveness of systems analysis and design.

Recognition that most software is domain dependent (DD) is extremely important because the most commonly used software life-cycle models are not adequate for DD software. The nature of DD software, and the need to manage its life cycle effectively, calls for a new approach to software design and the implementation of software development environments.

Changes in organizational structures, competitive environments, technologies and economies are altering the types and complexity of computer-based information systems. For methodologies, tools and techniques to evolve to meet these changing needs, research to assess current system development practices would be expected. However, there is little evidence that the evaluation of methodologies and improvement of the systems development process are keeping pace with technological and organizational changes. This paper analyses existing research on system development methodologies and discusses the research needed to provide the information scholars and practitioners will need for the evaluation, selection and development of methodologies in a changing environment.

Cet article etudie un des aspects des dernieres etapes dans le cycle de vie d'un systeme d'information a base d'ordinateur (CBIS's). On examine 4 metaphores de l'implementation d'un CBIS qui traitent des differentes esperances sur les developpements de calcul et les resultats probables: l'evolution technologique, la rationalite economique, le mouvement de structure et la politique d'organisation

The problems of designing large software systems were studied through interviewing personnel from 17 large projects. A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.

Ethnography is a style of qualitiative research method which has been discussed in a number of ways in association with the development of software systems. In this paper we identify a number of distinct uses to which ethnography and ethnographies have been put in information systems development: particularly the distinction between ethnographies for IS development and ethnographies of IS development. We also survey some of the recent proposals for integrating ethnographic practice into information systems work: ethnography within IS development. Our main aim in constructing this taxonomy is to serve as a useful framework for positioning our own ideas on the relationship between ethnography and IS development derived largely from our own ongoing research work in the area of software prototyping. The paper concludes with a discussion of two polar perspectives taken from the history of ethnographic studies which we feel are useful in framing the modern-day positioning of ethnography and IS development as well as highlighting some of the tensions involved in contemporary IS development.

It is our intention to challenge the commonly held assumption that information systems development (ISD) can be conceived of as a normative process reflecting conventional economic rationality. We ask: is systems development the rational process so eloquently described in the “classic” works of DeMarco (1978), Gane and Sarson (1979), Weinberg (1980), Yourdon (1982), Jackson (1983), and Martin (1985)? Or does this orthodox view fail to explain the actual practice of systems development? It is our view that even the basic assumptions about the rationality of the actors and the social processes they engage in need to be critically appraised. We suggest that if the assumptions about economic rationality are closely analyzed, it can be seen that they do not reflect the reality of systems development. ISD tends to defy rational explanations. As an alternative to basing our understanding of systems development on economic rationality, we contend that symbolism holds more promise. Instead of focusing on data flow diagrams, structured walkthroughs, requirements specifications, and the like, we concentrate on the role of myth, metaphor, and magic. These concepts offer considerable scope in interpreting the social actions that are embodied within ISD. We feel they facilitate a much richer understanding of systems development.

Abstract. A wide variety of approaches can be applied under the heading of case study research; this paper explicitly discusses the range of the alternatives. Many papers discussing case study research emphasize one particular variation of case study research only. The current paper provides an overview of the various uses of case study research in the information systems field by describing the different ways in which case study research can be used, using examples from published IS literature for illustration, and providing references to other method papers for more detailed discussion of each alternative. Researchers are reminded that case study research can be used in the positivist and interpretivist traditions, for testing or building theory, with a single or multiple case study design, using qualitative or mixed methods. The range of case study research alternatives makes it a highly versatile research strategy for IS

Rapid application development (RAD) is a contingent information systems development method that has arisen in response to business and development uncertainty in the commercial information systems engineering domain. Participatory design (PD) is a style of software development that has achieved some significance within a number of academic research areas and can be seen as a response to dissatisfaction with the underlying philosophy of dominant software development approaches. At the macro level, the two development styles appear divergent. However, at the micro level, there are many potential points of synergy. In the paper, both the RAD and PD traditions are reviewed and areas of possible cross-fertilisation are indicated. The efficacy of some of these points of synergy are illustrated in relation to aspects of empirical research on RAD approaches, particularly in relation to the utility of the concepts of scenarios and design breakdowns to RAD work.