ABSTRACT
A library's automated acquisitions system can be the workhorse of technical services. Developing a new acquisitions system for any automation vendor can be a challenge. How does an ILS vendor create an acquisitions system that meets the needs of libraries when workflows vary from library to library? Dynix has used a process called Contextual Inquiry as they develop a new acquisitions system. Contextual inquiry, or CI, is a process in which one or two members of a development team spend an amount time at libraries watching staff as they work while taking notes and asking questions. This happens before software coding even begins. This information is taken back to a development team where engineers are immersed in how libraries order, receive, and invoice serial titles. Only after the development team has a good understanding of the process does coding begin.
This presentation will discuss how an integrated library system (ILS) vendor develops software and describe the methods and processes we use. Although I think that ILS vendors probably use many of the same processes, my remarks will be based only on my own experience. [Article copies available for a fee from The Haworth Document Delivery Sendee: 1-800-HAWORTH. E-mail address: <docdelivery@haworthpress.com> Website: < https://www.HaworthPress.com" xmlns:xlink="https://www.w3.org/1999/xlink">https://www.HaworthPress.com >]
