diff --git a/book.org b/book.org index f2d332f..5079d00 100644 --- a/book.org +++ b/book.org @@ -1026,6 +1026,7 @@ We have drastically cut the time we initially spent on mandatory assignments by #+NAME: tab:usefweworkload | Task | Estimated workload (hours) | |-------------------------------------+----------------------------| +| | | | Lectures | 60 | |-------------------------------------+----------------------------| | Mandatory assignments | 540 | @@ -1966,14 +1967,15 @@ Table\nbsp{}[[tab:passfailcoursestatistics]] summarizes some statistics on the c #+CAPTION: The courses are taken by different student cohorts at different faculties and differ in structure, lecturers and teaching assistants. #+CAPTION: The number of tries is the average number of solutions submitted by a student per exercise they worked on (i.e. for which the student submitted at least one solution in the course edition). #+NAME: tab:passfailcoursestatistics -| | year | students | # ex. | solutions | tries | pass rate | -|---+------------+----------+-------+-----------------+-------+-----------| -| A | 2016--2017 | 322 | 60 | 167\thinsp{}675 | 9.56 | 60.86% | -| A | 2017--2018 | 249 | 60 | 125\thinsp{}920 | 9.19 | 61.44% | -| A | 2018--2019 | 307 | 60 | 176\thinsp{}535 | 10.29 | 65.14% | -| B | 2016--2017 | 372 | 138 | 371\thinsp{}891 | 9.10 | 56.72% | -| B | 2017--2018 | 393 | 187 | 407\thinsp{}696 | 7.31 | 60.81% | -| B | 2018--2019 | 437 | 201 | 421\thinsp{}461 | 6.26 | 62.47% | +| | year | students | # ex. | solutions | tries | pass rate | +|-----+------------+----------+-------+-----------------+-------+-----------| +| | | | | | | | +| A | 2016--2017 | 322 | 60 | 167\thinsp{}675 | 9.56 | 60.86% | +| A | 2017--2018 | 249 | 60 | 125\thinsp{}920 | 9.19 | 61.44% | +| A | 2018--2019 | 307 | 60 | 176\thinsp{}535 | 10.29 | 65.14% | +| B | 2016--2017 | 372 | 138 | 371\thinsp{}891 | 9.10 | 56.72% | +| B | 2017--2018 | 393 | 187 | 407\thinsp{}696 | 7.31 | 60.81% | +| B | 2018--2019 | 437 | 201 | 421\thinsp{}461 | 6.26 | 62.47% | Course A is subdivided into two successive instructional units that each cover five programming topics -- one topic per week -- followed by an evaluation about all topics covered in the unit. Students must solve six programming exercises on each topic before a deadline one week later.