CS476 Course Schedule

 

Spring 2022 (Tentative. Dates may be adjusted slightly and other assignments may be added)

 

Week	Topics and Assignments	Deliverables
1 (1/10)	Welcome! First day of class: Friday, 14 January, 2022 Opening Comments and Introduction	Syllabus Quiz, see BBlearn
2 (1/17)	Review/Presentation of available projects	Class: Presentation of projects
3 (1/24)	Project preferences Assmt: Project Preferences Memo	DUE: Project prefs memo due by: Wednesday, 1/26/2022 in hardcopy (printed) form at Michael's office, EGR 243 (under the door if he is not there). ASSIGNED: Projects will be assigned in class on Friday 1/28/2022
4 (1/31)	Team assignments, Task: Team startup Task: Create Team Website Assmt: Team Standards Doc and Team Inventory	Team Startup task & Initial website due: Friday 2/4/2022
5 (2/7)	Lecture: Conflict management, Assmt: Mini-Intro	All mentor meetings: Weekly task report
6 (2/14)	Assmt: Fully initialized team website	Due: Team Standards and Inventory
7 (2/21)	Lecture: Requirements Acquisition, Discussion: Tech Writing QuickRef Assmt: Technological Feasibility	Due: Mini-Intro: live, in-class presentations DUE: Peer Eval#1. Due: Close of Biz, Friday: Team website, ready for review.
8 (2/28)	Lecture: Prototyping
9 (3/7)	Lecture: Requirements in Industry Assmt: Requirements Specification Document	DUE: Tech. Feasibility draft: Hardcopy to mentor
10 (3/21)	Review: Requirements Doc spec, planning
11 (3/28)	Review: DR Presentation guidelines spec Task: Mini-team updates	DUE: Tech. Feasibility final. Prepared: 3min Team updates, verbally, in class DUE: Peer Eval#2.
12 (4/4)	Lecture: Configuration Management Planning for Design Review and Demos
13 (4/11)	Assmt: Project Info Mini-Video Assmt: Technical Prototypes Demos (Tech Demo "flight plan" template)	Due: Requirements Document Draft to mentor. DUE: Design Review Presentations, dry run with mentors. DUE after DR: Peer Eval#3.
14 (4/18)	Design Review I presentations (Teams-Room Assignments will be linked here shortly before)	DUE: Design review 1 (DR1), delivered live in class! Task: Schedule Prototype demo with mentor Due: Filled out Tech Demo flight plan to mentor for approval
15 (4/25)	Prototypes, progress and questions, loose ends (Last class meeting is December 3)	Due: Requirements Doc FINAL Due: Website up-to-date and ready for grading. Due: Approved & scheduled Tech Demo Due: Project Info mini-video completed
16 (5/2) FINALS	OFFICIAL FINAL EXAM TIME: Monday, 5/2, 12:30-2:30pm Take Final on BBlearn at or before regular finals time. Task: Course Evaluation	Due by final exam time at latest: -- Signed Reqs. document to your mentor -- Tech Demo completed with mentor -- Peer Eval#4. -- Proof of Course Eval

 

In the table above:

• Specific due dates are rarely used in the above schedule, because each team's mentor meeting is at a different time. Usually you will turn in deliverables to your mentor during the weekly mentor meeting. If that doesn't work out then, at latest, all deliverables shown as "due" in a particular week is due by 5pm on Friday of that week.
• A TASK is a small, fast job that you need to get done. Tasks may or may not have deliverables; if they do, they are generally very short, e.g., send me and/or someone an email. Due dates for tasks are generally expressed in "days after task can start", which usually means after I tell the class to get it done.
• An Assignment (Assmt) is a larger deliverable that you will want to get started on right away in the week that you see it in the schedule. Assignments are generally larger deliverables that will take the team a week or more to prepare.
• Example of GANTT Chart for the above project calendar: here

 

Don't forget:

• All deliverables (hardcopy or electronic) should have a cover sheet with team logo, team name, team members, class, assignment title, date. For evolving documents, a version number is also desirable.
• For smaller hardcopy document deliverables (<5 pages), a staple is adequate. Larger document deliverables should be bound in a professional report cover. No paper clips, dog-ears, or other "alternative" methods of grouping papers allowed.
• For document deliverables that are allowed in electronic form, they must be packaged in a single, professional, and clean PDF document.