You should be learning about each topic by reading the text, attending lectures, participating in in-class discussions, and by applying the methodologies and processes in your group projects.
Your understanding of each topic listed below will be evaluated based on how well your group projects apply the processes and methodologies covered in each topic, and based on your performance on the midterms.
There are a few additional notes after the schedule.
|
Week |
|
Topic |
Chapters |
Assignments and Activities |
|---|---|---|---|---|
|
1 |
Tuesday 1/9/01 |
Overview of Software Engineering and the class |
Survey |
|
|
Thursday 1/11/01 |
Group dynamics; Project management, managing people and groups |
1, 2, 4, 22 |
Discuss questions 4.9, 22.5, 22.10; Take photos |
|
|
2 |
Tuesday 1/16/01 |
Unified Modeling Language (UML) |
||
|
Thursday 1/18/01 |
Software development processes - overview of all activities involved |
3 |
Jot down ideas for questions 3.3 and 3.4. |
|
|
Configuration control (though not discussed in class) |
29 |
Jot down ideas for questions 29.1 and 29.6 |
||
|
3 |
Tuesday 1/23/01 |
Software development processes - waterfall model, RAD, spiral model |
Groups present and turn in project documents |
|
|
Thursday 1/25/01 |
Project Planning and Management |
Groups meet with professor to discuss projects |
||
|
4 |
Tuesday 1/30/01 |
Software architecture design |
10 |
Students turn in GME's and unofficial course evaluations; Jot down thoughts for 10.1, 10.3, 10.6 |
|
Thursday 2/1/01 |
Object-oriented design; The unified software development process |
12 |
||
|
5 |
Tuesday 2/6/01 |
Project 2 kick-off |
Project 1 code due on Monday evening; Project 1 documents due in class on Tuesday; Student present Project 2 proposals in class; Go over Project 2 assignment |
|
|
Thursday 2/8/01 |
Midterm #1 |
Midterm #1 |
||
|
6 |
Tuesday 2/13/01 |
Requirements analysis |
5 |
Brief Project 2 group discussions |
|
Thursday 2/15/01 |
Requirements analysis |
In-class questions |
||
|
7 |
Tuesday 2/20/01 |
Requirements engineering process |
6 |
Groups present and turn in project 2 documents |
|
Thursday 2/22/01 |
Project Planning, Management, Software Processes |
Groups meet with professor to discuss how they are progressing with their projects |
||
|
8 |
Tuesday 2/27/01 |
To be determined |
||
|
Thursday 3/1/01 |
Software Testing |
19, 20 |
||
|
9 |
Tuesday 3/6/01 |
User Interface Design |
15 |
Project 2 due on Wednesday evening |
|
Thursday 3/8/01 |
User Interface Analysis and Testing |
GME 2 |
||
|
10 |
Tuesday 3/13/01 |
Project demos; Final Lecture - Overview of the course |
official course evaluations |
|
|
Thursday 3/15/01 |
Midterm #2 |
Midterm #2 |