| Week | Date | Activities |
| 10 | W 6/1, Th 6/2 | Final project demo days |
| 10 | M 5/30, T 5/31 | NO CLASS |
| 9 | W 5/25, Th 5/26 | COVERED: Pair/extreme Programming |
| 9 | M 5/23, T 5/24 |
COVERED:
Unit testing with JUnitJUnit API Page ASSIGNED: Cockburn/Williams, The Costs and Benefits of Pair Programming; and Williams/Kessler, All I Really Need to Know About Pair Programming I Learned in Kindergarten; summary due at start of next lecture |
| 8 | W 5/18, Th 5/19 |
COVERED:
Testing
ASSIGNED: JUnit design team, Test Infected: Programmers Love Writing Tests, Java Report Magazine NO SUMMARY DUE, but I do expect you to do this reading and to be familiar with how to do JUnit test cases for next lecture. UPDATE: The links were broken and I don't have access to the files because I'm out of town all weekend. So you don't have to turn in the printout until next time. I will fix the links when I am back in town on Monday and reassign this. Please still do the Test Infected reading for Monday, but there is no turnin required. To get the printout: Set up JUnit on your machine, either in TextPad or in Eclipse. Then run the following DateTester test. Take a screen shot of the test case output (press the PrtSc key) in your TextPad or Eclipse window, then paste the screen shot into a drawing program such as Paint. Print the screen shot, bring it to next lecture, and turn it in. This will substitute for your summary. Directions: JUnit in TextPad: Marty's tutorial |
| 8 | M 5/16, T 5/17 |
COVERED:
Testing
ASSIGNED: Bruegge/Dutoit, Object-Oriented Software Engineering, Chapter 9: Testing (part 2); summary due at start of next lecture |
| 7 | W 5/11, Th 5/12 |
COVERED:
Programming by Contract
ASSIGNED: Bruegge/Dutoit, Object-Oriented Software Engineering, Chapter 9: Testing (part 1); summary due at start of next lecture |
| 7 | M 5/9, T 5/10 |
COVERED:
Design Patterns: Singleton, Memento, Flyweight
ASSIGNED: Horstmann, Object-Oriented Design and Patterns, Chapter 3: Guidelines for Class Design: Programming by Contract; summary due at start of next lecture |
| 6 | W 5/4, Th 5/5 |
COVERED:
Design Patterns: Iterator, Strategy, Composite, Decorator
ASSIGNED: Geary, Simply Singleton and Make Your Apps Fly; summary due at start of next lecture |
| 6 | M 5/2, T 5/3 |
COVERED:
Implementation phase;
Design Patterns: Factory, Command
ASSIGNED: Horstmann, Object-Oriented Design and Patterns, Chapter 5; summary due at start of next lecture |
| 5 | W 4/27, Th 4/28 |
COVERED:
more GUI, MVC, Observer / Observable and multiple views
ASSIGNED: No reading or summary assigned today. Please use this time to focus on your design documents and initial code! |
| 5 | M 4/25, T 4/26 |
COVERED:
Creating a GUI in Swing; M-V-C; Observer ASSIGNED: No reading or summary assigned today. Please use this time to focus on your design documents! |
| 4 | W 4/20, Th 4/21 |
COVERED:
UML Sequence Diagrams ASSIGNED: Deacon, Model-View-Controller Architecture; Sundsted, Observer and Observable; summary due at start of next lecture |
| 4 | M 4/18, T 4/19 |
COVERED:
SDS document;
Object-Oriented Design Heuristics (2) ASSIGNED: Fowler, UML Distilled: Sequence Diagrams; summary due at start of next lecture |
| 3 | W 4/13, Th 4/14 |
COVERED:
Object-Oriented Design Heuristics (1) ASSIGNED: Riel, Object-Oriented Design Heuristics (2); summary due at start of next lecture |
| 3 | M 4/11, T 4/12 |
COVERED:
Design phase;
UML class diagrams
UML generation tools: Violet, ArgoUML, ESS Model, Jude, Rational Rose, Visual Paradigm ASSIGNED: Riel, Object-Oriented Design Heuristics (1); summary due at start of next lecture |
| 2 | W 4/06, Th 4/07 |
COVERED:
Scrabble,
Paper Prototyping
ASSIGNED: Fowler, UML Distilled: Class Diagrams; summary due at start of next lecture |
| 2 | M 4/04, T 4/05 |
COVERED:
Use Cases ASSIGNED: Snyder, Paper Prototyping, Chapter 4; summary due at start of next lecture |
| 1 | W 3/30, Th 3/31 |
COVERED:
Requirements ASSIGNED: Cockburn, Writing Effective Use Cases; summary due at start of next lecture |
| 1 | M 3/28, T 3/29 |
COVERED:
 Syllabus,
Summaries,
Software LifecycleASSIGNED: Faulk, Software Requirements: A Tutorial; summary due at start of next lecture |
Week Su Mo Tu We Th Fr Sa
March
1 27 28 29 30 31
April
1 2
2 3 4 5 6 7 8 9
3 10 11 12 13 14 15 16
4 17 18 19 20 21 22 23
5 24 25 26 27 28 29 30
May
6 1 2 3 4 5 6 7
7 8 9 10 11 12 13 14
8 15 16 17 18 19 20 21
9 22 23 24 25 26 27 28
10 29 30 31
June
1 2 3 4
11 5 6 7 8 9 10 11
|
)