Prototypes Versus Pilot Systems: Strategies for Evolutionary Information System Development

Rzevski, George

doi:10.1007/978-3-642-69796-8_30

Cited by 18 publications

(10 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The search for a solution is based on the search for a definition which best fits current knowledge. The inevitable result of solution attempts is the acquisition of new knowledge (see, for example, discussions in [77,125]). The added insight pertaining to the environment, or the problem, normally comes from tinkering with a solution, as proposed by Rittel [119,121].…”

Section: Characterising Adaptive Designmentioning

confidence: 99%

Consilience for universal design: the emergence of a third culture

Далчер

2006

Univ Access Inf Soc

View full text Add to dashboard Cite

Consilience offers a powerful mechanism for borrowing from other disciplines, thereby extending the scope of what can be known. This paper looks at the foundations of the activity of design as a means of providing IT systems that cater for diverse needs. Developing systems that are expected to satisfy needs continuously (i.e., systems that are expected to evolve) calls for a dynamic activity of design that is responsive to changes in the environment. The contrast with the scientific assumption of ordered development invokes a new classification, supported by insights from other disciplines that place the range of approaches in context. Design is neither orderly nor linear; it implies a continuous and active search to resolve trade-offs and satisfy changing constraints. The paper concludes by making a case for design as an alternative culture that borrows from, and supports, both the scientific and the literary cultures. Acceptance of the role of practice as an interface alongside the more traditional cultures enables researchers and practitioners to access and adopt a larger variety of methods and general approaches underpinning an even larger corpus of insights. Consilience can occur at different levels and offer a variety of benefits. Balancing scientific enquiry with artistic flair and creativity through careful sensemaking that supports sharing across cultures provides the greatest benefit from learning to look across rather than blindly focusing inwards.

show abstract

Section: Characterising Adaptive Designmentioning

confidence: 99%

Consilience for universal design: the emergence of a third culture

Далчер

2006

Univ Access Inf Soc

View full text Add to dashboard Cite

show abstract

“…However, feedback from real-use experiences is important for several reasons. First, developers and users need a deeper understanding of how the system may support the users' work and what they require from the system [Boehm, 2000;Rzevski, 1984]. Second, real-use experiences are necessary in order for organizational consequences and opportunities of the system to emerge, especially in complex organizational settings where systems affect multiple interrelated stakeholder groups [Bossen, 2007;Orlikowski, 1996].…”

Section: Related Workmentioning

confidence: 99%

“…Pilot systems have much in common with prototypes, and proponents of a broad definition of prototypes may see pilot systems as a subclass of prototypes (e.g., Floyd, 1984). We prefer to distinguish pilot systems from prototypes to emphasize that pilot systems are properly engineered and evaluated in their intended environment with real data [Rzevski, 1984]. At the same time, pilot systems are not finalized and are therefore restricted to limited implementation.…”

Section: Introductionmentioning

confidence: 99%

Pilot Implementation: Learning from Field Tests in IS Development

Hertzum¹,

Bansler²,

Havn³

et al. 2012

CAIS

View full text Add to dashboard Cite

A recurrent problem in information-systems development (ISD) is that many design shortcomings are not detected during development, but first after the system has been delivered and implemented in its intended environment. Pilot implementations appear to promise a way to extend prototyping from the laboratory to the field, thereby allowing users to experience a system design under realistic conditions and developers to get feedback from realistic use while the design is still malleable. We characterize pilot implementation, contrast it with prototyping, propose a fiveelement model of pilot implementation and provide three empirical illustrations of our model. We conclude that pilot implementation has much merit as an ISD technique when system performance is contingent on context. But we also warn developers that, despite their seductive conceptual simplicity, pilot implementations can be difficult to plan and conduct. It is sometimes assumed that pilot implementations are less complicated and risky than ordinary implementations. Pilot implementations are, however, neither prototyping nor small-scale versions of full-scale implementations; they are fundamentally different and have their own challenges, which will be enumerated and discussed in this article.

show abstract

“…Iterative prototyping is the process of creating, in advance of the implementation, a working model (the prototype) that exhibits essential features of the final system and using this prototype to test aspects of the design, illustrate ideas or features, and gather early feedback. Pilot implementation involves using and evaluating a more mature but still unfinished pilot system (Rzevski, 1984) in a restricted manner. During the pilot period the system is used in its intended work environment and using real data.…”

Section: Effects-driven It Developmentmentioning

confidence: 99%

“…Planned changes are specified, in terms of desired effects expected to manifest from using the system. A pilot of the system is then implemented and tried out under conditions as close as possible to real use -a process sometimes referred to as a pi-lot study or pilot implementation (Glass, 1997;Rzevski, 1984;Turner, 2005). Actual use of the system allows for measuring the planned effects, for the emergent and opportunity-based changes to occur, and for the identification of curtailed effects.…”

Section: Effects-driven It Developmentmentioning

confidence: 99%

Effects-driven IT development

Hertzum

Simonsen

2010

Proceedings of the 11th Biennial Participatory Design Conference

View full text Add to dashboard Cite

We present effects-driven IT development as an instrument for pursuing and reinforcing Participatory Design (PD) when it is applied in commercial information technology (IT) projects. Effects-driven IT development supports the management of a sustained PD process throughout design and organizational implementation. The focus is on the effects to be achieved by users through their adoption and use of a system. The overall idea is to (a) specify the purpose of a system as effects that are both measurable and meaningful to the users, and (b) evaluate the absence or presence of these effects during real use of the system. Effects are formulated in a user-oriented terminology, and they can be evaluated and revised with users in an iterative and incremental systems-development process that involves pilot implementations. In this paper we investigate the design, pilot implementation, and effects assessment of an electronic patient record. Effects concerning, among other things, clinicians" mental workload were specified and measured, but apart from the planned changes associated with these effects the pilot implementation also gave rise to emergent, opportunitybased, and curtailed changes. We discuss our experiences regarding conditions for making the specification of effects and their real-use evaluation central activities in IT projects.

show abstract

Prototypes Versus Pilot Systems: Strategies for Evolutionary Information System Development

Cited by 18 publications

References 7 publications

Consilience for universal design: the emergence of a third culture

Consilience for universal design: the emergence of a third culture

Pilot Implementation: Learning from Field Tests in IS Development

Effects-driven IT development

Contact Info

Product

Resources

About