Systems Development Practice Research Articles

Combining Static and Dynamic Modelling Methods: A Comparison of Four Methods

A conceptual model of a system is an explicit description of the behaviour required of the system. Methods for conceptual modelling include entity-relationship (ER) modelling, data flow modelling, Jackson System Development (JSD) and several object-oriented analysis methods. Given the current diversity of modelling methods, it is important for teaching as well as using these methods to know what the relationships between them is and to be able to indicate what the (im)possibilities of integrating different methods are. This paper compares three classical modelling methods (ER, data flow, JSD) on their possibilities for integration and combination. It is shown that there is a common core of these methods, which centres around the concept of system transaction and that unifies the static view of a system taken by ER modelling, with the dynamic view taken by JSD and the functional view taken by data flow modelling. Several object-oriented analysis methods integrate these three views. This paper illustrates how this is done in the analysis stage of Object Modelling Technique. Finally, it is shown that the transaction decomposition table can be used as a pivot around which to combine different methods. The results of this paper can be used in teaching to explain the relationships and differences between the methods analysed here, and in system development practice to ease the transition from structured to object-oriented methods.

Co-operation in the Field of Information Systems

Research on information systems rests to a large extent on a tradition that is characterized by a ‘competition’ paradigm. In this article a paradigm of ‘co-operation’ is put forward on the basis of earlier research in other than information systems research areas. Practical examples from current practice of information systems management and development are drawn. The article puts on a taxonomy for categorizing co-operative efforts. The taxonomy is based on six generalizable determinants of relationship formation as presented by Christine Oliver in the article ‘Determinants of Interorganizational Relationships: Integration and Future Directions’ and on the framework of transaction costs as presented by Oliver E. Williamson.

Nigerian Practice in Computer Systems Development: A Multidisciplinary Theoretical Framework Applied to Health Informatics

Nigerian Practice in Computer Systems Development: A Multidisciplinary Theoretical Framework Applied to Health Informatics

What can we learn from chaos theory? An alternative approach to instructional systems design

In this article, the “goodness of fit” between ISD and chaos theory is explored by applying the key concepts of chaos theory to the process of developing an alternative ISD model. After a brief introduction to chaos theory and an exploration of the limitations of and/or the problems with conventional ISD models, the theoretical implications for developing an alternative ISD model are explored. The assumptions of a conventional ISD model are compared to those of chaos theory and dynamic nonlinear systems in order to derive theoretical implications and recommendations for future research and practice in instructional systems design and development.

Database conversion planning

In conventional approaches to Systems Development the crucial task of the exercise, deployment figures almost, at the end! The performance of the developed software can only be realized if and only if, there is a database to interact with. Surprisingly, this slips the attention of system developers! The challenge of converting the existing manual system, of all, the database maintained in paper volumes to that of computerized version, is not well accounted for. However, mundane this task, Database Conversion Planning (DBCP) , has a definite and dominant role to play in systems development. While handling several complex turnkey computerization projects, we are compelled to realize the criticality of DBCP. A careful consideration of these issues in the early stages of systems development has shown a multitude of benefits. As a result, we were able to deploy projects amidst several constraining and conflicting factors. The projects have won the appreciation of customers, of all, end-users. We would like to share the vision that had lead to the creation of these systems, where software and quality have only synonymous meaning! We finally wish that these thoughts will influence the practice of systems development or in general, software engineering.

Integrating systems development theory and practice in an information systems curriculum

Information Systems curricula have been criticized for not fully preparing students for effective assimilation into organizations. One of the reasons cited for this shortcoming is the chasm between theory and practice that often exists in many IS curricula. This paper examines this weakness by reviewing traditional methods of teaching IS courses, and by discussing specific course integration efforts by faculty at The American University. The case study described in this paper focuses on the application of the Cleanroom System Development Process (CSDP), a methodology that requires intensive cross-functional group interaction in student projects that span traditional course boundaries.

Understanding the social practices of systems developers

Abstract. The aim of this paper is to explore some of the ways in which we think about the development of information systems by drawing upon arguments articulated within the philosophy of science and the sociology of technology. It argues that many of these approaches operate on the basis of a reified and sociologically restricted view of technology. Drawing upon recent work in the sociology of technology the paper proposes a more thorough-going analysis of the social practice of information systems development and discusses examples from knowledge engineering and requirements analysis to illustrate its argument.

Case study in human factors evaluation

A human factors (HF) evaluation, carried out as part of the development of a set of computer-aided software engineering (CASE) tools, is presented and is used as an example of the processes and products of typical HF evaluation practice. The role of HF evaluation as a part of software quality assurance is identified, and typical current practice of HF evaluation is characterized. The details of the particular evaluation are then reported. First, its processes are described; these are determined by relating features of the system under development to the desired focus, actual context, and possible methods of the evaluation. Then the products of the evaluation are described; these products or outcomes are formulated as the user-computer interaction difficulties that were identified, grouped into three types (termed task, presentation, and device difficulties). The characteristics of each type of difficulty are discussed, in terms of their ease of identification, their generality across application domains, the HF knowledge that they draw on, and their relationship to redesign. The conclusion considers the usefulness of the evaluation, the inadequacies of system development practice it implies, and how to incorporate HF evaluation into an improved system development practice.

Symbolism and Information Systems Development: Myth, Metaphor and Magic

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.

Information systems development as social action: Theoretical perspective and practice

Information systems development (ISD) continues to receive considerable attention in the literature. Much of it, however, simply perpetuates the myth that ISD should somehow be conceived in technical terms. In this paper, we challenge this view by presenting systems development as a form of social action. The hypothesis offered is that ISD can be more effectively understood by applying seven basic building blocks of social action theories: Knowledge, Power, Subjective Meanings, Human Interests, Consensus, Conflict, and Resistance. It is the interplay of these seven elements which make up the fundamental basis of systems development. To show that our understanding of ISD is enhanced through viewing it as social action, we present evidence from four case studies. It is shown that the practice of systems development is reflected in our notion of social action; more specifically, that it makes sense to view information systems development as social action.

Software maintenance management: Changes in the last decade

AbstractCompared to a decade ago, when the first comprehensive study was done in software maintenance, many changes have occurred in the practice of system development. Longitudinal data were obtained by using the same survey instrument, updated to reflect current practices, and sampling the same population. Comparing the current with 1977 results has helped to identify the persistent problems and issues as well as the emerging problems and issues.One of the important, but somewhat disturbing, conclusions is that maintenance problems are pretty much the same as during the 1970s (except for minor changes), despite advances made in structured methodologies and techniques. In terms of specific problems, personnel problems of maintenance programmers, i.e. turnover and availability, and programmer effectiveness problems, i.e. skills, motivation and productivity, have shown a rise, while problems associated with users' knowledge of computer systems have declined.

Impact of information technology on organizations: The state of the art

This article gives an introduction to the field of impact research. After a short discussion of the role of information in organizational context, the interaction perspective on impact research is presented. Empirical research results in the field of impacts of IT on internal organization in 11 organizations in the fields of banking, services, government and industry are presented. In general the systems studied were useful in realizing more centralization and impersonal control. Professionals seemed to be very pleased with information systems, because they avoided tedious jobs and organizational bottle-necks, and gave them opportunities to do their work in a better way. This is very different from the experiences of non-professional workers, who met with more routinization, rigidity and job dissatisfactions. Competitiveness was very often increased due to big cost savings and better service to clients. The authors note that much extra research is needed, especially for making more accurate estimates of impacts and how they occur. This should become an integral part of systems development and information management practice in the future.

Post implementation evaluation of computer-based information systems: current practices

Contrary to the widely-held view that post implementation evaluations are performed to assess and improve the information system and the system development practices, this study suggests that in practice, the primary reason for such evaluations seems to be project closure and not project improvement.

Some fallacies in information systems development

What systems analysts believe about users and organizations inevitably shapes the practice of information systems development (ISD) but these beliefs can prove to be fallacious. In this article, five widely-held beliefs are discussed. They are: user involvement is beneficial; resistance to ISD should be overcome; integration of systems is a desirable and attainable goal; ‘our way is best’; organizational issues are not the concern of systems professionals. Using detailed case material from the USA and Canada, each belief is matched with empirical evidence revealing a large gap between belief and practice and between practice and the needs of the organization. The article ends with a discussion of the findings and gives pointers to improved practice.

China Light & Power's transmission system development practices

China Light & Power (CLP) is a Public Limited Company with responsibilities to its shareholders, the Hong Kong Government and the public at large in providing a secure, efficient and economical supply of electrical power to its supply area within the territory of Hong Kong. This article traces the history of CLP's transmission system developments over the past 40 years, which has been a period of vigorous and continuous growth and has produced some original engineering solutions to a range of unique problems encountered. Particular aspects of compact substation developments, within the densely populated Kowloon area, will be highlighted. A self-sufficient capability with a strong awareness of cost effectiveness have been central influencing factors in the development of the CLP system

Information systems strategy and end-user application development

End-user computing in organizations with different information systems strategies was studied to determine the nature and characteristics of user-developed applications, systems development practices, quality assurance methods, and policies and procedures for end-user development. The findings showed that the information systems strategies of the firms studied did not markedly affect end-user computing activities. In most of these firms, strategic end-user systems were being designed by functional specialists, suggesting their role as catalysts for introducing strategic uses of information technology in user departments in which computing had been primarily valuable for operational efficiency in the past. Formal systems development practices such as data validation, documentation, and data security were not being followed, indicating a need for user training. Although policies and procedures for hardware and software acquisition were in effect, users were largely unaware of policies or guidelines addressing application development issues.

The senior information systems design project seminar

One of the challenges of teaching MIS is preparing students to apply the knowledge they have gained in a real project. Although they have developed proficiency in problem-solving, structured design techniques, and programming during course work, many MIS students have never interviewed a user or been asked to make design changes at a user's request. In addition, many students have never had to work on a project team, manage schedules, and meet project deadlines. The senior information systems design project course provides students with an opportunity to apply systems concepts and techniques in the design of an information system. Students identify “live” projects and work on project teams. In the past, many of these projects have been programming design and implementation projects provided by local industry. However, in large-scale projects, students could not start with problem definition, proceed to requirements specification, and complete detailed design, because all of this could not be accomplished in a single term. As a result, they would do segments of larger projects. With the advent of the microcomputer, however, many smaller scale projects became available in offices seeking to automate records management, routine accounting, and other office automation systems. These projects created an opportunity for students to do an entire project, from systems analysis to detailed design. The purpose of this paper is to describe the objectives and procedures of the information systems design project seminar and to discuss the nature and scope of design projects conducted in university offices during the fall, 1985 quarter. The paper will describe the respective roles of student systems analysts and users, the systems development practices followed, and some of the successes and pitfalls of the experience.

Empirical investigation of systems development practices and results

A survey was conducted of 72 information system development projects in 23 major U.S. corporations. The characteristics of the organizations, their system development methodologies, and the information system projects were reviewed. The study focused on the early phases of systems development, especially systems analysis and systems development planning. Early plans and budgets were evaluated with respect to the results of the completed projects. An analysis of the development of these projects provides a summary description of systems development practice as performed in these leading organizations. Included with development practices, the study measured or estimated such aspects of the projects as user satisfaction and development time and cost overruns. The results provide useful insight into system development methodology, cost and time estimating, variables affecting user satisfaction, and the need to iteratively determine user requirements.

A management framework for systems users

Many business managers today are in need of practical guidance in determining which information systems management practices are appropriate for their particular organization. Of central importance is the management of the information systems development process. A field research study was conducted at five major U.S. corporations to determine those information systems development management practices that had proved successful. The research method consisted of in-depth interviews with managers and technical people at each company. In addition, the reputation of each company as a successful manager of the information systems function was validated using a set of organizational performance criteria developed by a panel of prominent information systems professionals. The results of the research are presented in the form of a planning and control framework of successful management practices. The framework describes and classifies those practices common to all companies and clearly differentiates those practices which varied significantly among the companies studied. The framework is designed to enable management to readily identify those information system development practices that have proved successful and to select from among them those most appropriate to the local situation. It can also serve as a guide for self-study on the part of the individual manager.