INFS 622 Syll=
abus – v1.0:
Initial Syllabus
|
Instructor:=
Office: Phone: E-mail: Office Hour= s: |
C. Randall Howard, Ph.D. Volgeneau Engineering Bu= ilding Room 5323 (703) 899-3608 by appointment |
Graduate As=
sistant:
Office: Phone: E-mail: Office Hour= s: |
Katherine Irvin by appointment kirvin@gmu.edu |
Course #:= INFS 622-002
Section: = 002
CRN: 13978
Course Title:= Systems Analysis and Design
Term:
Time: = Wednesdays, 19:20-22:00
Room: Robinson Hall B113
Prerequisites= : INSF 501, 515 and 590 or equivalent.
Textbooks:
IMPORTANT NOTE: The material posted for reading and reference is NOT to be distributed, posted or used outside of the INFS6= 22 session for Spring 2012. The material is copyrighted and is Intellectual Property of various parties.<= o:p>
Catalog Descr=
iption:
Integration of computing technolog= ies, system analysis, system design practices, and management criteria in the de= sign of large-scale information management and decision support systems. =
Learning Obje=
ctives:
INFS622 is a core-course for the CS and Applied-IT pro= grams. 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 app= ly 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
No=
te:
Grading is being streamlined to address issues experienced in previous
semesters. Changes in approach wil=
l be
announced!
Individual
Assignments:
The assignments are individ= ual unless otherwise specified. Assignments will be graded on correctness as we= ll as style and presentation.
Group
Project:
There will be a group resea= rch project. Each team is responsible for developing an integrated requirements specification and design document.
Each group will select a te= am coordinator or leader who will help coordinate the overall progress of the team. Each team member's individual contribution to the final documents mus= t be clearly identified. Each group will be called on to present material throug= hout the semester.
Group Project Checkpoint=
s:
Project checkpoints are an opportunity to receive feedback on their
progress. The content itself is not
graded per se; however, they:
·
Are
evaluated as to the completeness and intent of the effort to be complete.
·
Ser=
ve as
the Authority to Proceed (ATP) to the next phase.
Exams:
At the discretion of the pr= ofessor, a mid-term exam may be given. Ther= e will be a final exam covering lectures, readings and topics covered over the ent= ire semester. Exams must be taken at the scheduled time and place unless prior arrangements are made. Missed exams cannot be made up without these prior arrangements.
Professor’s Discretion:<= o:p>
Participation is a portion of both the group project and individual
grades. This has been a particular
challenge that we will be addressing throughout the semester in various, ad=
-hoc
manners – depending on how proactive the class is in averting “ad-hoc
manners”.
Warning: “ad-hoc” manners are not necessarily the preferable option
either.
All Sumissions
All work must be submitted at the scheduled time and p= lace 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. There will be a strictly enforced 10% penalty per day for late submissions unless otherwise specified.
IMPORTANT NOTES:
1.
All submissions’ f=
ile
names need to indicate student or group names.
a.
For individual
submissions, use this format:
Last
Name_First Name_Assignment=
Name
b.
For group submissi=
ons,
questions, etc. for the Professor,
&nb=
sp; =
&nb=
sp; =
&nb=
sp;
i. &nb=
sp;
CLEARLY mark the
subject of the item as w/ ATTN TO
PROFESSOR: subject
&nb=
sp; =
&nb=
sp; =
ii. &n=
bsp;
(I do not monitor
group discussion areas
&nb=
sp; =
&nb=
sp; =
iii. &=
nbsp;
Send a follow-up e=
mail
to the Professor that the item has been posted
&nb=
sp; =
&nb=
sp; =
iv. &n=
bsp;
For Submissions, u=
se
this format:
Group#, ArtifactName, Sta=
te (eg.,Initial, Draft, Final),
Version (e.g. #)
&nb=
sp; =
&nb=
sp; =
&nb=
sp;
v. &nb=
sp;
Submit on group’s =
File
Exchange area on blackboardons
2.&n=
bsp;
ALL submissions sh=
ould
be in MS Word, unless otherwise specified. In other words, DO NOT submit .PDF’s – I cannot provide feedback easily w/ .P=
DF’s.
3.&n=
bsp;
At the professor’s
discretion, a 10% penalty may be assessed for not following these instructi=
ons!
Table 1. Grading Distribution
|
Item |
Percent=
age |
|
Individual Assignments |
15% |
|
Project Work |
40% |
|
Exams |
30% |
|
Professor's Discretion |
15% |
Table 2. Grading Scale
|
Letter =
Grade |
Numeric=
al 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 |
MORE IMPORTANT NOTES:
Academic Integrity. It is your responsibility to know and to
follow Mason’s policy on academic integrity (http://academicintegrity.gmu.edu/honorcode/).
ODS Statement=
. If you have a disability and wish acad=
emic accommodations,
please see the Professor and contact the Office of Disability Services (703)
993-2474, (http://www2.=
gmu.edu/depts/unilife/ods//).
Honor Code St=
atement:
As with all GMU courses, INFS 622 = is governed by the GMU Honor Code. In this course, all assignments, exa= ms, 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 m= ay be obtained from the instructor or other students to understand the descrip= tion 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/.
INFS62 Integrated Lecture & Project Class Schedule
V1.0: Session 1
Schedule Note=
s:
·&nb= sp; Order is (re-)arranged to facilitate more ti= me to apply the discussion to the project artifacts
·&nb=
sp;
Project Artifacts w/in Lectures are highligh=
ted
in yellow.
·&nb=
sp;
Schedule WILL change as needed to facilitate
learning according to personality & makeup of the class
·&nb=
sp;
Items marked w/ a “[D] party:” indicat=
e a
deliverable from the party: lis=
ted
(e.g., Students, Groups, Professor)
·&nb=
sp;
Color Legend:
|
Red: Changed
/ Changing Items |
Yellow: Project Artifacts |
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 25 |
<=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Introduct=
ions <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Course &a=
mp;
Text Overview <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Class Res=
ource
Guide Overview <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Project T=
eaming
& Topic Time |
o
VW Case S=
tudy
Assigned (Read & Prepare to
Discuss at a later session) (www.hbr.org) |
|
|
January 27 |
|
<=
span
style=3D'font-size:10.0pt;font-family:Symbol;mso-fareast-font-family:Symb=
ol;
mso-bidi-font-family:Symbol'>· &nbs=
p;
<=
span
style=3D'font-size:10.0pt'>[D} Students:
Member Profiles <=
span
style=3D'font-size:10.0pt;font-family:Symbol;mso-fareast-font-family:Symb=
ol;
mso-bidi-font-family:Symbol'>· &nbs=
p;
<=
span
style=3D'font-size:10.0pt'>[D] Groups:
Initial Project Topic Requests Due |
|
|
January 29 |
|
· &nbs=
p;
<=
span
style=3D'font-size:10.0pt'>[D] Professor: Group Assignments Confirmed |
|
|
January 31 |
Last Day to Add/Drop (w/ no tuition liability)=
|
|
| Session 2 |
February 1 |
<=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Chapter 1=
ü The Systems Development Environment ü Architectural Approaches, Supplemental Text ü Chapter 3: Managing the Information Systems Pr=
oject <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Visio &am=
p;
PowerPoint Tips <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Preview
Homework <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Preview F=
inal
Exam? <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Project Work Time |
|
|
February 3 |
|
[D] Groups: Project
Core Charter Deliverables |
|
|
February 5 |
|
[D] Professor: Group Subject & Charter Confirmed |
|
| Session 3 |
February 8 |
<=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New";color:red'>o <=
/span>Groups
Present & Review “Project Charter” <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New";color:red'>o <=
/span>Presentation
Tips <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Chapter 7:
Structuring System Process Requirements |
|
| Session 4 |
February 15 |
o
Chapter 3:
Managing the Information Systems Project ü Risks ü
Chapter 4:
Identifying & Selecting Systems Development Projects ü Multi-C=
riteria
Analysis Table <=
![if !supportLists]>o
Chapter 5:
Initiating and Planning Systems Development Projects ü Breakev=
en
Analysis ü Risk
Mitigation Table <=
![if !supportLists]>o
Review Le=
vel-0
DFD Diagrams <=
![if !supportLists]>o
Project Work Time |
o&=
nbsp;
[D]Reminder: Re=
view
VW Case Study |
|
|
February 18 |
|
Out of Class Work S=
essions
for Product #1 (If Needed) |
| Session 5 |
February 22 |
<=
![if !supportLists]>o
Chapter 4:
Identifying & Selecting Systems Development Projects ü Multi-C=
riteria
Analysis Table ü Analysi=
s of
Alternatives <=
![if !supportLists]>o =
Chapter 5: Initiating and Planning Systems
Development Projects ü Risk
Mitigation <=
![if !supportLists]>o
Pulling t=
he
Analysis Proposal Together <=
![if !supportLists]>o <=
/span>Project Wor=
k Time |
· &nbs=
p;
<=
span
style=3D'font-size:10.0pt;background:#E5B8B7;mso-shading-themecolor:accen=
t2;
mso-shading-themetint:102'> [D] C=
lass: Discuss VW Case Study |
| Session 6 |
February 29 |
<=
![if !supportLists]>o
Chapter 2=
: The
Origins of Software <=
![if !supportLists]>o
Chapter 6:
Determining System Requirements <=
![if !supportLists]>o
Project R=
eviews ü
Exec Summ=
ary
Review ü
Presentat=
ion
Review ü
“Final To=
uches” <=
![if !supportLists]>o
Analysis
Project Time |
· &nbs=
p;
|
| Session 7 |
March 7 |
o
Project Work Time |
|
|
|
March 14 |
Spring Break – No Class |
|
| Session 8 |
March 21 |
o
Chapter 7=
a, b
& c: Structuring System Process Requirements ü 7a:Use =
Cases ü 7b:Acti=
vity
Diagrams ü 7c: Seq=
uence
Diagrams o
Chapter 8:
Structuring System Logic Requirements ü Data Mo=
del ü Class D=
iagram <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Analysis
Proposal Reviews Feedback <=
span
style=3D'font-size:10.0pt;font-family:"Courier New";mso-fareast-font-fami=
ly:
"Courier New"'>o
Set Path =
for
Design Phase |
·&=
nbsp;
|
| Session 9 |
March 28 |
o
Analysis
Proposal Presentations |
[D] Groups:
Analysis Proposal Product & Presentation Due |
|
Session 10 |
April 4 |
<=
![if !supportLists]>o
Chapter 1=
0:
Designing Forms & Reports <=
![if !supportLists]>o
Chapter 1=
1:
Designing Interfaces & Dialogues ü Usabili=
ty
Slides ü Final E=
xam
Preview ü Pert Di=
agrams o
Chapter 9=
: ü Designi=
ng
Databases o
Project Work Time |
·&=
nbsp;
<=
span
style=3D'font-size:10.0pt;background:#E5B8B7;mso-shading-themecolor:accen=
t2;
mso-shading-themetint:102'> [D}
Students: Homework
Assignment Due |
|
Session 11 |
April 11 |
o&=
nbsp;
Chapter 1=
2:
Designing Distributed & Internet Systems |
o
|
|
|
April 14 |
|
Out of Class Work S=
essions
for Product #1 (If Needed) |
| Session 12 |
April 18 |
o&=
nbsp;
Chapter 1=
3: System
Implementation o&=
nbsp;
Chapter 1=
4:
Maintaining Information Systems o&=
nbsp;
Project Work Time ü
Exec Summ=
ary
Review ü
Presentat=
ion
Review ü
“Final To=
uches” |
|
| Session 13 |
April 25 |
o
Current E=
vents
Discussions o
Wrapup o
Course |
|
| Se=
ssion 14 |
May 2 |
o&=
nbsp;
Design Pr=
oposal
Presentations |
[D] Design Proposal=
Product
& Presentation Due |
|
|
May 9 |
Reading Day |
|
| Session 15 |
May 16 |
o
<=
span
style=3D'font-size:10.0pt'>Final Exam |
[D]: Students: Final Exam Due |