INFS 622 Syllabus – v1.0:
INITIAL 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: |
Nan Li by appointment |
Course #: INFS 622
Course Title: Systems Analysis and Design
Term: Summer, 2011
Section: B01
Time: Tuesdays and Thursdays, 19:20-22:00
Room: Robinson Hall, A123
Prerequisites: INSF 501, 515 and 590 or equivalent.
Textbooks:
Catalog 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.
Professor’s Description:
INFS622 is a core-course for the CS and Applied-IT programs. Dr. Howard leverages his 28 years of system engineering experience to run heavily mentored group interactions along with industry-relevant lecture material. Students learn the material, and also know how to apply and connect the artifacts together by semester’s end. The result is a valuable skill that enables the students to “sell” a cohesive story that greatly increases the chance of acceptance and approval of any proposal or recommendation. In doing so, students learn to:
· Refine & apply new “translation and “language” skills to mediate between business & technical communities
· Tools to determine best fit to address the problems and shape solutions
·
Explain rationale and recommendations to
stakeholders
Grading:
Item |
Percentage |
Individual Assignments |
15% |
Project Work |
40% |
Exams |
30% |
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
Session # |
Date |
Lecture Focus |
Project Deliverables |
Assignments |
Session 1 |
June 7 |
· Course Overview ü Text ü Group Project · Architectural Approaches, Supplemental Text |
|
VW Case Study Assigned (Read & Prepare to Discuss) |
|
June 8 |
|
Students: Member Profiles & Group Subject Requests Due |
|
|
June 9 |
|
Professor: Group Assignments Confirmed |
|
Session 2 |
June 9 |
· 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 |
|
|
|
June 10 |
|
Groups: Project Charter "Strawman" or Analysis Section 2.0 Submitted |
|
|
June 11 |
|
Professor: Group Subject & Charter Confirmed |
|
Session 3 |
June 14 |
· Chapter 7: Structuring System Process Requirements ü DFD ü Decision Tables · Project Time ü Review Project Charters ü Project Work |
|
|
Session 4 |
June 16 |
· Preview Homework #1 · Project Time ü Review Level-0 DFD Diagrams ü Project Work · Chapter 3: Managing the Information Systems Project ü Risks · 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 |
|
June 19 |
Out of Class Work Sessions for Product #1?? |
|
|
Session 5 |
June 21 |
· 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 |
|
|
|
|
|
Session 6 |
June 23 |
· Review Deliverable #1 ü ·
Prep for Presentations |
|
|
Session 7 |
June 30 |
· Guest Lecturer: Bob Quinn –“Leading from Behind, Guiding Customers to Project Conclusions’ |
|
|
|
|
Midway Point |
|
|
Session 8 |
July 5 |
· Analysis Proposal Presentations – Round 1 |
Analysis Proposal Product & Presentation Due |
|
Session 9 |
July 7 |
·
Guest Speaker: Andrew Lopresti · Chapter 10: Designing Forms & Reports · Chapter 11: Designing Interfaces & Dialogues · Review Adjustment of Analysis Project |
|
Homework Due |
Session 11 |
July 12 |
· Chapter 7b & c: Structuring System Process Requirements ü Use Cases ü Activity Diagrams · Chapter 8: Structuring System Logic Requirements ü Data Model ü Class Diagram · Chapter 9: ü Designing Databases · Project Group Work |
|
|
Session 12 |
July 14 |
· Chapter 12: Designing Distributed & Internet Systems · Project Group Work |
|
|
Session 13 |
July 19 |
· Final Exam Preview · Project Group Work |
|
Final Exam Posted |
Session 14 |
July 21 |
· Chapter 13: System Implementation · Chapter 14: Maintaining Information Systems · Wrapup |
|
|
|
July 23 |
Out of Class Work Sessions for Product #2?? |
|
|
Session 15 |
July 26 |
Design Proposal Presentations |
Design Proposal Product & Presentation Due |
|
Session 16 |
July 28 |
Final Exam |
|
Final Exam Due |