INFS 622 Syllabus – v1.1:
Initial Syllabus Revised
|
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: Spring, 2011
Section: 002
Time: Monday, 19:20-22:00
Room: Art and Design Building 2026
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% |
|
Analysis Proposal Project |
20% |
|
Design Proposal Project |
25% |
|
Exams |
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 |
January 24 |
· Course Overview ü Text ü Group Project · Architectural Approaches, Supplemental Text |
|
VW Case Study Assigned (Read & Prepare to Discuss) |
|
|
January 26 |
|
Students: Member Profiles & Group Subject Requests Due |
|
|
|
January 30 |
|
Professor: Group Assignments Confirmed |
|
|
Week 2 |
January 31 |
· Review Project Deliverables & Base for Lectures · Chapter 1: The Systems Development Environment · Chapter 3: Managing the Information Systems Project ü Project Plan ü Project Schedule ü Cost/Benefit Analysis ü Risks · Groups Develop Project Charter |
|
|
|
|
February 3 |
|
Groups: Project Charter "Strawman" or Analysis Section 2.0 Submitted |
|
|
|
February 6 |
|
Professor: Group Subject & Charter Confirmed |
|
|
Week 3 |
February 7 |
· Guest Speaker on Project Management · Chapter 7: Structuring System Process Requirements ü DFD · Project Time ü Review Project Charters ü Project Work |
|
|
|
Week 4 |
February 14 |
· Preview Homework #1 · Project Time ü Review Level-0 DFD Diagrams ü Project Work · Chapter 3: Managing the Information Systems Project ü Risks · Chapter 7: Structuring System Process Requirements ü Decision Tables ü Use Cases ü Activity Diagrams · Chapter 4: Identifying & Selecting Systems Development Projects ü Multi-Criteria Analysis Table · Chapter 5: Initiating and Planning Systems Development Projects ü Breakeven Analysis ü Risk Mitigation Table · Presentation Tips |
|
Homework Assigned |
|
Week 5 |
February 21 |
· Preview Midterm · Chapter 2: The Origins of Software · Chapter 4: Identifying & Selecting Systems Development Projects · Chapter 6: Determining System Requirements · Project Time |
Deliverable #1 Due |
Discuss VW Case Study |
|
|
February 26 |
Saturday Work Sessions for Product #1 |
|
|
|
Week 6 |
February 28 |
· Review Deliverable #1 · Chapter 8: Structuring System Logic Requirements ü Data Model ü Class Diagram |
|
|
|
Week 7 |
March 7 |
· Guest Lecturer |
|
|
|
Week 8 |
March 14 |
SPRING BREAK |
|
|
|
Week 9 |
March 21 |
· Analysis Proposal Presentations – Round 1 |
Analysis Proposal Product & Presentation Due |
|
|
Week 10 |
March 28 |
· Guest Speaker: Andrew Lopresti · Chapter 10: Designing Forms & Reports · Chapter 11: Designing Interfaces & Dialogues · Review Adjustment of Analysis Project |
|
Homework Due |
|
Week 11 |
April 4 |
· Review Midterms · Chapter 7b & c: Structuring System Process Requirements ü Use Cases ü Activity Diagrams · Chapter 9: ü Designing Databases · Project Group Work |
|
|
|
Week 12 |
April 11 |
· Homework #2 Review (not being assigned) · Chapter 12: Designing Distributed & Internet Systems · Project Group Work |
|
|
|
Week 13 |
April 18 |
· Final Exam Preview · Project Group Work |
|
Final Exam Posted |
|
Week 14 |
April 30 |
· Chapter 13: System Implementation · Chapter 14: Maintaining Information Systems · Wrapup |
|
|
|
|
May 2 |
Saturday Work Sessions for Product #2 |
|
|
|
Week 15 |
May 9 |
Design Proposal Presentations |
Design Proposal Product & Presentation Due |
|
|
Week 16 |
May 16 |
Final Exam |
|
Final Exam Due |