CMIS 470: Systems Analysis and Design
Course Information:
Web
Page: www.siue.edu/~apowell
Office: FH 2311
Email: apowell@siue.edu
Phone: 650-2590
Required Textbook: Satzinger,
Jackson, and Burd, 2002. 2nd Edition.
Systems Analysis
and
Design in a Changing World. Course Technology / Thomson Learning. ISBN
0-619-06309-2. This is a rental book.
Optional
Textbooks: A reference book on how to use Microsoft
Project
Suggestions
include:
IDG
Books Worldwide Publishers, Copyright 2000
The Complete Idiot’s Guide to Project Management with Microsoft Project 2000, By Ron Black
Que
(a division of Macmillan Computer Publishing)
A reference
book on UML:
UML
Distilled, 2nd edition, By Martin Fowler with Kendall Scott
Addison-Wesley, Copyright 2000.
Handouts: You will receive several handouts throughout this
semester. I suggest you purchase a
3-ring binder for this course (at least 1.5, probably 2 inch).
This course is an extension of CMIS270. Building on your knowledge of the systems development life cycle, we will examine several other methods used in the analysis, design, and development of information systems. Methodologies included as topics in this class include Large Package Implementation (using SAP), Object-Oriented development, Rapid application development, Developmental prototyping, and Oracle. Project management essentials will be covered as you complete your senior research requirement.
· To solidify our understanding of the traditional systems development life cycle by:
▫ Revisiting the full framework and drilling down on the later stages of implementation and maintenance
▫ Taking a new application development project through all phases of the SDLC (except maintenance) using Oracle.
· To gain knowledge and understanding of the object-oriented approach to analysis and design.
· To consider alternative development methodologies and in what situations they may be particularly appropriate.
· To gain knowledge and understanding of issues, strategies, and tasks related to large package implementations (such as ERPs).
· To develop skills to use Oracle Designer as an alternative development methodology.
· To gain knowledge of standard practices in project management.
· To experience and practice project management (including project plan definition, tracking, and reporting).
· To conduct research that further examines a course topic, going more in-depth and more into real-world aspects of it.
Class sessions will vary in using lectures, hands-on-tutorials, in-class exercises, demonstrations, and other classroom experiences. Classes are designed to supplement the textbook and other readings. Because of the nature of the material in this course, the focus of the class sessions will be on integrating the material into the course as a whole.
Final course grades will be determined using the following fixed percentage cutoffs:
A = Excellent work. 90-100.
B = Good work. 80-89.
C = Acceptable work. 70-79.
D = Marginally acceptable work. 60-69.
F = Unacceptable work. Under 60..
Assessment |
Possible
Points |
Exam1 Covers Ch 14, 15, O-O pages, ERP handouts, lecture material |
150 |
Research
Requirement – Project Management Component Includes project definition deliverables,
status reports, Project completion report, peer evaluation |
130 |
Research
Requirement – End Product |
150 |
Oracle Designer
Assignments (5) |
75 |
Misc. Homework
Assignments (5) |
75 |
Exam 2 (Final
Exam) |
150 |
TOTAL POINTS |
730 |
Summary of Tools Used in this Class
· Oracle Designer
· Microsoft Project
· SAP R/3
IMPORTANT Course Policies!
DO YOUR OWN WORK.
All projects (except the
Research Requirements project) are to be done individually. If it is determined that
you copied someone else’s work, you will receive a failing grade for the
course.
This action is in
accordance with the SIUE policy on plagiarism that states: “… a student who
plagiarizes shall receive a grade of F in the course in which the act
occurs. The offense shall also be
reported to the Provost. A student who
is reported a second time shall be suspended for a period of not less than one
term. Should a student who has been
suspended for plagiarism be readmitted and be again found guilty of the
offense, he/she shall be permanently expelled from the University.” For further details, see http://www.siue.edu/POLICIES/1i6.html.
Don’t even think
about copying someone else’s work. You
are here to learn. Doing you own work on
assignments is a crucial part of the learning process. Exams will be designed to “unmask” students
who may not have worked individually on a homework assignment.
KEEP UP
We’re covering a lot of
ground in this class and there’s something due nearly every week. There is no time to fall behind and
recover. So you need to not fall
behind.
Each assignment will
carry an explicit due date, always a class meeting date. An assignment submitted after the due date
will receive a deduction of 5% for each day it is late (including weekends and
holidays). After one full week has
passed, the assignment will receive no credit.
SYLLABUS
|
Date |
Topic |
|
Notes |
|
WEEK 1 |
Course Introduction Instructor Introduction Quick review of the SDLC Implementation & Maintenance phase |
Chapter 15 |
Get Microsoft Project reference book Rent textbook |
|
WEEK 2 |
Object Oriented approach Use Case Diagrams Class Diagrams |
Ch3 84-86 Ch5 153-162 Ch7 237-250 |
Fill out time forms |
|
WEEK 3 |
Object Oriented approach Sequence Diagrams Initiate the research requirement project Library Search Hints |
Ch5 163-170 Ch5 176-183 Ch7 250-263 |
OO homework 1 DUE Receive team members |
|
WEEK 4 |
Project management Basics of Microsoft Project |
Appendix A Appendix B Project Management Handouts |
OO homework 2 DUE! |
|
WEEK 5 |
Package software, Intro to Large Package Implementation (LPI) Intro to hands-on SAP R/3 |
Chapter 14 ERP handouts |
RR PDD DUE MS Project Homework DUE! |
|
WEEK 6 |
What to expect for Exam 1 Team time for RR project Revew PDD |
|
RR WBS DUE ERP Homework DUE |
|
WEEK 7 |
Exam 1 Review PDD and WBS
|
|
|
|
WEEK 8 |
Rapid Application Development Extreme Programming Spiral Approach Developmental prototyping |
Chapter 13 pp. 529-553 |
RR – Baseline Project Plan DUE |
|
WEEK 9 |
Intro to Oracle Designer Oracle Designer: Process Modeling |
|
RR – Project Status Report DUE |
|
WEEK 10 |
Oracle Designer: E-R Diagramming |
|
OD Process Modeling homework DUE RR – Project Status report |
|
WEEK 11 |
Oracle Designer: FHD and the CRUD Matrix |
|
OD ERD homework DUE RR – Project status report DUE |
|
WEEK 12 |
Oracle Designer: Creating the Database Design (DDT) |
|
OD FHD and CRUD homework DUE RR – Project status report DUE |
|
WEEK 13 |
Oracle Designer: Generating the Database and Table API |
|
OD DDT homework DUE |
|
WEEK 14 |
Oracle Designer: Generating Prototype Applications |
|
OO Database and Table API homework DUE RR – Project Status Report DUE |
|
WEEK 15 |
Review of the Oracle Designer process What to expect for Exam 2 |
|
RR – Final End Product |
|
FINAL |
|
||