CSE 403: Software Engineering, Winter 2008 |
CSE Home | About Us Search Contact Info |
Week | Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|---|
1 |
1/6 |
1/7 ASSIGNED: Proposal
READ:
#1 (lifecycles) |
1/8 |
READ:
#2 (requirements) |
1/10 |
1/11
READ:
#3 (use cases) |
1/12 |
2 |
1/13 |
1/14 ASSIGNED: Project
READ:
#4a,b (teams) |
1/15 |
1/16
READ:
#5a,b (prototyping) |
1/17 |
1/18
READ:
#6 (OO design) |
1/19 |
3 |
1/20 |
1/21 |
1/22 |
READ:
#7 (UML class diagrams) |
1/24 |
1/25
READ:
#8 (UML sequence diagrams) |
1/26 |
4 |
1/27 |
1/28 |
1/29 |
READ:
#9 (design patterns) |
1/31 |
2/1
READ:
#10a,b (web patterns) |
2/2 |
5 |
2/3 |
2/4
READ:
#11 (prog. by contract) |
2/5 |
READ:
#12 (testing) |
2/7 |
2/8 |
2/9 |
6 |
2/10 |
READ:
#13 (unit testing) |
2/12 |
2/13 |
2/14 |
2/15
READ:
#14 (automation and acceptance testing) |
2/16 |
7 |
2/17 |
2/18 |
2/19 |
2/20 (no reading) |
2/21 |
2/22
READ:
#15 (integration testing) |
2/23 |
8 |
2/24 |
2/25
READ:
#16 (security 1) (read either #16 for Wed OR #17 for Fri) |
2/26 |
2/27
READ:
#17 (security 2) (read either #16 for Wed OR #17 for Fri) |
2/28 |
3/1 |
|
9 |
3/2 |
READ:
#18 (code reviews) (read either #18 for Wed OR #19 for Fri) |
3/4 |
READ:
#19 (refactoring) (read either #18 for Wed OR #19 for Fri) |
3/6 |
3/7 |
3/8 |
10 |
3/9 |
3/10 |
3/11 |
3/12 |
3/13 |
3/14 |
3/15 |
11 |
3/16 |
3/17 |
3/18 |
3/19 |
3/20 |
3/21 |
3/22 |