University of Denver Home Page University of Denver Home Page DU Department of Computer Science Home Page   Home Page for Catherine Durso  

Comp 1571, Fall 2005
Course Information and Syllabus

Course Calendar and Assignments


Instructor:

Catherine Durso
(email comp157x"AT"cs"DOT"du"DOT"edu)
Office: JGH 303, x13598
Office Hours: Tue. and Thurs. 11:00am-1:00pm

GTA:

Sada Narayanapa
(email comp157x"AT"cs"DOT"du"DOT"edu)
Office: JGH 320, x13316
Office Hours: Tue. and Thurs. 3:00pm-6:00pm


About This Course

In this course we study elements of procedural programming, including data types, flow of control, functions, arrays, pointers and strings, and file input and output.

You are will learn design skills, programming skills, and debugging skills. You will also improve your communication skills, including documenting your programs, listening to and speaking about technical material, and reading texts to learn information independently.

This is a demanding course that requires significant time and energy. It provides a basis for writing moderate-scale programs. Writing such programs is a skill almost universally required of people working in applied technical fields, so the effort you apply now will serve you greatly in the future.


Course Meeting Times

The lecture is held in CMK 309 at 2:00 on Mondays, Wednesdays and Fridays.


Required and Optional Resources


Grading

You will be evaluated based on weekly quizzes, homework assignments, programming projects, a midterm exam, and a final exam.

The quizzes will be given during the first five minutes of each Wednesday's class. They will be a quick closed book check on your awareness of the material covered the previous week.

Homework will be assigned and due approximately every two weeks. Please try the homework as soon as it is assigned. You'll be given an opportunity in class to ask questions about it.

Programming projects will be given about 4 times during the quarter.

There will be two exams in this course. The midterm exam will, tentatively, be given on Wednesday, October 19, in class. The cumulative final exam will be given on Saturday, November 19 from 2:00 to 3:45 p.m. in our regular classroom. This is the date determined by the registrar (see DU 2005 Fall Exam Schedule). Your enrollment in this class is a commitment to be available on that date.

Your attendance and class participation will be taken into account only in borderline cases.

The contributions of each type of work to your final grade are as follows:

evaluation typetotal percent contribution
Quizzes 10%
Homework 15%
Projects 25%
Midterm 25%
Final Exam 25%

Grading Policy:

Grade cut-offs are as follows: A (90 to 100 points), B (78 to 89 points), C (66 to 77 points), D (51 to 65), F (50 and less). Further curving may only improve your grade.

Late Policy: A 5/100 marks deduction penalty will be applied every 24 hours after the due date. In special circumstances the penalty may be revoked, but I reserve the right to do so.


Collaboration and Academic Honesty

When you turn in work in this course, you are implicitly agreeing that you have followed the rules for collaboration set forth for that assignment. You should not view in any way another person's assignment, nor should you possess electronic copies or hard copies of another person's assignment before that assignment has been graded and returned.

If you are stuck with a problem, you are strongly encouraged to seek help of the Instructor or the Teaching Assistant. Discussion of homework problems with your colleagues (other than your teammate when working in pairs) should be limited to what the problem requires and not how to solve it. You may not use or copy all or part of someone else's work. When using material from other sources or publications (including the Internet), you must understand, acknowledge and include a reference to them. Failure to do so will affect your grade adversely. Please make sure you have read and understood the information available in the following web page:DU Honor Code

Guidelines for Homework Assignments

A total of about 5 homework assignments will be handed out. These assignments are individual work and you must not consult with any of your colleagues, excepting the Instructor and the Teaching Assistant. You are encouraged to type your solutions. Handwriting is accepted as long as I find it to be readable, understandable and organized.

Homework assignments are due before midnight on the date specified in the assignment hand out (and course calendar). If you type your solutions, you must submit them electronically in either .TXT, .PDF or .DOC formats to the Teaching Assistant, cc-ing the Instructor. Please follow the following format for electronic homework assignment submissions and file naming: email your code as an attached file to the course account,

comp1571"AT"cs"DOT"du"DOT"edu,

and name your file

(Your last name/names)_Hwk(homework assignment number).c

Guidelines for Programming Assignments

Approximately four projects will be assigned. You may be required to work alone on some and in pairs on some. You might be asked to present your work in class. A project involves the design and a partial or total implementation of your solution to a given computational requirement. Projects are due at the time and date specified in the assignment hand out. All projects must be submitted electronically. Please follow the following format for electronic project assignment submissions and file naming: email your code as an attached file to the course account,

comp1571"AT"cs"DOT"du"DOT"edu,

and name your file

(Your last name/names)_Prj(Project assignment number).c

Your program must work correctly to receive credit. A program which does not compile will receive little credit. A program which works partially will receive partial credit. Your score improves if you attach notes documenting the incompleteness or bugs (include details of the circumstances under which they occur), since this shows the degree to which you tested your code.

Your program should be formatted logically, and should be easy to read.

Comment your code well - write comments that would be useful to someone who would have to debug, maintain or enhance your code. The quality of your comments is included in your grade.

Guidelines for Exams

Exams are given in class and are completely individual efforts. You may not give or receive assistance in any way. Feel free to ask me for clarification if you do not understand a question.


Course Calendar and Assignments

The calendar below contains links to homework assignments, programming projects, examples from class, and important dates for you to keep in mind.

Mon Tues Wed Thur Fri
Sept. 12
UNIX primer
Basic 1571 setup
Cygwin and Gvim download directions
Hello World


homework 1
secret_message


binary,hex,octal
Sept. 19


printf example
variables example
#define
scanf intro


homework 2
project 1
question 15 code
question 19 code
homework 1 due
Sept. 26


project 1, part 1 due
if example
while example
scanf loop


Oct. 3
for loop


homework 2 due
homework 3
project 1 executable



score example
example from class
function example
binary length
array example
bubble sort
Oct. 10


project 1, part 2 due


Oct. 17
project 2


homework 3 due


Oct. 24
in-class strings example

possible organization for
project 2

sample executable for project 2


homework 4
string example
Oct. 31
pass by reference
bar graph example, hint, hint





Nov.1

project 3
project 2 due
sizes of data types

file I/O with fprintf, fscanf
file I/O with fwrite, fread
Nov. 7
in-class 2-D array example


homework 4 due


Nov. 14
do...while() example
switch example
conditional example


project 3 due
function example

quiz 1
quiz 2
quiz 3
quiz 4

quiz 5
quiz 6
quiz 7
quiz 8
text file review

The cumulative final exam will be given on Saturday, November 19 from 2:00 to 3:45 p.m.


This page was last modified on: