SE2030
Schedule
Day-by day class materials
See the code and slides from the webpage. The code examples are numbered by week and class of week. For example, code/class2_1_XXX
is the code example from Week 2, Day 1 (That is, Monday of Week 2).
Tentative Schedule
Week | Day | Topics | Reading | Lab |
---|---|---|---|---|
1 |
1 | Introduction, Waterfall, Requirements | Use Cases
OUTCOMES (INDIVIDUAL): Understand use cases | |
2 | Project Introduction, Use Cases Use Cases | Reading: [link] [link] [link] | ||
2 |
1 | UML Sequence Diagrams | Tutorial: [link] | Sequence Diagrams
OUTCOMES (INDIVIDUAL): Generate Sequence diagrams (high level) |
2 | ||||
3 |
1 | Acceptance Criteria, Project teams formed | Tutorial:
[link] | System Testing
OUTCOMES (TEAM): Interpret Use Cases, Generate Acceptance criteria/system tests |
2 | ||||
4 |
1 | Design UML Class Diagrams | Reading: [link] | Observer Pattern
OUTCOMES (TEAM): Generate High-level UML Class Diagrams using the Observer pattern [link] |
2 | Half Exam 1 | |||
5 |
1 | Code Generation Tutorial: [link] | Version Control OUTCOMES (TEAM): Merge high level designs in EA, Generate code, check into Git repository, start development | |
2 | ||||
6 |
1 | Half-Exam 1 | Reference: [link] | OUTCOMES (TEAM): Continue development, write unit test |
2 | More Version Control and SourceTree, Branching | |||
7 |
1 | Half-Exam 2 | Read: [link] | OUTCOMES (TEAM): Add a dev branch, commit, add work on the dev branch |
2 | Update Presentations | |||
8 |
1 | Bug/defect tracking | OUTCOMES: Create a bug report by testing acceptance criteria. Find, resolve a bug, log it correctly in a bug tracking system. | |
2 | ||||
9 |
1 | Legal, Intellectual Property | Work time | |
2 | ||||
11 |
1 | Demos | ||
2 | Final Presentations | |||
11 |
Final Exam Week |
Half exams announced in Week 4, Class 1, and posted online Week 4, Tuesday (26 Mar 2019)
Acknowledgement
The original version of this schedule comes from Drs. Hornick and Riley.