Instructor: Carol E.B. Choksy, Ph.D., CRM
Office hours: Tuesdays, 1:00 to 3:00 pm
Office: Main Library 022
E-mail: cchoksy@indiana.edu
Telephone: (812) 856-2323
Using real-world examples we will study how information technology can successfully enable the exploitation of information by an organization. That exploitation will be examined from a number of different perspectives including business needs, user expectations, corporate culture, what technology can actually do, and compliance.
Students will learn how to assess and analyze the current processes and systems in place, both manual and automated, model those processes and systems, make recommendations for potential solutions, and create conceptual-level designs for those solutions. Students will also learn the basic principles of project management including scoping a project and managing scope creep, stakeholder management, team creation and management, identification of strategic and tactical threats to the project and when to prematurely terminate a project.
Whitten, Jeffrey, Lonnie D. Bentley, Kevin C. Dittman. Systems Analysis and Design Methods. 6th Edition. New York: McGraw-Hill, 2004.
Cleland, David I., Lewis R. Ireland. Project Management: Strategic Design and Implementation. 4th Edition. New York: McGraw-Hill, 2002.
Kloppenborg, Timothy J. and Petrick, Joseph A. “Leadership in Project Life Cycle and Team Character Development” Project Management Journal, 30 (June 1999)2: p. 8-14. In EBSCO Host
Roadmap for E-government in the Developing World. By the Working Group on E-government in the Developing World, Pacific Council on International Policy, Western Partner of the Council on Foreign Relations, April 2002. http://www.informationweek.com/story/showArticle.jhtml?articleID=15800298
Whiting, Rick. “Money Machines,” InformationWeek, 3 November 2003 http://www.informationweek.com/story/showArticle.jhtml?articleID=15800298
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+ |
2.3 |
Unsatisfactory work. Student performance demonstrates incomplete and inadequate understanding of course materials. |
| C- |
1.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. |
Academic misconduct (e.g. plagiarism) and personal misconduct by students in this class are defined and will be dealt with according to the procedures in the Indiana University Code of Student Ethics.
Class Participation—each student is expected to contribute to class discussion
By each individual
Create team PeopleSoft project plan
By teams
Due 1/20/04
Define ‘analysis’ in the systems context
2-page paper by each individual
Due 1/20/04
Review the strengths and weaknesses of MS SQL Server, Oracle and DB2 databases and give a recommendation to Indiana University which one is most appropriate for its university-wide applications
3-page paper by each individual, use tables where appropriate
Due 1/27/04
What is PeopleSoft, what does it do, how does it work, what is its architecture, what limitations does it have?
5-page paper by each individual
Due 2/10/04
Create team project plan for final project.
By teams
Due 2/17/04
What are the high-level business, functional, and technical requirements for the PeopleSoft system at Indiana University? Include a conceptual architecture, recommendations, and an analysis of impediments to successful implementation
By teams
Due 3/2/04
Evaluate your team. This can be in the form of a journal or a narrative. What are your teams strengths and weaknesses? What does each person contribute to the team? Who is the leader? Who feels most comfortable giving a recommendation? Who is the best analyst? Who is the best interviewer?
10-page paper by individuals
Due 4/20
IT project study. Study will include high-level business, functional and technical requirements, solution recommendations, any impediments to the problem, a system architecture, and at least two workflow diagrams. Teams will also present their findings to the class.
By teams
Complete Final Report and Presentation Due 4/27/04
| PeopleSoft project plan |
5% |
| ‘Analysis’ paper |
5% |
| Database paper |
10% |
| PeopleSoft paper |
15% |
| IU PeopleSoft project |
15% |
| Team evaluation |
10% |
| Team IT project study |
25% |
| Team IT project plan |
5% |
| Class participation |
10% |
| Date |
Topic |
Assignment |
Reading and Notes |
| 1/13 |
1. Analysis Introduction |
Choose teams for IUB PeopleSoft study and SAD project for each team. Teams begin looking for an IT project within the University to study Create team PeopleSoft project plan Due 1/20/04 Define ‘analysis’ in the systems context 2-page paper by each individual Due 1/20/04 |
Reading “Analysts in Action,” Episodes 1-3, Chapters 1-3 in Whitten, Bentley & Ditten and http://c2.com/cgi/wiki?WhatIsAnalysis Think about the definition of “analysis” Analysis: Indo-European root: leu, to cut OED Generally: The resolution or breaking up of anything complex into its various simple elements. A tabular statement or other form embodying the results of the above process; an abridgement exhibiting the essential heads; a synopsis or conspectus. Chemical: The resolution of a chemical compound into its proximate or ultimate elements; the determination of the elements of which it is composed; or, in the case of a substance of known composition, such as water, of the foreign substances which it may contain. Optics: the resolution of light into its prismatic constituents. Literature: the investigation of any production of the intellect, as a poem, tale, argument, philosophical system, so as to exhibit its component elements in simple form. Grammar: the ascertainment of the elements composing a sentence or any part of it. Math, modern analysis: the resolving of problems by reducing them to equations. Logic: the tracing of things to their source, and the resolution of knowledge into its original principles; the discovery of general principles underlying concrete phenomena. |
| 1/20 |
2. Project Management Introduction |
PeoleSoft project plan due ‘Analysis’ paper due Review the strengths and weaknesses of MS SQL Server, Oracle and DB2 databases and give a recommendation to Indiana University which one is most appropriate for its university-wide applications 3-page paper by each individual, use tables where appropriate Due 1/27/04 |
Reading Chapters 1-6, Cleland & Ireland Kloppenberg and Petrick article |
| 1/27 |
3. PeopleSoft, SIS & HRIS at Indiana University Introduction to project teams |
Database paper due What is PeopleSoft, what does it do, how does it work, what is its architecture, what limitations does it have? 5-page paper by each individual Due 2/10/04 |
Laurie Sullivan will speak Reading Chapters 18 & 20 in Cleland & Ireland The Working Group on E-government in the Developing World. Roadmap for E-government in the Developing World. Pacific Council on International Policy, Western Partner of the Council on Foreign Relations April 2002. http://www.informationweek.com/story/showArticle.jhtml?articleID=15800298 Whiting, Rick. “Money Machines,” InformationWeek 11/3/03 http://www.informationweek.com/story/showArticle.jhtml?articleID=15800298 |
| 2/3 |
4. Organizing the Project Team and Plan |
Teams finalize selection of IT project to study What are the high-level business, functional, and technical requirements for the PeopleSoft system at Indiana University? Include a conceptual architecture, recommendations, and an analysis of impediments to successful implementation. Teams will also make brief presentation to class on findings and recommendations By teams Due 3/2/04 |
Chapters 8-12 in Cleland & Ireland |
| 2/10 |
5. Requirements Gathering |
PeopleSoft paper due Teams finalize interviews for IT project study. Study will include high-level business, functional and technical requirements, solution recommendations, any impediments to the problem, a system architecture, and at least two workflow diagrams. Complete Final Report and Presentation Due 4/27/04 Create team IT project plan. Team project plan due 2/17/04 |
“Analysts in Action” Episodes 5-6 & Chapters 5-6 in Whitten, Bentley & Ditten |
| 2/17 |
6. Project Leadership, Communication & Issues |
Team project plan due |
Chapters 7, 16-17 Cleland & Ireland |
| 2/24 |
7. Modeling |
“Analysts in Action” Episodes 7-8 & Chapters 7-8 in Whitten, Bentley & Ditten |
|
| 3/2 |
8. Modeling |
PeopleSoft Requirements paper due Short team presentations on PeopleSoft due |
“Analysts in Action” Episode 9 & Chapters 9-11 in Whitten, Bentley & Ditten |
| 3/9 |
9. Project Evaluation |
Evaluate your team. 10-page paper by individuals Due 4/20 |
Discuss requirements documents Chapters 13-14 in Cleland & Ireland |
| 3/16 |
10. NO CLASS |
RELAX |
SPRING BREAK |
| 3/23 |
11. Build v. Buy |
“Analysts in Action” Episode 10 & Chapter 12 in Whitten, Bentley & Ditten |
|
| 3/30 |
12. Architecture |
“Analysts in Action” Episode 11 & Chapter 13 in Whitten, Bentley & Ditten |
|
| 4/6 |
13. Data and Documents |
“Analysts in Action” Episode 12 & Chapter 14 in Whitten, Bentley & Ditten |
|
| 4/13 |
14. Output, Input and Interface Design |
“Analysts in Action” Episode 13-15 & Chapters 15-17 in Whitten, Bentley & Ditten |
|
| 4/20 |
15. Storage Design |
Team Evaluation due |
http://whatis.techtarget.com/wsearchResults/1,290214,sid9,00.html?query=storage read each entry under the “Exact Match” section http://www.webopedia.com/Hardware/Data_Storage/ browse the “Terms” section |
| 4/27 |
16. Project Termination |
Final Report and Presentation Due |
Chapter 15 in Cleland & Ireland |