Examination Rules

 

You should read this entire page very carefully

The course will be evaluated by a project that is to be made by each student. However, next to this project, each student should make all the exercises which come along the course. Making the exercises is compulsory but the exercises as such are not graded. All files should be uploaded to your  private directory on the server located at \\sbesrv0016 which is accessible over the internet as: http://php.infonomics.nl.

The first week the you should practice by studying the book, going through the lecture sheets and making the exercises. The second week is devoted to the main project.

In order to pass the course, all exercises should be uploaded to the server.

  • All exercises should be uploaded before Monday, January 18 2010, 17.00 hours.
    (At this point in time, copies will be made of the entire web site and these copies will be used to check the requirements)

The project will be graded on functionality but also on style. So be aware to add comments and to use functions if appropriate. Don't make 'spaghetti code' (one file with hundreds of lines of code without clear structure). Note that only one project will be graded. If you make more than one project, indicate on your home page which project should be graded.

  • The project should be uploaded to the server before Monday, January 25 2010, so at Sunday at 23.59 the latest.

 

Rules:

1) All files should contain the name and id number of the student at the top the file. For instance, a html file should start with:

<!--First Name, last name, id number, date -->
<html>
<head>
</head>
<body>
</body>
</html>

2) All work, testing, coding etc. should be done on our server. It is not allowed to do this on another server and to copy the final result to our server. We will check whether your uploads show regular patterns and in case of doubt we hold the right to organise a meeting where you have to explain your coding. See also point 10.

3) Two students can work together (more is not allowed) on both the exercises and the project and thus hand in the same work. However, this cooperation should be mentioned in each file header and both students should upload all work under both accounts or upload the work to one account and create hypertext links from the other account to the actual work . Also note that both students should be able to explain how the scripts/programs work. See also point 10.

4) The index.html file in your private directory should link to all exercises and to the project. If you upload more than one project, the index file should also tell us what project has to be graded.

5) There is no resit for this skill straining.

6) Copying source code from other sources in the exercises is not allowed (except for the code given by the book or in the lectures. You always have to mention the fact some code is copied and that it is not your own work). See rule 8 on how to deal with copied code.

7) Copying source code in the project (from either fellow students, books, the internet or any other source) is allowed under the condition that it is not a substantial part (if you doubt, contact the staff) and under the condition that you indicate this clearly as pointed out in rule 9.

8) If some text/code is copied from other sources, e.g. from a fellow student or from the Internet, the copied part should be clearly indicated. For instance:

<!--First Name, last name, id number, date -->
<html>
<head>
</head>
<body>


<!-- the next part is copied from: http://www.php.com/filename-->

here comes the copied part

<!--end of copied part-->

</body>
</html>

9) If you copy code beyond these rules, you are excluded from the exam and will not have a second change. Again, in case of doubt, ask the staff.

10) We reserve the right to ask for a meeting to discuss the exercises and/or project, even after the course has finished, but within the standard limits of the examination period. The student should be able to explain the scripts/programs which are uploaded as parts of the coursework. Failure of this explanation can lead to a fail for the course. Note that we can track all uploads to our server and if this shows unregular patterns we hold the right to organise an oral discussion at the university premisses.