Course of the lab course

 

  • There are a total of 9 assignments, which have to be submitted and talked about during submission sessions. Seven of those submission session will be during the lecture period, for the eight and ninth assignment there will be a seperate appointment afterwards. The ninth assignment is called "Bonusaufgabe" because for most students of the german lab course it is not mandatory. 
  • To pass the programming exercise all nine assignments need to be solved completely, correctly and on time. Absence without a valid excuse during the introductory or any other session will lead to failing the lab course.
  • The solutions for the assignment have to be presented on a computer, usually during the week after the release of the assignment.
  • The solution needs to be handed in on time (at the beginning of the submission session) and all features asked for in the assignment need to be implemented.
    If a group is not present at the beginning of the submission session or knowingly submits a (clearly) incomplete solution, the concerned assignment will count as not solved (which will lead to failing the lab course).
  • The solution should feature good programming style: modulation, neat interface, use of parameters, meaningful identiers, indentation, inline documentation (class and method description, explanatory comments, etc) and well-arranged program layout. It is not allowed to add/use additional static or non-static fields or public methods to a class apart from the ones specified in the assignment. Additional private methods are permitted. The given/specified data types have to be used, conversion from one type to another type is prohibited (e.g. conversion of a class to a string and then comparison of two strings, or converting a list to an array to continue working with the array). 
  • Are mistakes discovered during the submission talk of the solution and is the programming in other respects considerate and proper, then the solution for the assignment can be corrected once.
    If the mistakes were discovered during the latest submission date, then the solution may be corrected within an hour without any consequences. If additional time is needed, the corrected solution must be presented before the next submission session (a separate appointment will be arranged).  During the semester a group may only use additional time exceeding an hour to correct two different assignments.
    If the mistakes were discovered during an early submission date, the corrected solution has to be submitted before the latest submission date for the specific assignment. If the corrected solution still does not meet requirements, the assignment will be considered handed in at the latest submission date and the rules for that apply.

 

Questions

 

  • Questions can be posted into the FH Wedel newsgroup “fhw.ps2”.
  • The ITE master students taking the English PS2 lab course can ask also their question during the tutorial sessions. If a group still has trouble solving the assignment even after consulting with their fellow students, they can ask the supervisor via email or face-to-face for advice.
  • Every group is responsible for backing up their program/solution and any other files (have a look at the RZ-Ordnung).
    Note: In case the repositories cannot be reached, it is helpful to have an up-to-date copy of the solution on an usb stick. 

 

 Absence/Illness

 

  • The active participation during presentation of both team members is compulsory. If one team member is excused an not present the other one has to attend the submission session and present the group’s solution.
  • If a team member is ill for multiple days of the week and can account for it through a medical certificate, an individual submission date can be arranged for the group. For this the group needs to contact the lab course supervisor prior to the regular submission session.
  • If both team members of a group are absent with valid excuse (if possible the supervisor should be informed beforehand via email or face-to-face) the assignment may be solved and the solution presented subsequently. 

 

Copying/"Teamwork"

 

  • If identical (or very similar) code(fragments) included in the solution of two or more groups are discovered, or if groups are caught copying a solution, all those involved will excluded from the lab course (and fail it). Consequentially cooperation of groups should not include specific code. 
    Note: All groups need to make sure that their files are removed from the harddiscs of the RZ-computers (including from the trash).
  • Any publication (or disclosure) of a solution is prohibited. The illegemitate publication of the solution will lead to exclusion from the lab course. This concerns the current as well as all previous assignments (including those from previous semesters). 
    The prohibition applies especially concerning publication on the internet or any intranet.
  • An already passed assignment can be retrospectively denied, if an identical solution or very similar solution is handed in as well (see points above).