CMIS 570: 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,
J., Jackson, R., and Burd, S. 2004. Systems Analysis & Design in a Changing World. 3rd edition. Thomson Course
Technology,
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).
Other readings my be assigned during the semester.
This course prepares you to become an information systems analyst, either internal to a corporation or as a consultant, and to manage systems development projects. Because these jobs are crucial to the IS field, the concepts and skills developed in this course are central to a career in information systems, i.e., this is a course for your career prospects. The course covers concepts of information systems, methodologies, and techniques used for systems analysis and design, and technologies used during the development of information systems. The course will take an applied approach. You will demonstrate your mastery of the material by applying what you learn in class and homework exercises, in exams, and in a running project. You will not implement an information system in this course. Rather, you will follow the process of systems analysis from inception of a project through the specification or what the system is to do.
Multiple methodologies for completing a systems development project will be introduced in this course. Methodologies covered in this class include: Systems development life cycle (SDLC), Object-Oriented development, Large Package Implementation (including SAP), Rapid application development, Developmental prototyping, and Oracle.
The overall course objective is for you to develop the concepts and skills needed to develop and information system using a variety of popular methodologies. Detailed objectives are:
· To develop an understanding of “systems”.
· To build an understanding of the Systems Development Life Cycle – the processes required to develop information systems.
· To analyze a business need for information and develop an appropriate strategy to solve the problem and hence provide the required information service.
· To learn to use a number of relevant analysis techniques (e.g., process, conceptual data models, use cases, class diagrams, sequence diagrams, etc.) to aid in defining information requirements.
· To consider alternative development methodologies and in what situations they may be particularly appropriate.
· To gain knowledge and understating of the object-oriented approach, and issues, strategies, and tasks related to large package implementations.
· To develop skills to use Oracle Designer as an alternative development methodology.
· To communicate systems design specifications effectively and persuasively in both written and oral forms.
· To gain knowledge of standard practices in project management.
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 class member contributions. 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. For this reason, classes will most often take a higher-level perspective than the text readings for that day, i.e., lectures will not necessarily address text directly, and they will not cover all of the detail in the text; they will build on what is presented in the text and contributions from class members. Bottom line: Read your textbook.
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.
Homework Assignments |
Points
possible |
| Traditional Development: 9 homework assignments |
280 |
| Object Oriented Development: 3 homework assignments |
90 |
| Oracle Development: 6 homework assignments |
180 |
Midterm Exam |
100 |
Final exam |
100 |
750 |
Homeworks
There are 18 assigned homework exercises for this course. These include:
Traditional Development: Problem Statement, Statement of Project scope, Gantt Chart, Cost-Benefit Analysis, Data flow diagram, Entity-relationship diagram, Alternative design specifications, Report Designs, and Screen Designs.
Object Oriented development: Use-case diagram, Class diagram, Sequence diagram
Oracle development: Process model, ERD, FHD/CRUD, DDT, API, Application screen
These homework assignments are to provide you with knowledge about how to develop a system using different methodologies. Doing assignments from different methodologies will enhance your ability to compare processes and outcomes of different system methodologies.
Class Participation
/ Professionalism
In this course, you share with me the responsibility of
your learning. Participation by class
members who have been involved in system development in the past (or currently)
will enhance the learning of all students.
You are expected to show respect, collegiality, and good citizenship
toward others is the class.
Project
A semester long project will be the basis for all homework assignments. You will be able to select a project on your own, subject to approval from the professor. Alternatively, you may choose to work on a case provided in class.
Exams
There will be three exams given in class. If English is not your first language, and you encounter words or phrases you do not understand on the exams, please do not hesitate to ask the instructor for clarification.
Timeliness: If you want full credit for a written assignment, you will have to turn it in at the beginning of class period on the day it is due. Late work will be accepted – at a 5% reduction per day. Once the homework assignment has been returned to those making the original deadline, no further homeworks will be accepted. If you have obligations that conflict with exam or assignment due dates you should make arrangements with the instructor as soon as possible. I make it a point to return all homeworks and exams within one week.
Missed Exams/Assignments: Make-up exams will be given only in extraordinary circumstances. If you expect to miss an exam or to be unable to meet assignment deadlines, please discuss this with the instructor prior to the scheduled date. If an unexpected illness or family death occurs, I will need documentation for you to make up the exam.
Accommodations for Students with Special Needs: Any student in this class who has a documented visual or physical impairment, hearing disability, or any other disability covered by the University Services for students with Disabilities should contact the instructor during the first week of class to discuss and arrange any instructional accommodations that may be necessary.
Academic Conduct: This goes without saying, but I will anyway. You are expected to abide by the Undergraduate Honor Code in this course. Further, you are expected, especially as information systems professionals in training, to respect campus computer resources and to use them productively and wisely. For example, you should not illegally copy software and you should refrain from sending abusive electronic mail messages.
All homework assignments 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.
|
Date |
Topic |
|
Notes |
|
WEEK 1 |
Course Introduction Instructor Introduction The Systems Analysis Environment |
Chapter 1 |
|
|
WEEK 2 |
Approaches to Systems Development SDLC |
Chapter 2 |
Select Project/Application |
|
WEEK 3 |
Project Planning / Tracking Feasibility Analysis Project Management |
Chapter 3 Appendix A |
Proj1: Problem Statement DUE |
|
WEEK 4 |
Requirements Analysis Entity-Relationship Diagrams |
Chapter 4 Chapter 5 pp. 152-181 |
Proj2: Gantt Chart DUE Proj3: Feasibility Analysis DUE |
|
WEEK 5 |
Intro to Object Oriented Approach Class Diagram Intro to Oracle Oracle ERDs |
Chapter 5 pp. 181-189 Handouts |
PRoj4: Statement of Scope DUE |
|
WEEK 6 |
Data Flow Diagrams |
Chapter 6 |
Proj5: ERD DUE Proj6: Class Diagram DUE |
|
WEEK 7 |
Data Flow Diagrams |
Chapter 6 |
Proj7: Oracle ERD Due |
|
WEEK 8 |
Use Case Diagrams Oracle Process Model |
Chapter 7 pp. 241-257 Handouts |
Proj8: DFD DUE |
|
WEEK 9 |
Midterm Exam |
Chapters 1-7, Appendix A, Handouts |
|
|
WEEK 10 |
Oracle FHD/CRUD OO – Sequence Diagrams Alternative Design |
Chapter 7 pp. 258-265 Chapter 11 pp. 401-423 Chapter 8 |
Proj9: Use Case DUE Proj10: Oracle Process Model DUE |
|
WEEK 11 |
SDLC Design Issues |
Chapter 11 Chapter 12 |
Proj11: Sequence Diagram Proj12: FHD/CRUD matrix |
|
WEEK 12 |
Alternative methodologies – LPI, RAD, XP, Prototyping |
Chapter 17 Chapter 18 Handouts |
Proj13: Alternative Design document |
|
WEEK 13 |
Oracle DDT Oracle Table API |
Handouts |
PRoj14: Report Designs |
|
WEEK 14 |
Oracle – Generate prototype Traditional Implementation |
Handouts Chapter16 pp. 625-654 |
PRoj15: DDT DUE Proj16: Table API DUE |
|
WEEK 15 |
Maintenance / Support Review |
Chapter 16 pp. 654-664 |
Proj17: Prototype Proj18: Screen designs |
|
FINAL: |
|
|
|