Instructors: Adele Hoskin (ahoskin@iquest.net); Debora Shaw (shawd@indiana.edu)
Introduction
L545 - Systems Analysis and Design is a part of the core curriculum for the SLIS Master of Information Science degree. The course provides a coherent and comprehensive view of the processes involved in developing formal information systems. Understanding these processes is essential for anyone working in an organization - an information-intensive and information-rich environment. Taking best advantage of information technologies involves knowing their capabilities and limits, and applying this knowledge to the problems needing solution in an organization.
L545 is based on a behavioral approach to information systems. The underlying assumption is that information systems should be designed to conform to the needs of users, and not vice versa. At the end of the term students should have acquired the knowledge and skills to:
Required: Jeffrey A. Hoffer, Joey F. George, and Joseph S. Valacich, Modern Systems
Analysis and Design,
second edition. Reading, MA: Addison/Wesley, 1999.
Additional readings will be placed on reserve in the SLIS Library.
Grading and Student Evaluation
The final course grade will be computed for each student on the basis of grades assigned
for the following:
Weekly project presentations &observation notes 20% Responses to presentations 10% Consistent and constructive class participation 30% Final Project 40% TOTAL 100%
Each student is expected to complete all course work by the end of the term. A grade of incomplete (I) will be assigned only if exceptional circumstances warrant, and incom-plete work must be completed by October 1, 2000.
Class format: - For every class, there are problems or exercises from the reading that are to be prepared for discussion. Be prepared to display your answers and participate in the class analysis.
At the end of each chapter are key terms. Choose the three terms you believe are the most important and write a brief description of each to be handed in. The three descriptions together should be no more than one page.
In the text on p.37 exercise #6 is a description of keeping an observation journal of observing systems analysis and design in everyday events. These observations are to be submitted by e-mail on each Tuesday to ahoskin@iquest.net.
Weekly Project Presentations: By Wednesday June 28 you will select groups of 3 to 5 students who will undertake a systems analysis project focusing on information handling. This will become your final project for the course. Each Wednesday, starting on June 28, your group will have no more than 7 minutes to report on your activities and progress. For the final project presentation, each class member will critique in writing and hand in the presentations of the other groups - this will be part of your class participation grade. A summary of comments from the class will be provided to the project team after class has ended.
Responses to Project Presentations: Following each project presentation we will have a few minutes to reflect and prepare notes. Then members of other project groups will pose questions to the presenting group to help clarify aspects that were unclear, and to explore ways of addressing problems identified.
Class Participation: includes class attendance, reading assigned material before coming to class, and preparation of exercises "for class discussion" listed with each session.
Final project: As noted above, the final project will be done in groups of 3 to 5. The project will focus on information handling in everyday life. The project is an analysis of the problem showing the decision points and effects of these decisions, modeling the dataflow, and applying (or rejecting) concepts learned in class. Can technology solve the problem? How do you decide?
SLIS Grading Policy
The following definitions of letter grades have been defined by student and faculty members
of the Curriculum Steering Committee and have been approved by the faculty as an aid in
evaluation of academic performance and to assist students by giving them an understanding
of the grading standards of the School of Library and Information Science.
| A | 4.0 | Outstanding achievement. Student performance demonstrates full command of the course materials and evinces a high level of originality and/or creativity that far surpasses course expectations. |
| A- | 3.7 | Excellent achievement. Student performance demonstrates thorough knowledge of the course materials and exceeds course expectations by completing all requirements in a superior manner. |
| B+ | 3.3 | Very good work. Student performance demonstrates above-average comprehension of the course materials and exceeds course expectations on all tasks as defined in the course syllabus. |
| B | 3.0 | Good work. Student performance meets designated course expectations, demonstrates understanding of the course materials and performs at an acceptable level. |
| B- | 2.7 | Marginal work. Student performance demonstrates incomplete understanding of course materials. |
| C+
C |
2.3
2.0 |
Unsatisfactory work. Student performance demonstrates incomplete and inadequate understanding of course materials. |
| C-
D+ D D- |
1.7
1.3 1.0 0.7 |
Unacceptable work. Coursework performed at this level will not count toward the MLS or MIS degree. For the course to count toward the degree, the student must repeat the course with a passing grade. |
| F | 0.0 | Failing. Student may continue in program only with permission of the Dean. |
Class Schedule
The class meets Monday and Wednesday evenings, 5:30-8:45 in Room 001 of the Main Library.
Monday June 19 - Introduction; The System Development Environment
Read: MSA&D Chapter 1 (pages 9-38) - Assignment #6, p. 37 - will be due weekly.
Wednesday June 21 - Managing the Information Systems Project
Read: MSA&D Chapter 3 (pages 69-105)
For class discussion: MSA&D Problems and Exercises, pages 101-102, #2, #6, #8, #9.
For your presentation next week: #11.
Monday June 26 - Making the Business Case
Read: MSA&D Chapters 5&6 (pages 157-184; 191-223)
For class discussion: MSA&D Problems and Exercises, page 182 #9, #10; page 222 #3, #4, #6
Wednesday June 28 - Determining System Requirements
Read: MSA&D Chapter 7 (pages 239-272)
For class discussion: MSA&D Problems and Exercises, page 270 #4, #7
Monday July 3 (yes, class does meet) - Process Modeling
Read: MSA&D Chapter 8 (pages 277-312)
For class discussion: MSA&D Problems and Exercises, page 306 #2, then extend to an e-retail situation; #7, #9
Wednesday July 5 - Logic Modeling
Read: MSA&D Chapter 9 (pages 319-337)
For class discussion: MSA&D Problems and Exercises, page 333 #3, #4
Monday July 10 - Conceptual Data Modeling
Read: MSA&D Chapter 10 (pages 343-378)
For class discussion: MSA&D Problems and Exercises, pages 373-374 #6, #12
Wednesday July 12 - Selecting the Best Alternative Design Strategy
Read: MSA&D Chapter 11 (pages 387-416)
For class discussion: MSA&D Problems and Exercises, pages 413-414 #4, #6, #13
Monday July 17 - Object-Oriented Analysis and Design
Read: MSA&D Chapter 12 (pages 433-484)
For class discussion: MSA&D Problems and Exercises, page 482 #8, #10
Wednesday July 19 - Lizzie Davenport, guest speaker
Read: Lyytinen, Kalle & Hirschheim, Rudy (1987). Information systems failures - a survey and classification of the empirical literature. In Oxford Surveys in Information Technology. Oxford University Press, v. 4, pp. 257-309. (On reserve in SLIS Library)
Monday July 24 - Rapid Application Development
Read: MSA&D Chapter 13 (pages 485-501)
For class discussion: MSA&D Problems and Exercises, page 500 #5, #10
Wednesday July 26 - Alice Robbin, guest speaker
Read: Andersen, David F. & Dawes, Sharon S. Technology, organizations, and people ; and, A forensic mental health database to implement a suicide prevention program. In: Government Information Management. Prentice Hall, 1991, pp. 48-75 and 135-144.
Monday July 31 - Oracle CASE Tools. John Fieber, guest speaker
Wednesday August 2 - Coping with the Realities of IT Planning. Mark Napier, guest speaker
Monday August 7 - Computer Related Risks
Read: Neumann, Peter G. (1995). "A systems-oriented perspective;" "A human-oriented perspective;" and "Implications and conclusions." In Computer Related Risks. ACM Press. Pages 203-311. (On reserve in the SLIS Library)
Wednesday August 9 - Final Project Reports