Skip to content

Latest commit

 

History

History
101 lines (85 loc) · 3.65 KB

Assignments.md

File metadata and controls

101 lines (85 loc) · 3.65 KB
Raw

Assignments

  1. Assignment 1
    • Assigned: 4/5
    • Initial work complete: 4/12 11:59 pm
      • 50% for running pipeline with passing unit test
      • 50% for working website
    • Code Reviews Due by: 4/13 11:59 pm
    • Review in class: 4/14 2:00 pm
    • Final turn in: 4/14 11:59 pm
  2. Assignment 2
    • Assigned: 4/14
    • Initial work complete: 4/26 11:59 pm
      • 50% for running pipeline with passing unit test
      • 50% for working website
    • Code Reviews Due by: 4/27 11:59 pm
    • Review in class: 4/28 2:00 pm
    • Final turn in: 4/28 11:59 pm
  3. Assignment 3
    • Assigned: 4/28
    • Initial work complete: 5/10 11:59 pm
      • 50% for running pipeline with passing unit test
      • 50% for working website
    • Code Reviews Due by: 5/11 11:59 pm
    • Review in class: 5/12 2:00 pm
    • Final turn in: 5/12 11:59 pm
  4. Assignment 4
    • Assigned: 5/12
    • Initial work complete: 5/26 11:59 pm
      • 50% for running pipeline with passing unit test
      • 50% for working website
    • Code Reviews Due by: 5/29 11:59 pm
    • Review in class: 5/31 2:00 pm
    • Final turn in: 5/31 11:59 pm
  5. Assignment 5
    • Assigned: 5/31
    • Initial work complete: 6/9 11:59 pm
      • 50% for running pipeline with passing unit test
      • 50% for working website
    • Code Reviews Due by: 6/11 11:59 pm
    • Review in class: 6/9 2:00 pm
    • Final turn in: 6/12 11:59 pm

Grading Breakdown

The below is subject to change.

0-64	F
65-66	D
67-69	D+
70-72	C-
73-76	C-
77-79	C+
80-82	B-
83-86	B
87-89	B+
90-94	A-
95+     A

Each assignment is a total of 100 points. Assignments may contain up to 10 points of extra credit. Assignments will also include an additional 10 points that can be awarded to one team per assignment for the best submission.

Fundamentals (up to 5 points + up to 100% deduction of final grade)

  • Code is clean (up to 5 points)
    • Follows best practices.
    • The simplicity first approach is followed.
    • The code is formatted well with out large amounts of whitespace or indenting issues
    • The PR git diff is clean and easy to read (no extra, unrelated files, or messy PR diffs)
  • 100% deduction if submission is late (for initial turn in date + final turn in date)
  • 50% deduction for broken pipeline with failing unit test by initial turn in date
  • 50% deduction for broken website by initial turn in date

Assignment (60 points)

  • Points are distributed among each bulleted assignment instruction with partial credit being possible for all parts of the assignment.

Final Corrections (5 points)

  • All code review comments addressed

Peer Review (PR review) (20 points)

  • The review should leave helpful inline comments on the code
  • Look for a PR with no reviews first
  • It is likely each PR will have more than 1 review, so you are also welcome to leave comments ontop of another students review either elaborating further or disagreeing with the review.
  • Make sure you review the assignment for each assignment instruction, commenting inline for each portion of the assignment.

Partnered (10 points)

  • 10 points for pairing for the assignment.

Extra Credit (up to 20 points)

  • These points given out at the instructor's discretion. These may not be given out if the assignment is not completed to a satisfactory level.
  • Extra credit is not avalible on all assignments.
  • 20 points of extra credit is not avalible on all assignments.
  • Half of the extra credit (10 points) is only (occassionally) avaliable to 1 group per assignment.

See the grading template here