forked from UoMCS/softeng
-
Notifications
You must be signed in to change notification settings - Fork 0
/
002-timetabling.Rmd
203 lines (128 loc) · 7.9 KB
/
002-timetabling.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
# Weekly timetable {.unnumbered #timetabling}
The weekly schedule for autumn 2022 is shown in table \@ref(tab:schedtable), based on [timetables.manchester.ac.uk](https://timetables.manchester.ac.uk/), see also [manchester.ac.uk/discover/key-dates](https://www.manchester.ac.uk/discover/key-dates/) key dates.
* Other than the introductory lecture in week 1, there are no lectures. Instead we have workshops which are more like labs and may contain mini-lectures
* Workshops are on Wednesdays at 9am and Thursdays at 2pm / 3pm depending on your lab group
<!--* [bit.ly/Tuesday-3pm-workshop](http://bit.ly/Tuesday-3pm-workshop)
* [bit.ly/Tuesday-4pm-workshop](http://bit.ly/Tuesday-4pm-workshop)
* [bit.ly/friday-1pm-workshop](http://bit.ly/friday-1pm-workshop)-->
* Team study sessions are on Tuesdays and Thursdays at 10am.
For online activities, everything is on Microsoft Teams.
<!--Because of constraints on the number of private channels in Teams, the year is arbitrarily split into two spaces:
1. [bit.ly/software-engineering-A](https://bit.ly/software-engineering-A)
1. [bit.ly/software-engineering-b](https://bit.ly/software-engineering-b)-->
Microsoft Teams is, as the name suggests, where you'll meet your team, details will appear here once teams have been assigned.
## Which lab should I go to {#campus}
You need to meet with your team in the team study sessions, these are assigned in week 1.
<!--
* **Teams 1-30**: 1.8 & 1.10
* **Teams 31-44**: LF31
* **Teams 44-56**: Tootill-->
The weekly schedule is shown in \@ref(tab:schedtable).
```{r schedtable, echo = FALSE}
io_table <- tibble::tribble(
~ "Week no." , ~ "Subject", ~ "Deadlines",
"**1**: 26th Sept" , "Automated build and test, see (ref:weekone)", "",
"**2**: 3rd Oct" , "Reading large codebases, see (ref:weektwo)", "IndCwk1, Fri 7th Oct, 6pm",
"**3**: 10th Oct" , "Debugging, see (ref:weekthree)", "",
"**4**: 17th Oct" , "Cost estimation, see (ref:weekfour)", "Mentoring week 1, IndCwk2, Fri 21st Oct, 6pm",
"**5**: 24th Oct" , "Test first development, see (ref:weekfive)", "TeamCwk1, 28th Oct, 6pm",
"**6**: 31st Oct" , "Reading week see (ref:weeksix)", "",
"**7**: 7th Nov" , "Git workflows, see (ref:weekseven)", "",
"**8**: 14th Nov" , "Software refactoring, see (ref:weekeight)", "Mentoring week 2",
"**9**: 21st Nov" , "Design for testability, see (ref:weeknine)", "",
"**10**: 28th Nov" , "Design patterns, see (ref:weekten)", "TeamCwk2, 5th Dec, 6pm",
"**11**: 5th Dec" , "Risk management and practice exam, see (ref:weekeleven)", "",
"**12**: 12th Dec" , "Open source challenge, see (ref:weektwelve)", "",
)
knitr::kable(io_table, caption = "The weekly schedule for this twelve week course, please note we are using the week numbering from the [timetables.manchester.ac.uk](https://timetables.manchester.ac.uk/) where week zero is welcome week, and week one is the first teaching week", booktabs = TRUE)
```
## Automating {#week1}
Events in the week starting 26th September:
1. **Team Study Tuesday**: Work on individual coursework 1 described in chapter \@ref(gitting)
1. **One off lecture** to introduce the course unit at 3pm on Friday 30th September, Lecture Theatre A, Engineering Building A [timetables.manchester.ac.uk](https://timetables.manchester.ac.uk/)
1. **Workshop**: Automated build and test with Duncan Hull
1. **Team Study Thursday** Work on individual coursework 1 described in chapter \@ref(gitting)
<!--1. **Coursework deadlines**: Individual individual coursework 1 can be pre-marked (automatically) if you submit by **6pm Tuesday 28th September** and finally marked when submitted by **6pm on Friday 1st October**-->
## Reading {#week2}
Events in the week starting 3rd October:
1. **Team Study Tuesday**: Individual coursework 2 starts, see chapter \@ref(conflicting). Meet your team on Teams
1. **Workshop**: Reading large code bases with Thomas Carroll
1. **Team Study Thursday** Working on coursework
1. **Coursework deadlines**: Individual coursework 1
## Debugging {#week3}
Events in the week starting 10th October:
1. **Team Study Tuesday**: Working on team coursework
1. **Workshop**: Debugging codebases with Thomas Caroll
1. **Team Study Thursday** Working on team coursework
1. **Coursework deadlines**: see blackboard
## Estimating {#week4}
Events in the week starting 17th October:
1. **Team Study Tuesday**: Working on team coursework
1. **Workshop**: Cost estimation with Duncan Hull
1. **Team Study Thursday** Meet your team mentor on Teams
## Testing {#week5}
Events in the week starting 24th October:
1. **Team Study Tuesday**: Working on team coursework
1. **Workshop**: Test first development with Anas Elhag
1. **Team Study Thursday** Working on team coursework
1. **Coursework deadlines**: TeamCwk1 due
## Pausing {#week6}
Events in the week starting 1st November (reading week). Take a break if you're ahead, or catchup if you've fallen behind.
1. There are no activities in reading week
## Workflowing {#week7}
Events in the week starting 7th November:
1. **Team Study Tuesday**: Marking interviews part 1 of 3, see \@ref(mint)
1. **Workshop**: Git workflows with Suzanne Embury
1. **Team Study Thursday** Marking interviews part 2 of 3, see \@ref(mint)
## Refactoring {#week8}
Events in the week starting 14th November:
1. **Team Study Tuesday**: Marking interviews part 3 of 3, see \@ref(mint)
1. **Workshop**: Refactoring with Anas Elhag
1. **Team Study Thursday** Second mentoring session
## Testing {#week9}
Events in the week starting 21st November:
1. **Team Study Tuesday**: Working on team coursework
1. **Workshop**: Design for testability Anas Elhag
1. **Team Study Thursday** Working on team coursework
## Patterning {#week10}
Events in the week starting 28th November:
1. **Team Study Tuesday**: Working on team coursework
1. **Workshop**: Design patterns with Sandra Sampaio
1. **Team Study Thursday** Working on team coursework
1. **Coursework deadlines**: TeamCwk2 due end of the week
## Managing {#week11}
Events in the week starting 5th December:
1. **Team Study Tuesday**: Marking sessions
1. **Workshop**: Risk management and practice exam with Sandra Sampaio
1. **Team Study Thursday** Marking sessions
## Challenging {#week12}
Events in the week starting 12th December:
1. **Team Study Tuesday**: Marking sessions
1. **Workshop**: Open source challenge with Sandra Sampaio
1. **Team Study Thursday**
1. **Coursework deadlines**:
## Tools {#tooling}
We'll be using the following tools:
### Microsoft Teams {#msfteams}
* Team study sessions take place on Microsoft Teams, login using your `@student.manchester.ac.uk` email address at [teams.microsoft.com](https://teams.microsoft.com/) or [download a native teams client](https://www.microsoft.com/en-gb/microsoft-teams/download-app) everthing else is in the guidebook at [software-eng.netlify.app/](https://software-eng.netlify.app/)
* Teams is also the place to go for livestream if you're following the workshops online
### Blackboard {#blackboard}
* Other course materials (slides and videos) can be found on at [online.manchester.ac.uk](https://online.manchester.ac.uk/)
### GitLab {#gitlab}
* GitLab issue tracker [gitlab.cs.man.ac.uk](https://gitlab.cs.man.ac.uk/)
<!--hacky way to get chapter references in tables-->
(ref:weekone) see section \@ref(week1)
(ref:weektwo) see section \@ref(week2)
(ref:weekthree) see section \@ref(week3)
(ref:weekfour) see section \@ref(week4)
(ref:weekfive) see section \@ref(week5)
(ref:weeksix) see section \@ref(week6)
(ref:weekseven) see section \@ref(week7)
(ref:weekeight) see section \@ref(week8)
(ref:weeknine) see section \@ref(week9)
(ref:weekten) see section \@ref(week10)
(ref:weekeleven) see section \@ref(week11)
(ref:weektwelve) see section \@ref(week12)
`Document version:` `r format(Sys.time(), '%d %B, %Y')`
Dennis Hilman
Yuxuan Zheng