Instructor: Rob Hasker (414-277-7326)
Drop-in times (office hours): See my home page: https://faculty-web.msoe.edu/hasker/
| Textbook: | Programming in C++ with zyLabs, F. Vahid and R. Lysecky, zyBooks, 2021, ISBN 979-8-203-95469-5 |
Course Description:
This course introduces students to the C and C++ programming languages. It relates the high-level computational model of these languages to their machine level execution, including details about number representation, a simplified view of microprocessor architecture. Students are introduced to the concepts of compilation, memory management, linking, efficient implementation of objects, and the Standard Template Library. The course contrasts type systems and other characteristics with those of other languages.
Note: students may receive credit for only one of CPE 2600 and CSC 2210.
Format: 4 lecture hours
Course Outcomes: On successful completion of this course, the student will be able to
Grading:
| Percentage | |||
|---|---|---|---|
| Structured Programming Assignments (SPA): | 30% | ||
| Readings: | 10% | ||
| Quizzes & exercises: | 10% | ||
| 2 Midterms: | 30% | ||
| Final Exam: | 20% | ||
| Total: | 100% |
The MSOE grading scale will be used, though higher grades may be awarded to individual students if it increases fairness. In addition, successfully demonstrating mastery of course outcomes is a prerequisite for a passing grade. This includes taking the final exam and, in some cases, completing assignments even if they are worth zero points.
Most materials will be available on my class web
site, https://faculty-web.msoe.edu/hasker/csc2210/
or in Canvas. For instance, quizzes will be in Canvas but links to notes
will be on the website. I will also communicate to the class on
Teams; it is critical you enable notifications for the Teams
entries for this class. Many announcements will be made that way and no
other. I may also use email at times. I expect you to check for electronic
communications at least once a day.
My office hours are listed as "drop-in" times to emphasize that you do not have to have an appointment to come see me. You can come other times as well! I am always glad to help students with challenges. I do expect you to have spent a few minutes checking for answers on the class website and Teams before requesting help, but absolutely would rather you ask for help than spend hours trying to find solutions on your own.
The first preference is face-to-face discussion. Always feel free to drop by my office with questions!! But if my office is not convenient (or it's the weekend), my general preference is to communicate through Teams. Email works, but generally the responses will be much slower. I also encourage you to post to the General channel for the course in Teams so other students can respond as well!
Most assignments will use esubmit. In most cases, the simplest and best way to get help is to submit to esubmit and then send me a Teams message with your questions. Be sure to tell me your code on esubmit is up-to-date so I do not have to start by asking if it is.
Lab solutions which do not run or which do not produce some correct output will be worth 0 points. However, you can get partial credit for partially working solutions. Estimate how long the lab will take, and contact your instructor if it takes much longer!
Unless otherwise announced, late solutions will be penalized 2% per day for up to 3 days. Because sometimes 3 days are not enough, students can use the More Time, Please! form to request 7 more days (for a total of 10 days). Note that penalties will continue to accrue over that time unless you have an adequate reason. You can document that reason on the form, but you might want to email your instructor to clarify such cases. See the form for additional policies; in particular, you can use this form for CSC 2210 just twice in a semester. Solutions submitted late (up to 3 days late without using the form and up to 10 days late with the form) are worth zero points. Unless you have written permission, all assignments must be submitted by the Saturday before the start of finals, including late assignments. Note that quizzes and exams have a due date and you will not be able to submit those after that due date (with or without the form). You can submit a late solution to any assignment with this policy; this includes reading assignments, programming assignments, and exercises.
All submitted work is expected to be consistent with the academic integrity guidance for CSC and SWE courses. This clarifies how the campus academic integrity policy applies to computing assignments including when citations are necessary. Generally, you can satisfy this policy simply by not copying code from other students into your projects and citing code you obtain online. You can help other students with their solutions, but do not help by showing them your code or writing code for them. Violations of this policy can result in penalties, typically a letter grade cut. Note that making a repository public enables cheating and violates campus policy. Electronic tools will be used to identify plagiarism, and students guilty of either copying or "loaning" out their code will be penalized.
Code will be graded for both correctness and meeting standards. The most frequent mistake is in using (hard) tab characters in source files - this is a practice that is strongly discouraged in industry, and it makes your code harder to grade. Configure your IDE to insert spaces instead of tabs.
If you are not using a private repository for your own assignments yet, it's time to start! A file on a single computer should be considered "lost" since machines frequently fail. You can create free, private repositories on BitBucket, GitHub, and other servers.
Missed quizzes cannot be made up, but at least one of the lowest quiz or exercise scores will be dropped. Many quizzes will be online with flexible times. Exams are in-person and scheduled during class time.
Do not skip class! If you do happen to miss, be sure to check for new materials and get the notes you missed from a friend before the next class period. You are responsible for anything missed! If you need to be excused for MSOE activities or religious observances, let me know in advance. If you're sick, it's obviously not a good idea to come to class. This includes days on which there are exams; just be sure to contact me as soon as you can get to a phone or computer.
Using phones and laptops during class to check social media or work on other assignments is a form of missing class!
Strongly consider taking hand-written notes for this class. The published notes omit many details on purpose. In many cases I will write code on the screen, and it is often much easier to track edits by hand than reproduce it with a keyboard. Note the campus printers will easily scan documents so you can organize your notes electronically.
Do not record or distribute video or audio of lectures without my permission.
When an exam is missed, I will determine whether to give you a make-up exam or increase the weight of the other exams. All students must take the final exam to receive a passing grade in the course unless the student has been excused in advance.
For students with documented disabilities, chronic medication conditions and mental health concerns: MSOE provides services to make reasonable accommodations available. If you are a student who requires or anticipates the need for accommodations, please contact Student Accessibility Services Office at 414-277-7281, by email at moureau@msoe.edu, or in person at K250 to discuss appropriate accommodations and eligibility requirements.