Our First Brainstorming Results

Jump to bottom

Quinton Pryce edited this page Feb 15, 2017 · 1 revision

This is the list of ideas we generated during our first brainstorming session:

Similarity Checking

Open Source option
- What does it do?
- How can we interact with it?
- How long does it take?
File type – source vs binary – sanity checks
What to compare against
- Current course
- Past offerings
- Other courses
Who submitted it
- Resubmission
- Retaking course
- Reusing own code from previous course – permission
- Instructor code
Trends of same users submitting similar code often. – same pairs of students.
Flag users for past instances, consistently having high percentage of similairity.
How does this fit in the bigger system? “external system”?
- Interaction? Git hooks on submit to repo? REST API?
How does user see their result?
Notify instructor

Repository Management for Student Submissions

Security
Permissions of Users, Authentication to Server, Sessions (Time Duration)
Versions
Limits of versions
User Rollback Options
File Lifespan
When can we delete a users information? When they re-take the course?
Organisation
File Backups
Records sorted by:
tags, UID
Conflicts
How will we deal with a user re-taking a course?
Deletion options

Ideas were generally formulated from thinking about how we can make a web interface for GIT in a simple and usable way.

Instructor:

Create course request
Submissions
- View
- Download
Create subgroups (filters)
Make a request to remove a student (dropped out)
Log in
Create assignments/dropbox submissions
Configuration of submission requirements
- Language(s) used
- Coding conventions
- Timestamps (due dates)
- Late penalties
Set limits on the similarity checker
Student-chosen submission version
- Defaults to latest version submitted

Admin

Define accepted files
Create/remove(archive?) course
Remove students (dropped out)