Computer Science 102 Spring 2023¶
- Name: Dr. Gregory M. Kapfhammer
- Office Location: Alden Hall 108
Instructor Office Hours¶
- Monday: 10:00 AM-11:00 AM, Alden Hall, 15 minute time slots
- Monday: 3:00 PM-4:00 PM, Alden Hall, 15 minute time slots
- Tuesday: 3:00 AM-4:00 AM, Alden Hall, 15 minute time slots
- Wednesday: 11:00 AM-12:00 noon, Alden Hall, 15 minute time slots
- Wednesday: 3:00 PM-5:00 PM, Alden Hall, 15 minute time slots
Scheduling Office Hours
To schedule a meeting with the course instructor during his office hours, please visit the schedule page of his web site and click the "Schedule an Appointment" link at the top of the page. Now you can schedule an appointment by clicking a suitable box in Google Calendar and then reserving an open time slot. At this point, the details about your chosen appointment will appear in both your Google Calendar and the instructor's Google Calendar. Please arrive five minutes in advance for your meeting and be aware that, by necessity, the meeting before yours may sometimes run late.
Course Meeting Schedule¶
- Discussion and Group Work Session: Monday and Wednesday, 9:00 AM-9:50 AM
- Programming Session: Friday, 9:00 AM-9:50 AM
- Laboratory Session: Friday, 2:30 PM-4:20 PM
An introduction to the foundations of computer science with an emphasis on understanding the abstract structures used to represent discrete objects. Participating in hands-on activities that often require teamwork, students learn the computational methods and logical principles that they need to create and manipulate discrete objects in a programming environment. Students also learn how to write, organize, and document a program's source code so that it is easily accessible to intended users of varied backgrounds. During a weekly laboratory session students use state-of-the-art technology to complete projects, reporting on their results through both written documents and oral presentations. Students are invited to use their own departmentally approved laptop in this course; a limited number of laptops are available for use during class and lab sessions. Prerequisite: Knowledge of elementary algebra.
- Prerequisite: CMPSC 100 or permission of the instructor.
- Distribution Requirements: QR, SP.
- Programming and Mathematical Thinking: A Gentle Introduction to Discrete Math Featuring Python by Allan M. Stavely
- Doing Math with Python: Using Programming to Explore Algebra, Statistics, and More by Amit Saha
- Week One: January 16 to January 20: Software Operation
- Week Two: January 23 to January 27: Making Connections
- Week Three: January 30 to February 3: Programming Constructs
- Week Four: February 6 to February 10: Python Functions
- Week Five: February 13 to February 17: Proactive Review
- Executable Examination One: February 17 during the laboratory session
- Week Six: February 20 to February 24: Data Containers
- Week Seven: February 27 to March 3: Using Monoids
- Week Eight: March 6 to March 10: Spring Break
- Week Nine: March 13 to March 17: Data Streams
- Week Ten: March 20 to March 24: Set Foundations
- Week Eleven: March 27 to March 31: Proactive Review
- Executable Examination Two: March 31 during the laboratory session
- Week Twelve: April 3 to April 7: Probability Functions
- Week Thirteen: April 10 to April 14: Mathematical Mappings
- Week Fourteen: April 17 to April 21: Object-Oriented Programming
- Week Fifteen: April 24 to April 28: Mathematical Objects
- Week Sixteen: May 1: Proactive Review
- Final Examination: Examination Code: A, Date: Thursday, May 4, 2023 at 9:00 AM
- Comprehensively covers all course modules
The grade that a student receives in this class will be based on the following categories. All of these percentages are approximate and, if the need to do so presents itself, it is possible for the course instructor to change the assigned percentages during the academic semester.
|Source Code Surveys||15%|
These grading categories have the following definitions:
Course Participation: Students are expected to regularly attend and actively participate in all class and laboratory sessions. After either an unexcused absence or a late attendance to a either a class or laboratory session on two separate occasions, a student's course participation grade will be reduced by half a percentage for each additional time they are absent or late in an unexcused fashion. Students who need to miss class or attend class late for an excused reason should communicate their situation to the course instructor as soon as possible. The content that a student commits to their GitHub repositories during the weeks devoted to proactive review are also a component of a student's grade for class participation.
Midterm Examinations: The midterms are online cumulative assessments covering all prior material from the class, programming, and laboratory sessions, as outlined on the course schedule. Unless prior arrangements are made with the instructor, all students should use their computer to take this test on the scheduled date and to complete it in the stated location while taking no more than the required amount of time. Each midterm is an executable examination that a student will complete through the use of GitHub, VS Code, and the programming tools installed on their laptops.
Final Examination: The final is an online cumulative assessment covering all of the material from the class, programming, and laboratory sessions, as outlined on the review sheet. Unless prior arrangements are made with the course instructor, all students will be expected to use their computer to take this test on the scheduled date and complete the test in the stated period of time.
Source Code Surveys: Graded on a checkmark basis and building on material in the textbook and the content covered during that week's in-person classroom sessions, source code surveys have the following goals: (i) help a learner to demonstrate that they can remember learned material by recalling facts, basic concepts, and answers to questions presented in the textbook and on the course web site and (ii) allow a learner to demonstrate an understanding of facts and ideas by translating, interpreting, and stating the main technical ideas presented through the textbook and course web site.
Programming Projects: Graded on a checkmark basis and building on material available in the textbook and the content covered during that week's in-person classroom session, the programming projects further equip a learner to solve new problems in the field of discrete structures by applying — in a new way — their knowledge of the both discrete mathematics and rigorous Python programming.
Engineering Efforts: These assignments invite students to explore different techniques for rigorously designing, implementing, evaluating, and documenting real-world Python programs. These assignments will invite students to use tools like a text editor, a terminal window, and a modern Python development environment to implement functions that strike the right balance between understandability, generalizability, and specialization. Students will also run experiments to evaluate the implementation of a program as they consider trade-offs in the efficiency and expressiveness of its implementation of a mathematical concept.
All assignments will have a stated due date shared through GitHub, GitHub Classroom, and Google Calendar. Electronic versions of the engineering efforts, programming projects, and source code surveys must be submitted to the instructor through a student's GitHub repository created by GitHub Classroom. No credit will be awarded for any course work that you submit to the incorrect GitHub repository. Unless special arrangements are made with the instructor, no work will be accepted after the published assignment deadline.
Using a report that the instructor shares with you through your assignment's GitHub repository, you will privately receive a grade for and feedback on each assignment. Your grade will be a function of whether or not you completed correct work that fulfills the project's specification and submitted it by the deadline.
It is mandatory for all students to attend the course sessions. If, due to extenuating circumstances, you will not be able to attend a session, then, whenever possible, please communicate with the instructor at least one day in advance to describe your situation. Students who have any signs of illness should not attend any in-person course sessions.
In order to minimize confusion and maximize learning, students must invest time to prepare for the class discussions, laboratory, and programming sessions. During the class periods, the course instructor will often pose challenging questions that could require group discussion, the creation of a Python program or data table, a vote on a thought-provoking issue, or an in-class presentation. Only those students who have prepared for class by reading the assigned material and reviewing the current course assignments will be able to effectively participate in these class discussions.
Importantly, only prepared students will be able to acquire the knowledge and skills that they need to be successful in this course, subsequent courses, and the field of web development. In order to help students remain organized and to effectively prepare for classes, the course instructor will maintain a class schedule with reading assignments and presentation slides, available at on this site. During the class sessions students will also be required to download, use, and modify web site components and data sets that are made available through means such as the course web site and a GitHub repository.
Students who are struggling to understand the knowledge and skills developed in either a class, laboratory, or programming session are encouraged to seek assistance from the course instructor and the student technical leaders. Students should, within the bounds of the Honor Code, ask and answer questions on the Slack workspace for our course; please request assistance from the instructor and student technical leaders first through Slack before sending an email. Students who need the course instructor's assistance must schedule a meeting through his web site and come to the virtual meeting with all of the details needed to discuss their question. Students can find out the office hour schedule student technical leaders by viewing the list of student technical leaders.
Using GitHub and Discord¶
This course will primarily use GitHub and Discord for all course communication, as summarized in the list of community connections. We will use GitHub for the sharing of both source code and course projects and for reporting issues in those materials. We will use two distinct Discord servers for all course discussions. The Proactive Programmers Discord Server provides a way for members of the proactive community to use text and video to chat with each other and will be the main forum for discussing technical content in data abstraction. The Allegheny College Computer Science Discord Server will be the main forum for Department of Computer Science announcements.
Although we will primarily use GitHub and Discord for class communication, the course instructor will sometimes use email to send announcements about important matters such as changes in the schedule. It is your responsibility to check your email at least once a day and to ensure that you can reliably send and receive emails. This class policy is based on the statement about the use of email that appears in The Compass, the College's student handbook; please see the instructor if you do not have this handbook.
The Academic Honor Program that governs the entire academic program at Allegheny College is described in the Allegheny Academic Bulletin. The Honor Program applies to all work that is submitted for academic credit or to meet non-credit requirements for graduation at Allegheny College. This includes all work assigned for this class (e.g., examinations and course assignments). All students who have enrolled in the College will work under the Honor Program. Each student who has matriculated at the College has acknowledged the following pledge:
I hereby recognize and pledge to fulfill my responsibilities, as defined in the Honor Code, and to maintain the integrity of both myself and the College community as a whole.
Computer science is an inherently collaborative discipline. People must work together to produce large, complex, and ultimately useful software systems. Because of this, the Department of Computer Science at Allegheny College encourages students to engage in collaboration. However, in the context of individual coursework, through which each student must demonstrate their own knowledge, there are certain forms of collaboration that are and are not acceptable.
Acceptable forms of collaboration include:
- Discussing high-level concepts, such as the use cases for
whileloops or the various methods that can add elements to a
- Referring someone to a course text book, course slides, example programs, or other resources that contain helpful information or instructions.
- Outlining the high-level steps to solving a problem or implementing a feature, without mentioning specific lines of code that need to be written.
- Discussing high-level concepts, such as the use cases for
Unacceptable forms of collaboration include:
- Sharing details about specific lines of code, including showing your source code to someone or looking at someone else's code.
- Copying someone else's source code, technical writing, program commands, or program output, even with some slight modifications.
- Typing source code, technical writing, or commands on someone else’s computer.
The aforementioned forms of communication are unacceptable because they make it difficult for both the course instructor and a learner to assess individual knowledge. Moreover, these unacceptable forms of collaboration can impede your learning or someone else's learning since an individual is less likely to understand source code or technical writing that they do not create by themself. Any student who participates in these unacceptable forms of collaboration, whether they are the one sharing, showing, looking, copying, or typing, are in violation of Allegheny College's Honor Code.
In summary, students should collaborate as long as they do so in acceptable ways. If a student needs assistance beyond what can be gained through acceptable forms of collaboration, they should seek help from the course instructor or a technical leader. If a student submits deliverables (e.g., source code or technical writing) that are nearly identical to the work of others, this will be taken as evidence of violating the Honor Code.
The Americans with Disabilities Act (ADA) is a federal anti-discrimination statute that provides comprehensive civil rights protection for persons with disabilities. Among other things, this legislation requires all students with disabilities be guaranteed a learning environment that provides for reasonable accommodation of their disabilities. Students with disabilities who believe they may need accommodations in this class are encouraged to contact Disability Services at 814-332-2898. Disability Services is part of the Learning Commons and is located in Pelletier Library. Please do this as soon as possible to ensure that approved accommodations are implemented in a timely fashion.
Referring to software, Frederick P. Brooks, Jr. wrote in chapter one of The Mythical Man Month, "The magic of myth and legend has come true in our time." Efficient Python programs that correctly use discrete structures to store and manipulate data have the potential to positively influence the lives of many people. Moreover, the design, implementation, evaluation, and documentation of Python-based software are exciting and rewarding activities! At the start of this class, I invite you to pursue, with great enthusiasm and vigor, this adventure in mathematics and Python programming.