---
# System prepended metadata

title: Autograder design thoughts (group 2)
tags: [ccss-summer-dev-projects]

---

# Autograder design thoughts (group 2)

###### 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 what courses I'm a part of
    - Log in
    - 
- Separate accounts
    - Current method uses unique identifiers for students
        - Current method gives you this link
        - Pat Morin's 2402 autograder allows you to input your student number and receive a 'secret key' in your email
        - Students might need to go back to their email to get the key again
        - This is easier for the current system since it relies on existing authentication
    - What would it look like to interface with the Carleton system?

- Student accounts
    - Should this just be on brightspace?
        - Each course might have their own autograder
            - You would find a link from the course
            - This can be for both students and professors, to remove the authentication process for autograder 
    - Should there 

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

### To consider

- What does creating a new assignment look like?
    - Want to be able to add some code
    - Want to be able to add files
    - Specify things about the assignment
        - Might want to add certain tests
    - What does authentication for this look like?
        - If we use the method of email codes to students, how does the prof get an authenticated account first?

- What does it look like when a prof sets this up for a course?
    - Want to import their class list
    - Assign each student from the class list a specific account and link that to their brightspace 

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

### To consider