Introduction to Programming II
Fall Semester, 2017
Continuation of object-centered design and implementation in C++. Building programs from modules. Data abstraction and classes to implement abstract data types. Static and dynamic memory allocation. Data structure implementation and algorithm efficiency. Lists, tables, stacks, and queues. Templates and generic programming.
The focus of the coures will be:
|Dr. Bill Punch|
|Office: 3147 Engineering||Office Hours: after class or by appointment|
|Phone: 517-353-3341||email: punch at msu dot edu|
|email is by far the best way to contact me|
Information related to the course is available on the Internet at:
Those files are also accessible from the CSE Instructional System under the
Discussion boards will also be on https://d2l.msu.edu
C++ Primer, 5th Ed. by Lippman, Lajoie,
Moo. ISBN-13:978-0321714114 . This is an optional
book, though very useful as a reference.
Mimir is a required element for the class. Much of your programming work will be turned in via Mimir. Lab 00 sets up for registering for Mimir.
Mimir gives you two weeks grace period before you are required to pay $25 for the semester. Mimir is a required registration for the course.
As of FS 17, CSE 232 has no lectures. Students attend a 1 hour recitation/laboratory session based on their Section number. There are also a set of students who even do the laboratory exercises strictly online.
The computing laboratory for CSE 232 is located in 3345 Engineering;
attendance at scheduled laboratory sessions is mandatory. Missing
laboratory sessions will reduce your final grade (see below).
The two-hour scheduled laboratory sessions are coordinated by Teaching Assistants, and are used to complete laboratory exercises and to consult with Teaching Assistants about other aspects of the course, e.g. projects.
The laboratory exercises are designed to be learning tools that complement the lectures and assigned readings. They are designed to be collaborative experiences where students work with each other and the Teaching Assistant to complete the lab exercises. Students who are habitually late will not receive credit when they arrive late to lab.
Each student's course grade will be based on the sum of the points earned in
the following categories:
|Examinations||(50% of total course points)|
|Computer Projects||(45% of total course points)|
|Exercises (in-class)||(5% of total course points)|
The following table gives the scale for course grades:
|4.0||90% of points available|
|3.5||85% of points available|
|3.0||80% of points available|
|2.5||75% of points available|
|2.0||70% of points available|
|1.5||65% of points available|
|1.0||60% of points available|
See: Academic Calendar 2017/18 for complete dates, but note that:
Two midterm examinations and a final examination will be conducted during
the semester, and will constitute 45% of the total course
points. These are a common night exam , see the schedule below.
You will be allowed one sheet of notes (8.5x11 inches) both sides,
but no electronic devices. Non-native English speakers may bring a paper dictionary.
For on-campus students these exams will be in-class exams held during the regular class times at the assigned lecture hall.
All issues related to the final examination will follow the policies and schedule of the University: MSU Final Exam Schedule.
Each week there will be one pre-lab exercise to warm you up for the week to come. These are online exercises. These exercises will not be graded, only marked on your reports as
Eleven computer projects will be assigned,
and will constitute 45% of the
total course points. The projects will include the design and
implementation of solutions using C++.
Project solutions are submitted electronically via
Computer Projects are to be done individually. Discussing problem-solving strategies with other students is encouraged, but as soon as the discussion turns to a particular implementation that must be done on your own.
Each project solution is electronically compared to all other solutions to identify similar solutions. Individuals that submit solutions that are essentially identical will receive a score of zero for that assignment, and will be reported to their Dean. A student who is involved in a second such incident of academic dishonesty will receive a grade of zero in the course. Since the comparison is done off campus, to protect your privacy do not include your name or PID in your project solution.
Under no circumstances should you share a project solution with another student. Simply showing your solution to another student almost guarantees a zero score: past experience shows that a student who asks to "look at" your solution will copy parts of it or pass it along to someone else who copies it.
The instructor reserves the right to modify course policies, the course
calendar, and assignment specifications.
Any extenuating circumstances that impact on your participation in the course should be discussed with your lecture instructor as soon as those circumstances are known (such as absences due to illness, religious observances, or other required school activities).
All students are expected to be responsible users of the computer system provided for this course. Account usage guidelines published by the Department of Computer Science and Engineering are posted under: Acceptable Use Policy