Computer Science Project

In this course, students will use the knowledge gained during the first quarter of the minor to plan and work on a desktop application of their own choosing. This application must aid with or solve a problem. Students must plan the development of this tool themselves and special attention must be given to the prioritization of the different requirements.

Knock-out criteria

This course has a number of knock-out criteria. Requirements that if repeatedly not met will result in your removal from the course. These are needed for us to properly assess your contribution to your group project:

• There are mandatory TA meetings each week which allow us to monitor your process. If you miss more than one without providing a valid reason to course-staff within 24 hours, you will be removed from the course.

• To track whether all group members are putting in equal effort, we require you to use Gitlab issues to assign tasks and use its time-tracking feature to track how much work you are doing. If after a warning you still do not do this, we will remove you from the course.

• Everyone needs to work on code and testing. If we notice you did not write any tests or did not write any code at the end of the course we cannot give you a passing grade.

GRADES

The grade for this course consists of 4 components:

• Project plan (25%)

• Endterm presentation (15%)

• Process (30%)

• Product (30%)

You will hand in a draft of the project plan at the end of week 1 for feedback. At the end of week 2 you will have to hand in the final version for grading.

In week 6 you will have a midterm presentation about your project. This presentations serves as practice for the final presentation and as a moment we use to see how you are progressing. Your final endterm presentation at the end of the course will be graded.

After the project is over, we will grade your product and process. For this we will use any information stored on GitLab as well as information from your assigned TA about the weekly meetings. There will be opportunities to get feedback on these areas during the quarter.

Each component will be assessed using a published rubric and for each item in the rubrics you need to reach at least a minimum level and receive a 5.

These grades are normally determined at group level, but if we notice significant differences in contribution towards the project we might adjust the individual grades accordingly.

Repairs

If you do not get a passing grade the first time for a component you might be able to repair it. This is only a possibility if you received at least a 4 for the component initially. A repaired grade is capped at a 6.

The repairs are the following:

• Project plan: Submit an improved plan a week later

• Endterm presentation: Redo the presentation as soon as possible.

• Process and product: We cannot provide a repair for all items of these rubrics, if you receive a failing grade we will try to determine a repair option on a case-by-case basis to make sure you still meet the learning objectives.