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

Blog #5 - "Introduction to Databases"

P. Tero (2004). "Introduction to Databases"

The article is very much an introduction to databases. That is to say, Tero doesn't get into much detail. He does however, cover four areas: SQL, websites/databases, scripts, and querys.

He explains that SQL is an acronymn for Structured Query Language. This is apparently the language in which relational databases speak to one another. Its operations look similar to HTML, but the similarities end there. Tero mentioned that popular database software programs use SQL but hide them behind the user interface.

He mentions briefly the relationship websites can have with databases. The only use for this I saw, for companies, based on his explanation was the idea of constantly having access to company records and orders via an intranet. With respect to his ideas on queries, the explanation was rather simple. He only says that they can be used to retrieve specific data. He also shows what a stringed query would look like in SQL. However, the explanation and examples ... and subsequent explanation of the examples are sparse.

The entire article seemed like an abstract or executive report that would be given to a company president, with the intent of convincing them of the necessity of using a database.

Library 2.0: Service for the Next-Generation Library

The article is outdated. It was written in 2006, and has long since been surpassed. The essence of the article is the then move towards library 2.0. This, of course, has already happened. The authors focus on what was relevant at the time. That is to say, they write about user generated content, online downloads, and reviews. This was very interesting in 2006, but we're in 2010. User generated content should be automatic.

Unfortunately, it is not true. Many libraries are still filled with Baby Booming Generation Exers and remain clueless to the changing trends and how to employ them.

I will say that for the time period, the authors had the right idea. User generated content was coming of age, so to speak. However, with the move towards newer better and more expansive "library 2.0" apps and methods, the article seems little more than an example of what libraries and librarians should be doing with respect to the changing technologies of the day.

Library 2.0: Service for the Next-Generation Library by: Casey, Michael E., Savastinuk, Laura C