Skip to content

Latest commit

 

History

History
131 lines (105 loc) · 5.45 KB

rubric_text.md

File metadata and controls

131 lines (105 loc) · 5.45 KB
Raw

Little Shop Rubric

  • Evaluator:
  • Team repo:
  • Team Members:

Notes:

Rubric Explanation

Each rubric metric below is graded on a 4-point scale:

  1. Below Standard
  2. Approaching Standard
  3. Meets Standard
  4. Above Standard

Feature Completeness

  1. Below Standard
  • Fewer than 75% of the user stories are complete.
  1. Approaching Standard
  • 75% of user stories are complete, but not all of them are fully implemented
  1. Meets Standard
  • All user stories are complete.
  1. Above Standard
  • All user stories are complete and additional extension work was attempted.

MVC Responsibilities

  1. Below Standard
  • Views, Controllers, and Models do not have a clear sense of responsibilities.
  • Examples: Views are making calls to the model or making database calls. Controllers are handling calculations, making multiple database calls, or handling presentation logic.
  1. Approaching Standard
  • Views contain logic that make significant additional calls to the database including Model class methods.
  • Controllers do a significant amount of processing of data that should exist at a model level.
  • Models process data in a way that is inefficient, or contains work that determines presentation logic. (how data might get viewed)
  1. Meets Standard
  • Views make some calls to the database for .each calls and branch logic.
  • Controllers push almost all work to the Models for reading/ writing to the database.
  • Models sufficiently process and retrieve data.
  1. Above Standard
  • Views only display data and do not make additional calls to the database; they may include branch logic.
  • Controllers request all data from Models except .all or .find calls and only do .create and .delete methods for writing data.
  • Models read/write all other data using branch logic or smaller methods.

Routing and Namespacing

  1. Below Standard
  • Routing is incomplete. (ie. Missing necessary routes for functionality)
  1. Approaching Standard
  • Running rake routes shows some endpoints which do not have code implemented.
  1. Meets Standard
  • Routing and namespacing are used properly for the scope of the app.
  1. Above Standard
  • Routing limits exactly which routes should be exposed for the app and nothing more.

Testing

  1. Below Standard
  • Testing is below 75% or not done.
  1. Approaching Standard
  • Testing is above 75% and below 98%.
  • Tests are poorly written/unclear objective of the tests.
  • Hard coding values rather than using variables.
  1. Meets Standard
  • 98% or better test coverage for feature.
  • 100% for model tests.
  • Using variables as opposed to hard coding values.
  • Use of within blocks for targeted feature testing.
  1. Above Standard
  • Very clear testdriven development.
  • Test files are extremely well organized and nested.
  • Utilize before(:each) blocks for sharing test setups.
  • 100% test coverage for features, and 100% of all model methods are tested.

User Experience and Styling/Layout

  1. Below Standard
  • Little or no styling or layout.
  • User workflow is significantly problematic. (unclear what routes are available or how to use the application)
  1. Approaching Standard
  • Styling is poor/ incomplete.
  • Layout does not utilize good HTML patterns.
  • Incomplete navigation for routes. (must manually type URIs)
  1. Meets Standard
  • Purposeful styling pattern and HTML layout using the application.html. erb file and application.css file.
  • Links/Buttons to reach all areas of the site.
  1. Above Standard
  • Extremely well styled and purposeful layout.
  • Excellent color scheme and font usage.
  • Easy to use and follow the application workflow. (ie. Do not have to search for links/ buttons for navigation)
  • Utilizes additional tooling, such as SCSS.

Authentication, Authorization

  1. Below Standard
  • Authentication or Authorization was largely incomplete.
  • Storing passwords as strings and not using bcrypt.
  1. Approaching Standard
  • Authentication or Authorization are not implemented fully.
  • Users could impact data that they should not be permitted to access or change.
  1. Meets Standard
  • Authentication and Authorization are implemented with clear responsibilities of each user type.
  • Proper handling of all redirects if a type of user does not have proper access.
  1. Above Standard
  • All areas of permitted use within the app are above and beyond what we have taught.

Documentation and Work Flow

  1. Below Standard
  • No README file exists.
  • Team has not implemented any project management tool.
  1. Approaching Standard
  • README is poor quality. (ie. No organization or flow of information. Missing key elements, such as, how to setup the project, what the project is for, who the contributors are, etc. )
  • Team has not utilized an effective project management tool to a productive level. (ie. User stories are not fully broken down. Developers are not assigned cards. Cards are not being moved effectively)
  1. Meets Standard
  • Team README describes the application to a satisfactory level. (Includes setup, description, versioning, etc.)
  • Team has utilized a project management tool to track their work effectively and clearly.
  1. Above Standard
  • Team has built a robust README. (Including screenshots of the app)
  • The team has additionally used a project management tool that clearly shows an excellent workflow to be highly productive. (Such as automating promotion/ closing of stories as they are developed)
  • PRs also include discussions between reviewers about the code.