Home

Introduction

Introduction

The Gophers team:

• Dmitri Lezama (Lead / Dev)
• Felicia Chan (Dev / Testing)
• Anderson Singh (Dev / Testing)
• Brandon Chandoo (Dev / Docs)
• Keshan Williams (Testing / Docs)

Project Scope and Purpose

The autograder performs the following:

• Accepts a zipped file with zero or more student submissions as zipped files
• Accepts zero or more .java files in a student submission
• Verifies if the required files are present
• Enforces the naming convention (FirstName_LastName_9DigitStudentID_A1.zip) onto each submission

• accepts incomplete submissions and provides 0 marks for any of the expected classes that are missing

Student submissions must strictly adhere to the naming format

FirstName_LastName_9DigitStudentID_A1.zip

For each valid submission, the student's first name, last name, and student ID are extracted directly from the file name.

Submissions that do not follow this exact naming convention will receive a grade of zero and throw an IllegalArgumentException when detected.

Submissions are expected to contain the .java and .class files in the root directory of the submission for the following classes:

• Chatbot
• ChatbotGenerator
• ChatbotPlatform
• ChatbotSimulation

If classes are missing or not in the root directory of the submission when extracted, the submission is awarded 0 marks for that class.

Submissions are awarded 0 marks if:

• The submission is not a .zip file
• The submission is empty
• The submission contains no .class or .java files
• All tests in the test suite fail

Evaluation Criteria

• Correctness: Verifies the functionality against predefined testcases, ensuring adherence to assignment specifications
• Performance: Measures execution of time and resource usage with limits to evaluate efficiency
• Feedback: Provides error details, failed cases and improvement suggestion
• Overall Score: Based on the successful tests in the test suite

Output Specification

• Generates a PDF report with the test case results, marks awarded, and detailed error feedback for each student submission
• The PDF is generated in the same output directory as the unzipped submission files
• The PDF report is clear, concise and presents room for improvement on the submission

| ← Home | Installation Guide→ |

Contents

Installation Guide Requirements and Use Cases Design Patterns and Adherence to SOLID Principles Grading Criteria and Rubric Phased Development Approach System Design Workflow for Submission Processing Testing and Evaluation