Course Syllabus

IMPORTANT NOTE:  All dates and policies contained in the CS 1810 syllabus and Canvas course are subject to change.  Students can expect to be informed immediately and clearly of any changes.

Critical Information

Instructor

Prof. Parker, 3144 MEB, erin.parker@utah.edu

Class meetings

Mondays and Wednesdays 11:50a-12:40p in WEB 1250

Lab sessions

Fridays 10:45-11:35a or 11:50-12:40p in WEB 1248

Attendance

Attendance is required at class meetings (Mondays and Wednesdays) and lab sessions (Friday).  Neither class meetings nor lab sessions are recorded.  Students who must miss due to illness or emergency should catch up by visiting TA help hours or instructor office hours (more information below).

Important dates

All exams are paper-based, administered in person, and may not be missed.

• Midterm 1 is Wednesday, February 12 during the class meeting.
• Midterm 2 is Wednesday, March 26 during the class meeting.
• Final Exam (cumulative) is Monday, April 28 10:30a-12:30p.

Final course grade

The final CS 1810 grade is comprised of exams 50%, assignments 35%, and labs 15%.

Communication

Course Information

CS 1810: Introduction to Computing Systems provides an elementary look at the systems and machinery that form the foundation of computing.  The course takes a bottom-up approach, tracing computation from bits to gates and the underlying structure of a computer to programming at the machine-, assembly-, and abstract language-level.

CS 1810 is a required course for students majoring in Software Development Links to an external site..  Students pursuing other majors should consult with the instructor or an academic advisor before continuing.

Learning objectives 

Upon completion of CS 1810, students are able to:

1. manipulate binary values and understand the consequences of the internal representation of numbers (including overflow and rounding error) and non-numeric data (such as characters)
2. express basic combinational Boolean logic as digital circuits and truth tables
3. describe the functional workings of a Von Neumann Architecture and write machine-language instructions for a basic Von Neumann Architecture simulation
4. compose simple programs in a RISC-like assembly language
5. implement elementary scientific solutions in a C-like programming language
6. summarize the levels of translation and tools that enable a program written in a high-level programming language to be executed on a computer
7. recognize the impact of memory accesses on program performance

Students can expect to achieve these outcomes only if they attend class meetings and lab sessions, as well as complete assignments, labs, and exams in good faith and on time.  Furthermore, students may vary in their competency level on these outcomes.

Course Materials

Website

The CS 1810 Canvas course is always under development, with updates to the class schedule, course notes, assignment specifications, and more, occurring regularly.  It is critical that students become familiar with the Canvas course right away and plan to visit it three times a week, at a minimum.

Textbook

There is no required textbook to purchase for CS 1810.  Reading is assigned from free, online sources.

Introduction to Computing Systems: From Bits & Gates to C/C++ by Yale Patt and Sanjay Patel is recommended for students who desire a deeper understanding of course concepts.

Course notes

The instructor often makes use of slides, sample source code and circuit diagrams, and other materials during class.  These items are posted to Canvas following the class meeting.

Laboratory practice

Lab sessions meet on Fridays to give students guided practice applying the concepts of CS 1810.  To avoid more participants than can be managed by the TA(s), students should regularly attend the lab section for which they are registered.  Infrequently attending a different lab section is allowed and need not be approved by the instructor.  Students should bring their own laptops or plan to borrow a laptop from the Marriott Library Links to an external site..

Personal computers

Students may use their own computers or ones borrowed from the library for completing assignments; however, broken tools or computers, or network connectivity issues are not sufficient basis for a deadline extension.  Plan ahead and use a campus lab computer if problems arise.

Student Evaluation

Assignments

The instructions for each assignment and its due date are posted on Canvas at least one week before it must be submitted. It is the student's responsibility to ensure the successful and timely submission of each assignment — start early and follow the instructions carefully.  Corrupted or missing files are not grounds for extensions — double-check your submissions and save a digital copy of all of your work in your College of Engineering account Links to an external site..  The timestamps of files outside of your College of Engineering account are not trusted.

Each assignment's deadline is followed by a one-day late period.  Late submissions are penalized 10%.  Note that 12a marks the start of a new day and -10%.

Exams

Midterm exams are to be given during class meetings on February 12 and March 26.  The final exam is cumulative and to be given 10:30a-12:30p April 28.  No exam may be taken at a different time for any reason other than a medical emergency or conflict with another exam, and documentation may be required.

Each student must bring their UCard (physical or mobile) to every exam, and they may be asked to show their UCard when turning in the exam.  All mobile UCards Links to an external site. must include a current and valid photo.  No other type of identification may be used for this purpose.

Labs sessions

Each lab is comprised of an instructor/TA-led activity and a paper worksheet, to be completed by students each Friday.

Regrades

Students desiring to appeal a score on an assignment, lab worksheet, or exam must do so via Gradescope.  All such appeals are due no later than one week after the score is published.

Letter grades

The following table is used to associate numerical scores with the corresponding letter grade.  Note the lack of rounding.

93 ≤ X ≤ 100 A 90 ≤ X < 93 A-

87 ≤ X < 90 B+ 83 ≤ X < 87 B 80 ≤ X < 83 B-

77 ≤ X < 80 C+ 73 ≤ X < 77 C 70 ≤ X < 73 C-

67 ≤ X < 70 D+ 63 ≤ X < 67 D 60 ≤ X < 63 D-

X < 60 E

Getting Help

To get help understanding course material, students may see the Teaching Assistant(s) during TA Help Hours, see the instructor during Office Hours, or post a question to Piazza.  To contact the course staff directly, use Piazza — use of the Canvas Inbox or email is discouraged for CS 1810 communications.  See the Instructions on how to get help page for details.

Policies and Guidelines

Laptop and mobile device policy

Students are expected to engage with the instructor and classmates during class meetings.  Laptops and mobile devices are permitted for note taking; however, research has shown that handwritten note taking is more beneficial to students than typed note taking¹.  All CS 1810 exams require students to handwrite solutions on paper, making handwritten note taking good practice.  Furthermore, laptops and mobile devices tempt students to multitask during class meetings, the success of which is wishful thinking for students who must focus in order to learn new and complex material.  For these reasons, students are discouraged from using laptops and mobile devices during class except when contributing to polling questions.

ADA statement

The University of Utah seeks to provide equal access to its programs, services and activities for people with disabilities.  If you need accommodations in the class, reasonable prior notice needs to be given to the Center for Disability & Access (https://disability.utah.eduLinks to an external site., 801-581-5020).  CDA will work with you and the instructor to make arrangements for accommodations. 

All written information in this course can be made available in alternative format with prior notification to the Center for Disability & Access.

Other polices and guidelines 

Students are bound by the following policies and guidelines:

• CS 1810 academic misconduct policy
• Kahlert School of Computing academic misconduct policy Links to an external site.
• Kahlert School of Computing policies and guidelines Links to an external site.
• Price College of Engineering guidelines Links to an external site.
• University of Utah Student Code Links to an external site.

Students should read and understand each of these documents, asking questions as needed.

¹Mueller, P. A. & Oppenheimer, D. M. (2014). The pen is mightier than the keyboard: Advantages of longhand over laptop note taking.  Psychological Science, 25(6), 1159-1168. doi:10.1177/0956797614524581.