Viewing Party Solo - Rubric

Back to Project Home

Feature Delivery

• Exceeds Expectations: All core requirements are complete and at least one extension.
• Meets Expectations: All core requirements are complete.
• Approaching Expectations: All core requirements are complete but not functioning exactly as intended.
• Below Expectations: Core requirements are incomplete or non-functional.

Testing

• Exceeds Expectations: Project achieves 100% test coverage and includes below expectations.
• Meets Expectations: Project achieves 90% or greater test coverage. In addition to “happy path”, project also includes “sad path”/edge case testing. Feature Tests stub external HTTP requests.
• Approaching Expectations: Project achieves 80-90% test coverage. Project may not include “sad path” or edge case testing.
• Below Expectations: Project does not achieve 80% test coverage.

Code Quality

• Exceeds Expectations: Student can demonstrate how API consumption portions of the project demonstrate all of the four pillars listed below. Student can identify areas where code can be refactored and how they may have created technical debt. Student has refactored into facade and service design pattern.
• Meets Expectations: Student can demonstrate how API consumption portions of the project demonstrate 2 of pillars listed below. Student can identify areas where code can be refactored. Student has refactored into facade and service design pattern.
• Approaching Expectations: Project demonstrates some gaps in code quality and/or application of MVC principles. Student can demonstrate how API consumption portions of the project demonstrate 2 of pillars listed below.
• Below Expectations: Project demonstrates poor factoring and/or understanding of MVC. Student can demonstrate how API consumption portions of the project demonstrate 1 of the pillars listed below.

4 Pillars of OO

• Project uses polymorphism
• Project uses encapsulation
• Project uses abstraction
• Project uses inheritance