University of Toronto, Department of Computer Science

CSC444 Software Engineering I   Fall 2002

 

 

Announcements

 

All course announcements after December 8 will be posted at...

 

http://www.cs.toronto.edu/~cosmin/TA/csc444h/

 

December 8

 

We will be posting the marks for assignments 1-4 and the demos on Wednesday.

We may be able to post assignment 5 and the trading results as well.

Assignment pickup location still has to be determined and will be announced.

 

Please submit any re-marking requests to the Engineering Undergraduate office in the basement of Sandford Fleming. Put the course code clearly on the envelope and make sure your e-mail address is on the request so we can notify you when the assignment has been reviewed.

 

December  4.

            The review handout.

 

November 20.

The change request for assignment 5.

 

 

November 18.

á      Note about demos: In order to run demos you have a choice of either using a notebook and the projectors or go to the lab. Please see details following the "demos" link in the calendar below.

 

October 23.

á       temporary lecture room changes for next week:

o      Mon. Oct. 28, Lec 01 AND Lec 02 will meet in WB116 Wallberg Building

o      Wed. Oct. 30,  Lec 01 AND Lec 02 will meet in MC102 Mechanical Engineering

á       assignment due date changes Ð since the assignments are released on this site to all tutorial groups at the same time, it has been requested that the due dates for the assignments be changed to Fridays Ðsee notes below

 

October 15.

 

 October 5.

 

September 27.

 

Prior Announcements

 

 

 

 

Instructors:

Kersti Wain-Bantin

Paulo Pacheco

 

kwain@ecf.toronto.edu

ppacheco@ecf.toronto.edu

 

SF3207  Thurs. 9-11am

SF3207  Mon. and Wed. 1-2 pm

 

Lectures   There are two lectures per week.

LEC 01

LEC 02

LEC 03

Pacheco

Wain-Bantin

Wain-Bantin

Mon. 12:00-13:00 GB248

Mon. 12:00-13:00 GB119

Tues. 10:00-11:00 MC102

Wed. 12:00-13:00 GB248

Wed. 12:00-13:00 GB119

Wed. 11:00-12:00 MC252

 

 

Tutorials (also known as practicals) are held  every week.

 

Mon

Wed

Thurs

Thurs

Fri

 

4-7 pm

6-9 pm

4-7 pm

7-10 pm

3-6 pm

week of

GB304

BA B024

GB404

WB 219

GB404

2-Sep

 

 

TUT011

 

TUT031

9-Sep

TUT021

 

 

 

TUT041

16-Sep

 

TUT021

TUT011

TUT041

TUT031

23-Sep

TUT021

TUT011

 

TUT031

TUT041

30-Sep

 

TUT021

TUT011

TUT041

TUT031

7-Oct

TUT021

TUT011

 

TUT031

TUT041

14-Oct

 

TUT021

TUT011

TUT041

TUT031

21-Oct

TUT021

TUT011

 

TUT031

TUT041

28-Oct

 

TUT021

TUT011

TUT041

TUT031

4-Nov

TUT021

TUT011

 

TUT031

TUT041

11-Nov

 

TUT021

TUT011

TUT041

TUT031

18-Nov

TUT021

TUT011

 

TUT031

TUT041

25-Nov

 

TUT021

TUT011

TUT041

TUT031

2-Dec

TUT021

TUT011

 

 

 

 

 

 

TAÕs

 

TUT011

Jeff Deng

William Andreopoulos

 

    jdeng@cs.toronto.edu

    andreowb@cs.toronto.edu

TUT021

Yuan An

Qingqing Zhou

 

    yuana@cs.toronto.edu

    zhouqq@cs.toronto.edu

TUT031

Cosmin Truta

Meng Sun

 

    cosmin@cs.toronto.edu

    meng@cs.toronto.edu

TUT041

Hang Pham

Faisal Zubair Qureshi

 

    hangp@cs.toronto.edu

    faisal@cs.toronto.edu

 

 

Grading scheme

due date

weight

bi-weekly assignments

as noted

5% for A1

13.5% each for A2-A5

software demo

in tutorials, weeks 10 through 12

6%

end of term exam

date to be announced

35%

Note that assignments and demo are all graded as team assignments.

 

About the Course
Syllabus, Course Goals & Rationale

Books & Readings

 

Lecture Schedule and Notes

  Lecture notes and assignments will become available during the term. This schedule is subject to change.

week

date

lecture 1

lecture 2

1

09/09/02

L00 orientation  .ppt  .pdf

L01 why software fails  .ppt  .pdf

2

16/09/02

L02 case studies  .ppt  .pdf

L03 software project  mngt  .ppt  .pdf

3

23/09/02

L04 software lifecycles .ppt   .pdf

L05 decomposition and abstraction  .ppt  .pdf

4

30/09/02

L06 procedural abstractions .ppt   .pdf

L07 data abstractions  .ppt  .pdf

5

07/10/02

L08 testing .ppt  .pdf

L09 reviews and inspections .ppt .pdf

6

14/10/02

Thanksgiving, no lecture

L10 formal verification  .ppt  .pdf

7

21/10/02

L11 debugging and exceptions .ppt .pdf

L12 software quality    .ppt  .pdf

8

28/10/02

L13 design representation   .ppt  .pdf

L14 requirements analysis .ppt  .pdf

9

04/11/02

L15 structured modeling .ppt  .pdf

L16 object oriented modeling  .ppt  .pdf

10

11/11/02

L17 formal modeling .ppt .pdf

L18 specifications  .ppt  .pdf

11

18/11/02

L19 software architectures .ppt .pdf

L20 software maintenance & reuse .ppt .pdf

12

25/11/02

L21 process modeling  .ppt  .pdf

L22 software measurement  .ppt  .pdf

13

02/12/02

L23 course summary   .ppt  .pdf

L23 course summary contÕd

 

Tutorials and Assignments

 

assigned

practical topic

assignment due

Sept 16 Ð Sept 20

A1. risk management

 

Sept 23 Ð Sept 27

measurement exercise and GQM paper

 

Sept 30 Ð Oct 4

A2. design documentation and test plans

A1

Oct 7 Ð Oct 11

testing

 

Oct 14 Ð Oct 18

phase 1 marketing presentations

A2

Oct 21 Ð Oct 25

A3. quality assessment

 

Oct 28 Ð Nov 1

inspection forms

 

Nov 4 Ð Nov 8

A4. integration reports

A3

Nov 11 Ð Nov 15

A5. documentation and change request

 

Nov 18 Ð Nov 22

demos

A4

Nov 25 Ð Nov 29

demos

A5

Assignments are due in the drop box on the second floor of the Sandford Flemming building at 3PM on the Friday. The exception is assignment A5 which is due at 5PM on Wednesday Dec 4.

 

Additional notes:

Risk management. .doc   .pdf

Examples of decomposition at the analysis/design level. .doc  .pdf

 

Exam

The following past exam papers are available. Please note that there may be changes in material covered on the course from year to year. Past exam papers can be treated as a guide to possible style and content of the exam paper, but should not be regarded as a guide to the topics that may come up on this year's exam.

 

1999 Exam paper             2000 Exam paper             2001 Exam paper

 

General Course Handouts

The orientation handout with details of course grading policy etc.

Notes on the software trading game

Specification for the software development project

and fig.2.1 of the specifications

Notes on alliances, plagiarism and collusion for team projects.