Time and Place:
Mondays, Wednesdays 3:00pm - 4:15pm in LSC 091
Instructor: Dr. R. McCloskey
Office: LSC 191
Telephone: 941-4221 (office),
941-7774 (CS Dept. office), 941-4250 (fax)
E-mail:
robert.mccloskey@scranton.edu
Course Web Page:
http://www.cs.scranton.edu/~mccloske/courses/cmps134/index_f22.html
Office Hours:
See schedule
CTLE:
Services for Students
Reporting Obligations
U of S Academic Code of Honesty
Textbook:
Building Java Programs: A Back to Basics Approach
(4th or 5th edition) by Stuart Reges and Marty Stepp,
published by Pearson.
(No MyLab (MyProgrammingLab?) code needed)
Exams and quizzes: Expect a 75-minute exam in late September and another one in early November. A comprehensive two-hour final exam will be administered sometime during Final Exam Week, which is December 13‐17. (Makeup exams will be offered only if circumstances warrant it, such as in the case of an emergency or sudden illness.)
A short quiz (taking about fifteen minutes) can be given during any class meeting, with or without prior warning.
Lab (CMPS 134L): Students are required to be registered for CMPS 134L, an associated Pass/Fail one-credit lab course that meets once per week for a 110-minute period.
In each lab meeting, students —typically working in pairs— will carry out activities and small assignments, some of which will result in artifacts to be submitted for grading. The work done in a lab will be marked as either absent, unsatisfactory, satisfactory, or noteworthy. To earn a Pass grade, a student's work must be marked either satisfactory or noteworthy in at least 75% of the scheduled labs.
Programming Assignments:
There will be approximately eight of them. Grades will be based upon not only correctness but also on subjective attributes such as quality of documentation and readability.
Submitted solutions must include comments that identify the student(s) submitting it (e.g., Chris Smith), the course and semester (in this case, CMPS 134, Fall 2022), the assignment number (e.g., Prog. Assg. #2), and a list of names of all persons who provided assistance in completing the work, including classmates, graduate assistants, tutors, and others. They should also include comments that point out any known flaws in the work.
As a general rule, work cannot be submitted more than 48 hours past the time that it is due. Consider those 48 hours to be a "grace period".
Students are allowed to collaborate with each other while working on assignments, but such collaboration is to be acknowledged, in writing, within the submitted work, as mentioned above. Collaboration should not go so far that it becomes untruthful for a student to claim that submitted work is, for the most part, his or her own. Under no circumstances is a student to copy the work of another or to allow another student to copy her/his work.
Grading: Approximate weights of graded items:
| Item | Approximate Weight |
|---|---|
| Semester Exams and Quizzes | 36% |
| Final Exam | 25% |
| Programming Assignments | 37% |
| Class Participation | 2% |
Mapping from numerical average to letter grade (approximate):
| Numeric Range | [94,100+] | [90,94) | [86,90] | [82,86) | [79,82] | [75,79) | [71,75] | [68,71) | [63,68] | [58,63) | [0,58) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Letter Grade | A | A- | B+ | B | B- | C+ | C | C- | D+ | D | F |
Intended Course Outcomes Upon completion of the course, a successful student will have the ability to do each of the following: