Rails Engine Evaluation

For the project eval, you should come prepared for a 10 minute presentation of your code to an evaluator.

The technical presentation portion is outlined below with what points should be covered. You should be able to present on all points even if you did not implement in code. If you have questions about the presentation, please let an instructor know before the evaluation day.

You should review each section of the rubric and strive to have a 3 in each section before attempting any 4s.

Technical Presentation

• 4: The student has a well organized presentation that addresses each point directly and uses technical vocabulary correctly throughout the presentation.
• 3: Student presents their code and is able to talk about all the presentation points.
• 2: Student presents their code and is able to talk about 3-4 of the presentation points.
• 1: Student is unprepared for the presentation and requires prompts from the instructor to talk about the code.

Presentation points:

[ ] Demonstration of functional completeness (Running the spec harness & Rails Driver)

[ ] Technical quality and organization of the code

[ ] Identifying code that should be refactored and how it would be refactored

[ ] Discussion of test coverage (happy and sad path and edge cases)

[ ] Approach to their ActiveRecord queries

Feature Delivery

• 4: Project completes all requirements and at least one extension.
• 3: Project completes all requirements
• 2: Project fails to complete 1 - 3 required endpoints
• 1: Project fails to complete more than 3 endpoints

Test Driven Development

• 4: Project achieves 100% test coverage at the unit and integration levels. The tests include sad path and edge case testing.
• 3: Project achieves greater than 90% test coverage
• 2: Project achieves greater than 80% test coverage
• 1: Project does not have 80% test coverage.

Technical Quality

• 4: Project demonstrates exceptionally well factored code.
• 3: Project demonstrates solid code quality and MVC principles.
• 2: Project demonstrates some gaps in code quality and/or application of MVC principles.
• 1: Project demonstrates poor factoring and/or understanding of MVC.

ActiveRecord

• 4: Project makes good use of an advanced ActiveRecord concept not taught in class
• 3: Project demonstrates good use of ActiveRecord using no ruby to process data that could otherwise be done by the database
• 2: Project makes good use of ActiveRecord, but drops to ruby enumerables for some query methods.
• 1: Project frequently uses Ruby where ActiveRecord could be used, or fails to use ActiveRecord effectively