CSci 1101: Dynamic Web Programming -- Syllabus.

[Home] [Syllabus] [Assignments] [Resources] [Course blog]

Syllabus

The syllabus will be updated throughout the semester. Dates, topics, assigned reading, and problem set due dates will be added or might change. All changes in assigned reading and due dates will be announced in class (and occasionally by e-mail). While I will do my best to update the web site accordingly, it is a student's responsibility to keep track of the problem set due dates and reading assignments. If you are not sure about due dates, please don't hesitate to ask.

Reading assignments are listed for the day when the material is first explained in class. You may read the material ahead of the lecture or after, either way is fine.

Policies on Collaboration and Use of Resources

Problem sets and labs are individual work, unless otherwise stated. While it's perfectly OK (and is encouraged) to discuss the problem sets in general terms with others in the class, your solution must be your own work. Copying any part of another person's solution (even if you modify the code) is considered academic dishonesty and will be dealt with according to the university's policy.

It is OK to use code (html, css, php, and SQL) found in a textbook or online, but such use must be credited (i.e. you have to state the exact source of the code and clearly explain how this code was used). Failure to credit the source constitutes academic dishonesty.

You may, and often should, use code from lecture notes or samples from the book as a starting point of your code. However, using large chunks of code "as is" (even with a proper credit) may significantly reduce your grade if your own contribution was small. If in doubt about what materials are appropriate to use and how, please ask the instructor.

Project work is done in groups. Members of the same group have free access to each other's code (and are encouraged to pair-program). Make sure to document contributions of each team member (in comments in the code or in a separate file). This will help me to properly grade your work in case the contributions of the team members where uneven. Communications with anyone outside of your group are limited to general discussion only, no code should be shared between groups.

Assignment deadlines and late policies. Problem sets and labs are submitted by uploading them to the server. Do not change your work after the deadline: I check the last modification time to determine whether the work was submitted on time. For project assignments you also need to send me an e-mail when you are finished.

If you need cannot finish the work on time, please get in touch with me by e-mail. Generally your work will be subject to late penalty (see below), but I am open to discussion of extensions if you have made a good progress on your assignment and have a concrete timeline for finishing it.

If a problem set is submitted late, credit may be deducted: if it is submitted before the next class meeting after the due date, it is graded out of 3/4 credit. After that it is graded out of 1/2 credit.

Keeping up with assignments is extremely important for success in this class. Don't get stuck - ask questions! If you feel that you are falling behind, you should talk to me to come up with a strategy to catch up and allocate time to work on the material.

Reading assignments

Reading assignments are posted for the day when the topic starts in class. The textbooks should also be used as a reference for problem sets and for project work.

Exams

There will be two in-class exams in this course. The exam dates are set. If you have an unavoidable time conflict with the exam time, please let me know right away.

Exams are open book, open notes. You may use the text books, your own notes, and code samples that you find helpful. If you would like to use a different text book on the test, please let me know ahead of time (please bring a copy) and I'll let you know if it it's OK.

Reading abbreviations in the syllabus:

Course topics and timeline