Assignments

CSCI 136
Fundamentals of Computer Science II
Spring 2022

Schedule | Assignments | Resources | Course Syllabus | Moodle

This page lists the anticipated programming assignments for the course. When an assignment is released, the assignment column will link to a detailed description of the assignment.

#	Due	Assignment	Collaboration
1	Tues. 1/18	Python Review	individual
2	Tues. 1/25	Python Review 2	Pair
3	Tues. 2/1	Stacks and Queues	individual
4	Tues. 2/8	Hash Maps	individual
5	Tues. 2/15	Recursion	individual
6	Tues. 3/1	OOP and Recursion	individual
7	Tues. 3/8	Threads	individual
8	Tues. 3/22	Regular Expressions	individual
9	Tues. 3/29	Fun with Linux	individual
10	Tues. 4/11	C++ Basics	individual
11	Tues. 4/19	C++ Memory Management	individual
12	Tues. 4/26	C++ Objects	individual

Due

Assignment

Collaboration

Tues. 1/18

Python Review

individual

Tues. 1/25

Python Review 2

Pair

Tues. 2/1

Stacks and Queues

individual

Tues. 2/8

Hash Maps

individual

Tues. 2/15

Recursion

individual

Tues. 3/1

OOP and Recursion

individual

Tues. 3/8

Threads

individual

Tues. 3/22

Regular Expressions

individual

Tues. 3/29

Fun with Linux

individual

Tues. 4/11

C++ Basics

individual

Tues. 4/19

C++ Memory Management

individual

Tues. 4/26

C++ Objects

individual

Submission. All assignments need to be submitted via Moodle. In the event of a Moodle failure, email your submission to me before the deadline. You should upload all the source files required by the assignment. You should also include any other source files which your programs depend on (things not in the standard Python library), and any image or sound files you use that were not provided to you. The top of every source file should include your name and a description of what the code does. All lab assignments must use appropriate documentation.

Deadline and late policy:

All assignments are due at 11:59AM on the stated date. Assignments arriving after 11:59AM are late.
Allow plenty of time to upload files, sometimes Moodle is slow.
Different: All assignments are due on time. After the due date/time is passed, 20% will be subtracted from your total if you turn it in before I download it. You will receive no grade if you turn it in after I have started downloading assignments. The time between the due date and when I download assignments is random, but I tend to do it the day after it is due, so you are taking your chances.

Grading. Your code will be graded on correctness, programming style (including comments), and efficiency. Partial credit is possible so if you run out of time, submit what you have. If you want to do well, start well in advance of the deadline. This allows time to seek help if you run into trouble. Software bugs can be difficult to find and are often easily found after a good night's sleep.

Collaboration policy. Programming is a creative process and no two programmers will solve the same problem in the same way. You are encouraged to discuss how to design a solution to a given problem with your classmates. But when it comes time to convert your design into code, you must write the code yourself. Be sure not to leave copies of your code where others might be able to access it (such as in the recycling bin of a lab computer). You may adapt code from the CSCI 136 course materials provided you cite what code you used in your program's comments.

Under no circumstances should you copy another person's code. Copying code from another student can result in an F in the course. A student providing code to another student is considered as guilty as the student copying it. Novices often mistakenly believe simple transformations can disguise a copied program. In actuality, copied programs often reveal themselves quite easily during grading. We can also use sophisticated software such as MOSS to detect plagiarized code.

Page last updated: April 29, 2022