CSci 1001: Introduction to the Computing World -- Syllabus.

[Home] [Syllabus] [Assignments] [Resources]


The syllabus will be updated throughout the semester. Dates, topics, assigned reading, and problem set due dates will be added or might change. All changes in assigned reading and due dates will be announced in class (and occasionally by e-mail). While I will do my best to update the web site accordingly, it is a student's responsibility to keep track of the problem set due dates and reading assignments. If you are not sure about due dates, please don't hesitate to ask.

Reading assignments are listed for the day when the material is first explained in class. You may read ahead the material ahead of the lecture or after, either way is fine.

Policies on Collaboration and Use of Resources

Problem sets and labs are individual work, unless otherwise stated. While it's perfectly OK (and is encouraged) to discuss the problem sets in general terms with others in the class, your solution must be your own work. Copying any part of another person's solution (even if you modify the code) is considered academic dishonesty and will be dealt with according to the university's policy.

It is OK to use code found in a textbook or online, but such use must be credited (i.e. you have to state the exact source of the code and clearly explain how this code was used). Failure to credit the source constitutes academic dishonesty.

Using code samples from the book or from lecture notes as a starting point of your code is perfectly reasonable. However, using large chunks of code "as is" (with a proper credit) may significantly reduce your grade if your own contribution was small. If in doubt about what materials are appropriate to use and how, please ask the instructor.

Project work is done in groups. Members of the same group have free access to each other's code (and are encouraged to pair-program). Make sure to document contributions of each team member (in comments in the code or in a separate file). This will help me to properly grade your work in case the contributions of the team members where uneven. Communications with anyone outside of your group are limited to general discussion only, no code should be shared between groups.

Reading assignments

Reading assignments are posted for the day when the topic starts in class. The textbooks should also be used as a reference for problem sets and for project work.

Exams and quizzes

The exam dates are set. If you have an unavoidable time conflict with the exam time, please let me know right away. In addition to exams there will be 5-8 short in-class quizzes throughout the semester. Quizzes will be given in the beginning of a class meeting and will not be announced in advance. The lowest quiz grade will be dropped (i.e. not counted towards the quiz total).

Exams and quizzes are open book, open notes. You may use the text books, your own notes, and code samples that you find helpful. If you would like to use a different text book on the test, please let me know ahead of time (please bring a copy) and I'll let you know if it it's OK.

Course topics and timeline

Tuesday Thursday
Week 1: January 16 - 19
Introduction and course overview. Basic elements of a computer. Computer hardware and software.
Reading: Ch. 1.
Internet and the World Wide Web.
Week 2: January 22 - 26
Web pages: Internet protocols; XHTML and CSS
Reading: Ch. 2, 3, additional reading (see resources).
Web pages: XHTML and CSS
Problem set 1 posted: basic elements of a computer; XHTML and CSS. Due Thursday, February 8.
Week 3: January 29 - February 2
Lab on XHTML and CSS
Web pages: XHTML and CSS
Week 4: February 5 - 9
Introduction to Javascript.
Reading: Ch. 4.
Javascript data types, expressions, random number generator.
Reading: Ch. 5.
Problem set 1 due
Problem set 2 posted: Javascript. Due Thursday, February 22.
Week 5: February 12 - 16
Lab on Javascript.
Javascript conditionals.
Reading: Ch. 11.
Week 6: February 19 - 23
History of computers; view of the future.
Reading: Ch. 6, current events.
Javascript functions.
Reading: Ch. 7
Problem set 2 due
Problem set 3 posted: history of computers; Javascript functions. Due Thursday, March 8.
Week 7: February 26 - March 2
Algorithms and computability; programming languages.
Reading: Ch. 8.
Javascript strings.
Reading: Ch. 15.
Week 8: March 5 - March 9
Javascript input, forms.
Reading: Ch. 9, additional reading.
Basics of pair programming.
Computer data representation; binary and hexadecimal systems.
Reading: Ch. 12
Problem set 3 due
Problem set 4 posted: forms, handling input, form validation. Due Thursday, March 30.
March 12 - March 16: SPRING BREAK, NO CLASSES
Week 9: March 19 - 23
Review for the midterm.
Week 10: March 26 - 30
Javascript form validation.
Javascript loops and arrays.
Reading: Ch. 13, 17. Problem set 4 due
Problem set 5 posted: data representation; Javascript arrays, loops, events. Due Thursday, April 12.
Week 11: April 2 - 6
More Javascript events.
Reading: additional reading.
Lab on Javascript arrays, loops, events.
Week 12: April 9 - 13
The von Neumann architecture; elements of a computer (put together a computer?) Computer security; encryption, secure communications.
Reading: additional materials. Problem set 5 due
Problem set 6 posted: an XHTML/CSS/Javascript project; security and ethical issues in computing. Due Tuesday, May 1
Week 13: April 16 - 20
Ethical and legal issues related to computing.
Reading: Ch. 18, current events.
Ethical and legal issues related to computing.
Week 14: April 23 - 27
Robotics, programming a robot.
More on robotics.
Week 15: April 30 - May 4
More on robotics.
Problem set 6 due
Review for the final.
Wrap-up and discussion.
Final exam: 8:30-10:30 am, Tuesday, May 8

The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.