Welcoming Message

Welcome to CS108! This is the first CS course for those CS students who do not have much background in Computing. Even though you may have learned some programming language before, this course will help you further develop your computational thinking skills. This course is also required/recommended for other non-CS majors. So you will find students from various disciplines and different stages of study.

Underpinning our endeavor of learning problem-solving skills is the reformed Christian’s perspective. Learning this subject (and other subjects) is not just a way of meeting our needs or securing our future. As instructed from the book of Genesis, we are called to work (learning is a form of work) and to reflect God’s glory in what we do. It is therefore important to keep this mindset as we strive to improve our problem-solving and programming skills in this course.

Instructors

• Prof. Rocky Chang

  • Office: NH299A

  • Email: rocky.chang@calvin.edu

  • Office hours (Wed 16:00-17:00), or by appointment.

• Graders/Assistants:

  • Grader: Priscilla Chen and Edom Maru

  • Lab assistants: Hye Chan Lee (8:00) Samuel Ntadom (10:20)

Lectures, labs, and study sessions

We will meet in a classroom for the lectures and in SB354 for the labs. There are two lab sections (A and B). Please attend only your own section unless you get my prior permission.

1. Lectures: 08:00 MWF, SB382

2. Labs: 08:00-9:40 (section A) and 10:20-12:00 (section B) on Thu in SB354

3. Study sessions: 19:00–21:00, Mon and Thu in SB337

Communications

• Outside of classes, we’ll mainly use edstem for class communications. Please turn on notifications to ensure getting timely announcements. You could participate in this forum by

  • Posting questions and answers (but not providing your code) on assignments, concepts discussed in class, etc.

  • Posting notes on articles or events that are relevant and beneficial to this course.

• Go to see Rocky during office hours or make appointment by sending him an email.

Course objectives

This course introduces computing as 1) a way of solving problems using the Python programming language for implementation and 2) a way of living out our Christian faith in technology-dominated societies. Students who complete this course will demonstrate that they can:

1. (L1) Use an Integrated Development Environment (IDE), such as Thonny, to write and debug programs;

2. (L1) Explain how the basic Python constructs below work and use them in coding.

   1. Python built-in data types (numbers, strings, boolean, lists, tuples, dictionaries, and sets)

   2. Control structures (if, else),

   3. Iterations (for loop and whileloop),

   4. User-defined functions,

   5. Python classes and objects,

   6. String processing and text files,

   7. Modules (built-in and import) modules,

   8. Guizero for graphical user interfaces (GUIs), and

   9. Python’s exception handling;

3. (L2) Document code using best practices and document functions and modules using Python’s docstings;

4. (L2) Improve code readability through naming, structure, and others;

5. (L2) Debug programs by inserting debugging code or using debuggers;

6. (L2) Design test cases to validate the correctness of a program;

7. (L2) Identify the data present in a problem to be solved;

8. (L2) Identify the key tasks required to solve a problem;

9. (L2) Implement the data in the problem using Python’s built-in data types and/or user-defined data types;

10. (L2) Design and implement a Python function to perform a task;

11. (L2) Design and implement one or more classes for a problem;

12. (L2) Design and implement a correct algorithm to solve a problem;

13. (L3) Compare different algorithms for solving a problem from the perspectives of time complexity and space complexity;

14. (L3) Articulate the limitations of computing (non-computability, intractability, precision, etc);

15. (L4) Propose, design and implement a feasible and useful class project using what is learned inside and outside classes; and

16. (L4) Articulate how learning this subject is part of your faith journey.

We classify these student learning outcomes (SLOs) into four levels (L1 - L4) which are adapted from the Bloom’s Taxonomy. In our model:

1. (Concepts and skills) L1 corresponds to the Bloom’s levels on “understand and remember”. You will spend most of your time on accumulating enough programming concepts and skills on this level using the Python programming language.

2. (Problem solving) The next layer L2 corresponds to the “apply and analyze” levels in the Bloom’s taxonomy. An important focus of L2 is to identify the data in the problem to be solved and the tasks required to solve it. Another equally important one is to implement these data and tasks using what is learned in L1. Code documentation and code readability are also part of this layer.

3. (Evaluation) L3 corresponds to the “evaluate” layer in the Bloom’s taxonomy. This includes comparing different algorithms of solving a problem and understanding the limitations of computing.

4. (New creation) The highest level L4 is to create a new appto address an important problem and to understand how the learning of this subject is part of your spiritual formation.

Pre/Co-requisites for this course

CS 108 does not assume that you have any programming experience, but it does assume a background in basic mathematics. Contact Rocky if you have any questions about your preparedness for this course. On the other hand, if you think you have already learned most of the materials in this course and would like to skip it, please also contact Rocky him. The co-requisite of CS108 and CS108L.

Teaching approaches

To achieve the SLOs in the Course Objectives section, we will employ various in-class and outside-class activities, which include:

1. POGIL (Process Oriented Guided Inquiry Learning) — L1 + L2

2. zyBooks reading — L1 + L2

3. In-class quizzes — L1 + L2

4. Code reviews — L1 + L2

5. In-class exercises and problem sets — L1 + L2 + L3

6. Weekly lab — L1 + L2 + L3

7. Programming homework — L1 + L2 + L3

8. Midterm test — L1 + L2 + L3

9. Weekly devotion — L4

10. Perspectival homework — L4

11. Lectures — L1 + L2 + L3 + L4

12. Final project — L1 + L2 + L3 + L4

POGIL (the workbook in DOCXthe workbook in PDF) is a student-centered, group-learning instructional strategy and philosophy which is proven to be effective over traditional teaching approaches. Together with the zyBooks reading assignments, you will be able to attain some basic knowledge and skills required in the SLOs under L1 and L2 through self- and group-learning. Based on this foundation, other activities, such as quizzes and lectures, are needed to achieve the SLOs in L1 and L2.

The SLOs in L3, on the other hand, can be achieved by learn-by-practising (e.g., in lab and homework) and expositions through interactive lectures and in-class exercises. The midterm project is designed to have you apply what you have learned in the first 8 weeks to solve a “small” problem. The final project goes a step further into the L4 SLO on creating a new app. As for the spiritual formation SLO, it will be achieved through weekly devotions, lectures, and perspectival homework.

The weekly rhythm and tasks

Each week is devoted to one (and occasionally two) topic in the syllabus. In a full week (i.e., with no missing class),

• Mon: We will devote the first class of the week to weekly devotion and POGIL. Before that you should have finished the assigned zyBook reading. You and your group member will self-learn the basics in the unit. A short quiz on the lab or homework assignment (or other activities) covered the week before will also be given as a timely feedback to you.

• Wed: We will focus on consolidating and deepening what you have already learned through zyBook and POGIL, and prepare you for the lab next day which provides more complex problems for mastering the units for that week and the previous weeks.

• Thu: Lab - pair programming

• You cannot change your assigned section without my approval.

• If feasible, you will work in pairs during the lab exercises.

• When you work in a pair, each one of you will submit your work.

• Put down both of your names and usernames in your submission.

• Fri: We will conduct code review on the last programming homework and lab assignment you have submitted and reflect on what you have learned in that week. We will also cover more indepth materials, if time permits.

Tentative schedule

Table 1: A tentative teaching schedule. Not included are the deadlines for other assessments.

Week	Topic	Mon	Wed	Thu	Fri	Remarks
1	Introduction	-	Lecture	Lab1	Lecture,POGIL
2	Variables and expressions	POGIL,quiz	Lecture	Lab2	CodeRev,lecture
3	Data types	POGIL,quiz	Lecture	Lab3	CodeRev,lecture
4	Decision structures	POGIL,quiz	Lecture	Lab4	CodeRev,lecture
5	Iterations	POGIL,quiz	Lecture	Lab5	CodeRev,lecture
6	Functions	POGIL,quiz	Lecture	Lab6	CodeRev,lecture
7	Objects and classes	POGIL,quiz	Lecture	Lab7	CodeRev,lecture
8	Spring break	-	-	-	-
9	GUI and modules	POGIL,quiz	Lecture	Lab8	CodeRev,lecture
10	Lists, dictionaries and sets	Midterm test	Advising	Advising	TBD	Dr. Santos teaches lectures.
11	Strings and text files	TBD	TBD	Lab9	TBD	Dr. Santos teaches lectures.
12	Exception handling	TBD	TBD	Lab10	TBD	Dr. Santos teaches lectures.
13	TBD	TBD	TBD	Lab11	Easter	Dr. Santos teaches lectures.
14	TBD	Easter	TBD	No lab	TBD	Dr. Santos teaches lectures.
15	TBD	TBD	TBD	No lab	Study day	Dr. Santos teaches lectures.
16	Project showcase

Final project

The overall objective of the final project is to demonstrate that you are able to apply what you have learned in this course through this self-initiated project. In particular,

1. Acquire skills and experience of working on a Python project independently.

2. Apply sound methodologies and practices to solve problems.

3. Elevate your Python programming skills by engaging in a larger codebase.

Check out the final project document for the details. The project is made up of 5 milestones which could help you make steady progress in completing your project well. Due to the tight schedule, there will be no extension.

1. Project proposal: 10% (due at 23:59 on Mar 28)

2. Project progress report: 15% (due at 23:59 on Apr 11)

3. Code review: 20% (due at 23:59 on Apr 25)

4. Report and code submission: 50% (due at 23:59 on Apr 30)

5. Showcase in the lab: 5% (exam period)

Assessments

Assessment components

CS 108 and CS 108L (They share the same grade.)

1. 5% — Preparation assignments (zyBook reading)

2. 10% — Programming homework assignments

3. 15% — Quizzes (cannot be made up without legitimate reasons)

4. 10% — Perspectival assignments

5. 10% — Midterm test

6. 20% — Lab (Lab attendance is required. Failure of attending a lab without legitimate reasons will receive 0 marks.)

7. 30% — Final project

Note that there is no final exam. Instead, we will have a project showcase during the time allotted by the registrar for the final exam. The date and time corresponding to your section will be different from the normal weekly meeting times.

Deadlines

1. ZyBook reading assignments: Due at 9:00 on the first class day of the week (usually Mon)

2. Homework: Due on Tue at 23:59 (have ∼10 days to finish it)

3. Perspectival assignments: Due on Wed at 23:59

4. Lab: Due on the next day (i.e., Fri) at 23:59

5. Quizzes: Given on the first Mon of the week

6. Midterm test: Mar 17 (Mon)

7. Final project:

   • Proposal: Due on Mar 18 (Tue) at 23:59

   • Progress report: Due on Apr 1 (Tue) at 23:59

   • Code review: Due on Apr 15 (Tue) at 23:59

   • Report and code submission: Apr 26 (Sat) at 23:59

   • Showcase in the lab: The assigned exam period

Late work

• You have at most 5 days for late submission of any assignment. 10% will be deducted from the attained score per each day late. Late submission for 5 days or more will receive 0 marks.

• To be precise:

      if late < 24 hours:
          -10% of the attained score
      else if < 48 hours:
          -20% of the attained score
      else if < 72 hours:
          -30% of the attained score
      else if < 96 hours:
          -40% of the attained score
      else if < 120 hours:
          -50% of the attained score
      else:
          -100% of the attained score

Grade computations

1. zyBook reading: Each reading assignment carries the same weight, regardless of the actual marks given by zyBook’s auto-grading.

2. Programming homework: The full mark for each assignment is usually 40 marks.

3. Quizzes: The full mark for each quiz is usually 20 marks.

4. Perspectival assignments: The marking for each question is based on a 4-point scale (0 to 4). 4 points correspond to A, 2 points to C and 0 points to F. Other conversions are based on linear interpolation.

5. Lab: The full mark for each lab is generally different. Each lab carries the same weight.

6. Midterm test: TBD

7. Final project: The marking for each criterion is based on a 4-point scale. The point-to-mark conversion is the same as for the perspectival assignments.

The mark-to-grade mapping for determining the final grade is given in Table 2 which is the same as the one in the Moodle system.

Incompletes

We will give an incomplete grade (I) only in unusual circumstances, and only if those circumstances have been confirmed by the Student Life Office.

Textbook and other resources

Throughout the class, we’ll use the following platforms and tools:

1. edstem — for posting and answering questions on labs, homework and other relevant topics

2. Moodle (use 24/FA CS-108-A for both class A and B) — Teaching plan, slides, perspectival assignments and projects

3. zyBooks — Reading, lab and homework assignments.

   • The text will cost $89 and can be accessed as follows:

     1. Sign up at learn.zybooks.com. Note that you must use your Calvin e-mail address (e.g., xyz27@calvin.edu).

     2. Enter zyBooks code: CALVINCS108Spring2025.

     3. Click Subscribe.

   • Though the ZyBooks text is interactive, you do have the option to print a PDF version of each chapter, which can be useful as a reference after the zyBooks electronic submission has ended.

4. Activities for CS1 in Python, T. Shepherd, C. Mayfield and H. Hu, Creative Commons

5. Thonny 4.1.7 (Python 3.10.11)

Values and policies

Accommodation policy

Calvin University is committed to providing access to all students. If you are a student with a documented disability, please notify a disability coordinator in the Center for Student Success (located in Spoelhof College Center 360) to discuss necessary accommodations. If you have an accommodation memo, please come talk to Rocky in the first two weeks of class.

Academic integrity in computing

• Feel free to discuss ideas with us or with your classmates, but don’t copy code.

• You may reuse someone else’s code provided that you make it clear what code you are reusing and what code you write yourself.

• We’ll grade you on the code you write.

• Note that ChatGPT, Claude and other similar systems are NOT allowed in this introductory course for the reasons explained in the class.

Calvin’s general statement on academic integrity

The student-faculty relationship is based on trust and mutual respect, which can be seriously undermined by the suspicion or reality of academic dishonesty. Academic Dishonesty includes, but is not limited to, plagiarism (students plagiarize when they do not credit the sources of their writing - the words, information, ideas, or opinions of others), improper group work, reuse of a paper from another course and/or cheating on a test. Students are encouraged to speak to their faculty member with specific questions related to academic dishonesty. For further clarification or information, please visit this link.

Responsible use of technology

We expect you to abide by the guidelines expressed in the policies given in your institution’s technology policy (for students on campus, see Calvin’s Technology Policy Documents).

Diversity and inclusion

It is our intent that students from all backgrounds and perspectives are well served in this course. God delights in diversity; so will we in this course. If you or someone else is hurt by anything said or done in class, let us know so we can work toward a remedy.

Etiquette

We expect you to treat students and instructors for this course with respect by adopting courteous communication practices throughout the semester in all venues, including online forums. No personal attacks, trolling, or other kinds of bad language will be tolerated.