Showcase

Case 1: Monitoring student programmers (individual projects)

• Scenario: RepoSense is used to monitor a Software Engineering course in which students build a project over 8 weeks.

• Links: report | repo containing the settings

• Example usages:

  • To compare students based on the amount of code written, we can sort by contribution, as done in this view.
  • This view shows us code written by a specific student.

Case 2: Monitoring student programmers (team projects)

• Scenario: Similar to case 1 above, but this time students are doing team projects.

• Links: report | settings

• Example usages:

  • To find the breakdown of the work done, we can tick the breakdown by file type checkbox, as shown in this view. After that, we can filter out certain file types by un-ticking the file type.
  • To find how teams compare in terms of total work done, we can tick the merge all groups check-box and sort groups by Contribution, as seen in this view. Also, note how to reduce clutter.
  • This view shows the activities near the submission deadline of 8 November 2021 (note how some have overshot the deadline and some others show a frenzy of activities very near to the deadline).

Case 3: Monitoring student programmers (multiple external projects)

• Scenario: Similar to cases 1 and 2 above, but this time, each student works on multiple projects. Furthermore, most projects are external OSS projects, not within the control of the teacher.

• Links: report | settings

• Example usages:

  • This view shows the commit messages written by a specific student.
  • Note how we can use the group by drop-down to organize activities around projects or individual authors.
  • Similarly, we can use the merge all groups check-box to see the sum of activities in a specific project or by a specific student.