Saint Louis University |
Computer Science 150
|
Dept. of Math & Computer Science |
There are four different types of assignments for this course.
Homework Assignments are typically pen-and-paper problems for reinforcement, and due at classtime.
Programming Assignments are larger programming projects that are to be completed outside of class and submitted electronically. General information about preparing and submitting the assignments can be found below.
Quizzes are the pen-and-paper problems that we give in class at the beginning of most Friday meetings.
Exams occur once before mid-semester and then during final's week.
Please make sure you understand the policy towards Academic Integrity.
Late assignments will be accepted, with penalty in accordance with our Late Policy.
The following table lists all assignments, ordered by due date.
| Assignment | Topic | Due | Collaboration Policy | Solutions |
|---|---|---|---|---|
| hw01 | Object-Oriented Design | individual | ||
| quiz01 | Object-Oriented Design | individual | soln | |
| quiz02 | Graphics | individual | soln | |
| prog01 | Artist | individual | ||
| hw02 | Using Python's Built-in Types | individual | soln | |
| quiz03 | Using Python's Built-in Types | individual | soln | |
| prog02 | DNA Reversal | pair | soln | |
| hw03 | For Loops | individual | soln | |
| quiz04 | For Loops | individual | soln | |
| prog03 | Checker Board | individual | soln | |
| hw04 | More Control Structures | individual | soln | |
| quiz05 | Conditionals | individual | soln | |
| prog04 | Programming Contest | individual | soln | |
| hw05 | Functions | individual | soln | |
| quiz06 | Functions | individual | soln | |
| hw06 | Functions and Exceptions | individual | soln | |
| quiz07 | More Functions | individual | see hw06 | |
| prog05 | Hangman | pair | ||
| hw07 | Defining Classes | individual | soln | |
| quiz08 | Class Definitions | individual | soln | |
| prog06 | Ball | individual | ||
| hw08 | Good Software Practices | individual | soln | |
| quiz09 | Good Software Practices | individual | soln | |
| prog07 | Spell Checker (Part I) | pair | ||
| hw09 | Inheritance | individual | soln | |
| quiz10 | Inheritance | individual | soln | |
| prog08 | Spell Checker (Part II) | pair | ||
| hw10 | Deeper Understanding | individual | soln | |
| quiz11 | Deeper Understanding | individual | soln | |
| prog09 | Animal | individual | ||
| hw11 | Recursion | 9:00am, Friday 23 April 2010 | individual | soln |
| quiz12 | Recursion | In class: Friday 23 April 2010 | individual | soln |
| quiz13 | Recursion | In class: Friday 30 April 2010 | individual | soln |
| prog10 | Boggle | 11:59pm, Sunday 2 May 2010 | pair |
For each assignment, you must submit all source code files that you have created or modified. For some assignments, we may provided you with a number of files containing source code or data that need not be modified. There is no need to resubmit such files.
You are required to submit a text file, ideally titled readme.txt, with every program you submit. Please do not submit any formatted files such as those produced by Microsoft Word or other word processors. It will be read at the time your program is graded, so it allows you to give helpful information.
The content of the file must include:
Your name
An estimate of the amount of time spent on the assignment.
A clear citation of any help you received on this program from other (approved!) sources, as detailed in the policy on Academic Integrity.
An overview of your program and any interesting design decisions that you made. Please include any other discussion that you feel will be helpful when grading your assignment. For example, if there are known bugs, briefly discuss them in this file.
Some of our program assignments explicitly require the inclusion of additional, specific information in this file. Please read the individual program assignments carefully.