CPSC 329 Syllabus

Reading, when assigned, is to be done for the class period where it is listed.

Dates for things in light gray are tentative and may shift slightly.

		Assignments
Week 1: 9/1-9/5 Topics: introduction; understanding what the software needs to do (functionality)

Mon	Slides: introduction		homework #0 homework #1 due Wed Sep 3

Tue		lab #1 Introduction to Eclipse due Tue Sep 9

Wed	Slides: good software, understanding phase (single-sentence summary, user goals, features, requirements)		homework #2 due Fri Sep 5
			homework #2 due Fri Sep 5
Fri	Slides: understanding phase (Klondike and Wa-Tor examples, requirements discovery, requirements document) Examples: in-class Wa-Tor example		homework #3 due Mon Sep 8 (revise for Wed Sep 10)
Week 2: 9/8-9/12 Topics: version control and SVN; understanding what the software needs to do (usage)

Mon	Slides: hw2 comments (user goals, features, requirements) version control and SVN user interactions and scenarios

Tue		lab #2 Subversion due Tue Sep 16

Wed	Slides: scenarios		homework #4 due Fri Sep 12
			homework #4 due Fri Sep 12
Fri	Slides: use case diagrams and use cases hw2/3 comments (requirements documents)		homework #5 due Mon Sep 15
Week 3: 9/15-9/19 Topics: design (determining classes and responsibilities)

Mon	Slides: scenarios comments and use cases wrapup design phase (introduction, identifying classes)		homework #6 due Wed Sep 17

Tue		lab #3 Subversion II due Tue Sep 23

Wed	Slides: identifying responsibilities comments on use case diagrams and use cases Examples: WATOR class list (as generated in class)		homework #6b due Fri Sep 19
			homework #6b due Fri Sep 19
Fri	Slides: sequence diagrams, UML class diagrams Examples: some sequence diagrams for Klondike: new game diagram, WSD file; move cards around diagram, WSD file partial class diagram for Klondike (based on the sequence diagrams above)		homework #7 due Mon Sep 22	project #1 understanding phase due Fri Sep 26
Week 4: 9/22-9/26 Topics: technologies (threads); human-computer interaction and UI design

Mon	Slides: threads Examples: creating threads (subclassing `Thread`): CountdownThread.java, CountdownThreadDemo.java creating threads (implementing `Runnable`): Countdown.java, CountdownDemo.java waiting for a thread to finish (`join`): SlowCountdown.java, JoinDemo.java politely shutting down a thread: SlowCountdown2.java, ShutdownDemo.java ATM example, no mutual exclusion: BankAccount.java, SimpleATM.java, SimpleATMDemo.java ATM example, mutual exclusion: BankAccount.java, SynchATM.java, SynchATMDemo.java counter example, no mutual exclusion: Counter.java, SimpleCounter.java, Entrance.java, SimpleGardenDemo.java counter example, mutual exclusion: Counter.java, SynchCounter.java, Entrance.java, SynchGardenDemo.java		homework #8 due Wed Sep 24

Tue	Reading: Eck, Introduction to Programming Using Java, sections 12.1-12.2	lab #4 Threads due Tue Sep 30

Wed	Slides: UI design References/Reading: User Interface Design for Programmers How to Design a Great User Experience

Fri	Slides: UI design comments on lab 3		homework #9 due Mon Sep 29
Week 5: 9/29-10/3 Topics: UI design; implementation

Mon	Slides: comments on project phase 1 comments on CRC cards, sequence diagrams, class diagrams			project #1 design phase due Mon Oct 6

Tue		lab #5 Swing due Tue Oct 7

Wed	Slides: UI design discussion (WATOR) usability

Fri	Slides: choosing data structures comments on hw 7 and lab 4 (sequence diagrams, class diagrams, threads, SVN) Examples: WATOR sequence diagrams: configure parameter settings, observe simulation (1), observe simulation (2) WATOR class diagram
Week 6: 10/6-10/10 Topics: implementation and testing

Mon	Slides: choosing data structures

Tue		lab #6 JUnit due Tue Oct 21		programming assignment WATOR due Mon Oct 20

Wed	Slides: defensive programming and testing lab 5 comments (SVN, general Java, GUI stuff)

Fri	Slides: testing (developing test cases, automated testing, JUnit, designing for testing)
Week 7: 10/13-10/17 Topics: advanced threads, client-server networking

Mon	fall break (no class)
Tue	fall break (no class)

Wed	Slides: threads (threads vs `Timer`, coordinating threads with `wait`/`notify`) client-server networking Examples: coordinated countdown (wait/notify): CoordinatedCountdown.java, CountdownMaster.java, CoordinatedCountdownDemo.java producers and consumers (wait/notify): PrimeProducer.java, PrimeConsumer.java, ProducerConsumerDemo.java simple client and server: Server.java, Client.java Reading: Eck, Introduction to Programming Using Java, section 12.3.4 and section 11.4

Fri	Slides: client-server networking (exceptions, protocols) some comments on project 1 Examples: basic joke server, with support for multiple types of jokes and remote shutdown: JokeServer.java, JokeClient.java, ShutdownClient.java, KnockKnockJoke.java
Week 8: 10/20-10/24 Topics: client-server networking, developing networked programs

Mon	Examples: threaded joke server (supporting simultaneous clients): JokeServer.java, ClientServicing.java, JokeClient.java, SlowJokeClient.java, KnockKnockJoke.java threaded joke server with remote shutdown: JokeServer.java, ClientServicing.java, JokeClient.java, SlowJokeClient.java, ShutdownClient.java, KnockKnockJoke.java		project #1 implementation due Mon Nov 3

Tue		lab #7 Networking due Tue Oct 28

Wed	Slides: threads, networking, and streams (race conditions, multiple stream objects) designing client-server programs Examples: threaded joke server with remote shutdown: JokeServer.java, ClientServicing.java, JokeClient.java, SlowJokeClient.java, ShutdownClient.java, KnockKnockJoke.java

Fri	Slides: designing client-server programs comments on lab 6 Examples: protocol examples: reversi, joke server (note slightly different notation - here the solid arrow is used to indicate an interaction being initiated, and a dashed arrow is used to indicate a response - this helps distinguish between cases whether the other side has to read some information to know what use case is occurring vs just knowing what step this is)
Week 9: 10/27-10/31 Topics: object oriented design principles

Mon	Slides: class design (5 Cs) reflecting on our development process			homework #10 due Wed Oct 27

Tue		lab #8 Networking II due Tue Nov 4

Wed	Slides: object oriented design principles (information hiding, encapsulation, loose coupling) Examples: original guitars code: Guitar.java, Inventory.java, FindGuitarTester.java

Fri	Slides: object oriented design principles (code to the interface, avoid mutable classes, Law of Demeter) some comments on implementation Examples: revised guitars code: Guitar.java, Inventory.java			homework #11 due Wed Nov 5
Week 10: 11/3-11/7 Topics: object oriented design principles

Mon	Slides: improving reusability and organization WATOR comments

Tue	project #1 UI presentations (in lab)	project #1 writeup due Fri Nov 7

Wed	Slides: improving reusability and organization lab 7 comments			project #2 understanding part A due Mon Nov 10

Fri	Slides: designing for flexibility (encapsulate what varies, open-closed principle) hw 10 & 11 comments
Week 11: 11/10-11/14 Topics: more advanced object-oriented design

Mon	Slides: designing for flexibility (more encapsulate what varies and open-closed principle examples, Liskov substitution principle)			project #2 understanding part B due Wed Nov 12

Tue		lab #9 Encapsulate What Varies due Tue Nov 18	homework #12 due Fri Nov 14

Wed	Slides: designing for flexibility (favoring composition over inheritance, more encapsulate what varies examples)			project #2 design due Wed Nov 19

Fri	Slides: designing for flexibility (greater complexity - stack example) design patterns (introduction, Strategy) comments on Pente
Week 12: 11/17-11/21 Topics: design patterns

Mon	Slides: design patterns (maze solver and Strategy, Observer) lab 8 comments Examples: maze solver (hw12): subclass version, composition version (the split of "same" and "varies" code is the same in both versions; the difference is where the "varies" code is - in subclasses of `MazeSolver`, or in separate objects that are plugged into `MazeSolver`)

Tue		lab #10 Strategy and Observer due Tue Nov 25

Wed	Slides: MVC Examples: beat generator: class diagram, code reversi: class diagram, code			project #2 implementation due Thu Dec 18

Fri	Slides: principles and patterns (Don't Repeat Yourself, Factory Method / Abstract Factory, Decorator, Visitor)
Week 13: 11/24-11/28 Topics: design patterns

Mon	Slides: WATOR design (larger version of the starting class diagram)

Tue	Slides: some ideas about the in-class exercises	in-class exercises

Wed	Thanksgiving break (no class)
Fri	Thanksgiving break (no class)
Week 14: 12/1-12/5 Topics: code review

Mon	code review: meet in Gulick 208	lab #11 Code Review and Redesign due Tue Dec 9

Tue

Wed	code review: meet in Gulick 208

Fri	Slides: project 2 phase 2
Week 15: 12/8-12/12 Topics: wrapup and project

Mon	Slides: wrapup

Tue

Wed	work on project: meet in Gulick 208

Fri	work on project: meet in Gulick 208 Notes: lab 11 discussion
Reading Period and Exams: 12/13-12/19

Sat

Sun

Mon

Tue

Wed

Thu	final exam Thu 12/18 1:30-4:30pm available on Canvas exam information	end-of-semester deadline no work accepted after 12/18 4:30pm

Fri

CPSC 329 Syllabus

Week 1: 9/1-9/5

Week 2: 9/8-9/12

Week 3: 9/15-9/19

Week 4: 9/22-9/26

Week 5: 9/29-10/3

Week 6: 10/6-10/10

Week 7: 10/13-10/17

Week 8: 10/20-10/24

Week 9: 10/27-10/31

Week 10: 11/3-11/7

Week 11: 11/10-11/14

Week 12: 11/17-11/21

Week 13: 11/24-11/28

Week 14: 12/1-12/5

Week 15: 12/8-12/12

Reading Period and Exams: 12/13-12/19