INFS 622 Syllabus
Instructor: Office: Phone: E-mail: Office Hours: |
C. Randall Howard, Ph.D. Volgeneau Engineering Building Room 5353 (703) 899-3608 by appointment |
Graduate Assistant: Office: Phone: E-mail: Office Hours: |
TBD
by appointment |
Course #: INFS 622
Course Title: Systems Analysis and Design
Term: Fall, 2009
Section: 001
Time: Wednesday, 19:20-22:00
Room: Innovation Hall 203
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 |
15% |
Midterm Exam |
15% |
Analysis Proposal Project |
20% |
Design Proposal Project |
25% |
Final Exam |
15% |
Class Participation |
10% |
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.
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:
Week |
Date |
Lecture Focus |
Project Deliverables |
Assignments |
Week 1 |
September 2 |
· Course Overview · Chapter 1: The Systems Development Environment · Architectural Approaches, Supplemental Text |
|
VW Case Study Assigned (Read & Prepare to Discuss) |
|
September 4 |
|
Member Profiles Due |
|
|
September 6 |
|
Group Assignments Made |
|
Week 2 |
September 9 |
· Chapter 2: The Origins of Software · Chapter 3: Managing the Information Systems Project · Preview Homework #1 |
Group Subject Submitted |
|
|
September 11 |
|
Group Subject Confirmed |
|
Week 3 |
September 16 |
· Strategic Planning, Supplemental Text · Chapter 4: Identifying and Selecting Systems Development Projects · Chapter 5: Initiating and Planning Systems Development Projects |
|
Discuss VW Case Study Homework #1 Assigned |
Week 4 |
September 23 |
· Chapter 6: Determining System Requirements · Chapter 7: Structuring System Process Requirements · Chapter 7 Appendix: OOA-D Use Cases · Project Work |
Deliverable #1 Due |
|
Week 5 |
September 30 |
· Chapter 7 Wrapup (Likely) · Chapter 8: Structuring System Logic Requirements · Chapter 8-Appendix:: OOA-D Sequence Diagrams & Activity Diagrams · Presentation Tips · Review Deliverable #1 · Preview Midterm |
|
Homework #1 Due Midterm Posted |
|
October 3 |
Saturday Work Sessions for Product #1 |
|
|
Week 6 |
October 7 |
· Chapter 9: Structuring System Data Requirements · Chapter 9 Appendix:: OOA-D Object Modeling – Class Diagrams · Homework #1 Reviewed |
|
|
Week 7 |
October 14 |
Analysis Proposal Presentations |
Analysis Proposal Product & Presentation Due |
Midterm Due |
Week 8 |
October 21 |
· Review Midterms · Review Product #1 Results |
|
|
Week 9 |
October 28 |
· Chapter 10: Designing Databases · Homework #2 Preview |
|
Homework #2/EC Assigned |
Week 10 |
November 4 |
· Chapter 11: Designing Forms & Reports · Chapter 12: Designing Interfaces & Dialogues |
|
|
Week 11 |
November 11 |
· Chapter 13: Finalizing Design Specifications · Chapter 14: Designing Distributed & Internet Systems |
Deliverable #2 Due |
|
Week 12 |
November 18 |
· Chapter 15: System Implementation · Chapter 16: Maintaining Information Systems · Review Deliverable #2 · Final Exam Preview |
|
Homework #2/EC Due Final Exam Posted |
Week 13 |
November 25 |
Thanksgiving Recess – No Class |
|
|
Week 14 |
December 2 |
Review Homework #2, Wrapup |
|
|
|
December 5 |
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 |