A syllabus is a document that outlines the key components of a course, including the topics to be covered, the schedule of classes, assessment methods, required materials, and other important information. It serves as a guide for both instructors and students to understand the expectations and structure of the course.
This is an advanced-level course where we apply practical programming (Python) to complex problems. Please note very complex problems do not always require complex solutions - but sometimes they do!
By the conclusion of this course, you will:
Your final grade is determined by completing two projects over the course of the year. Each project consists of 4 parts:
So there are a total of 8 summative assessments. This class follows the MYP design cycle.
You must bring a fully (or mostly) charged school-issued computer to this class. There will be electrical outlets so you can plug in your computers.
When you are asking a technical question it is important you ask it correctly. Please read and understand this very short guide how to ask a good technical question.
This course follows the policies at the American School of Warsaw. The URL to those policies can be found by clicking this url:
There are four broad rules in this classroom:
Academic integrity is an expectation of all members of our school community and is afforded the utmost value by all members of the faculty. The academic reputation of our students and the school in the wider community depend on it. Academic expectations extend to all assessed and non-assessed school work -- formative or summative -- and to all documentation produced for the university and college applications in High School.
It is the expectation at ASW that all work and documentation submitted by students is entirely their own.
Academic integrity means:
citing appropriately those whose work is used in the preparation of school work
completing school work without the input of others whose knowledge of the task might advantage the student unfairly
submitting work for assessment that is representative of the student’s own learning and not that of others, individually or collectively
maintaining a level of confidentiality and personal ownership of one’s own work, both assessed and non-assessed
adhering to ethical and honest practice during examinations and assessments
Academic Misconduct is behavior that contradicts the values and philosophy of academic integrity.
Student Academic Misconduct The IB defines student academic misconduct as “deliberate or inadvertent behavior that has the potential to result in the student, or anyone else, gaining an unfair advantage in one or more components of assessment.” It generally falls into one of the following categories:
Plagiarism: using or copying ideas or work that isn’t your own, without giving credit to the person or source
Collusion: copying or sharing work in situations when students are expected to work independently; includes helping others to plagiarize
Duplication: submitting the same work for more than one task (often in different subjects or years)
Misconduct Before, During, or After an Assessment: behavior that unfairly advantages a student during a test, exam, or in-class assessment; this is often referred to as “cheating”
Inclusion of inappropriate research or data: using data that has been collected unethically and/or using data that has been made up or changed
In addition, as per the Upper School Handbook, absence from any class for the purpose of preparing or studying for another class is not permitted. Skipping an assessment will be considered an act of academic dishonesty and treated as such. A student’s academic integrity will also be questioned if missing assessments or assignments becomes a pattern.
The full Academic Integrity Policy can be found at this link.
Week 1: Course Orientation
Week 2: Course Orientation
Week 3: Programming
Week 4: Programming
Week 5: Programming
Week 6: Programming
Week 7: Programming
Week 8: Programming
Week 9: Programming
Week 10: Programming
Week 11: Holiday
Week 12: Design: Developing Ideas
Week 13: Design: Developing Ideas
Week 14: Design: Creating the Solution
Week 15: Design: Creating the Solution
Week 16: Design: Creating the Solution
Week 17: Design: Creating the Solution
Week 18: Holiday
Week 19: Holiday
Week 20: Holiday
Week 21: Design: Creating the Solution
Week 22: Design: Creating the Solution
Week 23: Design: Creating the Solution
Week 24: Design: Creating the Solution
Week 25: Design: Creating the Solution
Week 26: Design: Creating the Solution
Week 27: Design: Creating the Solution
Week 28: Holiday
Week 29: Design: Understanding a Problem
Week 30: Design: Evaluation
Week 31: Design: Developing Ideas
Week 32: Design: Developing Ideas
Week 33: Design: Developing Ideas
Week 34: Design: Developing Ideas
Week 35: Design: Creating the Solution
Week 36: Design: Creating the Solution
Week 37: Holiday
Week 38: Design: Creating the Solution
Week 39: Design: Creating the Solution
Week 40: Design: Creating the Solution
Week 41: Design: Creating the Solution
Week 42: Programming
Week 43: Programming
Week 44: Programming