Spring 2018 COMP 413-001

Some Key Dates
15 Jan (Week 1): no class (MLK Holiday)

31 Jan (Week 3): project 1 due Wednesday night

12 Feb (Week 5): quiz 1

16 Feb (Week 5): project 2 due Friday night

19 Feb (Week 6): test 1

05 Mar (Week 8): no class (Spring Break)

16 Mar (Week 9): project 3 due Friday night

19 Mar (Week 10): quiz 2

26 Mar (Week 11): test 2

26 Mar (Week 11 Monday): withdrawal deadline

16 Apr (Week 14): test 3

23 Apr (Week 15): last class + possible quiz 3

28 Apr (Week 15): project 4 due Saturday night

30 Apr: (Week 16) test 4 (final exam)

 

Preliminary Schedule (Based on Dr. Yacobellis' Fall 2017 COMP 313 Schedule – Subject to Change)

    

Previous version (Fall 2017)


Week 1: 15 January - No class, Martin Luther King Holiday


Week 2: 22 January

Sessions

  • 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 3: 29 January

Sessions

  • 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

Homework

  • Project 1 due Wednesday night, January 31


Week 4: 5 February

Sessions

  • 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

 

Week 5: 12 February

Sessions

  • Quiz 1: short quiz on first 2 SE Radio episodes, patterns and dependencies
  • announcements
    • test 1 roadmap on Sakai
  • 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: overviewbook 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, February 16

 

Week 6: 19 February

Sessions

  • test 1
  • announcements
    • project 3 team formation
  • 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 7: 26 February

Sessions

  • announcements
    • team members posted on Sakai and Piazza
    • team repositories: cs313f17teamNp3
  • 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 8: 5 March - No class, Spring Break


Week 9: 12 March

Sessions

Reading/Podcasts

Homework

  • Project 3 due Friday night, March 16

Week 10: 19 March

Sessions

Reading/Podcasts

    • APPP chapters 33, 23, 32, 15, 21
      • Adapter - 33
      • Facade - 23
      • Observer - 32
      • State - 15
      • Command - 21


Week 11: 26 March

Sessions

Reading/Podcasts

Homework

  • Project 4 extra credit extended state machine assignment due Saturday by 11:55pm (optional, can wait until next week) 


Week 12: 2 April

Sessions

  • announcements
    • reminder: you should have listened to SE Radio episode 65 last week on embedded systems!
  • test 2 discussion - as needed
  • detailed discussion of testing in clickcounter and stopwatch examples
  • in-class group exercise: create a comprehensive set of unit tests for Project 4
    • also capture these to submit as part of each Group's Project 4 submission
  • more Android examples - only if time
  • possibly time to work on Project 4 in your teams

Reading/Podcasts

Homework

  • Project 4 extra credit tests (and extended state machine) assignment due Saturday by 11:55pm


Week 13: 9 April - may combine some of this with Week 12

Reading/Podcasts

  • APPP chapters 7-9, 18, 19
    • What is Agile Design; The Single-Responsibility Principle; The Open/Closed Principle
    • Sequence Diagrams
    • Class Diagrams
  • SE Radio episode 12 on concurrency (covered in quiz 3)


Week 14: 16 April - may combine some of this with Week 13

Reading/Podcasts


    Week 15: 23 April

    • Quiz 3: short quiz on next 3 SE Radio episodes, embedded systems (65), concurrency (12), and software architecture (23)
      • Replaced with time to fill in the IDEA survey
    • announcements
      • IDEA survey reminder - IDEA survey closes 4/27 at 11:59pm
      • test 4 (final exam) next week - practice exam in Week 15 folder
    • 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, April 28, by 11:55pm

    Reading/Podcasts


    Final Session (Week 16): 30 April - 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)
      • events
      • threads
      • sharing
    • 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
    Subpages (2): Project 1 Project 2
    Comments