scholarly journals Vartotojas informacinių sistemų plėtros procese

2008 ◽  
Vol 46 ◽  
pp. 57-66 ◽  
Author(s):  
Ona Barčkutė
Keyword(s):  
Information System ◽  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Information Systems Development

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.

Bringing the Social and Organisational Issues into Information Systems Development

2003 ◽  
pp. 5-21 ◽  
Author(s):  
David Avison ◽  
Trevor Wood-Harper
Keyword(s):  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Information Systems Development ◽  
The Social ◽  
History Of ◽  
Oriented Approach ◽  
Contingency Approach

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.

Challenges during the Development of Transnational Information Systems

1997 ◽  
Vol 12 (2) ◽  
pp. 99-106 ◽  
Author(s):  
Angøle L. M. Cavaye
Keyword(s):  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Information Systems Development ◽  
Case Research ◽  
National Boundaries

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.

Outlining organisational failure in information systems development

2003 ◽  
Vol 12 (4) ◽  
pp. 319-327 ◽  
Author(s):  
Markos Goulielmos
Keyword(s):  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Organisational Learning ◽  
Information Systems Development ◽  
Diagnostic Model ◽  
Learning From Failure ◽  
Research Findings ◽  
Is Development

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.

scholarly journals Information Systems Development Methodologies and all that Jazz

10.28945/2805 ◽  
2004 ◽  
Author(s):  
Lukasz Michalec ◽  
David A Banks
Keyword(s):  
Information System ◽  
Information Systems ◽  
Ad Hoc ◽  
Systems Development ◽  
Information Systems Development ◽  
Shared Meaning ◽  
Specific Focus

This paper explores the relationships between jazz and the development of information systems. Similarities are drawn between music in general and information systems development methodologies and jazz is taken as a specific focus. The idea of music as an information system in its own right is outlined. As systems development methodologies move from formal approaches towards more ad hoc forms, the lessons that can be learned from jazz, such as improvisation and shared meaning, may become increasingly useful.

Information Systems Development Outcomes

2011 ◽  
pp. 48-62 ◽  
Author(s):  
M. Gordon Hunter
Keyword(s):  
Decision Making ◽  
Information System ◽  
Information Systems ◽  
System Development ◽  
Systems Development ◽  
Information Systems Development ◽  
Information System Development ◽  
Development Outcomes ◽  
Positive Agreement

When is an information system development outcome considered a success and when is it considered a failure? What factors contribute to a conclusion of either success or failure? How does the situation arise to create the environment which contributes to the above conclusions? Generally, an information system is considered a success when it does what it is supposed to and/or the user is satisfied with the system’s performance in support of the information-providing and decision-making responsibilities. Naturally, this area is fraught with the problems inherent in divergent interpretations of “what it is supposed to do,” “satisfaction,” and “systems performance.” Suffice it to say, when the systems developer and user are in positive agreement about these interpretations, the information system development outcome may be considered successful.

Sign in / Sign up

Export Citation Format

Share Document