INFS 622 Syllabus – v1.0
January 1, 2013: Initial Syllabus (DRAFT)
|
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: |
Katherine Irvin by appointment kirvin@gmu.edu |
Course #: INFS 622
Course Title: Systems Analysis and Design
Term: Spring 2013
January 22, 2013 – May 14, 2013
|
Section: |
003 |
002 |
|
CRN: |
21517 |
13112 |
|
Time: |
Wednesdays, 16:30-19:10 |
Wednesdays, 19:20-22:00 |
|
Room: |
Krug Hall 19 |
Krug Hall 5 |
Prerequisites: INSF 501, 515 and 590 or equivalent, or by permission.
Textbooks:
IMPORTANT NOTE: The material posted for reading
and reference is NOT to be distributed, posted or used outside of the INFS622
session. The material is copyrighted and
is Intellectual Property of various parties.
Catalog Description:
Integration of computing technologies, systems analysis, system design practices, and management criteria in the design of large-scale information management and decision-support systems. Includes cases, computing lab.
Learning Objectives:
INFS622 is a core-course for the CS, Applied-IT and HAP Informatics programs. Dr. Howard leverages his 30+ years of system engineering, architecture and consulting 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 communitiesthe
· Tools to determine best fit to address the problems and shape solutions
·
Explain rationale and recommendations to
stakeholders
Ground Rules
This syllabus serves as our
“contract” for the course and the semester.
Such items as the textbook, topics, learning objectives, grading, etc.
are conveyed in this syllabus.
Students are expected to prepare
BEFORE class on material scheduled for each session. This is vital to encourage participation,
which is a vital element of Professor’s Discretion.
While the workload is designed to be
as balanced throughout the semester:
ü
The front part of the
semester is heavier by nature
ü
There are points at
which the workload is heavy though
ü
It is up to the students
to prepare accordingly
Other ground rules are listed in the
first lecture. These are listed to help
facilitate a smoother running of the semester.
Students are expected to review the material and leverage it to the
fullest.
Grading
Table 1. Grading Distribution
|
Item |
Percentage |
|
*Homework Assignments |
15% |
|
Project Work |
35% |
|
*Midterm Exam |
20% |
|
*Final Exam |
20% |
|
Participation |
10% |
*NOTE: These are INDIVIDUAL, which means NO collaboration with other previous or current students!
Exception: Study groups for exams are allowed, but the exams themselves are INDIVIDUAL
Each project deliverable grade is broken as follows:
Table 2. 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 |
All Sumissions
All work must be submitted at the scheduled time and place unless prior arrangements are made. Missed reports cannot be made up without these prior arrangements.
All assignments will be graded on correctness as well as style and presentation. Each assignment is due on the announced date before 12 midnight, with the exception of the project that are due before class begins on presentation day. There will be a 10% penalty per day for late submissions unless otherwise specified.
IMPORTANT
NOTES:
1.
All submissions’
file names need to indicate student or group names.
a.
For individual
submissions, use this format:
LastName_First_Name_AssignmentName
b.
For group
submissions, questions, etc. for the Professor,
i. CLEARLY mark the subject of the item as w/ ATTN TO PROFESSOR: subject (I do not monitor group discussion areas)
ii. Send a follow-up email to the Professor that the item has
been posted
iii. For Submissions, use this format:
Group#_ArtifactName_State (eg.,Initial, Draft,
Final), Version (e.g. #)
iv. Submit on group’s File Exchange area on Blackboard
2.
ALL submissions
should be in MS Word, unless otherwise specified. In other words, DO NOT submit
.PDF’s – I cannot provide feedback easily w/ .PDF’s.
3.
A 10% penalty may be
assessed for not following these instructions!
MORE IMPORTANT NOTES:
Academic Integrity. It
is your responsibility to know and to follow Mason’s policy on academic
integrity (http://oai.gmu.edu/honor-code/masons-honor-code/).
SafeAssign. The
professor utilizes the tool provided as part of Blackboard to check assignments
against published resources AND other students’ work.
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). The Computer Science Department’s Honor Policy is in force as well, and can be found at the following URL: http://cs.gmu.edu/wiki/pmwiki.php/HonorCode/CSHonorCodePolicies
To stay safe:
· Provide citations for your work – group and individual – even if it is “adapted from”.
· Do not work in groups to complete individual work.
· Do not copy and paste material from the text except for short, pithy definitions that cannot necessarily be re-worded easily.
ODS Statement. If you have a disability and wish academic
accommodations, please see the Professor and contact the Office of Disability
Services (703) 993-2474, (http://www2.gmu.edu/depts/unilife/ods//).
INFS62 Integrated Lecture & Project Class Schedule
V1.0: Session 1
Schedule Notes:
· Order is (re-)arranged to facilitate more time to apply the discussion to the project artifacts
·
Schedule WILL change as needed to facilitate
learning according to personality & makeup of the class
·
Schedule adjustments will be conveyed in the Rolling_Class_Session_Plans_Takeaways,
and changes not reflected in this document.
·
Items marked w/ a “[D] party:” indicate a
deliverable from the party: listed
(e.g., Students, Groups, Professor)
·
Color Legend:
|
Mauve: Items are due |
Pale Blue: Milestones or Events |
Project Work Time Allowed in Class |
|
Session # |
Date |
Lecture
Session Focus |
Due
Dates & Deadlines |
|
Session 1 |
January 23 |
o
Introductions o
Professor
Supplement: ü Course, Text & Resources Overview ü Overview & Scoping a Project o
Project Teaming & Topic Time |
o
|
|
|
January 24 |
|
o
[D] Students:
Member Profiles & Request o
[D] Groups: Set
Project Topic Requests Due |
|
|
Jan 29 |
Last Day to Add/Drop (w/ no tuition liability) |
|
|
Session 2 |
January 30 |
TEXT: PART ONE PLANNING
PHASE o
Chapter 1 The
Systems Analyst And Information Systems Development o
Chapter 5
Process Modeling o
Summer School
Case Study o
Jumpstart
Project Teams’ Core Artifacts |
o
[D]Chapter 5 DFD
Context & Chapter 4 Use Case Readings in book o
[D]Mock Trial Test |
|
Session 3 |
February 6 |
o
Chapter 2
Project Selection And Management ü Discuss VW Case Study o
Chapter 3
Requirements Determination o
Project Work Time |
o
[D]Homework #1 Due o
[D]Discuss VW Case Study (www.hbr.org) |
|
Session 4 |
February 13 |
PART TWO ANALYSIS PHASE o
Chapter 4 Use
Case Analysis o
Project Work Time |
o
[Review] Core
Foundations Draft (Core detailed in
INFS622 Class & Artifact Overview) |
|
Session 5 |
February 20 |
o
Chapter 6 Data
Modeling o
Project Work Time |
|
|
Session 6 |
February 27 |
PART THREE DESIGN PHASE o
Chapter 7
Moving Into Design o
Project Work Time |
o
[Review]Analysis
Draft |
|
Session 7 |
March 6 |
o
Chapter 8
Architecture Design o
Project Work Time |
|
|
|
Mar 13 |
Spring Break |
|
|
Session 8 |
March 20 |
o
Mid-term Exam o
Chapter 9 User
Interface Design o
Project Work Time |
[D] Groups: Analysis Proposal Product Due [D] Student Survey / Checkpoint |
|
Session 9 |
March 27 |
o
ReviewStudent Survey / Checkpoint o
Chapter 14 The
Movement To Objects |
|
|
Session 10 |
April 3 |
o
Chapter 10 Program
Design o
Chapter 11 Data
Storage Design |
o
|
|
Session 11 |
April 10 |
o
Presentation
Tips o
Final Exam Prep o
PART FOUR
IMPLEMENTATION PHASE o
Chapter 12
Moving Into Implementation o
Project Work Time |
[D] Homework #2 |
|
Session 12 |
April 17 |
o
Chapter 13
Transition To The New System o
Project Work Time |
o
[Review]Design
Draft |
|
Session 13 |
April 24 |
o
Current Events
Discussions o
Wrapup o
Course Evals |
o
[Review]Presentation |
|
Session 14 |
May 1 |
o
Analysis & Design
Proposal Presentations |
[D] Analysis &
Design Proposal Products & Presentations Due [D] Course & Project Member Evaluations |
|
Session 15 |
May 8 |
o
Final Exam [10 questions] |
|