LIS754
– Information Storage and Retrieval
3 Credit Hours
Fall 2007
Instructor:
Frank Cervone
Time: Saturday, 9:00 -
Location: Lewis 330
E-mail: fcervone@dom.edu
IM: HFCervone (AIM/Yahoo)
Skype: frank.cervone
Office
hours: before class or by appointment
Course Description (from
the GSLIS course catalog)
Introduction to the concepts and
techniques of systems analysis and design and their application to information
systems and services. Systems analysis is broadly
defined, including related topics such as cost-benefit analysis and operations
research. Topics include critical path methodology, basic queuing theory,
retrieval system evaluation and measurement, and human factors in information
systems design. The course also offers an introduction to logical data
structuring.
Prerequisites
Objectives
This
course is designed to provide a foundation for understanding the issues related
to information system analysis ande design,
particularly in the context of libraries and information agencies.
At
the conclusion of this course, learners will be able to:
·
Intelligently explain the purpose of
structured systems analysis and design
·
Identify the phases associated with
the software/systems development life cycle.
·
Explain the importance of
information to an organization and why and how it should be managed as any other
resource owned by the organization.
·
Identify the function of entity
relationship diagrams and data flow diagrams in structured systems analysis and
design.
·
Discuss the common methods used to
define the logic associated with all data flow diagram
processes.
·
Discuss the importance of evaluating
project feasibility and how to perform cost based analysis.Define systems analysis and systems life-cycle in
clear terms
Texts
|
Required:
|
Shelly, G. B, Cashman, T. J., and Rosenblatt, H. J. (2008). Systems Analysis and Design,
7th ed. Boston: Thomson Course Technology. ISBN:
978-1-4239-1222-4 |
|
Reserve: |
Additional readings may be
assigned. These will be made available through the course site on
Blackboard. |
Evaluation
Students
are expected to attend, prepare for, and actively participate in all class
activities. Attendance at the on-site
meeting at St. Catherine on September 14 is mandatory. All course participants share
intellectual responsibility for the content of the course. Therefore, learners are expected to ask
questions as well as share informed comments, opinions, and suggestions
in a professional and respectful manner during all class activities.
As a graduate level course, this course covers a wide breadth of material and while it is more important that learners in the class demonstrate the ability to apply the information to problems and issues related to systems design, I need to be able to judge how well you understand the material and can apply it in a professional setting.
To achieve this end, there
are three major graded components of the course: online discussions, exams (a
mid-term and final), and a final project. Each component is explained
below:
·
Online discussions – For the majority of the weeks in
the semester, the class will discuss a research issue. Your answers to these
questions should be from two to four paragraphs per question or component of a
question posed. Your answers should be posted to the course web site by the due
date. Late assignments will not be
accepted without prior arrangements having been made.
·
Exams – the mid-term exam will cover
Chapters 1-7 and the final will cover Chapters 8-11 as well as Toolkits 3 and 4.
·
Course project – During the course of the semester, you will be working with an on-going
case study to implement a project using the material presented in the course.
Projects will be evaluated on both process and product. The process evaluation
includes means and methods used and the product evaluation includes content,
completeness, format, and grammar. More information on the course project
will be provided during our face-to-face meeting on September 14.
Your final grade will be the
composite score of the following:
|
Online
discussions |
10 points each @
25% |
|
Mid-term
exam |
100 points @
20% |
|
Final
exam |
100 points @
20% |
|
Course
project |
100 points @
35% |
The grading scale
is
|
A |
94-100 |
|
A- |
90-93 |
|
B+ |
86-89 |
|
B |
82-85 |
|
B- |
78-81 |
|
C+ |
74-77 |
|
C |
70-73 |
|
C- |
65-69 |
|
D |
60-64 |
|
F |
0-59 |
Course Calendar
|
Date |
Topic |
Readings for this
class session |
Online
discussions |
|
9/14 |
Introduction
|
Chapters 1 and 2
|
1 – Topic to be announced.
Due by September 22.
|
|
9/22 |
Requirements modeling
|
Chapter 3
|
2 – Topic to be
announced –
Due by September 29. |
|
9/29 |
Data and process
modeling |
Chapter 4
|
3 – Topic to be
announced – Due by October 3.
|
|
10/6 |
Object
modeling |
Chapter
5 |
4 – Topic to be announced – Due by October 13. |
|
10/13 |
Development
Strategies |
Chapter
6 |
5 – Topic to be announced – Due by October
20. |
|
10/20 |
Output and User
Interface Design |
Chapter
7 |
6 – Topic to be announced
– Due by October 27.
|
|
10/27 |
Data
Design |
Chapter
8 |
7 – Topic to be announced
– Due by November 3.
|
|
11/3 |
System
Architecture |
Chapter
9 |
8 – Topic to be announced
– Due by November 10.
|
|
11/10 |
Systems
Implementation |
Chapter
10 |
9 – Topic to be announced
– Due by November 17.
|
|
11/17 |
Systems Operations,
Support and Security |
Chapter
11 |
10 – Topic to be announced
– Due by December 1.
|
|
12/1 |
Financial Analysis
Tools |
Toolkit
3 |
11 – Topic to be announced
– Due by December 8.
|
|
12/8 |
Project Management
Tools |
Toolkit
4 |
12 – Topic to be announced
– Due by December 15.
|
|
12/15 |
Final
Week |
Finish up your course
project - Due by December
18. |
|
"All students of the GSLIS are
expected to observe high standards of academic honesty and integrity. Any
student whose conduct violates such standards may be subject to disciplinary
action as determined by due process." (GSLIS Bulletin, p. 48) It is
your responsibility to ensure that your work conforms to the standards of
academic honesty and integrity of the University. Failure to follow these
standards will result in a failing grade for the affected assignment or project.
Last updated: 8/28/2007 9:10:00
PM