Persistence and Change in System Development: A Dialectical View

2003 ◽  
Vol 18 (2) ◽  
pp. 69-92 ◽  
Author(s):  
Rajiv Sabherwal ◽  
Michael Newman

This paper seeks to advance our understanding of the dynamics of persistence and change in information systems development. Towards this goal, it draws upon dialectical theory, which enables viewing persistence and change during IS development relative to the thesis operating at that time. This approach recognizes that the nature of the system itself often changes during the development process. This also allows simultaneous attention to persistence and change, combining persistence with certain elements of the thesis along with change in some other elements. Empirically based on three cases, the paper provides insights into the content and process elements of theses, governing the characteristics of the system and the nature of the development process, respectively. It offers one possible explanation for the evolution of the IS development process and some insights into the strategies for improving this process through greater attention to the theses and the dialectic processes.

2003 ◽  
Vol 12 (4) ◽  
pp. 319-327 ◽  
Author(s):  
Markos Goulielmos

Defines the concept of “organisational failure” in information systems (IS) development, and proposes a diagnostic model drawn from research done into IS consultancy firms that develop systems using a variety of methodologies. The research involved a qualitative study aimed at the nature of the development process and the role of organisational issues in this process. The model’s elements and relationships were determined by the research findings. Presents two cases of failure that show how IS failure is rooted in organisational pathology and examine existing failure concepts. The concept and model proposed can be used by practitioners and management before and during a project for diagnosing organisational failure before it interferes with IS development and afterwards for extracting deeper rooted organisational learning from failure.


Author(s):  
David Avison ◽  
Trevor Wood-Harper

Multiview is a framework to support the information systems development process. It was formulated originally in 1985, but has been developed and changed since that time. It was originally defined to take into account the human and organisational aspects of information systems development, as the alternative methodologies of the time–and most since that time–took a very technology-oriented approach. Furthermore, it is a contingency approach, and again this compares with the alternative bureaucratic and prescriptive methodologies. In this chapter, we describe the history of Multiview, and we reflect on the experiences of using it in action in many organisations.


Author(s):  
S.C. Lenny Koh ◽  
Stuart Maguire

The development of information systems (IS) has for many years been regarded as the domain of the technical expert. In what appears to be a growing number of instances systems appear to be having negative effects on the organization. A regular spate of system failures may have identified serious flaws in the system development process. Organizations may often be significantly affected by the implementation of IS. Future IS development may increasingly be trans-organizational and therefore increase the potential for dysfunctionality. Even changing one line of code may have repercussions within a department/organization. To implement a totally integrated system within an organization without adequate preparation could have serious consequences for the financial well-being of the company. The development of information systems is a complex process, one with many opportunities for things to go wrong. To try and control this complex process a methodology was required that would bring more discipline to the IS development process. There is a need to make more efficient use of the resources that are available. Historically, IS has been developed using the system.development.life.cycle. (SDLC). This has been the prevailing methodology for medium and large system projects. However, the use of accepted methodologies for IS development have not guaranteed the successful implementation of information systems.


2019 ◽  
Author(s):  
FRANCIS KAGAI

Despite continued evolution of information systems methodologies for more than three decades, the rates of software rejection and failure are still high. This paper investigates the technological environment as a major cause of such disruptions. Additionally, the paper evaluates Agile and DevOps as the remedial methodologies for managing the adverse impact of technological disruptions. The main findings affirm both Agile and DevOps as methodologies that emanated from improvements or re-engineering of earlier methodologies. Further findings discern most methodologies; including agile and DevOps; as not strategically focused but appraise DevOps as the most progressive methodology towards this respect. Rather than re-invent the wheel and come up with a new methodology, a framework that aligns DevOps for use in strategic information systems development is proposed. Besides, a more realistic definition of operations is postulated to bolster the alignment.


2012 ◽  
Vol 9 (1) ◽  
pp. 135-164 ◽  
Author(s):  
Damjan Vavpotic ◽  
Olegas Vasilecas

The paper presents a decision model and a tool that helps to find an information systems development methodology (ISDM) for a computer-based business information system (IS) that is suitable to a certain IS development project or an organization dealing with IS development. The intention of the model is not only to suggest a certain ISDM, but also to propose the properties an ISDM should have to suite the project or the organization. It is designed in a way that facilitates experimentation with different project, organization and ISDM properties. Based on the model we created a tool that has been applied on several cases in which we validated the correctness of its recommendations and established that it can have a significant positive contribution in the process of ISDM selection and in the process of improvement of existing ISDM.


1997 ◽  
Vol 12 (2) ◽  
pp. 99-106 ◽  
Author(s):  
Angøle L. M. Cavaye

There is an increasing interest in and demand for information systems that transcend organizational and national boundaries – transnational information systems. The interorganizational and international nature of these systems introduces development difficulties. Transnational information systems are developed on an ad hoe basis; there are currently no set tools and guidelines to aid their development. This paper addresses transnational information systems development using case research to raise issues concerning the transnational information systems development process and to discuss actual development difficulties and their solutions.


Sign in / Sign up

Export Citation Format

Share Document