# Autograder design thoughts (group 4)

###### tags: `ccss-summer-dev-projects`

## When a student uses the platform, what should it look like?

### To consider

- As a student, I should be able to see the courses I'm in
- I should be able to see the different assignments in each course

- There should be a tutorial section showing students how to submit their code

- I should be able to submit and test only part of the assignment
- Assignments could be broken down into "milestones" where you have to complete a certain part first before moving on
- I should be able to add a tag showing what data structure I'm using on the submissions of each part, and compare the test feedback of different data structures used

- Possibly add best practices in coding submissions (i.e. commenting)
- I should be able to see what common mistakes are made so I can avoid them

- Option to paste the code, or import from desktop

- Login via student credientials

- My previous submissions' details (clean idea)

## What a prof uses the platform, what should it look like?

### To consider

- What does creating a new assignment look like?
- Tutorial/walkthrough in creating a new assignment on the platform

- Display of the class list

- to be able to make assignments for different classes, and have them organized separately

## When a student submits an assignment, what considerations should there be?

### To consider

- As a student, I should be able to see the time-efficiency in my submission (and the average time-efficiency among the class)
-
- I should be able to get feedback as to what's wrong with my submission
- Along with the feedback a professor could link resources or reference slides to aid the student's learning
-