Differences

This shows you the differences between two versions of the page.

--- course_outline [2022/03/08 16:18] – bil
+++ course_outline [2022/03/30 18:25] (current) – bil
@@ Line 5: / Line 5: @@
 Study materials and lab tasks will be posted here.
+--></html>
-====== Week 11 (to be completed by Wednesday, April 7) ======
+====== Week 11 (to be completed by Wednesday, April 6) ======
 ==== Due ====
-The only due item this week is your Peer Assessment 4 feedback on the design documents you have received, due on Wednesday, April 7.
+The only due item this week is your Peer Assessment 4 feedback on the design documents you have received, due on Wednesday, April 6.
+You should of course be working towards completing your project so you can present all its features at the progress report meeting that will take place this week, similar to what we did prior to the midterm submission. These meetings will take place on either Monday or Wednesday using the **lecture Zoom link** as follows:
+=== Monday, April 4 ===
+  * 11:30 - 11:40 Discussion with the whole class as usual
+  * 11:40 - 12:00 Group 1
+  * 12:00 - 12:20 Group 3
+  * 12:20 - 12:40 Group 5
+  * 12:40 - 13:00 Group 6
+  * 13:00 - 13:20 Group 7
-You should of course be working towards completing your project so you can present all its features at the last progress report meeting that will take place this week.
+=== Wednesday, April 6 ===
+  * 11:30 - 11:40 Discussion with the whole class as usual
+  * 11:40 - 12:00 Group 8
+  * 12:00 - 12:20 Group 9
+  * 12:20 - 12:40 Group 11
+  * 12:40 - 13:00 Group 12
+  * 13:00 - 13:20 Group 13
-There is no lab task, but the TAs will be available for any make up lab tasks necessary.
 ==== Study material ====
@@ Line 23: / Line 41: @@
 For more on refactoring, you can watch this [[https://echo360.ca/media/8cd73b73-479e-433e-bd76-aa1f09d0098b/public|instructor video]] on it. Feel free to do this after the term is finished.
+Click [[https://echo360.ca/media/a3c2cf5e-6e2a-4970-b694-a00e8f81a4cd/public|here]] for the lecture video.
 ==== Lab task ====
-There is no lab task, but the TAs will be available for any make up lab tasks necessary.
+There is no lab task, but a TA will be available in the lab on Monday for any questions you may have.
 ==== Weekly goals ====
@@ Line 32: / Line 52: @@
   - Learn about refactoring
   - Provide feedback on the design documents you received before the deadline
-  - Prepare for the last progress report meeting with the customer
+  - Prepare for the progress report meeting with the customer
   - All requirements must be implemented and tested
   - Documents are being finalized
-====== Week 10 (to be completed by Wednesday, March 31) ======
+====== Week 10 (to be completed by Wednesday, March 30) ======
 ==== Due ====
@@ Line 42: / Line 68: @@
 There are two things due this week:
-  - Peer Assessment 4 will be posted on Thursday (Mar 25). You will be submitting your design document on Wednesday, March 31 to receive feedback. As usual, you will be graded for the feedback you will provide.
+  - The lab task as described below.
-  - For the lab task, you will demonstrate how you debugged one of the bugs you team received last week.
+  - The draft of your design document. See the PeerScholar submission link for more details.
 ==== Study material ====
+This week we take a look at testing again. {{:codecoverage.pdf|These slides}} discuss the two topics we will focus on:
+  - Test coverage. Start by watching this [[https://echo360.ca/media/dadaa02f-eb08-44cc-b471-9d2895a0ccf7/public|instructor video]] on the topic. The code in the video is in the TestCoverage project in [[https://github.com/biltzerpos/TeachingCode|this github repository]]. The build.gradle file that came with the repository has all these features as well. Use JaCoCo and create test coverage reports. Work on improving the coverage of your test code.
+  - GUI testing. Start by watching this [[https://echo360.ca/media/cdaba2af-3b4c-4989-98d5-999b398e9d32/public|instructor video]] on the topic. The code in the video is in the JavaFXSample project in [[https://github.com/biltzerpos/TeachingCode|this github repository]]. Next, check out the [[https://github.com/TestFX/TestFX|TestFX github page]] for more information. Add appropriate GUI test cases to your system. GUI tests are not required for the final submission.
+Click [[https://echo360.ca/media/e2f8a073-fd21-4c18-abac-c0dd13a46581/public|here]] for the Week 10 lecture video.
 ==== Lab task ====
-Your team should divide the bug reports you received last week among the team members. You should respond to all the bug reports assigned to you on github.
+Compute the code coverage of your code and make plans on how to improve it.
-Choose one of the bug reports assigned to you. Use the debugging facilities of Eclipse (set breakpoints, step through etc) to trace the source of the bug and fix it.  Demonstrate the above process to the TA (revert to a commit that still has the bug to demonstrate if necessary).
 ==== Weekly goals ====
-  - Learn about debugging
+  - Learn about code coverage
-  - Produce a complete draft of your design document and submit it by the deadline
+  - Learn about GUI testing
-  - Ensure other documents are also being worked on
+  - Submit a draft of your design document for peer feedback.
-  - All requirements must be implemented and ready for testing/debugging
+====== Week 9 (to be completed by Wednesday, March 23) ======
-====== Week 9 (to be completed by Wednesday, March 24) ======
 ==== Due ====
-There are two things due this week that are both related to bug reporting:
+For Peer assessment 3, you are required to submit 3 bug reports for each of the two projects you are evaluating. See the PeerScholar link for more details. Preparing these bug reports is also your lab task for the week (see below).
-  - For Peer assessment 3, you are required to submit 3 bug reports for each of the two projects you are evaluating. See the PeerScholar link for more details.
-  - For the lab task, you will choose one of these bug reports and demonstrate the bug to the TA.
 ==== Study material ====
@@ Line 81: / Line 106: @@
 ==== Lab task ====
-Choose one of the bug reports you created this week, demonstrate to the TA the incorrect behaviour, and present the bug report.
+Create the 3 bug reports as indicated above.
 ==== Weekly goals ====
@@ Line 87: / Line 112: @@
   - Learn about bug reporting
   - Produce constructive bug reports for peer systems
+  - Fix problems identified in your midterm submission feedback
   - Implementation on all new requirements must be underway
-  - Your system must be able to handle simple tabs for all three instruments by now
-====== Week 8 (to be completed by Wednesday, March 17) ======
-==== Due ====
-There are two things due this week:
-  - The lab task as described below.
-  - The current version of your system. See the PeerScholar submission link for more details.
-==== Study material ====
-This week we take a look at testing again. {{:codecoverage.pdf|These slides}} discuss the two topics we will focus on:
-  - Test coverage. Start by watching this [[https://echo360.ca/media/dadaa02f-eb08-44cc-b471-9d2895a0ccf7/public|instructor video]] on the topic. The code in the video is in the TestCoverage project in [[https://github.com/biltzerpos/TeachingCode|this github repository]]. Next, update your system to use JaCoCo and create test coverage reports. Work on improving the coverage of your test code.
-  - GUI testing. Start by watching this [[https://echo360.ca/media/cdaba2af-3b4c-4989-98d5-999b398e9d32/public|instructor video]] on the topic. The code in the video is in the JavaFXSample project in [[https://github.com/biltzerpos/TeachingCode|this github repository]]. Next, check out the [[https://github.com/TestFX/TestFX|TestFX github page]] for more information. Add appropriate GUI test cases to your system.
-==== Lab task ====
-Demonstrate to the TA the code coverage for the part of the code that you are responsible. Briefly discuss how you plan to improve the coverage of your tests.
-==== Weekly goals ====
-  - Learn about code coverage
-  - Learn about GUI testing
-  - Repeated from last week: Study the additional requirements posted about the project and start implementing them
-  - Produce a version of the system that implements as many requirements as possible for submission on Wednesday, Mar 17.
---></html>