A+ : The project goes beyond fulfilling basic requirements. It demonstrates accurate visual and intended engineering logic, effective spatial or system integration, artful placement of digital assets, crafty execution, and exceptionally thorough documentation.
A : The project satisfies all requirements and delivers a solid, functional result that accurately reflects and mirrors the intended design concept.
B+ : The project fulfills all base requirements, but falls slightly short of realizing the initial engineering/design concept. Additional iterations or measures are needed to fully demonstrate the proposed idea.
B to D- : The project contains all required components, but falls short in technical execution (e.g., code does not run properly, logic contains errors, or build quality is unrefined). Grades within this range depend on the level of completion, functional stability, and effort shown.
D- and below: Course Policy Infractions: Assigned to students who miss 3 or more classes OR fail to submit more than 2 assignments on time, regardless of project performance.
Students enter this course with varying levels of prior experience. Therefore, grades are not based solely on pure technical success or specific artistic styles.
This course uses an additive grading system: all students start at 0 points and earn their grade through completing assignments and meeting criteria. Grades are not deducted down from 100%. If you arrive prepared for sessions and actively participate, you will succeed in this course.
For complete details on university-wide grading standards and policies, please refer to the UNL College of Engineering.
Team project grades are assessed separately from individual grades, and each student receives an individual score. Weekly Peer Review surveys evaluate team performance and measure individual contributions. The teaching team uses this feedback to assist with team dynamics and ensure fair grading, preventing non-contributing students from receiving unearned credit.
Peers are a vital learning resource. Reach out on Discord via #student-help or #assignment-question for technical issues. When posting, include clear details and screenshots so your classmates can assist effectively.
Define clear completion milestones for your demo simulation. Establish baseline functionality before committing heavy resources to a single aspect (e.g., finalizing environment detail before testing HMD interactions). Be realistic with your time—a fully functional demo always beats an unfinished, high-fidelity vision.
Missing class during team activities disrupts your group’s timeline and workflow. Attendance at all lectures and sections is required. In the event of an illness or emergency, provide documentation and notify your TA ahead of time. If you miss a class, you are responsible for catching up with your teammates immediately.
© You-Jin Kim
Nebraska–Lincoln 🌽