Assignments
The accompanying table indicates assignments and due dates for Computer
Science 213 and are subject to the following notes.
-
Unless otherwise indicated, textbook references are to Gary Nutt
Operating Systems: A Modern Perspective, Third Edition,
Addison-Wesley, 2004, ISBN: 0-201-77344-9.
-
Supplemental problems are stated later on
this page.
-
Unless otherwise stated,
-
collaboration IS NOT allowed on assignments either from the text or from
the supplemental problems, but
-
collaboration IS allowed on laboratory exercises.
-
you may use language references to determine relevant C syntax and
semantics. Since C syntax is standardized, we will consider C syntax and
semantics to be "general knowledge", and you need not cite your reference
sources.
-
you may consult only the textbook and the C syntax references for
information regarding alorigthms. All non-syntax consultations (including
the textbook and C references) require formal citation within the related
program or exercise.
-
You always may consult the instructor regarding questions on labs or
assignments (at least if the instructor is in his office with the door open).
-
Programs are to be submitted in the program format
given below.
Due Date | Collaboration Allowed | Chapter | Problems
|
|
Fri., Sept. 3 | Yes
|
| Lab. Exercise 1
|
Fri., Sept. 10 | Yes
| 2
| Lab. Exercise 2, Part A
|
Mon., Sept. 13 | Yes
| 2
| Lab. Exercise 2, Part B
|
Fri., Sept. 17 | Yes (Required)
| 5
| Lab. Exercise 3
|
Tues., Sept. 28 | Yes
| 6
| Lab. Exercise 4
|
Fri., Oct. 1 | Yes
| 7
| Lab. Exercise 5, Part A
|
Mon., Oct. 4 | Yes
| 7
| Lab. Exercise 5, Part B
|
Mon., Oct. 11 | Yes
| 8
| Lab. Exercise 6
|
Fri., Oct. 15 | Yes
| 9
| Lab. Exercise 7, Parts A and B
|
Tues., Oct. 26 | Yes
| 9
| Lab. Exercise 7, Part C
|
Fri., Oct. 29 | Yes
| 9
| Lab. Exercise 8
|
Fri., Nov. 5 | Yes (Required)
| 10-11
| Lab. Exercise 9, Part A
|
Mon., Nov. 8 | Yes (Required)
| 12-13
| Lab. Exercise 9, Part B
|
Fri., Nov. 19 | Yes
| --
| Lab. Exercise 10
|
Tues., Nov. 30 | Yes (Required)
| --
| Lab. Exercise 11
|
Tues., Dec. 7 | Yes
| --
| Algorithms in code or pseudocode for each
process within Lab. Exercise 12
|
Fri., Dec. 10 | Yes
| --
| Lab. Exercise 12
|
Submitting Programs For This Course:
In turning in any programs for the course, please follow these directions:
-
The first six lines of any C program should be comments containing
your name, your mailbox number, your lab section, and an identification
of assignment being solved. For example:
/**************************************
* Henry M. Walker *
* Box Science II *
* Laboratory Section 213L.04 *
* Assignment for Friday, September 1 *
**************************************/
Also, a comment is needed for every definition of a C function, stating in
English what that program unit is supposed to do.
-
Obtain a listing of your program and a record of relevant test runs using the
script command:
-
Within a terminal window (before running C), begin
recording session with the statement
script filename
where filename is the name of the file in which you want the session
stored.
-
Within the script file,
-
Print a copy of your program with the command
cat C-file.c
where C-file.c is the name of the file containing
your C program.
-
If your work involves several files, list the main
program first with the cat command; then list any supplementary
files.
-
Compile your program with the gcc command, and run it with
appropriate test cases to check the correctness of your program.
-
When your runs are complete, stop the script session by typing
<Ctrl/D>.
- Print the record of your session by typing
lpr filename
-
Either write on your printout or include a separate statement that argues
why your program is correct, based upon the evidence from your test runs.
Some Grading Notes:
This document is available on the World Wide Web as
http://www.walker.cs.grinnell.edu/courses/213.fa-04/assignments.shtml