CLASS SCHEDULE
Software Engineering - CPTE 209 - Winter 2009
Date |
Topic |
Source Material |
Assignments |
Instructor |
Wed
Jan 06 |
Principles of good Software Engineering | PowerPoint | ||
Mon
Jan 11 |
Principles of good Software Engineering | PowerPoint | ||
Wed
Jan 13 |
Semester Project - Jumpstart | B1 | ||
Mon
Jan 18 |
MLK day - no class | |||
Wed
Jan 20 |
Software Requirements | SWEBOK 2 | Dant | |
Mon
Jan 25 |
Agile - Overview | Powerpoint | ||
Wed
Jan 27 |
Agile - Overview | Powerpoint | ||
Mon
Feb 01 |
Silver Bullet papers | Article1 Article2 | U1 | |
Wed
Feb 03 |
XP | Beck | ||
Mon
Feb 08 |
XP | Beck (Online lecture) | ||
Wed
Feb 10 |
Software Design | SWEBOK 3 | Dant | |
Mon
Feb 15 |
Testing/Metrics | Testing Powerpoint | B2 | |
Wed
Feb 17 |
Project reports and Junit | |||
Mon
Feb 22 |
Book Reports | Student presentations | B3 | Dant |
Wed
Feb 24 |
Software Construction | SWEBOK 4 | Dant | |
Mon
Mar 01 |
Spring Break | |||
Wed
Mar 03 |
Spring Break | |||
Mon
Mar 08 |
Project + Metrics | Metrics Paper metrics powerpoint | ||
Wed
Mar 10 |
SOFTWARE CONFIGURATION MANAGEMENT | SWEBOK 7 | U2 | Dant |
Mon
Mar 15 |
Project Management/Risk Analysis/Metrics | management powerpoint | ||
Wed
Mar 17 |
SOFTWARE ENGINEERING MANAGEMENT | SWEBOK 8, and ACM code of Ethics | ||
Mon
Mar 22 |
SOFTWARE ENGINEERING PROCESS | SWEBOK 9 | Dant | |
Wed
Mar 24 |
SOFTWARE ENGINEERING TOOLS AND METHODS | SWEBOK 10 | Dant | |
Mon
Mar 29 |
PROJECT working session | |||
Wed
Mar 31 |
SOFTWARE QUALITY, RELATED DISCIPLINES | SEBOK 11, 12 | ||
Mon
Apr 05 |
Process Improvement & QA - CMMI; ISO | Processmax CMMI Process improvement in class lecture | ||
Wed
Apr 07 |
UML | class lecture | U3 | |
Mon
Apr 12 |
Summary and Review | Beck, lectures, powerpoint review | ||
Wed
Apr 14 |
Comprehensive Written Exam | Everything sample1 sample2 sample3 sample 4 | Dant | |
Mon
Apr 19 |
Project working session - Patterns | lecture notes | ||
Wed
Apr 21 |
Project Working Session | Meet in the Advanced Lab | ||
Sun
Apr 25 |
Final Exam - 10an till noon | project demo and documentation | ||
One of the most important things you can learn as a student in the school of computing is to continuously clarify requirements and client expectations. You are expected to do this for your class assignments,
All assignments must be submitted by email. Deadline for all assignments is midnight the day of the assignment except for class presentations which are due at the beginning of class. Refer to the schedule above for due dates.
Select and read an approved book. Book must be be somehow related to the course topic. Prepare a PowerPoint presentation to be given as an in-class book report. Book report should include both general overview information as well as an in-depth review of the major points made by the book. Presentation should take about 20 minutes. The class should learn something as a result of your presentation. Content covered in the report may be covered on the next test.
Title | Author | Assigned to: |
Theory of Constraints | Eliyahu M. Goldratt |
|
It's Not Luck | Eliyahu M Goldratt |
|
Waltzing With Bears | Tom
Demarco, Timothy Lister
|
|
Peopleware: Productive Projects and Teams | Tom Demarco, Timothy Lister | Chris Brown |
Getting Real: The smarter, faster, easier way to build a successful web application |
37signals | Brent Wagner |
Agile estimating and planning | Mike Cohn | Steven Nhut Luu |
Report should not substantially replicate material otherwise covered in the course.
B1: Book selection due
B2: Completed PowerPoint slides due
B3: Presentations start
As a class project, you will be specifying, developing, and testing a website. Details will be added to the assignment as the semester progresses. Deliverables will include variations on the following.
P1: Business goals, requirement and constraints, project plan
P2: Actor Model, Context Diagram, Domain Model and up dated P!
P3. Web design, update p2
P4. Increment 1, system and test cases, updated P3
P5 Increment 2, system and test cases, updated P4
P6, increment 2, system and test cases, updated P5
P7: Poster presentation
UML
Each student will present one of the UML diagrams to the class, explaining its purpose and illustrating with an example.
U1: Diagram selection due
U2: Completed PowerPoint slides due
U3: Presentations start
Diagram | Student |
Class | Chris |
Sequence | Cannon |
State | Steven |
Activity | Brent |
Component | |
Deployment | |
Use Case |
Unit Testing
Additional Assignments may be added as the semester progresses