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.
"Read" refers to chapters in vanVliet (2000).
|
Date |
Discuss in Class |
Read |
Project milestones |
|
Week 1 - M, April 3 |
Overview of software engineering. |
|
Conduct survey |
|
Week 1 - W, April 5 |
Group dynamics. Project management. |
1, 2, 5 |
Hand out Project 1. Groups assigned. |
|
Week 2 - M, Apr 10 |
Software life cycle. Process models. |
2, 3 |
|
|
Week 2 - W, Apr 12 |
Project Planning |
8 |
Students present project plans. |
|
Week 3 - M, Apr 17 |
Software architecture |
10 |
Initial project documents submitted. |
|
Week 3 - W, Apr 19 |
Group projects |
|
Groups meet with instructor |
|
Week 4 - M, Apr 24 |
Software design (guest lecture) |
11 |
|
|
Week 4 - W, Apr 26 |
Object-oriented design. UML. (guest lecture) |
12 |
Projects submitted Sunday, April 30. |
|
Week 5 - M, May 1 |
Software engineering lessons learned from Project 1 |
|
Project demos |
|
Week 5 - W, May 3 |
Midterm exam |
|
|
|
Week 6 - M, May 8 |
Project 2 Kickoff |
|
Students present project ideas. Project 2 groups formed. |
|
Week 6 - W, May 10 |
Midterm Discussion |
|
Students present group plans. |
|
Week 7 - M, May 15 |
Requirements engineering |
9 |
|
|
Week 7 - W, May 17 |
Requirements engineering |
|
Initial project documents submitted. |
|
Week 8 - M, May 22 |
Group projects |
|
Groups meet with instructor |
|
Week 8 - W, May 24 |
Testing |
13 |
|
|
Week 9 - M, May 29 |
(Memorial Day Holiday) |
|
|
|
Week 9 - W, May 31 |
User interface design |
16 |
Projects submitted Sunday, June 4. |
|
Week 10 - M, June 5 |
Software engineering lessons learned from Project 2 |
|
Project demos |
|
Week 10 - W, June 7 |
Review |
|
|