CSCI 317: Spring 2019 Meeting and Assignment Schedule
Michael A. Heroux
|Date||Assignment and Exercises||Notes|
|January 14||Video lecture and assignment: |
Approximating Pi Using Simulations Video, Slides
Assignment due: January 21
|No class: In Houston|
|January 18||No class: In Houston|
|January 21||In class lecture: Class Introduction and User Stories|
Assignment: Approximating Pi in C++. Due February 1.
Assignment: User stories to define GitHub usage model Due January 25.
|January 25||In class lecture: |
The 0th Little Pig
Phase 1 Teams
GitHub Usage Model Decisions
In class team presentations:
Design tools user stories and options.
Create team policies
|January 28||No class: In Washington, DC|
|February 1||In class team presentations: |
Design Tools Presentations
In class lecture: The Fisher-Yates (Knuth version) Algorithm
Agile Small Teams
Assignment: Development environments user stories and options
Assignment: PlayingCards class design. Due Feb 8.
|February 4||In class: |
Review of Team Policies and Checklists - Reference A-Team-Tools Site
Development environment presentations.
|February 8||In class team presentations: |
PlayingCard design review.
Solitaire Implementation Strategy.
|February 11||Assignment: C++ unit testing user stories and options.||No class: TGIM|
|February 15||In class lecture: |
Code formatting with clang-format
How to time code execution
|February 18||In class team demo: Unit testing tools presentations. |
In class team demo: Solitaire simulator MVP demo.
|Note: Class starts at 3 pm.|
|February 22||In class lecture: |
|February 25||No class: TGIM|
|March 1||In class project deadline and demo: Solitaire simulator demo and assessment. See checklist |
Assignment: Take-home essay due by 8 pm.
Assignment: Team Assessment Form
Assignment: Software Practices Survey
|March 4||No class: Spring Break|
|March 8||No class: Spring Break|
|March 11||In class lecture: “Bright Spots” and valgrind.|
|March 15||In class team presentations: Bright Spots from your team |
In class video: “Scaling Yourself as a Software Developer”
Assignment: Solitaire - Part 2
|March 18||In class discussion: Scaling yourself |
Assignment: March Madness Predictor
|March 22||No class: In Paris|
|March 25||In class competition: Solitaire Prizes|
|March 29||In class lecture: Reproducibility, Productivity and Sustainability|
|April 1||No class: In Santa Fe|
|April 5||In class: Status check on March Madness Predictor|
|April 8||No class: In London|
|April 12||In class: Status update on March Madness Predictor|
|April 15||In class: Using OpenMP for Parallel Programming||Note: Class starts at 3 pm.|
|April 19||No class: Easter Break|
|April 22||No class: Easter Break|
|April 26||In class: Lottery winning and bringing on a new team member.|
|April 29||In class: Course Concepts Review||Note: Class starts at 3 pm.|
|May 3||In class: Final Review of Solitaire and March Madness Projects. Provide a brief summary and pointers to artifacts that address our Quality Assessment Checklist.|
|May 6 - 10||Finals week: 15-minute Individual Interviews. See these Interview Preparation Prompts for discussion topics.||Note: Scheduled individually during finals week.|