CS2023 -  Procedural Program Development Winter 2004

Course Objectives

• decompose a larger problem into smaller subproblems and design and implement functions to solve these subproblems,
• write clearly written C programs using any of the elements of ANSI C,
• use UNIX tools to develop multi-file C programs, and
• create reusable software modules by designing and implementing application programming interfaces in C

C for Java Programmers, Tomasz Muldner, Addison Wesley, 2000.
 

Instructor

Eric Aubanel
Office: GW-E108
Hours: When my door is open, or by appointment
E-mail: aubanel@unb.ca
 

Schedule

MWF 10:30 - 11:20 am
Room: HC11
 

Website

Additional information, including the assignments, is made available via the course web site:
www.cs.unb.ca/profs/aubanel/cs2023. Students are responsible for checking this site on a regular basis.
 

Lecture Notes

Lecture notes will be posted on the course website no later than one day before the relevant lecture. However, they are not a replacement for attending class, are not meant to stand on their own -  I will often add extra material in class.
 

Laboratory

You will have access to the Linux workstations in ITD415.
I will be scheduling one or more lab sessions, beginning with an introduction to compiling and running C programs in Linux early in the term.
 

Marking Scheme

Assignments	30%
Midterm	20%
Final Exam	50%

You must obtain a mark of 50% or more on the final exam in order to score higher than a 'D' in this course.
 

Assignments

Assignments must be completed in accordance with the course's C Language Coding Standard. As with earlier computer science courses, each assignment must have a cover page stapled to it. Submitted work must be your own. Please refer to section IX (Academic Offences) on page 49 of the 2003-2004 Undergraduate Calendar or online.

Students who disagree with their evaluation should resubmit their assignment to the instructor with a written explanation of the issue and a proposed remedy. Errors in addition should be reported directly to the instructor, in person, after class or by arrangment. For each assignment, two submitted assignments will be put on reserve in the Engineering Library with identifying information removed, illustrating what was expected (and accomplished) by class members.

Late assignments will be assessed for feedback, but no mark recorded, with the following exceptions:

• medical grounds
• compassionate grounds
• prior arrangments have been made with the instructor's approval

NO CALCULATORS will be allowed on the midterms OR the final exam. The midterms and the final exam will be CLOSED BOOK tests.

• The midterm exam will be held in class on Monday February 16, 10:30 am, in class. This date is firm, so do not schedule any other activities for this time. Make-up midterm exams will not be given; if the midterm exam is missed for good reason (e.g. if you provide a proper medical excuse), the weight of the midterm will be transferred to the final exam.
• The final exam will be scheduled by the Registrar's Office.

A computer account for the Linux workstations in ITD415 will be provided to each student. Email messages advising students of their accounts and initial passwords will be sent out early in the term. It is possible to use the computers in ITD415 remotely from any other computer connected to the Internet using telnet or secure shell (ssh).

Students may work on their own computers, but should do so in a UNIX/Linux environment (either installed directly on their computer, or accessed remotely via telnet or ssh). Putty (download here) is a good windows telnet/ssh client. Another option is to install Cygwin, a UNIX development environment for Windows. Both putty and Cygwin are free! Some of you may even have access to an Apple computer running a version of OS X, which is based on UNIX. However please note that electronically submitted programming assignments will be compiled and run on FCS Linux workstations, so it would be a good idea to test them here.
 

Course Topics

Lectures and assignments will be based on material from the course text and from other books which will be placed on reserve (see below). Topics may include:

• Introduction to UNIX: shells, pipes, redirection, useful UNIX tools, compiling, linking, and executing programs.
• Introduction to C: program structure, data types, control structures, functions, text files, C preprocessor.
• Modular programming: motivation for modularity, scope, linkage, and multifile programs.
• Program management tools: makefiles and source control
• Testing and debugging
• Intermediate C: pointers and memory management, strings, arrays, structures
• Design and implementation of C interfaces

The following books have been placed on reserve in the Engineering Library. The two C language books are there to complement the approach taken in the course textbook by Muldner, whereas the others contain material covered in class but not found in Muldner's book.

• The C Programming Language, Second Edition, Brian W. Kernighan and Dennis M. Ritchie, Prentice Hall, 1988.
• C Programming, a Modern Approach, K.N. King, Norton, 1996.
• The Practice of Programming, Brian W. Kernighan and Rob Pike, Addison Wesley, 1999.
• Code Complete, Steve McConnell, Microsoft Press, 1993.
• Managing Projects with Make, Andrew Oram and Steve Talbott, Oreilly, 1991
• Applying RCS and SCCS, by Don Bolinger and Tan Bronson, Oreilly, 1995
• Your UNIX, The Ultimate Guide, Sumitabha Das, McGraw-Hill, 2001