The system development life cycle and digital library development

This article is more about generic system development life cycles than about "digital library system life cycles." The main idea is that there is a standard set of steps that all systems undergo. It can honestly be applied to any system. The steps, in a nutshell are: Preliminary investigation, Problem analysis, Requirements analysis, Decision analysis, Design, Construction, Implementation, Operation and support. I'll very briefly explain them.

Preliminary investigation is determining what, if anything, needs to be done. Problem analysis determines the shortcomings of the current system. Requirement analysis determines the cost and time needed to undergo the change. Decision analysis is when the "higher ups" determine whether or not the plan is feasible. Design builds the idea for the system while Construction builds the actual system. Implementation puts the system into place. Operation and support use and trouble shoot the system.

The article explained, fairly well, the process by which systems change over. I should mention that the author wrote about the difficulties of the final stage (having two concurrently running systems). The situation, according to the article, happens because it is the easiest way to transition from old to new systems. The trouble is that the organization must then maintain both systems.

While they eventually fully integrate the new system, it is only on step one of its life cycle ... only to soon be replaced by another.



MANAGING DIGITAL LIBRARIES:
THE VIEW FROM 30,000 FEET
The system development life
cycle and digital library
development
H. Frank Cervone
Northwestern University, Evanston, Illinois, USA