NTNU Norges teknisk-naturvitenskapelige universitet
  Fakultet for informasjonsteknologi, matematikk og elektroteknikk > Institutt for datateknikk og informasjonsvitenskap

IT2105 - Funksjonell Programmering, Høst 2006

Contents
  • Home

  • News

  • Schedules

  • Lectures

  • Curriculum

  • Assignments

  • Results

  • Grading

  • Mailing List

  • Lisp


  • Assignments

    Overview

    There will be 9 assignments (also called exercises or homework sets) — 6 regular and 3 advanced. For every exercise you will be given 1 week to send your solutions, unless stated otherwise. This year, the final 3 assignments will be components of a single, poker-player system.

    Determination of pass/fail on homeworks is based on a combination of quantitative facts (number of problems correctly answered) and qualitative issues, such as the style of one's code. Bad style will be penalized in cases where it deviates significantly from the concepts stressed in the course.

    All homeworks must be done and delivered individually (unless stated otherwise). You are free to discuss problems with your classmates, but keep the discussions at a high level. Each student must produce the working code themselves. Direct copying of homework answers will result in an immediate failing mark (F) for the entire course. This pertains to the copier as well as the source!

    Delivery Instructions

    Homeworks 1 to 6 will be handed out and should be delivered electronically via It`s Learning (accessible only from innsida).

    When delivering, all students must use the following naming convention:

    • h[assignment number]-[student number].scm.

    For example the deliverable of student 123456's first homework should be named as follows:

    • h1-123456.scm

    File contents

    Please take care of the following.

    • Include your student number and the number of the problem set in the header of the file. This will prevent mistakes if we need to make printed copies.
    • Include the numbers of the exercises so that it is clear which question each answer corresponds to.
    • Your code has to be easily readable and runnable.
    • If an exercise requires a comment or a textual answer rather than code, you should include it as a comment in the code file instead of writing a separate report file. In general, code files are preferred to formatted reports.
    • Unless otherwise mentioned in the exercise text, include at least three test cases and their results for each procedure in your delivery.

    Sample delivery

    File h1-123456.scm:

    ;; student 123456
    ;; problem set 2
    ;; (version 3 - yet another correction in 2.2)
    
    ;; 2.1
    ;; the procedure does truly do something but I can't guess, sorry
    ;;  maybe it divides 0 by 0
    
    ;; 2.2
    (define (recursion)
      ;; solves all problems by solving them
      (recursion))
    

    Results

    Results will be published in the "Results" section of the website. Your student number will be used to identify your score.


    Reservation of time for Project Demo

    About 20 students have delivered the first six assignments. Hoping that most of you work in pairs, I have made available 12 time slots to be reserved for a demo session. If there are no slots ready and you still want to register, please let us know as early as possible.

    Send me an email if you can't find an empty slot (hoversta<at>idi).

    The demos will be at Rill.

    Click on empty slots to select that time slot for you/your group.

    Wed, Nov 29: 10:00 : Halvard Amble

    Wed, Nov 29: 10:15 : Eskil Lauritsen, Mats Skillingstad

    Wed, Nov 29: 10:30 : Ulf Lilleengen, Ruben Spaans

    Wed, Nov 29: 10:45 : Tor Brede Vekterli

    Wed, Nov 29: 11:00 : John H. Anthony

    Wed, Nov 29: 11:15 : Sigurd Segtnan

    Redaktør: Kontorsjef Bård Kjos  Kontaktadresse: Boye A. Høverstad  Sist oppdatert: 24.11.2006