Schedule
Warning! This schedule, like much of the course, is under development and may change significantly.
| Week 0 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 1 | Th | 8/24 |
An introduction to CSC 321
We look at the “big picture” of the course. |
No reading | No lab |
|
|
| Week 1 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 2 | T | 8/29 |
Getting started with Ruby
We start to investigate some issues in Ruby. |
No lab | |||
| 3 | Th | 8/31 |
Ruby, continued
We continue to investigate some issues in Ruby. |
No lab |
|
||
| Week 2 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 4 | T | 9/5 |
Getting started with Rails
We start thinking about Rails and its infrastructure. |
No lab |
|
||
| 5 | Th | 9/7 |
More fun with Rails
We experiment with some real Rails installations. |
No lab |
|
||
| Week 3 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 6 | T | 9/12 |
An introduction to software engineering
We consider three models of software engineering and delve more deeply into agile practices |
No lab |
|
||
| 7 | Th | 9/14 |
Key ideas - Software as a service and user stories
We consider two key ideas in software design (or at least this class’s model of software design): a model of software in the cloud and a mechanism for understanding user requirements. |
No lab | |||
| Week 4 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 8 | T | 9/19 |
Behavior-driven design (BDD) and Test-driven Development
We consider two key ideas in software development and testing, one of which emphasizes high-level functionality and one of which emphasizes procedure-level functionality. |
|
No lab | ||
| 9 | Th | 9/21 |
Work Time
|
No reading | No lab |
|
|
| Week 5 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 10 | T | 9/26 |
Modeling basics
We begin to consider issues of modeling data in general. |
No reading | No lab |
|
|
| 11 | Th | 9/28 |
Modeling, continued
We continue to consider issues of modeling data, in both Rails and in SQL. |
No reading | No lab | ||
| Week 6 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 12 | T | 10/3 |
Legacy code and the UML
We consider a variety of issues related to better design. |
No reading | No lab |
|
|
| 13 | Th | 10/5 |
Design patterns
We consider some basic issues pertaining to design patterns |
No reading | No lab |
|
|
| Week 7 | |||||||
| # | Day | Date | Topic | Reading(s) | Lab | Work Due | |
| 14 | T | 10/10 |
Software design experiences
|
No reading | No lab |
|
|
| 15 | Th | 10/12 |
Wrapup
|
No reading | No lab |
|
|