AMIS 835 - Systems Analysis and Design
Winter 2003
MW 8:00 - 10:00 PM     Gerlach 355

1. INSTRUCTOR:
       Dr. John Butler
        OFFICE:
            448 Fisher Hall, Fisher College of Business, The Ohio State University,
            Columbus, Ohio 43210
        OFFICE HOURS:
            By Appointment
        OFFICE PHONE:
            (614) 688-8679
        E-MAIL:
      butlerj@cob.ohio-state.edu
         the subject of all messages must be AMIS 835

2. COURSE TEXTS:

  1. Required text: Systems Analysis and Deisgn: An Active Approach by George M. Marakas; and my lecture notes.
  2. This syllabus serves as an interactive entry point into all materials covered in this class. It WILL be updated frequently during the quarter, so check often for new links, notes, messages, and other related material.
3. COURSE DESCRIPTION & OBJECTIVES:

The focus of this course is the study of systems, and the principles of systems analysis and design. This course introduces you to organizational systems analysis and design, and presents ideas that provide powerful insights about a large spectrum of analysis and design issues. This course aims to give you a feeling for the problems and techniques of systems analysis and design, and the application of such techniques to real life business analysis problems.

4. STUDENT RESPONSIBILITIES:
 
You are expected to have read carefully the assigned portion of the book prior to coming to class (and I encourage you to discuss it with friends); most of the class time will be devoted to the discussion of applications and extensions of the material in the book. 
You are expected to complete all assignments. The assignments are to be completed in teams. Submit only one report per group. 
You may work on assignments together (for example, discuss how to work a problem or rough out a solution), but every group must turn in work that has been completed individually. Solutions may not be “copied” and “pasted” by multiple groups.  The purpose of the assignments is not to find a solution on the Internet or from students who took this class previously.  If you do find some useful information on the web or from another source it should be referenced!  Evidence of cheating in any form will be met with serious punishment including formal channels at the University level. 

5. GRADING POLICY:
 
There is one exam and one final project, each worth 35% of the total score. No makeup exams will be arranged. 
Homework and lab assignments will be given in class. The homework & lab assignments are worth 20% of the total score. No credit is given for late homework. 
The remaining 10% is assigned to class participation and quizzes. Quizzes on the reading assignment can be expected.

6. TENTATIVE SCHEDULE:
 
 
Week Topic Readings Class Notes Assignments
1
Jan 6, 8
Intro to Systems Analysis & Design
Problem Identification
Chapter 1
Chapter 2
chap1.ppt
chap2.ppt
2
Jan 13, 15
Cross-cutting Activites
Picking IS/IT Projects
Appendix A
Chapter 3
AppA.ppt
chap3.ppt
HW#1 due 1/13
3
Jan 22
MLK DAY 1/20 : No class
Requirements Analysis

Chapter 4
Value Focused Thinking

chap4.ppt

HW#2 due 1/22
4
Jan 27, 29
Value Focused Thinking
 

Estimation and Biases

VFT at Seagate
VFT in E-commerce

Chapter 8, pp. 219-235

VFT-Seagate.ppt
 

Estimation.ppt

5
Feb 3, 5
Modeling the Processes
Modeling the Data
Chapter 5
Chapter 6
chap5.ppt
chap6.ppt
6
Feb 10, 12
Examples of Data and Logical Modeling
Object Oriented OOAD

Appendix B

appB.ppt
7
Feb 17, 19
*Snow Day*

Diverse Envioronment Design
CASE Tools
Design Concepts

Chapter 9
Chapter 7
Chapter 10

chap9.ppt
chap7.ppt
chap10.ppt

8
Feb 24, 26
Design Concepts
 

Exam Wednesday, 2.26.02

Chapter 11
Chapter 12
Chapter 13
chap11.ppt
chap12.ppt
chap13.ppt
HW#3 due 2/24
9
Mar 3, 5
Presentations
Presentations
10
Mar 10, 12
Presentations
Presentations
Final
Projects
Write ups due  3/17 @ 5:00PM 
** graduating seniors writeups due on 
    3/12 @ 5:00 PM

7. ARRANGEMENTS FOR ASSIGNMENTS:

Assignments may be completed in groups or individually depending on the specific assignment. Only one report is to be submitted per group when a team is used. To prevent free-riding the group may be split at any time during the quarter, by written notification to the professor. Free-riding is further discouraged in that questions from the assignments will appear on the exams, and peer-evaluation will be solicited.

Note that some assignments might take more than a few hours to finish. You should submit the required material to your professor. The assignments are due at the beginning of the class session. No late assignments will be accepted - no exceptions.

8. MESSAGES:

01/20/03 Here are a couple of organizations that are related to Systems Analysis and Design

9. GRADES:
 

10.  CONTACT INFO
 
 
e-mail entire class, exclude Butler
e-mail entire class, including Butler