Course OverviewCMSC 106 is an introduction to computing and program development in the C programming language. This includes a brief introduction to basic computer concepts, an understanding of the UNIX operating system sufficient for writing class programming assignments, studying the syntax and semantics of the basic control structures of C, learning C's fundamental data types and structures, understanding the design and methodical construction of computer programs, learning how to test and debug programs, and lastly, practice in these through creating several programs in C. See here to check the prerequisites and restrictions for this course.
The course Piazza page is your best source for getting course information. TA office hours, additional resources and essential course information will appear on Piazza, and all course-related questions will also be answered on Piazza to ensure all students have equal access to the information.
Course TopicsFollowing topics will be covered in this course (subject to change).
- Introduction to computer programming
- Basic program syntax
- Data types, declarations, expressions, variables
- Conditional statements
- Iteration statements
- User-defined functions, standard library functions, scope, call-by-reference
- Storage classes
- Arrays (single and two-dimensional arrays)
- Strings, character and string library functions
- Structures, structures as parameters, array of structures
- Instructor: Dr. Ilchul Yoon (Office: AVW3171)
- Semester period: August 27, 2018 - December 10, 2018
- Lecture hours: MW 2:00pm - 3:15pm (Room: CSI 3117)
- Discussion (Lab) hours: MW 5:00pm - 5:50pm (Room: CSI 1121)
- TA: Xuchen You, Jasraj Singh, and Jizhen Wang -- Check Piazza for the TA email addresses
- Title: C Programming, 2nd edition
- Author: K.N. King
- ISBN: 9780393979503
Clicker (or App)
Clicker questions will often be introduced in lectures. You can purchase the Clicker device at bookstore or you can install the Clicker app on your handheld device. The license is free. You can find out how to register here.
Additional Notes on Projects
- Deadlines - All projects are due at 11 pm on the specified day in the project description. You have until 11 pm of the next day to submit your project with a 10% penalty. Notice that after the late period, you will not receive any points for your project. For example, if a project is due on Wednesday at 11 pm, you have until Thursday at 11 pm to submit a late project with a 10% penalty (10% of the assigned points to the project, not your earned points). Any submission after Thursday 11 pm will receive 0 pts.
- Submit Server - You need to use the submit server for project submissions. We will not accept projects submitted otherwise (e.g., e-mail, etc.). Make sure that your project works in the submit server, otherwise you will not get any credit.
- Which Project Gets Graded - Your grade for an project will be based on the submission with the highest score after the late penalty (if any) has been applied.
- Good Faith Attempt - You must satisfy a minimum set of requirements for each project (Good Faith Attempt) otherwise you will not pass the course (automatic grade of F). Each project defines its own good faith attempt criteria and a deadline to provide an implementation that satisfies it. If you start a project on time, and look for assistance (if required) you should have no problems satisfying the Good Faith Attempt. The Good Faith Attempt guarantees you have at least the mimimum level of skills expected from this course. Notice that you will not receive extra points for completing the good faith attempt. The grade you obtain for a project will be based on your ontime/late submission.
- Closed Projects - All programming assignments in this course are to be written individually (unless explicitly indicated otherwise). Cooperation between students is a violation of the Code of Academic Integrity. Remember the purpose of projects is for you to learn the class material and do well in projects.
- Do not post your assignments' implementation online (e.g., GitHub) where they can be seen by others. Making your code accessible to others can lead to academic integrity violations. Even if the course is over, do not make your code available to others.
- As you work on a project, submit your project often even if you have not finished. We monitor submit server submissions and can provide assistance based on submit server results.
Note that academic dishonesty includes not only cheating, fabrication, and plagiarism, but also includes helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. In short, all submitted work must be your own.
Cases of academic dishonesty will be pursued to the fullest extent
possible as stipulated by the Office
of Student Conduct.
It is very important for you to be aware of the consequences of cheating, fabrication, facilitation, and plagiarism. If the student is found to be responsible of academic dishonesty, the typical sanction results in a special grade "XF", indicating that the course was failed due to academic dishonesty. If you have any doubt as to whether an act of yours might constitute academic dishonesty, please contact your TA or the course coordinator.
For more information on the Code of Academic Integrity or the Student Honor Council, please visit http://www.shc.umd.edu.
Examples of Academic Integrity Violations
The following are examples of academic integrity violations:
- Hardcoding of results in a project assignment. Hardcoding refers to attempting to make a program appear as if it works correctly (e.g., printing expected results for a test).
- Using any code available on the internet/web or any other source. For example, using code from Sourceforge.
- Hiring any online service to complete an assignment for you.
- Discussing project implementations (everything beyond clarifications) with your classmates.
- Sharing your code with any student.
- Providing ideas/suggestions on how to solve/implement a programming assignment.
- Looking at another student's code.
- Using online forums to ask for help regarding our assignments.
Additional information can be found in the sections titled "Academic Integrity" and "Code of Student Conduct" available at Course Related Policies.
Disabilities Support Accommodations
In case academic accommodations are needed, you must provide a letter of accommodation from the Office of Accessibility and Disability Services (ADS) within the first TWO weeks of the semester. For details, see the section titled "Accessibility" available at Course Related Policies.
Excused Absence and Academic Accommodations
The university allows for self-documentation for some absences. If you
need to be excused for an absence from a single lecture, recitation, or
lab due to your illness (or other reasons), you shall make a reasonable
attempt to report prior to the class. (Use the absence report feature in
the grade server).
Upon returning to the class, present with a self-signed note attesting to the date of your illness (or other reasons). Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(i) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.
Self-documentation may NOT be used for the midterm exams and the final exam, and it may only be used for only 1 class meeting (or more, if you choose) during the semester. Any student who needs to be excused for a prolonged absence (2 or more consecutive class meetings), or for the exams, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment and indicate the time frame that the student was unable to meet academic responsibilities. In addition, it must contain the name and phone number of the medical service provider to be used if verification is needed. No diagnostic information will ever be requested. Note that the "Medical Discharge Summary" from the Health Center will NOT be accepted as evidence of doctor's recommendation for your absence.
For additional details, see the section titled "Attendance, Absences, or Missed Assignments" available at Course Related Policies
The department and faculty take student feedback seriously. At the end of the course visit https://www.courseevalum.umd.edu/ to complete your course evaluations.
- Please bring your laptop to your discussion (lab) sessions and to lectures. If you don't have a laptop, we will pair you up with a classmate.
- If you are experiencing difficulties in keeping up with the academic demands of this course, you may contact the Learning Assistance Service located at 1101 Shoemaker Building.
- UMD Course related policies can be found at http://www.ugst.umd.edu/courserelatedpolicies.html
- Although every effort has been made to be complete and accurate, unforeseen circumstances arising during the semester could require the adjustment of any material given here. Consequently, given due notice to students, the instructor reserves the right to change any information on this syllabus or in other course materials.
All course materials are copyright UMCP, Department of Computer Science © 2018. All rights reserved. Students are permitted to use course materials for their own personal use only. Course materials may not be distributed publicly or provided to others (excepting other students in the course), in any way or format. Although every effort has been made to be complete and accurate, unforeseen circumstances arising during the semester could require the adjustment of any material given here. Consequently, given due notice to students, the instructor reserves the right to change any information on this syllabus or in other course materials.