CMPS 144
Computer Science II
Fall 2022

Time and Place:

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

Office Hours:  See schedule

Course Web Page:  http://www.cs.scranton.edu/~mccloske/courses/cmps144/index_f22.html
Textbook: None

U of S Academic Code of Honesty

CTLE: Services for Students

Reporting Obligations

Catalog Description:

CMPS 144 - Computer Science II, 3 credits
(Prerequisites: CMPS 134, CMPS 134L, and either MATH 114 or MATH 142; co-requisite: CMPS 144L)

This course emphasizes object-oriented software development, addressing both software engineering and programming. Topics include modularization, abstraction, encapsulation/information hiding, software reuse, software testing, classic data abstractions (e.g., lists, trees) and algorithms (e.g., sorting, searching), recursion, program correctness, and basic algorithm analysis.

Student Learning Outcomes

Upon completion of the course, a successful student will

Exams and quizzes:  Tentatively, there will be mid-term exams in early October and early November. A comprehensive two-hour final exam will be administered sometime during Final Exam Week (December 13‐17). (Makeup exams will be offered only if circumstances warrant it, such as in the case of an emergency or sudden illness.)

Expect a short quiz (taking about fifteen minutes) every two weeks or so.

Lab (CMPS 144L):   Students are required to be registered for CMPS 144L, an associated Pass/Fail one-credit lab course that meets once per week for a 110-minute period.

In each lab meeting, students working in pairs will carry out exercises 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 lab sessions.

Programming Assignments: 

Expect approximately seven of them. Grades will be based upon not only correctness but also on subjective attributes such as quality of comments, code formatting, modularity, 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 144, 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 describe any known flaws in your program's behavior. This is important, because not being aware of such flaws suggests that whatever testing you did was inadequate.

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" ending with a strict deadline.

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 (or that of his/her team, in the case of a team project). Under no circumstances is a student to copy the work of another or to allow another student to copy her/his work.

Grading: Weights of graded items (approximate):

ItemApproximate
Weight
Mid-term Exams30%
Quizzes8%
Final Exam24%
Programming Assignments36%
Class Participation2%

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