|
CSCI 3130 Summer 2011 Tentative schedule and partial readings and resource list |
|||
|
# |
Date |
Topics and Readings |
Deliverables |
|
1 |
Tue May 3 |
Syllabus, overview + project description |
|
|
2 |
Thu May 5 |
Project charter Software lifecycle Software documentation - Doxygen www.doxygen.org/index.html - Read the manual: - In particular: documenting the code: http://www.stack.nl/~dimitri/doxygen/docblocks.html - Will generate html that describes the code Project documentation |
May 5: MS1 out May 5: MS2 out |
|
3 |
Tue May 10 Kirstie @ CHI |
Guest lecturer: Robert Hawkey Real world description of software development lifecycle in the games industry |
|
|
4 |
Thu May 12 Kirstie @ CHI |
Guest lecturer: Robert Hawkey Practical software engineering practices/tools: Debugging Daily builds and automated builds, Code reviews, code standards Software configuration management (subversion) - http://code.google.com/edu/tools101/scm.html - Subversion hooks Estimation - Pre-assignment: Watch 10 Deady Sins of Software Estimation Webinar http://adtmag.com/webcasts/2011/03/construx-10-deadly-sins-of-software-estimation.aspx?partnerref=con4 |
May 12: Wk 1 project report due May 12: MS1 due |
|
5 |
Tue May 17 |
Formal Software requirement specification (SRS) and project plans - Project survival skills: http://www.stevemcconnell.com/sgskill.htm |
May 17: MS3 out |
|
6 |
Thu May 19 |
Principles of Software Design (Ch 15 of rec. text) |
May 19: Wk 2 project report due May 19: MS2 due |
|
7 |
Tue May 24 |
Data flow models, state models, UML |
|
|
8 |
Thu May 26 |
Validation & Verification |
May 26: Individual SRS review out May 27: Wk 3 project report due May 27: MS3 due |
|
9 |
Tue May 31 |
Software Design Process Software architecture (Ch 18 of rec. text) Software Design Specification templates and examples: - Wiki with good examples of various pictorial design representations |
May 31: MS 4 out |
|
10 |
Thu Jun 2 |
Object oriented design process (UML) – slides uploaded as a reference – class cancelled due to illness |
June 3: Wk 4 project report due June 3: Individual SRS review due |
|
11 |
Tue Jun 7 |
Risk Management |
|
|
12 |
Thu Jun 9 Kirstie @ Boeing |
Class cancelled, project work: refine your design documents, start with your implementation plans |
June 9: Individual design review out Jun 10: Wk 5 project report due June 10: MS 4 due |
|
13 |
Tue Jun 14 |
Change request management |
|
|
14 |
Thu Jun 16 |
Software Quality/Refactoring 1 |
June 17: Wk 6 project report due June 17: Individual design review due
(now due June 20th, 3pm) June 20: MS5 out |
|
15 |
Tue Jun 21 |
Refactoring 2 |
|
|
16 |
Thu Jun 23 |
Software Testing 1 |
June 24: Wk 7 project report due |
|
17 |
Tue Jun 28 |
Software Testing 2 |
|
|
18 |
Thu Jun 30 |
Software Testing 3: Interactive guest lecture with Iain McCowatt, Program Test Manager, CGI in Teaching Lab 2 |
June 30: Wk 8 project report due July 4: MS5 due (3pm) July 4: MS6 out |
|
19 |
Tue Jul 5 |
Integration |
|
|
20 |
Thu Jul 7 |
Software Engineering Methodologies: waterfall, prototyping, spiral |
July 8: Wk 9 project report due |
|
21 |
Tue Jul 12 |
Software Engineering Methodologies: Agile, RAD, scrum |
July 12: Individual Ass 1 out July 12: Project presentation details out |
|
22 |
Thu Jul 14 |
Course evaluation (4:05pm) Software Engineering Methodologies: Extreme programming, team software process |
July 15: MS 6 due (3pm) July 15: Wk 10 project report due |
|
23 |
Tue Jul 19 |
No class - Group Work |
|
|
24 |
Thu Jul 21 Kirstie @ SOUPS |
No class - Group Work Presentation skills resources: - Includes a video: http://www.wikihow.com/Do-a-Presentation-in-Class - Powerpoint slides illustrating what to do and not to do: http://www.cmos.ca/effectivepresentations_DJones_files/v3_document.htm - http://www.lrc.centennialcollege.ca/tutorserv/Presentations/Presentation%20Skills.htm - Software demo tips: http://grattisfaction.com/2010/01/how-to-give-a-better-software-demo/ |
July 22: Wk 11 project report due |
|
25 |
Tue Jul 26 |
Project Presentations: - Group A - Group B - Group E |
July 26: Project presentation |
|
26 |
Thu Jul 28 |
Project Presentations/Post-mortem: - Group C - Group D |
July 29: Wk 12 project report due July 29: Final Project Due July 29: Individual Ass #1 due |
|
Item |
Description |
Due |
Grades |
|
MS1 |
Group website |
May 12 |
2% |
|
MS2 |
Project charter/feasibility document |
May 19 |
3% |
|
MS3 |
SRS & Project plan |
May 27 |
10% |
|
Individual Document reviews |
SRS Review |
June 3 |
10% |
|
MS4 |
Design Documents |
June 10 |
10% |
|
Individual Document reviews |
Design Review |
June 17 |
10% |
|
MS5 |
Change request management |
July 4 |
5% |
|
MS6 |
Software test plan |
July 15 |
10% |
|
Project presentation |
Description & demo of project |
July 26/28 |
10% |
|
Final project documents (modified to address feedback/current reality) |
Project Charter SRS & Project plan System Design and detailed design documents Test Plan Test Reports User Manual Deployment Guide Weekly project reports Minutes of project meetings |
July 29 |
20% |
|
Individual Assignment 1 |
Post-mortem report/peer assessment |
July 29 |
10% |
|
|
|
Total |
30% Individual, 70% Group work |
|
Note: Weighting of group marks to team members may vary. Anything less than an equal distribution will only occur if there is documentation (e.g, weekly project reports, and project deliverable documentation) in addition to peer assessments that reveal inequities in effort and commitment. |
|||