CMPUT 404

Lab Procedure

• H01 Monday Signup Sheet

• H02 Wednesday Signup Sheet

• You must demo your individual lab work to a TA during the lab to receive marks.

  • If you submit on eClass but don't demo you will get a zero.
  • You can demo over Zoom or in person.
  • Demos are during the second half of your registered lab section on BearTracks (6:00 PM-7:50)
• Labs are due on eClass/Github at 4PM before the date of your registered lab in section in BearTracks.
  • If you are in the Monday lab, your due date is 4PM Monday.
  • If you are in the Wednesday lab, your due date is 4PM Wednesday.
  • If you demo but don't submit you will get a zero.

The TAs will do their best to keep strictly to the schedule on the demo signup sheet.

Online/Zoom demos are a privilege. If you are not prepared for your online demo, the TA will not mark your work and will move on to the next student. It doesn't matter if you're having audio problems, video problems, zoom problems, internet problems, etc. when your time slot is over, the TA will move on to the next student, and you will lose marks.

If you are worried about your audio, video, zoom, internet connection, etc. attend and demo in person instead of online.

Labsignments (Lab Assignments)

1. HTTP
2. Django
3. Heroku
4. Pelican
5. Flask

All labsignments

Lab Marking

Rubric

Your grade on the lab is the percentage of your code that you completed and can demonstrate to the TA during your demo that you understand. You must be able to explain your code to the TA and explain why you chose to write your code the way you did.

For example, you might be asked to explain:

• Why you chose a certain structure?
• Why you needed a particular variable?
• The role a method serves in letting two classes communicate.
• The difficulties you had when developing your code.

Note that simply reading the code to the TA does not count as understanding.

Examples

1. Example:
   • Your code works perfectly.
   • You can explain your code to the TA during the demo.
   • Grade: 100
2. Example:
   • Your code works perfectly.
   • You can explain most of your code to the TA during the demo, but you can't explain why you chose to use a while loop instead of a for loop for a critical component.
   • Grade: 90
3. Example:
   • Your code works perfectly.
   • You can explain some of your code to the TA during the demo.
   • But, it seems like you don't understand half of the code for one of two problems in the lab.
   • Grade: 75
4. Example:
   • Your code is halfway complete.
   • You can explain your code perfectly.
   • Grade: 50
5. Example:
   • Your code works perfectly.
   • You can only explain half of your code.
   • Grade: 50
6. Example:
   • Your code is halfway complete.
   • You can only explain half of your code.
   • Grade: 25
7. Example:
   • Your code works perfectly.
   • You can't explain any of your code, and it doesn't seem like you understand it at all.
   • Grade: 0
8. Example:
   • Your code mostly works. The TA estimates it is 80% done.
   • You can't explain any of your code, and it doesn't seem like you understand it at all.
   • Grade: 0
9. Example:
   • Your code doesn't work at all.
   • Grade: 0
10. Example:
    • Your code looks like it isn't even for the current lab
    • Grade: 0
11. Example:
    • Your code works perfectly
    • You can explain your code to the TA with no problem
    • But, you forgot to submit it on eClass
    • Grade: no grade (but this counts the same as a 0)
12. Example:
    • Your code works perfectly
    • You can explain your code to the TA with no problem
    • But, you plagiarized, misrepresented your work, or other academic misconduct (cheating)
    • Grade: 100, and you get interviewed by the instructor, and you get interviewed by the Dean's office, and you probably get sanctioned by the Dean's office, and you probably receive letter of reprimand, and the Dean's officer can set your grade to 0 anyway. Or the Dean's officer might fail you for the entire course, or whatever they decide, they have their own rules.