Bringing the Social and Organisational Issues into Information Systems Development

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.

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.


Author(s):  
Boris Wyssusek ◽  
Helmut Klaus

Ontology has attracted considerable attention in information systems analysis and design (ISAD) research. Ontology is philosophy and bears its own substance and history of debates, which quite often have not been accounted for in information systems research. A more comprehensive consideration of well-known philosophical issues of ontology may help to apprehend precisely the transfer of ontological concepts into ISAD, including insights regarding their limitations and to articulate directions towards further research. In particular, this requires expanding of the scope of current debates in information systems towards the socio-philosophical aspects of ontology. Only then, it will be possible to determine whether ontology can direct the project of theoretical foundation for ISAD. An outline of the critique of the prevailing rationalistic methodical understanding of information systems development in contemporary IS literature illustrates how the indiscriminating borrowing of philosophical presuppositions has encumbered current understandings. Critical reflection upon these presuppositions can get over persuasions and bring about theorisation.


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.


2008 ◽  
Vol 46 ◽  
pp. 57-66 ◽  
Author(s):  
Ona Barčkutė

Didėjanti konkurencija verčia įmones plėsti informacinių sistemų (IS) taikymo sritis. Taip pat daugėja sistemas naudojančių asmenų, keičiasi technologijos, todėl išskirtinai tampa aktualu sukurti ir įgyvendinti vartotojams priimtiną ir patogią bendravimo su IS formą. Vartotojų nepripažinta sąsaja – viena iš svarbių priežasčių, darančių įtaką, kad IS projektai žlugtų. Todėl geriausias būdas šioms problemoms spręsti yra į sistemos kūrimo darbus kuo plačiau įtraukti vartotojus.Straipsnyje nagrinėjama organizacijos informacinių sistemų plėtra, remiamasi tradiciniu funkciniu požiūriu ir plėtros procesui darančia įtaką komponentų integracija, koncentruojamas dėmesys į vartotoją. Vartotojo vaidmuo sistemos plėtros procese nagrinėjamas atsižvelgiant į IS projektų žlugimo priežastis ir akcentuojant tuos darbų barus, kuriuose eilinio vartotojo patirtis ir nuomonė yra būtina. Kai eiliniai vartotojai ir informacinių sistemų specialistai nebendradarbiauja, sukurtos sistemos neveiksmingos. Straipsnis parengtas remiantis literatūros analize ir darbo autorės atlikto tyrimo rezultatais.Users in information systems development processOna Barčkutė SummaryInformation systems (IS) play an important role in today’s organizations. The usage of everyone IS must increase the efficiency of organization activities. Right systems development helps us achieve this goal. So, the development process for today’s information systems need a framework with integrate viewpoint and system users perspective assigning especial role them. Any useful information system can‘t be developed without systems users and builders properly collaboration.


Author(s):  
Fran Ackermann ◽  
Colin Eden

Identifying what different stakeholders in a business need from Information Systems development has always been seen as problematic. There are numerous cases of failure as projects run over time, over budget, and, most significantly, do not meet the needs of the user population. Whilst having a structured design process can go some way towards reducing the potential of failure, these methodologies do not attend sufficiently to clarifying and agreeing objectives or to considering the social and cultural elements inherent in the ownership and adoption of any new system. Instigating an effective, and structured, dialogue between users, developers and, when appropriate, sponsors, is therefore a critical consideration. Linking user needs, as they see them, to the language of IS developers and vice versa is crucial. Both parties need ownership. This chapter focuses upon the use of causal mapping, supported where appropriate by special software, that facilitates the development of a shared understanding (of both business needs and IT opportunities) and through this common platform enables a negotiated and agreed outcome. The nature of the outcome invites translation to structured design processes.


Sign in / Sign up

Export Citation Format

Share Document