Instructor

 Fangtian Zhong, email: fangtian.zhong@montana.edu, office hours: Mondays, Wednesdays and Fridays, 9:00am - 9:50am (not available during holiday/university day)

TAs

Necz, Andras, email: andras.necz@student.montana.edu, office hours: Wednesdays, 11am - 1pm

Lab Assistant

Sulzbacher, Nicholas, email:nicholas.sulzbacher@ecat1.montana.edu
Costello, Shane, email:shanecost2002@gmail.com

Announcement

Class codes: linklist.c and linklist1.c

Quiz11

Quiz11 will cover content on week13 and week14. Please review the codes and slides provided.

Course schedule

Date Lecture Topic (notes linked) Textbook Chapter Classwork Due/Quiz Lab Due
Week1        
Wednesday 08/21 Intro & syllabus / course slack   Classwork 1  
Friday 08/23 Course server; intro Linux and vim; classwork submission setup   Classwork 2  
Week2        
Monday 08/26 Intro to C; more Linux & vim, codes in class 2.1 Classwork 3  
Wednesday 08/28 Git and GitHub   Classwork 4  
Friday 08/30 More intro to C 2.1-2.6 Practice Quiz (ungraded) Lab 1
Week3        
Monday 09/02 No class      
Wednesday 09/04 Functions,codes:divide_conquer.c and print_area_circum.c 3.1-3.5 Classwork 5  
Friday 09/06 Functions, codes: abs and mathlib 3.1-3.5 quiz1 Lab 2
Week4        
Monday 09/09 Logical operators; if and switch statements;codes: test.c and if_statement and comparison.c 4.1-4.8 Classwork 6  
Wednesday 09/11 More logical operators; if and switch statements;codes: cal_tax and ship 4.1-4.8 Classwork 7 quiz2
Friday 09/13 Loops;codes:compound.c and do_while.c and forloop.c 5.1-5.8   Lab 3
Week5        
Monday 09/16 Loops;codes:factorial.c and sum.c and nested_loop.c 5 Classwork 8  
Wednesday 09/18 Conditional operator;codes:cond_operator.c and print_nums.c and read_nums.c redirection Appendix C-4, C-5 Classwork 9 quiz3
Friday 09/20 Arrays     Lab 4
Week6        
Monday 09/23 Arrays 7 Classwork 10  
Wednesday 09/25 Arrays as function arguments 7 Classwork 11 quiz4
Friday 09/27 Searching, sorting arrays 7   Lab 5
Week7        
Monday 09/30 Pointers; file i/o;codes:sizeofp.c and fpinout.c 6 Classwork 12  
Wednesday 10/02 Pointers;codes:nofile.c and nopointer.c and noarray and separatenum 6 Classwork 13  
Friday 10/04 More pointers 6 quiz5 Lab 6
Week8        
Monday 10/07 C type strings; 8 Classwork 14  
Wednesday 10/09 C type strings;codes: fgets.c and fgetsfile.c and scanf.c and strassign.c and strcat.c and token.c 8 Classwork 15  
Friday 10/11 C type strings;codes: pstr.c 8 quiz6 Lab 7
Week9        
Monday 10/14 Structs;codes:planet.c and student.c 10 Classwork 16  
Wednesday 10/16 Structs 10 Classwork 17  
Friday 10/18 Structs: codes:arraypointer.c and student.c and student.h. 10 quiz7 Lab 8
Week10        
Monday 10/21 Splitting C program into multiple files   Classwork 18  
Wednesday 10/23 Compilation review + Makefiles   Classwork 19  
Friday 10/25 Makefiles     Lab 9
Week11        
Monday 10/28 Command line arguments 12 Classwork 20;quiz 8 Mid-course survey
Wednesday 10/30 Sorting an array of pointers;codes:example.c   Classwork 21  
Friday 11/01 Pointer arithmetic   Classwork 22 Lab 10
Week12        
Monday 11/04 Dynamic memory allocation 13 Classwork 23 quiz9
Wednesday 11/06 Dynamic data structures (Linked List);codes: linklist.c and linklist1.c 13 Classwork 24  
Friday 11/08 Dynamic data structures (Linked List)     Lab 11
Week13        
Monday 11/11 No Class      
Wednesday 11/13 Dynamic data structures (Dynamic Arrays)   Classwork 25  
Friday 11/15 Dynamic data structures (Dynamic Arrays)   Classwork 26  
Week14        
Monday 11/18 Memory profiling with valgrind   Classwork 27  
Wednesday 11/20 Bit operators; binary and hexadecimal   Classwork 28  
Friday 11/22       Lab 12
Week15        
Monday 11/25 No Class      
Wednesday 11/27 No Class      
Friday 11/29 No Class      
Week16        
Monday 12/02 Bit masking   Classwork 29  
Wednesday 12/04 No Class (Self Study)     Lab 13
Friday 12/06     quiz12 (comprehensive)  

Catalog description

3 Credits. PREREQUISITE: CSCI 127. Programming knowledge. Introduces imperative programming and the C standard library. Course covers pointers, memory management and structures.

Course Info

This course meets for lectures on Mondays, Wednesdays, and Fridays from 8:00-8:50am in Leon Johnson Hall 346. The first 30 minutes of lecture will be spent learning new material, and the last 20 minutes will be spent on small programming assignments (or on short quizzes). We will use Slack as the primary method of course communication, and all course information will be posted on this website or on the Slack server; D2L will be used only for grading.

There is an optional lab on Fridays from 12:00pm to 4:00 pm in ROBERT 111 that you may attend to get extra help.

Note that this class is for Computer Science and Computer Engineering majors. If you are not one of those majors, you should take CSCI 109 instead of this course.

Course Resources

Textbook

The textbook is optional for this course, but is a good resource for anyone who is interested. Most classwork and lab programming assignments will come from the book, and lectures are based on the content in the book as well.

Problem Solving and Program Design in C, by Jeri R. Hanley & Elliot B. Koffman, Eighth Edition.

You can find free PDFs of the textbook online.

Linux server

We have a shared course server for you to develop, compile, and run your C programs on. Details for how to access the server can be found on the lecture 1 page.

Optional open lab and TAs

There is an optional lab on Fridays from 12:00 to 16:00 pm in ROBERT 111. Note that there is no lab during the first week of classes (Friday, August 23rd)! However, after this week, even when no lab is due, there will still be TAs in the lab to help you.

Instructor office hours

My office hours are 9:00am-9:50am on Mondays, Wednesdays and Fridays in the Barnard 352. You can also contact me on Slack to set up a different meeting time, and join the slack by the link, or drop by my office (Barnard 352) if my door is open. You can find office hours for all CS faculty here.

SmartyCats

There is SmartyCats tutoring for this course! Visit their website to find out more. You can also apply to be a SmartyCats tutor yourself for other CS courses you’ve taken, or for this one next semester.

Computer Science Success Center

There are free tutors available in Barnard 259. More information here.

Slack server

All course communication will be through our course Slack server. See D2L announcement for link. Please change your nickname to your full name (first and last). Additionally, I suggest managing your notification settings. You may also need to manage the application notification settings on your device.

Course outcomes

By the end of the course, students should be able to:

  • Navigate a Linux operating system using the command line.
  • Use vim to edit files.
  • Use git to version control their work.
  • Write code using C syntax.
  • Build computer programs using the C language.
  • Take advantage of major capabilities of the C language, including pointers, dynamic memory allocation and structs.
  • Apply the power of pointers, structs and strings to C programs.
  • Apply the programming knowledge you learned to solve basic real-world problems.

Grading

You will be graded on the following:

  • 29 classwork assignments (lowest five dropped): 20%
  • 13 labs (lowest two dropped): 40%
  • 12 in-class quizzes (lowest two dropped): 40%

Your grade will be determined by your total score as follows: 93+: A; 90+: A-; 87+: B+; 83+: B; 80+: B-; 77+: C+; 73+: C; 70+: C-; 67+: D+; 63: D; 60: D-.

Bonus

There are three ways to earn bonus points in this class.

Catch errors in course materials

If you find an error in any of the course materials (typo, incorrect statement, etc.), post in the #errors-in-course-material channel on Slack. I will decide whether it’s truly an error and not a duplicate. If it is really an error, you get a quarter of a point. Only the first person to post about an error gets the points. You can earn a max of 1 total point toward your 100 for the course (for four errors).

Additional work throughout the semester

Since five classworks, two labs and two quizzes are dropped, your work on dropped assignments may be counted as a bonus. You get:

  • 0.5 point for a score of 80% or more on any lab beyond your required 11, and
  • 0.1 point for any completed classwork beyond your required 24.
  • 0.5 point for a score of 80% or more on any quiz beyond your required 10

Course survey and evaluation

If 75% or more of the class completes the mid-semester course survey, the whole class gets 1 bonus point. Same goes for the course evaluation.

Late assignment policies

To run a course of this size we cannot accommodate individual requests for extensions on assignments; therefore, we have strict rules for when assignments are due, but have some leeway built in. Please read the bullet points below carefully, respect the policy, and get help early if you are having any problems. We want you to succeed!

  • You are responsible for any announcements about assignments made in class, on Slack, on D2L, and here on the course website.
  • All assignments are due on their due date by the Anywhere on Earth (AoE) timezone, which is 6 hours behind Bozeman (Actually, it’s only 5 hours behind during standard time, but we’ll go with 6 hours behind at all times). This means that the real due date is 6am the following day. If you submit labs and programs within 24 hours of the due date, you get 25% off of whatever score you earn. If you submit within two days of the due date you get 50% off. Otherwise, no points are possible.
  • You can submit as many times as you would like; only your last submission will be graded.
  • Classwork cannot be submitted late.

Missed quiz policy

Note that quizzes are taken in-class. Any conflicts with a quiz must be discussed with me prior to missing the quiz. I follow University policy on makeups, which allows that serious illness or a serious family emergency are valid reasons requiring an accommodation.

Collaboration policy

On all assignments, you may:

  • Share ideas with others.
  • Help others debug their code (or receive help debugging your code from someone else).

You may not (unless the assignment explicitly says you can):

  • Share your code with other people.
  • Submit code that you did not write.
  • Use generative AI (e.g., ChatGPT) to search for approaches or ideas to assigned coding problems.
  • Modify someone else’s solution and claim it as your own.
  • Post your own solutions on the internet.
  • Post the course assignments or quizzes on the internet.

Academic misconduct

In line with the MSU student code of conduct, if I or the teaching assistants suspect that you have committed academic misconduct, we will schedule a meeting with you to discuss. If, after the meeting, we believe that you did commit academic misconduct, you will receive a 0 on the assignment and I will submit a report to the Dean of Students. It’s just not worth it to cheat in this course.

Important dates

The last day to drop the course online (with no instructor or advisor approval) is September 4th. The last day to drop without a W grade (instructor or advisor approval required) is September 11th. The last day to drop with a W grade (instructor and advisor approval required) is November 13th. See the full add/drop schedule for more information.

Diversity statement

Montana State University’s campuses are committed to providing an environment that emphasizes the dignity and worth of every member of its community and that is free from harassment and discrimination based upon race, color, religion, national origin, creed, service in the uniformed services (as defined in state and federal law), veteran’s status, sex, age, political ideas, marital or family status, pregnancy, physical or mental disability, genetic information, gender identity, gender expression, or sexual orientation. Such an environment is necessary to a healthy learning, working, and living atmosphere because discrimination and harassment undermine human dignity and the positive connection among all people at our University. Acts of discrimination, harassment, sexual misconduct, dating violence, domestic violence, stalking, and retaliation will be addressed consistent with this policy.

Accommodations

If you have a documented disability for which you are or may be requesting an accommodation(s), please contact me and the Office of Disability Services as soon as possible.

How to succeed in this class

What you can do:

  • Keep up with the course by attending class, checking Slack, being aware of the course schedule, and doing all assignments on time.
  • Be an active participant in class. This means asking and answering questions in class and on Slack, seeking help when needed, and contacting the instructor or the course assistants using Slack if you have any questions outside of class time.
  • Be respectful of your classmates, your instructor, and the course assistants.
  • Do your own work.

What I can do:

  • Grade promptly (exact guarantees TBD).
  • Respond to all Slack messages and emails within one business day.
  • Create a course atmosphere conducive to learning by respecting all of my students and being enthusiastic about course material and my role in helping you learn.

This syllabus, course lectures and presentations, and any course materials provided throughout this term are protected by U.S. copyright laws. Students enrolled in the course may use them for their own research and educational purposes. However, reproducing, selling or otherwise distributing these materials without written permission of the copyright owner is expressly prohibited, including providing materials to commercial platforms such as Chegg or CourseHero. Doing so may constitute a violation of U.S. copyright law as well as MSU’s Code of Student Conduct.

Instructors are free to use this material in their own courses. Feel free to drop me a line if you do but no need.