Web page for CSC301H Introduction to Software Engineering at University of Toronto, Fall 2013
|
Daniel Levy dlevy@cs.toronto.edu BA3008 Athabasca, Smallwood, Winnipeg, and Nipigon |
Neil Padgett neil.padgett@utoronto.ca BA2175 Huron, Great Bear, Superior, and Lake of the Woods |
Sreekumar Rajan sreekumar.rajan@utoronto.ca GB248 Erie, Dubawnt, Ontario, Melville, and Great Slave |
Mahsa Sadi mhsadi@cs.toronto.edu BA2159 Reindeer, Manitoba, Nettilling, and Amadjuak |
Student are encouraged to use the CSC301 discussion board on Piazza as their first point of contact for asking questions, class discussions and other useful information. Important notifications about the course, as well as job opportunities and upcoming events, will appear there.
Slides from lecture will be posted on a separate page.
There are no required textbooks for this courses. Required readings will be made available electronically on piazza.
The primary aim of the course is to teach agile software development methods. These techniques will be practiced on a course project that lasts for the duration of the term. Each assignment will be an iteration or "sprint." The project will be carried out in groups of six, to be assigned by the instructor.
Deadlines for deliverables and milestones are scheduled as follows.
No late assignments will be accepted.
| Deliverable | Weight | Due Date | Grading |
| Sprint 0, Preliminary | 2% | September 25, 22:00 | Rubric |
| Sprint 0, Final | 8% | October 2, 22:00 | Rubric |
| Sprint 1, Preliminary | 3% | October 15, 22:00 | Rubric |
| Sprint 1, Final | 12% | October 23, 22:00 | Rubric |
| Sprint 2, Preliminary | 3% | November 5, 22:00 | Rubric |
| Sprint 2, Final | 12% | November 13, 22:00 | Rubric |
| Final Release | 20% | Various Dates on or before December 3, 23:59:59 | Rubric |
| Date | Team and Project |
| November 18 | Team Nettilling - East Scarborough Storefront |
| November 20 | Team Smallwood - CitizenBridge |
| November 22 | Team Athabasca - CitizenBridge Team Lake of the Woods - North York Seniors Centre |
| November 24 | Team Winnipeg - TABS on Toronto Team Nipigon - TABS on Toronto Team Reindeer - Cultural Hotspot Team Amadjuak - East Scarborough Storefront |
| November 25 | Team Manitoba - Cultural Hotspot |
| November 30 | Team Superior - North York Seniors Centre |
| December 1 |
Team Erie - Ultrasound in Nepal Team Dubawnt - Ultrasound in Nepal |
| December 3 | Team Melville - ACORN Canada Team Ontario - ACORN Canada Team Huron - Election Tycoon Team Great Bear - Election Tycoon Team Great Slave - Invstg8.net |
Final project demos will be held on Saturday, November 30 during a full-day event. Project clients and the general public will be invited to attend.
Quizzes will be held every week on Thursday except for the first and last weeks of the term. They are closed book.
One of the goals of this course is to teach students to work effectively as team members. Individual participation and contribution to the term project will be assessed through peer evaluation. Consequently, every student will be required to submit evaluations of all their team members at the conclusion of each sprint. Students will be graded on the quality of the peer evaluation that they produce and their own growth as a team member.
Peer evaluations are due on October 4, October 25, November 15, and December 3.
Grading Rubric for peer evaluations
The final exam is worth 25% of the overall mark for the course. It is composed of 3 sections (short-answer, medium-answer and long-answer), and is 3 hours in length.
You are allowed one 8.5"x11" hand-written two-sided reference sheet in the exam. No other aids are permitted.
Students must earn at least 40% on the final exam in order to pass the course.
All assignments in this course will be done in teams, with grades awarded to the team as a whole. Team members are strongly encouraged to discuss design ideas, coding issues, etc., with one another. You are also encouraged to use the tutorial hour on Thursday to hold team meetings, design sessions, etc.
However, collaboration between teams should be treated the same way as collaboration between individuals in past courses. You and your teammates may discuss and compare general approaches with members of other teams, and talk about how to get around specific difficulties (e.g., how to use a Java performance profiling tool on CDF with Eclipse), but you should never look at another team's solution to an assignment, even in draft form.
Plagiarism (the act of representing someone else's work or ideas as your own---is a form of academic dishonesty, and is treated very seriously, regardless of whether you are the donor or the recipient. Please refer to the material provided by Office of Student Academic Integrity for details.
This web page will serve as the course information page.