Some
Key Dates
13 Sep (week 3): project 1 due
20 Sep (week 4): quiz 1
23 Sep (week 4): project 2 due
27 Sep (week 5): test 1
11 Oct (week 7): no class (Mid-Semester
Break)
21 Oct (week 8): project 3 due
25 Oct (week 9): quiz 2
01 Nov (week 10): no class - updated 04 Nov (Friday): withdrawal deadline 08 Nov (week 11): test 2 - updated
29 Nov (week 14): test 3 06 Dec (week 15): last class + quiz 3
10 Dec (week 15): project 4 due - updated
13 Dec: test 4 (final)
Week 1: 30 August
Session
- organizational
matters
- introduction:
instructor, TA
- course objectives
- course texts
- course roadmap
(see the last page of this document)
- Piazza discussion
forum (mandatory subscription – link through Sakai)
- how to get help
- prerequisites and
review topics: 271 313
overview
- motivation,
including embedded systems
- brief overview of
batch versus event-based programming
- requirements
- functional: y =
f(x)
- nonfunctional:
additional properties of f, e.g.
- testability
- most
important nonfunctional requirement
- allows
testing whether functional requirements are met
- good
architecture often happens as a side-effect (APPP pp. 36-38)
- performance
- scalability
- e.g.
performance for large data sets: asymptotic order of complexity
(big-Oh) in terms of input size n
- reliability
- maintainability
- static versus
dynamic NFRs
- discussion of
projects 1 and 2
- course software
with demo
- prerequisite
assessment
Reading/Podcasts
Week
2: 6 September
Session
- announcements
- data structures
- linear vs.
nonlinear
- position-based
vs. policy-based (see also here)
- performance
- tying data
structure choices to requirements
- data abstraction
- addressing:
pointers, references
- aggregation (product
types): structs, records
- example: node in
a linked list
- variation (sum
types): tagged unions, multiple implementations of an interface
- example: mutable set abstraction
- add element
- remove element
- check whether an element is present
- check if empty
- how many elements
- several possible implementations
- reasonable: binary search tree, hash table, bit vector
(for small underlying domains)
- less reasonable: array, linked list
- see also here
- group activity: problem 4 on prerequisite assessment
Reading/Podcasts
- OOPUJ chapters 4,
5
- Object Roles and Polymorphism;
Method Overloading
Week
3: 13 September
Session
- announcements
- project
1/software installation check-up
- Quiz 1 next week
- discussion of
project 2
- basics
of object-oriented programming up to genericity (Generics)
- Inheritance and Composition
- Interfaces
- Abstract Classes
- More on Test-Driven Development
- JUnit Annotations, test methods, and examples
Reading/Podcasts
Homework
- Project
1 due Tuesday, September 13
Week
4: 20 September
Session
- Quiz
1: short quiz on first 2 SE Radio episodes, patterns and dependencies
- announcements
- basics
of object-oriented programming - through the rest of the
online document
- Generic types
- Supplemental
material: Java Collections, data structures, and Object-inherited methods
(see course slides)
- Optional topic -
Coad: modeling with UML and color: overview, book
chapter
- reverse
engineering JUnit tests (test 1 topic)
- introduction to
Design Patterns
- Overview
- Factory method,
Strategy, Visitor
- Resources
- tutorialspoint
website
- Bob Tarr pdf
slides on Sakai
- APPP Design
Pattern references
- Factory:
Chapter 29
- Strategy:
Chapter 22
- Visitor:
Chapter 35
- project 3
introduction (only if time)
Reading/Podcasts
- Bob Tarr pdf slide
sets on Factory, Strategy, and Visitor Design Patterns
- Agile Principles,
Patterns, and Practices in C# (APPP) chapters 1-3 and Design Patterns
chapters as above
- Agile Practices;
Extreme Programming Overview; Planning
- Factory,
Strategy, and Visitor Design Patterns
Homework
- Project
2 due Friday, September 23
Week
5: 27 September
Session
- test
1
- announcements
- more Design
Patterns
- Decorator and
Composite
- Visitor revisited
- Resources
- tutorialspoint
website
- Bob Tarr pdf
slides on Sakai
- APPP Design
Pattern references
- Decorator:
part of Chapter 35
- Composite:
Chapter 31
- Visitor:
Chapter 35
- project 3
- Shapes interface
and Visitor<Result> generic interface
- concrete Shapes:
Circle, Rectangle, ...
- concrete Visitors:
Draw, Size, and Bounding Box
- project 3 TODOs
(Android Studio: Tools => View => TODO)
- project 3
Decorators: Outline, Stroke, Location, ...
- Android Canvas
and Paint classes and online documentation
- Unit tests using
Gradle and Mockito; the Fixtures class
Reading/Podcasts
- Bob Tarr pdf
slide sets on Decorator, Composite, and Visitor Design Patterns
- APPP chapters
4-6 and Design Patterns chapters as above
- Testing;
Refactoring; A Programming Episode
- Decorator,
Composite, and Visitor Design Patterns
- SE
Radio episode 167 on unit testing
Week
6: 4 October
Session
- announcements
- team members
posted on Sakai and Piazza
- team
repositories: cs413f15teamNp3
- discussion of test
1
- continued project
3 detailed discussion
- more classes,
including Fixtures
- Mokito "white
box" unit tests (esp. for the Bounding Box Visitor)
- how to run the
unit tests
- expressions and vexpressions Java
examples - using a Visitor<Result> interface to visit arithmetic
expressions
- coding guidelines
- UML diagrams and
30-minute in-class group activity
- create a UML
class diagram for project 3 (hand-drawn is best)
- Submit (a picture
of) the diagram plus a brief write up about how you did it on Sakai - one
per group
- Agile development
(if time)
Reading/Podcasts
Week 7: 11 October (Mid-Semester Break)
Week
8: 18 October
Session
- announcements
- any remaining
questions about project 3
- reminders: Quiz 2
next week (2 SE Radio podcasts), test 2 the following week
- principles of
object-oriented programming: SOLID
- S - Single
Responsibility Principle
- O - Open Closed
Principle
- L - Liskov
Substitution Principle
- I - Interface
Segregation Principle
- D - Dependency
Inversion Principle
- References
- SOLID and
other basic object-oriented design principles ("SOLID +
2"): presentation
- Android example
programs
Reading/Podcasts
Homework
- Project
3 due Friday, October 21
Week
9: 25 October
Session
- Quiz
2: short quiz on second 2 SE Radio episodes, unit testing
(167) and refactoring (46)
- announcements
- test 2 in Week 11 (Week 10 class has been cancelled)
- more design
patterns (all from Week 8)
- Adapter
- Facade
- Observer
- State - including
a review
- Command
- modeling and
introduction to Project 4
- Android framework
overview
Reading/Podcasts
- APPP chapters 33,
23, 32, 15, 21
- Adapter - 33
- Facade - 23
- Observer - 32
- State - 15
- Command - 21
Week 10: 1 November
no class due to Science Days presentation conflict Week
11: 8 November
Session
- test
2 (90 minutes)
- stopwatch internals - objectives, architecture, and design plus demo
- mapping the stopwatch state machine to Java code
- clickcounter overview and demo
- Android
- possible overview of simplebatch and simpledraw
- possibly time to work on Project 4 in your Groups
Reading/Podcasts
Week
12: 15 November
Session
- announcements
- reminder: you should have
listened to SE Radio episode 65 last week on embedded systems!
- test 2 discussion
- as needed
- UML Extended State Machines (with guards)
- in-class group exercise: create a dynamic UML extended state machine model for Project 4
- capture these to submit as part of each 2-person team's Project 4 submission
- agile design: process, not event: presentation
- design smells: usually subjective, sometimes objective
- rigidity: difficult to change
- fragility: easy to break
- immobility: difficult to reuse
- viscosity (of software, of environment): it is difficult to do the right thing
- accidental complexity: e.g., overdesign
- needless repetition (DRY)
- opacity
- design perfume
- refactoring
- MVA in clickcounter and stopwatch; MVP and MVVM
- possibly time to work on Project 4 in your Groups
- extra topic - immutability
Reading/Podcasts
- same as week 11
- relevant
architectural/design patterns
- event
listener/callback
- APPP chapters 7-9, 18, 19
- What is Agile Design; The Single-Responsibility Principle; The Open/Closed Principle
- Sequence Diagrams
- Class Diagrams
Homework - Project 4 extra credit extended state machine assignment due Friday by 11:55pm
Week
13: 22 November
- announcements
- test 3 next week - practice test is in Week 13 on Sakai
- detailed discussion of testing in clickcounter and stopwatch examples
- in-class group exercise: define a comprehensive set of unit tests for Project 4
- also capture these to submit as part of each 2-person team's Project 4 submission
- event-driven programming
- possibly time to
work on Project 4 in your Groups
Other topics Reading/Podcasts
- APPP chapters 10-12
- The Liskov Substitution Principle (LSP)
- The Dependency-Inversion Principle (DIP)
- The Interface Segregation Principle (ISP)
- SE
Radio episode 12 on concurrency (covered in quiz 3)
Homework - Project 4 extra credit tests assignment due Tuesday, November 29, by 11:55pm
Week
14: 29 November
- test
3
- announcements
- course IDEA survey
opens 11/28 and closes 12/11
- Quiz 3 next week
- concurrency
- example: prime
number checker
- direct execution
- asynchronous
(background) execution
- cloud-based
execution
- time to work on Project 4
Reading/Podcasts
Homework - Project 4 extra credit tests assignment due tonight by 11:55pm
Week
15: 6 December - last class
- Quiz
3: short quiz on next 3 SE Radio episodes, embedded
systems (65), concurrency (12), and software architecture (23)
- announcements
- IDEA survey
reminder - IDEA survey closes 12/11 at 11:59pm
- test 4 (final exam) next week - practice exam in Week 15 folder
- test 3 discussion,
if needed
- final topics from
Week 14, if needed
- Cloud Computing - XaaS (X as a Service)
- possible Java 8
overview
- possible in-class
time to finish Project 4
Homework - Project 4 due Saturday night, December 10, by 11:55pm (updated due date)
Reading/Podcasts
Final Session (Week 16): 13
December - final exam
- announcements, if
any
- test
4 (final)
Reading/Podcasts
Dr. Läufer’s Course Outline
|
Overall
Outline of Topics (subject to revision)
- organization, motivation, introduction (1 week: 1
total)
- what makes software good?
- requirements: functional vs. nonfunctional
- the importance of testing
- basics of object-oriented programming (2 weeks: 3
total)
- semantics: reference vs. value, equality vs.
identity
- types and classes: relationships, polymorphism
- code organization: member access,
packages/namespaces
- agile development process (1 week: 4 total)
- overview
- testing
- refactoring
- continuous integration and delivery
- object-oriented design principles (2 weeks: 6 total)
- overview
- SOLID
- designing with interfaces
- agile object-oriented modeling (2 weeks: 8 total)
- main UML diagrams: class, state machine, sequence
- archetypes and colors
- software design patterns (2 weeks: 10 total)
- key patterns from APPP and HFDP
- concurrent programming (3 weeks: 13 total)
- distributed programming (1 week: 14 total)
- overview and principles
- connecting to web services
Typical
structure of a weekly session
- OOPUJ or APPP or PA topics
- project discussion and related topics
- pair/group presentation or other activity
Typical
assignments over a two-to-three-week period
- reading
- listening to SE (Software Engineering) Radio episodes
- programming project
|
|
