TDDC60 Programming: Abstraction and Modelling

Examination

• LAB ASSIGNMENTS
• Lab Deadline Calendar & Documents
• Lab Assignment: Evaluation
• Lab Assignment: Delivery
• Lab Sessions
• QUIZZES

---

This course has 8 examinations: 5 required Lab Assignments and 3 Quizzes. The grading will follow this scheme:

On time with labs	Project	Quizz	Course
yes	VG	VG	5
yes	VG	G	4
yes	G	VG	4
yes	G	G	3
no	VG	VG	4
no	VG	G	3
no	G	VG	3
no	G	G	3

---

LAB ASSIGNMENTS

The Lab Assignments in a programming course are an opportunity for students to apply the techniques and concepts they have learned. In this course, we encourage regular delivery, quality work, and good effort.

There are 5 required Lab Assignments. It is very unlikely that students will be able to "keep up" with the course if they do not make regular progress on their programming skills. Therefore, each Lab Assignment has a deadline of kl. 18:00 on a Friday -- and students are expected to deliver a completed Lab Assignment by its deadline. In most cases, students will be notified if the Lab Assignment was acceptable or not by kl. 17:00 the following Monday; if a Lab Assignment was not acceptable, there will be information about how to fix it.

In practice this means completing one Lab Assignment (roughly) every other week. There are also optional Lab Assignments in the form of small projects (see the schedule below). These will be available during Quiz weeks and are a very good way for students to apply the various techniques covered. Note: in addition to reading SICP, these optional Lab Assignments are the best way to prepare for a Quiz during a Quiz week. It is not possible to submit the optional Lab Assignments through the PRAM delivery system; students who want feedback on this optional Lab Assignments should contact the Course Assistant directly. Students are not able to get any Delivery Points for the optional labs.

Lab Deadline Calendar

Below is a calendar of the Lab Assignment deadlines. Note that by Monday, October 30th, all labs must be successfully completed for you to receive credits for the lab course on time.

Week	Day	Date	Time	Content	SICP
35	Fri	1/9	18.00	Lab Assignment 01	1.1 - 1.2
36	(optional)			Lab 01a (optional)	1.3
37	Fri	15/9	18.00	02 Lab Assignment	2.1 - 2.3
38	(optional)			Lab 02a (optional)	2.4
39	Fri	29/9	18.00	Lab Assignment 03	3.1 - 3.2
41	Thu	12/10	18.00	Lab Assignment 04	3.2
41	(optional)			Lab 05 (optional)	3.3
44	Mon	30/10	18.00	All labs

Only two out of three lab sessions per week will be attended by a lab assistant. Check with your assistant if those sessions are not listed here.

• Y2A, Ola Leifler(pdf)

Obs! In order to get points/grades for this term, Lab Assignment 05 and all incomplete Lab Assignments must be submitted via the PRAM Delivery system by 18:00 hours Friday, October 13. If we require any additional revisions to Lab Assignments submitted by Friday, October 13, students will have until the following Friday (October 20) at 18:00 hours to complete and submit them.

---

Lab Assignment: Evaluation

Each Lab Assignment includes a specification of what needs to be done. In order to pass the course, all Lab Assignments need to be acceptable. In some cases there will be minor problems with a submitted Lab Assignment, in which case we will simply tell the team about the issue without requiring them to re-submit the Lab Assignment. If there are significant problems with a submitted Lab Assignment, we will provide information about what needs to be revised ("komplettering") -- and how the revision should happen (verbal presentation, re-submit Lab Assignment document, etc.).

Obs! It is important to understand that although there is a clearly defined specification for a Lab Assignment, there is also a "spirit of intent." For example, in many cases, there already exist Scheme libraries (or primitives) that will greatly reduce (or eliminate) the coding requirements of the Lab Assignment; using these would violate the spirit of the assignment. Therefore, our evaluations are just like the evaluations that occur in real life: they include elements that are subjective and personal. The evaluations are subjective in the sense that the evaluators have to make their own judgments about how well the result follows the "spirit of the assignment." The evaluations are personal because the evaluators are also trying to adapt the feedback and suggestions to the specific needs of different students.

---

Lab Assignment: Delivery

Students should submit their Lab Assignments through the PRAM Delivery System. In order to use the system, students must register themselves and their team-mates. Life will be much easier for everyone if students come and do this during the first scheduled Lab Session of the course.

If a student does not come to the first Lab Session, contact the Course Assistant for information about registering to use the PRAM Lab Delivery System.

Students register by logging into their LIU accounts and following the instructions after they type: 

~TDDC60/register

Students should then setup their accounts so that they have the proper directores and are able to run Dr. Scheme. Type the following:

~TDDC60/setup

This should make it possible for the student to run Dr. Scheme by simply typing (without quotes): "drscheme &"

It will also create the appropriate Lab sub-directories for the student. Please use these to store Lab files.

Students should submit their Lab Assignments by logging into their LIU accounts and following the instructions after they type:

~TDDC60/submit

Note that it is only possible to submit through the PRAM Delivery System if you are using a computer at IDA.

---

Lab Sessions: scheduled times for computer-rooms

On average, there are 2 scheduled Lab Sessions (LA) every week; these are times when specific computer-rooms are available to students in the course.

For some students, the 4 hours of scheduled computer-room time during the week may not be enough to complete a Lab Assignment. If students need more time, they need to make their own arrangements (work at home, find an available computer at LIU, etc.)

---

Quizzes

There will be 3 Quizzes (DU) during the the course; these occur (roughly) every other week on a Friday; please see course schedule for exact details. The final exam will be given Tuesday, December 19th. The exact location is yet to be determined but it will show in the general Web-based student exam calendar.

Week	Day	Date	Time	Quiz
36	Fri	8/9	8-10	1
38	Fri	22/9	8-10	2
41	Tue	10/10	10-12	3
51	Tue	19/12	8-12	Final exam, for those who didn't pass the quizzes

• Students will have 1 hour and 45 minutes (ie, Quizzes will begin at 15 minutes past the hour) to complete a Quiz.
• Students must take the Quizzes as individuals (ie, not in "pairs").
• OBS! All students must present a valid picture-ID when taking a quiz. Students who arrive without one will not be allowed to take the quiz. No exceptions.
• In most cases, students can expect to get back their graded quizzes by the Friday following the quiz.
• The quizzes will all include several kinds of typical situations that programmers encounter: determining what code will do (even if it has errors or seems "odd"); determining whether code will execute properly; identifying bugs in code and fixing them; turning a problem statement into well-written code; and diagramming different aspects of process evolution. Students can expect the quizzes to contain 8 problems related to the Lab Assignments, the relevant sections of SICP, and any additional topics indicated in the PRAM course documents.

Quizzes will not cover the following material from SICP:

• SICP sub-sections marked "Example" (or "Extended Exercise") that illustrate concepts, mechanisms, and techniques in the context of specific kinds of tasks or algorithms -- such as determining whether numbers are prime or building a program for algebraic manipulaton. These Example sub-sections are interesting in their own right -- and for students who are comfortable with (or want to learn) their subject matter, they can be very helpful. However, we do not expect students to study or know the details of the Example sub-sections. So, for example, we will not test students on the details of Huffman Encoding.
• SICP section 2.5
• SICP sections 3.3.3-3.5 (ie, anything in SICP after page 272)

Note also that although there is a reference to "message passing" in chapter 2, this topic will be covered in Quiz 3 (not Quiz 2).

---