Home | Syllabus | Calendar and Class Notes | Projects | Homework | Participation | Grades
Course Outline, Class Notes Links, and Assignment Due-Date Calendar
Project assignments, with appropriate deliverables and dates for their completion are given below. These dates are firm, with at least the up-front expectation that there will be no extensions or exceptions. It is nearly impossible to slip dates and still get it all done in the semester.
|
Week #
|
Day
|
Date
|
Topic
|
Class notes |
Text
Chapters |
Project Assignment / Due Date
|
# Weeks
|
|
1
|
Tu
|
1/20
|
Introduction, demographic survey, Life Cycle |
-
|
-
|
-
|
|
|
Th
|
1/22
|
Life Cycle, Systems Analysis, product concept statement, form teams |
1 & 4
|
-
|
-
|
||
|
2
|
Tu
|
1/27
|
Systems Analysis, exercises |
-
|
5
|
-
|
-
|
|
Th
|
1/29
|
Systems Analysis exercises, Design |
5
|
1.0
|
|||
|
3
|
Tu
|
2/3
|
Scenarios & Screen Design, exercise |
-
|
-
|
-
|
-
|
|
Th
|
2/5
|
Scenarios & Screen Design show & tell Benchmark Tasks, Usability Specifications |
-
|
-
|
-
|
||
|
4
|
Tu
|
2/10
|
Benchmark Tasks, Usability Specifications, exercise, show & tell |
-
|
8
|
Project 2: Systems Analysis |
1.5
|
|
Th
|
2/12
|
Rapid Prototyping, exercise |
9
|
-
|
-
|
||
|
5
|
Tu
|
2/17
|
Rapid Prototyping exercise |
-
|
-
|
-
|
-
|
|
Th
|
2/19
|
Usability evaluation (Intro), Usability evaluation (Before data collection) |
10
|
Project 3: Scenarios, Screen Design, and Early Prototype |
1.5
|
||
|
6
|
Tu
|
2/24
|
No lecture, meet as needed to discuss projects |
-
|
-
|
-
|
-
|
|
Th
|
2/26
|
No lecture, meet as needed to discuss projects |
-
|
-
|
-
|
-
|
|
|
7
|
Tu
|
3/2
|
Usability evaluation (During data collection), critical incident exercise (individual) Ideal -- data collection tool concept Usability evaluation (After data collection) |
-
|
-
|
-
|
|
|
Th
|
3/4
|
Usability evaluation (During data collection): in-class demo Finish: Usability evaluation (After data collection) |
-
|
-
|
-
|
||
|
Spring Break Week - Enjoy your trip to Florida, or Myrtle
Beach, or Christiansburg, or wherever!!
|
|||||||
|
8
|
Tu
|
3/16
|
Usability evaluation (During data collection) team exercise |
-
|
-
|
Project 4: High-Fidelity Prototype and Usability Specifications |
2.5
|
|
Th
|
3/18
|
Usability evaluation (After data collection) team exercise In-class exercise Kiosk RP & evaluation show & tell |
-
|
Prototype demos (detailed task-driven demos for GTA): all teams |
-
|
||
|
9
|
Tu
|
3/23
|
Team project prototype demos (in-class overview) |
-
|
-
|
Prototype demos (detailed task-driven demos for GTA):
all teams
|
-
|
|
Th
|
3/25
|
User Action Framework, design guidelines (1-28) |
-
|
Prototype demos (detailed task-driven demos for GTA): all teams 6:30 PM: Deadline for team prototype grading with GTA |
-
|
||
|
10
|
Tu
|
3/30
|
User Action Framework, design guidelines (29-50) |
- |
2
|
- |
-
|
|
Th
|
4/1
|
User Action Framework, design guidelines (51-55), Usability guidelines exercises, Usability Inspection |
-
|
-
|
-
|
||
|
11
|
Tu
|
4/6
|
Web usability |
-
|
3.0
|
||
|
Th
|
4/8
|
Usability problem analysis |
-
|
-
|
|||
|
12
|
Tu
|
4/13
|
Usability problem analysis |
-
|
-
|
-
|
-
|
|
Th
|
4/15
|
Human-to-human communication, Wrap up |
-
|
-
|
-
|
||
|
13
|
Tu
|
4/20
|
Project 7: Oral Presentations:
Teams 1, 2, 3 |
-
|
-
|
Project 6: Design Iteration (Teams 4, 5) Project 7: Oral Presentations (Teams 1, 2, 3) |
2.0
|
|
Th
|
4/22
|
Project 7: Oral Presentations: Teams 4, 5 |
- |
-
|
-
|
||
|
14
|
Tu
|
4/27
|
Usability problem analysis: practice |
-
|
-
|
||
|
Th
|
4/29
|
Safety valve day, for class scheduling |
-
|
-
|
|||
|
15
|
Tu
|
5/4
|
Review and Faculty Evaluation (attendance required) |
-
|
12
|
Project 8: Team Member Evaluations |
-
|
|
Tuesday
|
5/12
|
Final Exam, 1:05 PM |
-
|
||||