|
|
BA 4850 Information
Systems Design Fall 2009 |
|
Course Instructor: |
Dr. Joseph Rottman |
|
|
|
228 CCB |
|
|
|
368- 7370 Cell |
Office Hours: |
|
|
516-6288 Office |
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,
Fourth or Fifth edition
Grades: 10% Group lectures/exercises and active class
participation 200
Points
20%
Final Term Paper 400
Points
70%
Group IS Design Project 1400
Points
Total 2000
Points
Expectations: • Students are expected to actively contribute to class discussions and participate in exercises.
•
Late assignments will not be accepted except in the case of a documented
medical 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 weeks 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 by 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 (at least twice during the semester). Note: the team’s assessment of an individual’s performance will 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, the Statement of Work 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.
Tentative
Class Schedule
|
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 |
16 – 17 – 18 |
|
10 |
Implementation and Status Reports |
20 |
|
11 |
Group Status Reports and Presentations |
N/A |
|
12 |
Maintenance and Diffusion Term Papers Due |
21 |
|
13 - 16 |
Preliminary Presentations and Status Reports |
N/A |
|
17 |
Final Presentations |
N/A |
Final Exam Schedule
|
Section |
Date and Time |
|
E01 T 6:55 |
Tuesday, 15 December 07:45 – 09:45 PM |