> For the complete documentation index, see [llms.txt](https://ios-course.cornellappdev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ios-course.cornellappdev.com/resources/archived-past-semesters/sp23/logistics/grading-and-project-faqs.md). # Grading ### Breakdown
~Assignment~
P1 - Swift Playground10%
P2 - UIKit & Autolayout10%
P3 - Navigation & Delegation10%
P4 - UITableView10%
P5 - UICollectionView10%
P6 - Networking I10%
P7 - Networking II10%
Hack Challenge Final Project30%Hack Challenge
Attendance10%Attendance
Extra Credit10-15%Extra Credit
To pass this class, you should at least complete all of the minimum project requirements. Things like doing extra credit opportunities (completing challenge problems, filling out course surveys, answering other Ed posts, etc.) will also be taken into account. Each student will also be given **3 total slip days** to cover any emergency or other conflict. **We will also drop the project with the lowest score.** After all slip days have been used, we will be deducing 10% from that project's grade per day submitted late (1 day = 90% max for that project, 2 days = 80%...) **No late submissions will be accepted after the Wednesday following the normal submission deadline.** In addition, the final project is weighted more heavily than the rest of the individual projects, so if you don’t do so great on the usual project assignment, a solid final project can boost your grade significantly. We want everyone to succeed and learn in the class! In summary, if you want to pass this class you will need to put some effort into it. We will send out emails to students before the drop deadline if they are in jeopardy or are struggling in the class. ### **FAQs**
Q: What is the late policy? **A:** Projects are due Monday at 11:59pm, but we will continue to accept projects until the following Wednesday. Any projects turned in afterward will not be accepted for credit.
Q: When will my project be graded? A: We grade on a weekly cycle from the submission deadline, grades for last week's assignments will be released the following Monday.
Q: How exactly are grades calculated for this class? A: As a reminder, this is a pass-fail (S/U) class. We calculate grades by summing up your project grades and extra credit and dividing by the total possible points. If you receive above a 70%, you will definitely pass the course; however, this isn't a hard threshold. Please see us in office hours or create a private Ed post if you are concerned with your grade. If we feel you are struggling, we will send an email a week before the drop deadline notifying you of your status.
Q: The grader made a mistake on my project, can I request a regrade? A: If you feel that the grader made a mistake on your project, create a private Ed post. In the post remember to include the project number and details as to why you think a mistake was made. Please note that regrades are an extra burden on the graders - we are all volunteering to help you succeed in this course, so please double-check that you have followed all project requirements, named your project correctly, and checked that your project compiles.
### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ios-course.cornellappdev.com/resources/archived-past-semesters/sp23/logistics/grading-and-project-faqs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.