If from chapter 7 it must demonstrate some pointers, from chapter 8 we require classes and inheritance (with UML diagrams!), and from 9 the use input and/or output into named files.
[ schedule.html ]
must have comments that identify you, the project in the book, and what
you are doing!
Hand in UML diagrams for all classes you declare. You can draw these by hand on you code listings.
Make the code as simple and as clear as you can: Do the simplest thing that can possibly work first, and then use Don't repeat yourself to improve the code.
I want to be able to read your code and know what it does, and what it should do! Comments should explain anything complicated or buggy.
Our grading method is described in the CSci202 syllabus.
Hand in the code. No cover sheets, folders, etc. No test runs.
Print it out, staple it, and hand it in!
We will forgive some incomplete or buggy work as long as you explain what
You can resubmit this project if you got less than an A and more than an F (1..9 points)
the class after the grade work is returned.
Quizzes and Finals
Don't be surprised if a test requires you to recall what you
did when you wrote this project.
The CS202 syllabus has the rules, deadlines, and hints:
[ syllabus.html ]
. . . . . . . . . ( end of section CS202 Project 1 Requirements) <<Contents | End>>