Engineering 7893 Software Engineering

Instructor Dr. D. K. Peters
Lectures M, W, F 10:00-10:50 EN1051
Lab slot M 14:00-16:50 EN3076
Office hour Friday 15:00-16:00, or by appointment
T.A. Brian Kidney

Schedule and Examples | Evaluation | Web Submit | Links | FAQ

Detailed Schedule and Examples

The following is the tentative schedule of lectures and assignments for the term. Lecture topics may change slightly as the term progresses. Click an assignment to view it. Click on a topic to view printable form (Portable Document Format) of the class notes. These may not always be available in advance of the lectures and are not to be considered a substitute for attending class.

If you need information about the file formats, or instructions for downloading them check here.

#Date Deadline Lecture 10:00-10:50 Lab 14:00-16:50 Examples/Handouts
1M 05.05 Introduction Info. sheet, SOCCER Specification, Background survey
2W 05.07 Software Development Process
3F 05.09 Team selection WinCVS (Dr. Norvell)
4M 05.12 Development Process (cont'd) Applying UML & Patterns (video) EN1001 Soccer Tools Documentation
5W 05.14 Sofware Engineering Principles Context Free Grammars
6F 05.16
7M 05.19 Software Design Applying UML & Patterns (video) EN1001
8W 05.21
9F 05.23
10M 05.26 Class cancelled
11W 05.28 Software Specification netlayerstates.pdf
12F 05.30 Simulator preliminary design Soccer Tools Source
13M 06.02 Simulator Design review meetings
14W 06.04
15F 06.06 Simulator testing Simulator Tester notes
16M 06.09 specification (cont'd)
17W 06.11
18F 06.13 Verification & Validation
19M 06.16
20W 06.18
21F 06.20 Simulator implementation beta JUnit JUnit demo
M 06.23 Mid-term break
W 06.25
22F 06.27 Controller preliminary design
Verification (cont'd) Additional simulator test cases
23M 06.30 Controller Design review meetings
24W 07.02 dnf.cpp
25F 07.04 Review
26M 07.07 Mid-Term Test
M 07.21 Controller Verification Report Competition
F 08.01 Final Design documents and implementation, Team assessment


There is no prescribed text for this course.



The project component is broken down as follows:
Simulator preliminary design10%
Simulator implementation beta15%
Controller preliminary design10%
Controller verification10%
Final design documents25%
Final implementation10%

Related Links

How to Write JavaDoc Comments
A good introduction to properly commenting your code so that javadoc produces useful results. I strongly encourage you to follow it.

back to Dennis Peters' homepage

Last modified: Tue 2003.07.22 at 10:18 NDT by Dennis Peters