• Classes resume on Tuesday, February 3, 2009.
• Instead of meeting in SC203, we will be meeting from now on in the SEL (CSEB2056).
• I look forward to seeing you at 4pm on Tuesday, 3 Feb, in CSEB2056.
• Please bring your laptop with you if possible. There are also 5 workstations in the SEL.
• We will be meeting at the regular times until Thursday 19 February.
• We shall start by working on the requirements for the bridge controller. We will also review the use of the Spin tool for verifying the specifications. The purpose of this is to help you prepare for the home test.
• We will announce the due dates for the remaining grading units after we have our first class meeting.
• [Feb 3, 2009] During class today we decided that
  • Phase3 is due in the last week of class. Due date: Tuesday Feb 17, 2009, by noon. As part of the grading, you will be required to make an appointment with the TA to demonstrate your work (Book Phase 3 Meeting).
  • The Hometest is due in the week after class: Due date: Monday Feb 23, 2009, by 4pm.(this has been extended to noon on Wed. Feb. 25th).
  • The last quiz may be replaced with a grade equivalent to the larger of Phase3 or the Hometest. [If you would like to take the Quiz (which will be oral) instead, please contact the instructor by Feb 11th.
• Classes resume Feb 2. Classes end Feb 19. Exams start Feb 20. Exams end March 3. Winter classes start March 3.

This course deals with the elicitation, specification and analysis of software requirements and provides a critical description of available methods and tools, and practical exercises on applying these methods and tools to realistic problems. Three lecture hours per week. Prerequisites: General prerequisites, including CSE 3311.

Required textbook: Ian Alexander, et. al, Writing Better Requirements, Addison-Wesley, 2002. Suggested Textbooks

Lecture times: TR16:00-17:30 25 SC 203

Weekly Office and Lab Hour: Thursday 2.30pm to 3.30pm in the Software Engineering Lab CSEB2056 (also look in CSEB2045).

Note: this course has a large project where you must elicit and document requirements for a significant system. The requirements must also be implemented in code which must be tested against the requirements. Expect the project to take a significant amount of time. You may work on your own or in teams of at most two members. See the Important Dates for timing of deliverables. In addition, there is one scheduled labtest and 3 quizzes during class time (please see Important Dates so that you can schedule your time accordingly).

Participants in the course: please login (see below↓) to see the full array of resources for this course.