Collaborative Software Engineering Project

Modern software development is not just about knowing the right programming language or the right technology stack. It is as important to know how to work together in a team to get a serious programming project done.

In this course, you will learn how to collaboratively create a software system. The contents of this course include learning about teamwork, interpreting requirements given by a client and breaking them down into actionable tasks, using popular collaboration tools like GitLab to plan and track project progress, using collaborative tools like Git, and learning popular frameworks and libraries to bring the project to success.

The first weeks of the course will be structured through lectures to get you and your group started, afterwards, the course will transition into the implementation phase, in which you will work on the project. Every group will be supervised by a TA.

This course has mandatory attendance starting from W2. Missing more than one meeting without a valid reason will result in a failing grade (not repairable!). The lecturers can grant exemptions if these reasons are raised proactively. In addition, weekly contributions to the team results are expected, which are part of the personal process grade.

The course has several pass/fail assignments, which must all be passed:

• Defining a code of conduct (repairable: R2)

• Conducting an effective meeting (individual, not repairable!)

• Providing constructive feedback with the AID model (individual, repairable: R2)

• Versioning source code in Git (individual, repairable: R2)

The final grade for students who pass these pass/fail assignments is then determined through the following assignments:

• Personal Process (10%, individual, repairable: R1)

• Tasks and Planning (25%, repairable: R1)

• Code contribution and code reviews (25%, repairable: R1)

• Implemented Features (25%, repairable: R2)

• Technology (15%, repairable: R2)

Partial grades are rounded to .1. The final grade is the weighted average of the partial grades and rounded to .5. To pass the course, each partial grade has to be >=5.0 and the final grade has to be >=6.0.

Any partial grade >=4.0 and <6.0 can be repaired, but the repair is capped at a 6.0. The repair method depends on the assignment (as indicated for every assignment).

• R1: Students will receive an individual assignment that involves planning, programming, and a code review. The assignment will take place over four fixed weeks in Q3 and will be assessed in an oral examination.

• R2: The original assignment can be resubmitted.

We may choose to assess students individually if we become aware of large performance differences in a team. In these cases, we will request a detailed list of all contributions from each team member to complement and elaborate the interaction traces that we find in the team repositories (e.g., contributions to the deliverables).

--- Please Note ---

• The full specification of the minimum criteria, deadlines and more information about the assessment will be posted on Brightspace.

• There is NO resit opportunity for this course.

• Partial grades are not carried over to the next academic year.

Disclaimer: information may change depending on unforeseen circumstances or measures (see: TER Art 29, sub 4)