Computer Science 1300
There are four different types of assignments for this course.
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.
Homework Assignments are typically pen-and-paper problems for reinforcement, and due at classtime on Thursdays.
Quizzes occur most Fridays.
Exams occur once during the semester and once during finals week.
Please make sure you understand the policy towards Academic Integrity.
Late quizzes and homework assignments are not accepted. Late programming assignments will be accepted, but with penalty in accordance with our Late Policy.
|prog01||Artist||11:59pm, Monday, 11 September 2017||individual||Art Show|
|prog02||DNA Reversal||11:59pm, Monday, 18 September 2017||pair|
|prog03||Backgammon||11:59pm, Tuesday, 26 September 2017||pair||soln|
|prog04||Programming Contest||11:59pm, Tuesday, 3 October 2017||individual|
|prog05||Interest Calculator||11:59pm, Monday, 16 October 2017||pair|
|prog06||Ball||11:59pm, Monday, 6 November 2017||individual|
|prog07||"Did you mean Billiken?"||11:59pm, Monday, 13 November 2017||pair|
|prog08||Animal||11:59pm, Tuesday, 21 November 2017||individual|
|prog09||Twitter Trends||11:59pm, Tuesday, 5 December 2017||pair|
|prog10||Disk Usage||11:59pm, Monday, 11 December 2017||individual|
|hw01||cs1graphics warmup||11:00am, Wednesday 6 September 2017||individual||soln|
|hw02||Using built-in types||11:00am, Wednesday, 13 September 2017||individual||soln|
|hw03||For loops||11:00am, Wednesday, 20 September 2017||individual||soln|
|hw04||Conditionals||11:00am, Wednesday, 27 September 2017||individual||soln|
|hw05||While Loops and Functions||11:00am, Wednesday, 4 October 2017||individual||soln|
|hw06||Error Checking and Exceptions||11:00am, Wednesday, 11 October 2017||individual||soln|
|hw07||Defining a Class||11:00am, Wednesday, 1 November 2017||individual||soln|
|hw08||Good Software Practices||11:00am, Wednesday, 8 November 2017||individual||soln|
|hw09||Inheritance||11:00am, Wednesday, 15 November 2017||individual||soln|
|hw10||Deeper Understanding||11:00am, Tuesday, 28 November 2017||individual||soln|
11:00am, Tuesday, 5 December 2017
|hw12||Recursion||11:00am, Friday, 8 December 2017||individual||soln|
|quiz01||cs1graphics||11:45am, Friday, 8 September 2017||soln|
|quiz02||Using built-in types||11:45am, Friday, 15 September 2017||soln|
|quiz03||Loops||11:45am, Friday, 22 September 2017||soln|
|quiz04||Conditionals||11:45am, Friday, 29 September 2017||soln|
|quiz05||While Loops + Functions||11:45am, Friday, 6 October 2017||soln|
|quiz06||Error Checking and Exceptions||11:45am, Friday, 13 October 2017||soln|
|quiz07||Defining a Class||11:45am, Friday, 3 November 2017||soln|
|quiz08||Good Software Practices||11:45am, Friday, 10 November 2017||soln|
|quiz09||Inheritance||11:45am, Friday, 17 November 2017||soln|
|quiz10||Deeper Understanding of Objects||11:45am, Friday, 1 December 2017||soln|
|quiz11||Dictionaries||11:45am, Friday, 8 December 2017||soln|
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:
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.