Change Module -> Course

README.md

@@ -10,7 +10,7 @@
 
 ## Updating content
 
-1. Checkout the branch of the module e.g., `cs2103`
+1. Checkout the branch of the course e.g., `cs2103`
 1. Update content using MarkBind syntax ([How to use MarkBind](https://github.com/MarkBind/markbind-cli/wiki))
 1. `markbind serve` to start the local server (to preview changes). This command also initiates the live-preview ability i.e. when any changes to the MarkBind code is saved, the site is auto-generated and the Web page (that was opened by the `serve` command) auto-refreshes to show the new content. This works well for small websites but not so well for this website. Recommended to shutdown the server (`Ctrl+C`) before doing further edits.
 1. When you are happy with the edits, use the `markbind deploy` to deploy to the GitHub website at the `origin` repo.

_module-CS2103/timetables-fragment.md → _course-CS2103/timetables-fragment.md

@@ -1,15 +1,15 @@
 <span id="lectures-s1">
 
 {{ lecture_table_headers | trim }}
-{{ module }}/T | ICube Auditorium | Friday **1600**-1800
+{{ course }}/T | ICube Auditorium | Friday **1600**-1800
 
 * The lecture recording will be made available later during the same day.
 </span>
 
 <span id="lectures-s2">
 
 {{ lecture_table_headers | trim }}
-{{ module }}/T | ICube Auditorium | **1400**-1600
+{{ course }}/T | ICube Auditorium | **1400**-1600
 
 The lecture recording will be made available later during the same day.
 </span>

_module-CS2103/weeklyAdminTasks-fragment.md → _course-CS2103/weeklyAdminTasks-fragment.md

@@ -4,8 +4,8 @@
 week1: [
   {id: 'submit_pre_lecture_quiz', deadline: get_date(date_w1_start, 7), graded: true},
   {id: 'set_up_tools', deadline: "before the lecture"},
-  {id: 'submit_pre_module_survey', deadline: get_date(date_w1_start, 4), graded: true},
-  {id: 'learn_about_the_module'},
+  {id: 'submit_pre_course_survey', deadline: get_date(date_w1_start, 4), graded: true},
+  {id: 'learn_about_the_course'},
   {id: 'attend_the_first_lecture'}
 ],
 week2: [
@@ -22,7 +22,7 @@ week4: [
 ],
 week5: [
   {id: 'submit_post_lecture_quiz', graded: true},
-  {id: 'submit_midterm_feedback_for_the_module', deadline: get_date(date_w5_start, 8), deadline_type: 'info'},
+  {id: 'submit_midterm_feedback_for_the_course', deadline: get_date(date_w5_start, 8), deadline_type: 'info'},
   {id: 'practice_peer_evaluations_on_TEAMMATES', deadline: get_date(date_w5_start, 6), graded: true}
 ],
 week6: [

_module-CS2103/weeklyAdminTopics-fragment.md → _course-CS2103/weeklyAdminTopics-fragment.md

@@ -1,10 +1,10 @@
-{% from "_module-" + module + "/weeklyTpTasks-fragment.md" import weekly_tp_themes with context %}
+{% from "_course-" + course + "/weeklyTpTasks-fragment.md" import weekly_tp_themes with context %}
 
 {% set admin_topics = [
-  {level: 1, id: "moduleOverview", title: module_pair + ": " + module_name, link: "moduleOverview.html", alt: "Module Overview"},
+  {level: 1, id: "courseOverview", title: course_pair + ": " + course_name, link: "courseOverview.html", alt: "Course Overview"},
   {level: 1, id: "usingThisWebsite", title: "Using this Website", link: "usingThisWebsite.html", highlight: "true", priority: 1},
-  {level: 1, id: "moduleExpectations", title: "Module Expectations", link: "moduleExpectations.html", priority: 2},
-  {level: 0, id: "moduleStructure", title: "Module Structure"},
+  {level: 1, id: "courseExpectations", title: "Course Expectations", link: "courseExpectations.html", priority: 2},
+  {level: 0, id: "courseStructure", title: "Course Structure"},
     {level: 2, id: "weeklySchedule", title: "Weekly Schedule", link: "weeklySchedule.html", priority: 3},
     {level: 2, id: "lectures", title: "Lectures", link: "lectures.html", priority: 3},
     {level: 2, id: "tutorials", title: "Tutorials", link: "tutorials.html", priority: 2},
@@ -19,7 +19,7 @@
     {level: 2, id: "ip-w4", title: "iP: Week 4", link: "ip-w4.html", priority: 2},
     {level: 2, id: "ip-w5", title: "iP: Week 5", link: "ip-w5.html", priority: 2},
     {level: 2, id: "ip-w6", title: "iP: Week 6", link: "ip-w6.html", priority: 1},
-    {level: 2, id: "ip-w7", title: "iP: Week 7", link: "ip-w7.html", priority: (4 if module == "CS2103" else 1)},
+    {level: 2, id: "ip-w7", title: "iP: Week 7", link: "ip-w7.html", priority: (4 if course == "CS2103" else 1)},
     {level: 2, id: "ip-w8", title: "iP: Week 8", link: "ip-w8.html", priority: 1},
     {level: 2, id: "ip-grading", title: "iP: Grading", link: "ip-grading.html", priority: 2},
   {level: -1, id: "project", title: "Team Project (tP)"},
@@ -49,8 +49,8 @@
   {level: 1, id: "participation", title: "Participation Marks", link: "participation.html", priority: 2},
   {level: 1, id: "gradeBreakdown", title: "Grade Breakdown", link: "gradeBreakdown.html", priority: 2},
   {level: 0, id: "appendices", title: "Appendices"},
-    {level: 2, id: "appendixA-principles", title: "Apdx A: Module Principles", link: "appendixA-principles.html", priority: 4},
-    {level: 2, id: "appendixB-policies", title: "Apdx B: Module Policies", link: "appendixB-policies.html", priority: 1},
+    {level: 2, id: "appendixA-principles", title: "Apdx A: Course Principles", link: "appendixA-principles.html", priority: 4},
+    {level: 2, id: "appendixB-policies", title: "Apdx B: Course Policies", link: "appendixB-policies.html", priority: 1},
     {level: 2, id: "appendixC-faq", title: "Apdx C: FAQ", link: "appendixC-faq.html", priority: 1},
     {level: 2, id: "appendixD-help", title: "Apdx D: Getting Help", link: "appendixD-help.html", priority: 2},
     {level: 2, id: "appendixE-gitHub", title: "Apdx E: Using GitHub", link: "appendixE-gitHub.html", priority: 1},

_module-CS2113/timetables-fragment.md → _course-CS2113/timetables-fragment.md

@@ -1,13 +1,13 @@
 <span id="lectures-s1">
 
 {{ lecture_table_headers | trim }}
-{{ module }}/T | ~~LT19~~ | Friday **1600**-1800
+{{ course }}/T | ~~LT19~~ | Friday **1600**-1800
 </span>
 
 <span id="lectures-s2">
 
 {{ lecture_table_headers | trim }}
-{{ module }}/T | ICube Auditorium | **1400**-1600
+{{ course }}/T | ICube Auditorium | **1400**-1600
 </span>
 
 <span id="tutorials-s1">

_module-CS2113/weeklyAdminTasks-fragment.md → _course-CS2113/weeklyAdminTasks-fragment.md

@@ -3,8 +3,8 @@
 {% set weekly_admin_tasks = {
 week1: [
   {id: 'set_up_tools', deadline: "before the lecture"},
-  {id: 'submit_pre_module_survey', deadline: "by Friday 2359"},
-  {id: 'learn_about_the_module'},
+  {id: 'submit_pre_course_survey', deadline: "by Friday 2359"},
+  {id: 'learn_about_the_course'},
   {id: 'attend_the_first_lecture'}
 ],
 week2: [
@@ -26,7 +26,7 @@ week5: [
 week6: [
   {id: 'submit_coding_exercises', graded: true},
   {id: 'submit_post_lecture_quiz', graded: true, deadline: "before the lecture"},
-  {id: 'submit_midterm_feedback_for_the_module', deadline: get_date(date_w6_start, 15), deadline_type: 'info'}
+  {id: 'submit_midterm_feedback_for_the_course', deadline: get_date(date_w6_start, 15), deadline_type: 'info'}
 ],
 week7: [
   {id: 'submit_post_lecture_quiz', graded: true}

_module-CS2113/weeklyAdminTopics-fragment.md → _course-CS2113/weeklyAdminTopics-fragment.md

@@ -1,10 +1,10 @@
-{% from "_module-" + module + "/weeklyTpTasks-fragment.md" import weekly_tp_themes with context %}
+{% from "_course-" + course + "/weeklyTpTasks-fragment.md" import weekly_tp_themes with context %}
 
 {% set admin_topics = [
-  {level: 1, id: "moduleOverview", title: module_pair + ": " + module_name, link: "moduleOverview.html", alt: "Module Overview"},
+  {level: 1, id: "courseOverview", title: course_pair + ": " + course_name, link: "courseOverview.html", alt: "Course Overview"},
   {level: 1, id: "usingThisWebsite", title: "Using this Website", link: "usingThisWebsite.html", highlight: "true", priority: 1},
-  {level: 1, id: "moduleExpectations", title: "Module Expectations", link: "moduleExpectations.html", priority: 2},
-  {level: 0, id: "moduleStructure", title: "Module Structure"},
+  {level: 1, id: "courseExpectations", title: "Course Expectations", link: "courseExpectations.html", priority: 2},
+  {level: 0, id: "courseStructure", title: "Course Structure"},
     {level: 2, id: "weeklySchedule", title: "Weekly Schedule", link: "weeklySchedule.html", priority: 3},
     {level: 2, id: "lectures", title: "Lectures", link: "lectures.html", priority: 3},
     {level: 2, id: "tutorials", title: "Tutorials", link: "tutorials.html", priority: 2},
@@ -19,7 +19,7 @@
     {level: 2, id: "ip-w4", title: "iP: Week 4", link: "ip-w4.html", priority: 2},
     {level: 2, id: "ip-w5", title: "iP: Week 5", link: "ip-w5.html", priority: 2},
     {level: 2, id: "ip-w6", title: "iP: Week 6", link: "ip-w6.html", priority: 1},
-    {level: 2, id: "ip-w7", title: "iP: Week 7", link: "ip-w7.html", priority: (4 if module == "CS2103" else 1)},
+    {level: 2, id: "ip-w7", title: "iP: Week 7", link: "ip-w7.html", priority: (4 if course == "CS2103" else 1)},
     {level: 2, id: "ip-w8", title: "iP: Week 8", link: "ip-w8.html", priority: 1},
     {level: 2, id: "ip-grading", title: "iP: Grading", link: "ip-grading.html", priority: 2},
   {level: -1, id: "project", title: "Team Project (tP)"},
@@ -48,8 +48,8 @@
   {level: 1, id: "participation", title: "Participation Marks", link: "participation.html", priority: 2},
   {level: 1, id: "gradeBreakdown", title: "Grade Breakdown", link: "gradeBreakdown.html", priority: 2},
   {level: 0, id: "appendices", title: "Appendices"},
-    {level: 2, id: "appendixA-principles", title: "Apdx A: Module Principles", link: "appendixA-principles.html", priority: 4},
-    {level: 2, id: "appendixB-policies", title: "Apdx B: Module Policies", link: "appendixB-policies.html", priority: 1},
+    {level: 2, id: "appendixA-principles", title: "Apdx A: Course Principles", link: "appendixA-principles.html", priority: 4},
+    {level: 2, id: "appendixB-policies", title: "Apdx B: Course Policies", link: "appendixB-policies.html", priority: 1},
     {level: 2, id: "appendixC-faq", title: "Apdx C: FAQ", link: "appendixC-faq.html", priority: 1},
     {level: 2, id: "appendixD-help", title: "Apdx D: Getting Help", link: "appendixD-help.html", priority: 2},
     {level: 2, id: "appendixE-gitHub", title: "Apdx E: Using GitHub", link: "appendixE-gitHub.html", priority: 1},

_module-TEE3201/mid-semester-survey-results.md → _course-TEE3201/mid-semester-survey-results.md

@@ -4,7 +4,7 @@
 </h1>
 
 <p class="lead">
-Given below are the summary results of your ratings on various aspects of the module and my general comments on some
+Given below are the summary results of your ratings on various aspects of the course and my general comments on some
 of them.
 </p>
 
@@ -34,13 +34,13 @@ Can't comment. I have stopped attending them.<br><span class="text-info bg-info"
 **:fas-comment: My comments:**
 
 
-Good to see that lecture briefings are generally well-received. 
+Good to see that lecture briefings are generally well-received.
 Also keep in mind that they are meant to be 'briefings' only -- as the learning the full content is expected to be
 done at your own pace, using the textbook and the pre-recorded videos.
-    
+
 </div>
-        
-        
+
+
 ---
 
 <a id="Q2"/>
@@ -63,16 +63,16 @@ Can't comment. I don't watch them.<br><span class="text-info bg-info"></span><sp
 
 
 Good to see that pre-recorded lecture videos are generally well-received.
-I'll continue to improve the existing ones and add more videos. 
-    
+I'll continue to improve the existing ones and add more videos.
+
 </div>
-        
-        
+
+
 ---
 
 <a id="Q3"/>
 
-### Module website{.text-info}
+### Course website{.text-info}
 
 %%Option%% | %%Count%% %%(/12)%% | %%Percentage%%
 -------|-------|-----------
@@ -88,16 +88,16 @@ Poor<br><span class="text-info bg-info"></span><span class="text-light bg-light"
 **:fas-comment: My comments:**
 
 
-The feedback for the module website seems to be generally positive but there are areas to improve too.
+The feedback for the course website seems to be generally positive but there are areas to improve too.
   I will continue to try and improve the website whenever I can.<br>
   In the meantime, I thank you for your patience with the website -- it's not easy to disseminate that much
   of information in a way that fits everyone's expectations %%(e.g., some prefer more content to be more 'visual'
   while others prefer minimalistic presentation)%%,
   and I realize that ==it is not easy for you to consume that much of information== either.
-    
+
 </div>
-        
-        
+
+
 ---
 
 <a id="Q5"/>
@@ -118,26 +118,26 @@ Too low. <br><span class="text-info bg-info"></span><span class="text-light bg-l
 **:fas-comment: My comments:**
 
 
-* **If the workload is too high:** I realize this module can feel heavy, especially if you don't have prior programming
+* **If the workload is too high:** I realize this course can feel heavy, especially if you don't have prior programming
   experience, and also if you have a day job too.<br>
-  That said, SE modules are usually heavy because learning SE skills needs a lot of practice.<br>
+  That said, SE courses are usually heavy because learning SE skills needs a lot of practice.<br>
   I try to alleviate the workload problem by keeping deadlines fairly flexible and maintaining a low bar for
   the minimum you need to do to get a decent grade.<br>
-  It's OK to fall behind a bit when you are busy with other things, as long as you don't fall too far behind. 
+  It's OK to fall behind a bit when you are busy with other things, as long as you don't fall too far behind.
 * **If you have room for more work:**
   * Try to do more in the project: The project is open ended are you are encouraged to do as much as you want.
     You can refer to [Monty full description](https://nus-tee3201.github.io/2023/programming/chapters/monty.html) to find
     more things you can do with it.
   * Learn the optional topics i.e., level 4 topics.
-    
+
 </div>
-        
-        
+
+
 ---
 
 <a id="Q4"/>
 
-### The pace of the module{.text-info}
+### The pace of the course{.text-info}
 
 %%Option%% | %%Count%% %%(/12)%% | %%Percentage%%
 -------|-------|-----------
@@ -154,16 +154,16 @@ Too slow. Please speed up a lot.<br><span class="text-info bg-info"></span><span
 
 
 * **If the pace is too fast for you:** Not to worry; thanks to the iterative approach we use for covering topics,
-  you'll get multiple chances to solidify your familiarity of a topic/tool. Do what you can every week and 
+  you'll get multiple chances to solidify your familiarity of a topic/tool. Do what you can every week and
   ==try not to fall too far behind== though.
-* **If the pace is too slow for you:** Also cover the optional topics. 
+* **If the pace is too slow for you:** Also cover the optional topics.
   Also, go deeper into the Python topics covered. Python resources are generally easy to find online.
   If that's not enough, drop me a note with which topics/aspects you would like to leann more and I can suggest
   more resources for you.
-    
+
 </div>
-        
-        
+
+
 
 ---
 
@@ -174,7 +174,7 @@ Also note my **general response given at the bottom of this document**.</md></p>
 
 <table style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">
 <tr style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">
-<th style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">Any other feedback about the module?</th>
+<th style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">Any other feedback about the course?</th>
 </tr>
 <tr style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">
 <td style="border: 1px solid grey; border-collapse: collapse; padding:10px; text-align:left">
@@ -200,7 +200,7 @@ Also note my **general response given at the bottom of this document**.</md></p>
 
 
 
-The theory part of this module is relatively light as the module is not part of a computing degree. If you are interested, you can refer to a bigger version of the textbook at https://se-education.org/se-book/ (while most content in there are general SE, code examples are in Java only).</markdown>
+The theory part of this course is relatively light as the course is not part of a computing degree. If you are interested, you can refer to a bigger version of the textbook at https://se-education.org/se-book/ (while most content in there are general SE, code examples are in Java only).</markdown>
 </span></box>
 </td>
 </tr>
@@ -246,8 +246,8 @@ Given below are some general responses to points you guys (and past students) ra
   In the meantime, you can get more programming practice by doing more in the project.
   You can refer to [Monty full description](https://nus-tee3201.github.io/2023/programming/chapters/monty.html) to find
   more things you can do with it.
-* **Looking for more feedback on code written?**: Unlike lower-level programming modules, giving specific feedback
-  on code written in an SE module takes a lot more expertise/effort, and such feedback is still rather subjective.
-  We do not do that in any of our SE modules.
+* **Looking for more feedback on code written?**: Unlike lower-level programming courses, giving specific feedback
+  on code written in an SE course takes a lot more expertise/effort, and such feedback is still rather subjective.
+  We do not do that in any of our SE courses.
   Instead, we train students to slowly learn how to self-judge your own code.
-  In addition, we'll be teaching you some code quality guidelines that you can apply to your code later.
+  In addition, we'll be teaching you some code quality guidelines that you can apply to your code later.