Instructor Guide - Assessment Rubrics

This section provides detailed rubrics for evaluating student work throughout the Physical AI & Humanoid Robotics course. Each rubric is aligned with learning objectives and provides clear criteria for assessment.

General Grading Philosophy

The course uses competency-based assessment with an emphasis on practical implementation and problem-solving skills. Students are evaluated on both technical competency and their ability to apply concepts to real-world robotic problems.

Grade Scale

• A (90-100%): Demonstrates mastery of concepts with sophisticated implementations
• B (80-89%): Shows solid understanding with effective implementations
• C (70-79%): Meets basic requirements with adequate implementations
• D (60-69%): Partial completion with significant issues
• F (Below 60%): Inadequate completion or fundamental misunderstandings

Lab Exercise Rubric

Scoring Template

Each lab exercise is worth 100 points total, distributed as follows:

Component	Points	Criteria
Code Implementation	40	Correctly implements required functionality
Code Quality	20	Well-structured, documented, and maintainable code
Problem-Solving	20	Demonstrates understanding through debugging and adaptation
Documentation	10	Clear comments, README, and usage instructions
Reflection Report	10	Analysis of challenges, solutions, and learning outcomes

Detailed Criteria

Code Implementation (40 points)

• 40 (Excellent): All required functionality implemented with optimization and error handling
• 32 (Proficient): All required functionality implemented correctly
• 24 (Adequate): Most functionality implemented with minor issues
• 16 (Below Expectation): Basic functionality present but with significant errors
• 8 (Unsatisfactory): Incomplete or non-functional implementation

Code Quality (20 points)

• 20 (Excellent): Well-structured, efficient, and follows best practices
• 16 (Proficient): Good structure and readability with minor improvements needed
• 12 (Adequate): Basic structure with some readability issues
• 8 (Below Expectation): Poor structure affecting readability
• 4 (Unsatisfactory): Unreadable or unstructured code

Quiz Assessment Rubric

Multiple Choice Questions (5 points each)

• 5 (Correct): Correct answer with understanding demonstrated
• 0 (Incorrect): Incorrect answer or lack of understanding

Short Answer Questions (10-15 points each)

Criteria	15 points	12 points	9 points	6 points	3 points
Accuracy	Completely accurate with detailed explanation	Mostly accurate with explanation	Generally accurate with partial explanation	Some accuracy with minimal explanation	Minimal accuracy with little explanation
Completeness	Covers all aspects thoroughly	Covers most aspects	Covers basic aspects	Covers minimal aspects	Incomplete response
Clarity	Very clear and well-articulated	Clear and understandable	Generally clear	Somewhat clear	Unclear or confusing

Programming Assignment Rubric

Standard Assignment Breakdown (100 points)

Component	Points	Description
Requirements Fulfillment	40	Implementation of specified functionality
Technical Implementation	25	Correct use of course concepts and techniques
Code Quality	20	Structure, readability, and maintainability
Testing and Validation	10	Adequate testing and validation of functionality
Documentation	5	Code comments and user documentation

Detailed Scoring Guide

Requirements Fulfillment (40 points)

• 40 (Exceeds Expectations): All requirements exceeded with additional features
• 35 (Meets Expectations): All requirements met with high quality
• 30 (Approaches Expectations): Most requirements met with minor deficiencies
• 20 (Below Expectations): Some requirements met with significant gaps
• 10 (Well Below Expectations): Few requirements met

Technical Implementation (25 points)

• 25 (Exemplary): Sophisticated, efficient implementation demonstrating deep understanding
• 21 (Proficient): Effective implementation showing solid understanding
• 17 (Adequate): Functional implementation showing basic understanding
• 12 (Developing): Basic implementation with technical errors
• 6 (Beginning): Incomplete or fundamentally flawed implementation

Final Project Rubric

Capstone Project (200 points total)

Component	Points	Description
System Design	40	Architecture and integration across modules
Technical Implementation	50	Quality of code and system integration
Functionality	40	System works as intended across all modules
Performance Evaluation	30	Thorough testing and analysis
Documentation & Presentation	25	Quality of documentation and presentation
Reflection & Future Work	15	Thoughtful analysis of project and next steps

System Design (40 points)

• 40 (Exceptional): Innovative, well-justified design with exceptional integration across modules
• 34 (Excellent): Well-designed system with strong module integration
• 28 (Good): Solid design with adequate module integration
• 20 (Satisfactory): Basic design with minimal integration
• 12 (Needs Improvement): Poor design with inadequate integration
• 4 (Unsatisfactory): Incoherent or incomplete design

Functionality (40 points)

• 40 (Highly Effective): System performs all required tasks with exceptional reliability
• 34 (Effective): System performs all required tasks reliably
• 28 (Adequately Effective): System performs most tasks with minor issues
• 20 (Minimally Effective): System performs basic tasks with significant issues
• 12 (Ineffective): System has major functionality problems
• 4 (Non-functional): System does not function as required

Peer Review Rubric

Peer Review Assignment (5 points per review)

Criteria	5 points	4 points	3 points	2 points	1 point
Constructiveness	Highly constructive feedback with specific suggestions	Constructive feedback with some suggestions	Generally constructive with limited suggestions	Somewhat constructive, general suggestions	Unhelpful or unconstructive feedback
Technical Accuracy	Accurate assessment of technical implementation	Mostly accurate technical assessment	Generally accurate with minor errors	Some technical understanding evident	Limited technical understanding
Clarity	Very clear and well-articulated feedback	Clear and understandable feedback	Generally clear feedback	Somewhat clear feedback	Unclear feedback
Timeliness	Reviewed by deadline with detail	Reviewed by deadline	Reviewed by deadline with minimal detail	Up to 24h late	More than 24h late

Project Presentation Rubric (50 points total)

Component	Points	Criteria
Content Knowledge	15	Depth of understanding of project components
Technical Explanation	15	Clear explanation of technical implementation
Demonstration	10	Effective live demonstration of system
Organization	5	Clear and logical presentation structure
Communication	5	Articulation and response to questions

Content Knowledge (15 points)

• 15 (Expert Level): Comprehensive understanding with ability to explain complex concepts
• 12 (Proficient): Strong understanding with clear explanations
• 9 (Competent): Good understanding with adequate explanations
• 6 (Developing): Basic understanding with unclear explanations
• 3 (Beginning): Limited understanding and poor explanations

Attendance and Participation Rubric (100 points per semester)

Participation Quality (60 points)

• 60 (Exceptional): Regular participation with insightful contributions
• 50 (Strong): Frequent participation with valuable contributions
• 40 (Adequate): Occasional participation with relevant contributions
• 25 (Limited): Minimal participation with basic contributions
• 10 (Insufficient): Rare participation with little to no value

Attendance (40 points)

• 40 (Perfect): All classes attended
• 35 (Excellent): 1-2 absences with valid reasons
• 30 (Good): 3 absences with valid reasons
• 20 (Satisfactory): 4-5 absences or 3-4 with unexcused
• 10 (Poor): More than 5 absences or more than 4 unexcused

Special Considerations

Late Work Policy

• 1-24 hours late: 5% deduction
• 24-48 hours late: 10% deduction
• More than 48 hours late: 25% deduction
• More than 1 week late: Not accepted without instructor permission

Collaboration Policy

• Code sharing: Not permitted for individual assignments
• Idea sharing: Encouraged with proper attribution
• Group work: Clearly defined with individual accountability
• Citation of sources: Required for any external code or resources used

Accommodation Guidelines

Extended Time Accommodations

• Students with documented needs receive 50% extended time on assignments
• Testing accommodations provided as per disability services guidelines
• Modified rubrics available when deemed educationally appropriate

Alternative Assessment Options

• Oral examinations instead of written for students with writing difficulties
• Demonstration-based assessment for students with test anxiety
• Modified project scope for students with documented chronic conditions

Quality Assurance Measures

Inter-rater Reliability

• Sample assignments double-graded by multiple instructors
• Regular calibration meetings for grading consistency
• Student appeals process for grade disputes

Feedback Quality

• Specific, actionable feedback for all assignments
• Timely return of graded work (within one week)
• Opportunities for feedback discussion during office hours

Continuous Improvement

Rubric Review Process

• Quarterly review of rubric effectiveness
• Student feedback integration on assessment methods
• Industry professional input on evaluation criteria
• Alignment verification with learning objectives

Sample Grading Comments

Positive Feedback Examples

• "Your implementation shows sophisticated understanding of the underlying concepts"
• "Code is well-structured and follows best practices"
• "Excellent problem-solving approach to the debugging challenge"

Constructive Feedback Examples

• "Consider refactoring this function to improve readability"
• "Add more comprehensive error handling for edge cases"
• "The algorithm works but could be optimized for better performance"

Next Steps

Continue to Pedagogical Notes or return to Instructor Guide Home.

Navigation

← Previous: Weekly Lesson Plans | Next: Pedagogical Notes → | Instructor Guide Home →