BA 4850 Information Systems Design Spring 2005

Course Instructor:	Dr. Joseph Rottman	rottman@umsl.edu
	228 CCB	www.umsl.edu/~rottman/BA310
	842-4507 Home	Office Hours:
	516-6288 Office	4:00 – 6:00 TR and by appointment
Note: When communicating with me, please be sure to indicate your section and team numbers.

Course Description: System design, implementation, and methods of systems installation and operation are presented. A system development project is required. This course builds on the skills learned in BA 3810 (Information Systems Analysis) and has at its core the design and development of an information system.

Prerequisites: BA 3845, BA 3810, one of either BA 3815 or BA 3816, and a minimum campus GPA of 2.0.

Text: Hoffer, J.A., J.F. George and J.S. Valacich, Modern Systems Analysis and Design, Second Edition or Third Edition

Grades: 40% Exams (Midterm 20% and Final 20%) 800 Points

10% Group Lectures and Participation 200 Points

50% Group IS Design Project 1000 Points

Class Participation: Attending class is the responsibility of the student. Late assignments or tests will not be accepted except in the case of a documented emergency.

Please set all beepers / cell phones to vibrate each class period.

Academic Honesty: Students are expected to adhere to the University of Missouri’s policy on Academic Honesty.

Group IS Design Project:

• During the first week of the semester, teams will be formed with the goal to diffuse the level of IS skill as well as the exposure to possible design opportunities. The selection of a “problem” to solve with the creation of a new system as well as the tools used for that creation will be the responsibility of the team. The system that you analyzed in Systems Analysis is “fair game” for this class since the design of an information system depends on an accurate analysis of the system needs. If you choose a different system, it is expected that the analysis tools learned in Systems Analysis will be utilized.
  
  
• Since the design project will be the result of a group effort (all group members will initially receive the same grade), you will have the opportunity to evaluate your team members (twice during the semester) and I will make adjustments as necessary. Note: the team’s assessment of individual’s performance can affect (favorably or adversely) that individual’s grade.
  
  
• The projects will be judged on the ability of the application and documentation to meet the needs of the user as detailed in the Baseline Project Plan and the System Proposal.

• Presentations (both oral and written) are expected to be of professional quality. This includes format, correctness and style.
  
  
• Expect to spend considerable time outside of class designing and testing your system.
  
  
• Additional information will be distributed later in the semester concerning the projects.
  

Important Dates:

Spring 2005

Class Work begins 8:00 AM	Monday	January 10
Spring Break Begins	Saturday	March 19
Classes Resume	Monday	March 28
Classes End	Monday	May 2
Intensive Study Days	Tues. and Wed.	May 3 and 4
Final Examinations Begin	Thursday	May 5
Spring Semester Closes	Friday	May 13
Commencement	Saturday	May 14

Tentative Class Schedule

Winter 2004

Approximate Week	Topic	Text Chapters
1	Introduction, Syllabus and Team Selection	N/A
2 – 4	Review of Analysis	1 – 14
5 – 7	Forms, Reports, Interfaces and Dialogues -First Group Presentations	14 – 15
8 – 9	Data Modeling and Databases -Mid Term Exam	16 – 17 – 18
10	Implementation and Status Reports	20
11	Group Status Reports and Presentations	N/A
12	Maintenance and Diffusion	21
13	Preliminary Presentations and Status Reports	N/A
15	Final Presentation and Exam	N/A

Final Exam Schedule

Section	Date	Time
D01 TR 2:00– 3:15	Thursday, May 12	2:45 - 4:45 pm
E01 TR 5:30 – 6:45	Tuesday, May 10	5:30 - 7:45 pm