Instructors

Cinda Heeren, Ph.D.
c-heeren@
2213 Siebel Center for Computer Science
Wade Fagen, Ph.D., Illinois '13
waf@
2215 Siebel Center for Computer Science

Course Assistants

  • Alec Mori
  • Corly Leung
  • Han Chen
  • Kelly Mack

All addresses are @illinois.edu

Course Description

Topics Covered

  • Programming
  • Data and Manipulation
    • Data Conversion
    • Data Manipulation
    • Data Analytics
  • Data Visualization
    • JSON data representation, d3.js

Languages and Tools

  • Python
  • JavaScript
  • git
  • Flask (Python)
  • d3.js

Grading

There is a total of 100 points available in this course that are earned throughout the semester. The distribution of the 100 points are as follows:


Course Grade

Your final course grade will be determined by the number of points you have based on the following scale:

Points Earned Final Grade Points Earned Final Grade Points Earned Final Grade
97+A+ 93-96.9A 90-92.9A-
87-89.9B+ 83-86.9B 80-82.9B-
77-79.9C+ 73-76.9C 70-72.9C-
67-69.9D+ 63-66.9D 60-62.9D-
0-59F

Academic Integrity

Cheating is taken very seriously in CS 205 and all cases of cheating will be brought to the University, your department, and your college. You should understand how academic integrity applies to Computer Science courses. Note that the recommended sanctions for cheating on a programming assignment includes a loss of all points for the assignment and that the final course grade is lowered by one whole letter grade.

You are a respected individual in a community of collegiality and trust. We honor and believe your word. We trust what you say and will generally not ask for proof. However, with trust comes responsibility. Violation of trust will not be tolerated. In particular, acts not befitting this community such as cheating (e.g., collaboration on homeworks or exams that are not meant to be collaborative) fall in the category of violation of trust. Individuals who commit such acts will lose the privileges of trust and receive grade reductions as described above.

With the exception of the in class work and the labs, your work in this class must be your own. Your work must be a result of individual work and you are responsible for protecting your work. In the past, we had cases of copying solutions from other students without their knowledge. To avoid having your work copied without your knowledge:

It is reasonable to to speak to others about the lecture, readings, or lab work. It is also reasonable to speak in broad terms about assignments and reasonable to share one or two lines of code from your program to have help finding a bug in your code.

However, do not share flow-charts, algorithms, "pseduo-code", or speak in technical terms about an assignment. Do not share code that is working. Do not send or post an entire function or a full program to a friend or publicly in any way. Do not copy a solution from the internet or a previous semester.