INFS 622 Syllabus
Instructor: Office: Phone: E-mail: Office Hours: |
C. Randall Howard, Ph.D. Volgeneau Engineering Building Room 5323 (703) 899-3608 by appointment |
Graduate Assistant:
Office: Phone: E-mail: Office Hours: |
Dalal Al-Arayed dalaraye@gmu.edu by appointment |
Course #: INFS 622
Course Title: Systems Analysis and Design
Term: Fall, 2010
Section: 002
Time: Wednesday, 19:20-22:00
Room: Art and Design Building L008
Prerequisites: INSF 501, 515 and 590 or equivalent.
Textbooks:
Course Description:
Integration of computing technologies, system analysis, system design practices, and management criteria in the design of large-scale information management and decision support systems.
Grading:
Item |
Percentage |
Individual Assignments |
10% |
Midterm Exam |
15% |
Analysis Proposal Project |
20% |
Design Proposal Project |
25% |
Final Exam |
15% |
Professor's Discretion |
15% |
Grading Scale:
Letter Grade |
Numerical Range |
A+ |
97-100 |
A |
92-96 |
A- |
90-91 |
B+ |
88-89 |
B |
82-87 |
B- |
80-81 |
C+ |
78-79 |
C |
72-77 |
C- |
70-71 |
Individual
Assignments:
Assignments are announced during class. The assignments are individual unless otherwise specified. Assignments will be graded on correctness as well as style and presentation. Each assignment is due on the announced date before 12 midnight. There will be a strictly enforced 10% penalty per day for late submissions unless otherwise specified.
Group Project:
There will be a group research project. Each team is responsible for developing an integrated requirements specification and design document. Each group will select a team coordinator who will help coordinate the overall progress of the team. Each team member's individual contribution to the final documents and models must be clearly identified. At the end of the semester each group will have a presentation session.
Exams:
There will be a midterm exam and a final exam covering lectures and readings. The final exam (comprehensive) includes topics covered in the entire semester. Exams must be taken at the scheduled time and place unless prior arrangements are made. Missed exams cannot be made up.
NOTE: All submissions’ file names need to indicate student or group
names. All submissions should be in MS
Word, unless otherwise specified.
Honor Code Statement:
As with all GMU courses, INFS 622 is governed by the GMU Honor Code. In this course, all assignments, exams, and project submissions carry with them an implicit statement that it is the sole work of the author, unless joint work is explicitly authorized. Help may be obtained from the instructor or other students to understand the description of the problem and any technology, but the solution, particularly the design portion, must be the student's own work. If joint work is authorized, all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation. (© Jeff Offutt) . For more information, see http://honorcode.gmu.edu/.
Schedule:
· Order is re-arranged to facilitate more time to apply the discussion to the project artifacts
· Project Artifacts w/in Lectures are highlighted in yellow.
· Schedule WILL change as needed to facilitate learning
Week |
Date |
Lecture Focus |
Project Deliverables |
Assignments |
Week 1 |
September 1 |
· Course Overview ü Text ü Group Project · Chapter 1: The Systems Development Environment · Architectural Approaches, Supplemental Text |
|
VW Case Study Assigned (Read & Prepare to Discuss) |
|
September 3 |
|
Students: Member Profiles & Group Subject Requests Due |
|
|
September 5 |
|
Professor: Group Assignments Confirmed |
|
Week 2 |
September 8 |
· Review Project Deliverables & Base for Lectures · Chapter 3: Managing the Information Systems Project ü Project Plan ü Project Schedule ü Cost/Benefit Analysis ü Risks · Preview Homework #1 · Groups Develop Project Charter |
|
|
|
September 9 |
|
Groups: Project Charter "Strawman" or Analysis Section 2.0 Submitted |
|
|
September 11 |
|
Professor: Group Subject & Charter Confirmed |
|
Week 3 |
September 15 |
· Guest Speaker on Project Management · Chapter 7: Structuring System Process Requirements ü DFD ü Use Cases ü Activity Diagrams · Project Time ü Review Project Charters ü Project Work |
|
|
Week 4 |
September 22 |
· Chapter 2: The Origins of Software · Chapter 4: Identifying & Selecting Systems Development Projects · Presentation Tips · Project Time |
|
Discuss VW Case Study Homework #1 Assigned |
Week 5 |
September 29 |
· Chapter 5: Initiating and Planning Systems Development Projects · Chapter 6: Determining System Requirements · Preview Midterm |
Deliverable #1 Due |
Midterm Posted |
|
October 2 |
Saturday Work Sessions for Product #1 |
|
|
Week 6 |
October 6 |
· Review Deliverable #1 · Chapter 8: Structuring System Logic Requirements ü Data Model ü Class Diagram · Chapter 9: Designing Databases · Homework #2 Reviewed |
|
Homework #1 Due |
Week 7 |
October 13 |
· Project Work |
|
|
Week 8 |
October 20 |
· Analysis Proposal Presentations – Round 1 |
Analysis Proposal Product & Presentation Due |
|
Week 9 |
October 27 |
· Guest Speaker · Chapter 10: Designing Forms & Reports · Chapter 11: Designing Interfaces & Dialogues · Review Midterms · Homework #2 Preview |
|
· Midterm Due · Homework #2/EC Assigned |
Week 10 |
November 3 |
· Review Adjustment of Analysis Project · Chapter 12: Designing Distributed & Internet Systems |
|
|
Week 11 |
November 10 |
· Review Deliverable #2 · Group Work |
Deliverable #2 Due |
|
Week 12 |
November 17 |
Thanksgiving Break |
|
|
Week 13 |
November 24 |
· Review Deliverable #3 per feedback on Deliverable #2 · Go-over Homework #2, · Final Exam Preview |
Deliverable #3 Due |
Homework #2/EC Due Final Exam Posted |
|
December 1 |
· Chapter 13: System Implementation · Chapter 14: Maintaining Information Systems · Wrapup |
|
|
Week 14 |
December 4 |
Saturday Work Sessions for Product #2 |
|
|
Week 15 |
December 9 |
Design Proposal Presentations |
Design Proposal Product & Presentation Due |
|
Week 16 |
December 16 |
Final Exam |
|
Final Exam Due |