Tuesday, Thursday, Period M (9:25-10:40 AM), Room 126
|
The Textbook Course Description Course Objectives Course Policies Grading System Course Schedule |
Prof. Thomas A. Easton
|
OFFICE: Rm. 108
OFFICE HOURS: 12-3 PM MW, 9:30-12 AM TTh OFFICE PHONE: 859-1331 HOME PHONE: 338-1074 CANCELLATION PHONE NUMBER: 859-1140 Click here to email me:  |
THE TEXTBOOK
Essentials of Systems Analysis and Design, 5th Edition
Joseph S. Valacich, Joey F. George, and Jeffrey A. Hoffer
Prentice Hall, 2012 (ISBN 0-13-706711-9)
Essentials of Systems Analysis and Design, 5th Edition
Joseph S. Valacich, Joey F. George, and Jeffrey A. Hoffer
Prentice Hall, 2012 (ISBN 0-13-706711-9)
This course teaches the student the analysis and design of information systems, whether computer-based or manual. It provides an understanding of the system development and modification process, enables students to evaluate and choose a system development methodology, emphasizes the factors for effective communication and integration with users and user systems, and stresses the role of ethics in systems analysis & design. (Prerequisite: CS 115 and junior standing)
See "Course policies" below for details on testing and grading.
See "Course policies" below for details on testing and grading.
After completing this course, students will:
- Understand the role of the systems analyst and the principles of effective, ethical business systems design.
- Understand the kinds of information needed to analyze and design business systems.
- Be able to analyze and present business system requirements.
- Be able to identify systems analysis/design and life cycle management concerns in a typical business environment.
- Be familiar with various system design methodologies and their integration with various life cycle management concerns.
Students should always read their assignments and come to class prepared to discuss the material. Each student may be absent twice without penalty. Each additional two absences without a medical excuse (no others are acceptable) will cost the student three points on the course grade.
Grading will be based on four team-based project reports (5% of grade each; 20% total), seven quizzes (the lowest two will be dropped; 5% of grade each; 25% total); two exams (15% of grade each; 30% total), and a final exam (25% of grade). See the Course Schedule for details.
Students who plagiarize tests and projects will receive zeros for the work in question, with no makeup opportunities.
Grading will be based on four team-based project reports (5% of grade each; 20% total), seven quizzes (the lowest two will be dropped; 5% of grade each; 25% total); two exams (15% of grade each; 30% total), and a final exam (25% of grade). See the Course Schedule for details.
Students who plagiarize tests and projects will receive zeros for the work in question, with no makeup opportunities.
A (94 - 100) A- (90 - 93)
B+ (87 - 89) B (83 - 86) B- (80 - 82)
C+ (77 - 79) C (73 - 76) C- (70 - 72)
D+ (67 - 69) D (63 - 66) D- (60 - 62)
F (below 60)
| DATE | TOPIC | ASSIGNMENT | |
| Tues Jan 10 | What Is Systems Analysis? | Read Chapter 1: The Systems Development Environment | |
| Why Bother? | Read The Case of the Killer Robot--1 (zipped on Moodle) | ||
| Thurs Jan 12 | Discussion of Case Studies | Be prepared to discuss the cases on pp. 24-25 | |
| Project Teams: Choose a business problem related to information systems; prepare a brief (2-3 pp.) paper describing the problem, what needs to be done to solve the problem, how success will be measured, and how you will know when the problem has been solved. Due Tues Jan 17; counts for 5% of grade. | Report #1 Consider saving a copy in your e-Portfolio. | ||
| Tues Jan 17 | Details Matter! | Read The Case of the Killer Robot--2 | |
| Choose Teams for Projects | |||
| Quiz #1 | (on Chapter 1) | ||
| Thurs Jan 19 | Getting Software Done | Read Chapter 2: The Sources of Software | |
| Intro to continuing case study | Petrie's Electronics. p. 40 | ||
| Tues Jan 24 | Project Management | Read Chapter 3: Managing the Information Systems Project, pp. 42-64 | |
| Quiz #2 | (on Chapter 2) | ||
| Thurs Jan 26 | Project Management | Read Chapter 3: Managing the Information Systems Project, pp. 64-75 | |
| The Need for Cooperation | Read The Case of the Killer Robot--3 | ||
| Tues Jan 31 | Discussion of Petrie's Electronics Case | Be prepared to discuss the case on pp. 80-81 | |
| Stakeholders at War | Read The Case of the Killer Robot--4 | ||
| REVIEW FOR EXAM | (on Chapters 1-3) | ||
| Thurs Feb 2 | EXAM #1 | ||
| Tues Feb 7 | Initiating and Planning | Read Chapter 4: Systems Planning and Selection, pp. 82-90 | |
| Thurs Feb 9 | Feasibility Analysis and Baseline Plan | Read Chapter 4: Systems Planning and Selection, pp. 90-113 | |
| Tues Feb 14 | Discussion of Petrie's Electronics Case | Be prepared to discuss the case on pp. 119-121 | |
| Project Teams: Choose an approach to solving the problem you described in your last paper. Prepare a brief (2-3 pp.) paper analyzing the feasibility of this approach. Due Tues Feb 29; counts for 5% of grade. | Report #2 Consider saving a copy in your e-Portfolio. | ||
| Quiz #3 | (on Chapter 4) | ||
| Thurs Feb 16 | System Requirements | Read Chapter 5: Determining System Requirements, pp. 122-135 | |
| How Far Do Requirements Go? | Read The Case of the Killer Robot--5 | ||
| Mon Feb 20 - Fri Feb 24 | WINTER BREAK | ||
| Tues Feb 29 | Modern Methods | Read Chapter 5: Determining System Requirements, pp. 135-146 | |
| Thurs Mar 1 | Discussion of Petrie's Electronics Case | Be prepared to discuss the case on pp. 150-151 | |
| Quiz #4 | (on Chapter 5) | ||
| Tues Mar 6 | Data Flow Diagrams | Read Chapter 6: Structuring System Requirements: Process Modeling, pp. 152-171 | |
| Thurs Mar 8 | Logic Modeling | Read Chapter 6: Structuring System Requirements: Logic Modeling, pp. 171-177 | |
| Tues Mar 13 | Discussion of Petrie's Electronics Case | Be prepared to discuss the case on pp. 185-187 | |
| REVIEW FOR EXAM | (on Chapters 4-6) | ||
| Thurs Mar 15 | EXAM #2 | ||
|
Drop Date:
After Mar 16 you cannot drop the course without getting a grade. No W or L! |
|||
| Tues Mar 20 | Conceptual Data Modeling | Read Chapter 7: Structuring System Requirements | |
| Thurs Mar 22 | Discussion of Petrie's Electronics Case | Be prepared to discuss the case on pp. 229-231 | |
| Project Teams: Identify the processes, data flows, entities, and relationships involved in your project and prepare appropriate diagrams. Due Tues Apr 3; counts for 5% of grade. | Report #3 Consider saving a copy in your e-Portfolio. | ||
| Quiz #5 | (on Chapter 7) | ||
| Mon Mar 26 - Fri Mar 30 | SPRING BREAK | ||
| Tues Apr 3 | The Design Stage: Forms and Reports | Read Chapter 8: Systems Design, pp. 232-246 | |
| Thurs Apr 5 | The Design Stage: Interfaces and Dialogues | Read Chapter 8: Systems Design, pp. 246-266 | |
| Project Teams: Describe the interfaces (forms and reports, and dialogues) needed for your project in a 2-3 page paper. Due Tues Apr 10; counts for 5% of grade. | Report #4 Consider saving a copy in your e-Portfolio. | ||
| Tues Apr 10 | Discussion of Petrie's Electronics case | Be prepared to discuss the case on pp. 270-271 | |
| The Killer Robot Interface | Read The Case of the Killer Robot--6 | ||
| Quiz #6 | (on Chapter 8) | ||
| Thurs Apr 12 | Database Design | Read Chapter 9: Designing Databases, pp. 272-289 | |
| Tues Apr 17 | Database Design cont. | Read Chapter 9: Designing Databases, pp. 289-309 | |
| Thurs Apr 19 | Discussion of Petrie's Electronics case | Be prepared to discuss the case on pp. 315-317 | |
| Quiz #7 | (on Chapter 9) | ||
| Tues Apr 24 | Putting it all together! | Read Chapter 10: Systems Implementation and Operation | |
| Discussion of Petrie's Electronics case | Be prepared to discuss the case on pp. 358-359 | ||
| Thurs Apr 26 | Testing Really Matters! | Read The Case of the Killer Robot--7 | |
| Read The Case of the Killer Robot--8 | |||
| Ethics Summary | Read The Case of the Killer Robot--9 | ||
| Mon Apr 30 | FINAL EXAMS BEGIN | ||
| EXAM DAY | FINAL EXAM | ||
Syllabus last modified December 12, 2011.