Syllabus

Computer Programming 1

2016-2017 Syllabus

Contact Information

Instructor: Bethany Petr

Phone: 301-279-8577

Email:

Course Materials:

Course Description

This course introduces the basic principles of computer programming as well as fundamental computer science concepts, within the context of widely accepted programming languages. Topics covered include number systems and terminology, input and output via user interfaces, simple and structured data types, variables, control statements, functions, recursion, string manipulation, lists and matrices, file handling and classes. Emphasis is placed on developing effective problem-solving techniques through programming projects.

The software used in class isMicrosoft Visual Studio, which provides an integrated development environment which allows students to write code (in C++) with color-coded visual cues and provides a debugging environment to assist them in correcting errors. Students will submit the majority of assignments through Google Classroom and receive direct feedback via document comments in Google Classroom as well.

1 | Page

Syllabus

The Vision Guiding My Classroom

Students are actively engaged in their own learning. Students trust me to provide the support they need to discover an appreciation of technology and to bolster their growth as cooperative information seekers, users, and problem-solvers, versed in the skills needed to confront the explosion of technology in the world surrounding them. Students are comfortable being themselves and using their individual strengths to contribute to their own learning and the learning of their peers.

Grading

This course is considered Advanced Level by MCPS, and, as such, will provide a weighted grade.

Students will be graded on a weighted scale with the following components:

  • Homework for Completion/Practice (5%) - Shorter programs/problems/questions. Homework is to be completed independently. Collaborating on homework will result in a zero for the assignment.
  • Projects (45%) –Assessments completed during the course of instruction/development of the concepts for a specific unit. This category may consist of any/all of the following: questions, projects, problem sets, programs
  • Quizzes and Tests (50%) – Assessments conducted at the conclusion of a specific topic or unit. This category may consist of any/all of the following: quizzes, tests

Scores on Edline

It is your responsibility to monitor the scores you receive through Edline. If you perceive that an error has been made, you must bring it to my attention within one week of the score's entry in order for me to examine the issue. This one week period does not extend beyond the end of any marking period, however.

Acceptable and Unacceptable Collaboration

There will be many times when we work in pairs or small groups to generate collaborative solutions. In these cases, you will turn in a single piece of work for which each group member claims responsibility.

When an assignment is not specified to be completed in collaborative groups, the following rules apply:

The following rules are set forth by the University of Maryland Computer Science Department, and do a good job of describing what is considered cheating in computer programming.

Excerpt from:

The decision as to whether a student has cheated depends on the intent of an assignment, the ground rules specified by the instructor, and the behavior of the student. The following two guidelines help an instructor decide if cheating has occurred:

  • Program plagiarism will be suspected if an assignment that calls for independent development and implementation of a program results in two or more solutions so similar that one solution can be converted to the other(s) by a series of simple commands.
  • Cheating will be suspected if a student who completed an assignment cannot explain both the intricacies of the solution and the techniques used to generate that solution.

It is unreasonable to expect a complete definition that would cover all cases because each situation is important enough to merit careful, individual scrutiny; however, it is helpful to have guidelines and precedents. As a general rule, if you do not understand what you are handing in, you are probably cheating. If you have given somebody the answer, you are probably cheating. In order to help you draw the line, here are some examples of clear cases of cheating:

Examples of Cheating:

  • Turning in someone else's work, in whole or in part, as your own (with or without his/her knowledge).
  • Turning in a completely duplicated assignment.
  • Allowing another student to turn in your work as his/her own.
  • Allowing someone else to examine or copy your code or written assignment, either in draft or final form.
  • Reviewing files from another student or source, including retyping their files.
  • Several people writing one assignment and turning in multiple copies, all represented (implicitly or explicitly) as individual work.
  • Stealing an examination or solution from the instructor or course staff.
  • Copying from another student during an exam, quiz, or midterm. This includes receiving exam-related information from a
    student who has already taken the exam, or providing exam-related information to a student who has not yet taken the exam.

On the other hand, we encourage you to discuss the exercises with other students. But the discussion is limited to clarifying the assignments and sketching a general approaches to a solution. You should never look at another person's program to help you write yours, nor allow another student to look at your program. It isimportant that you do your own work so as to maximize your learning. Here are some examples of acceptable collaboration:

Examples of Not Cheating:

  • Turning in work done alone or with the help of the course's staff.
  • Getting or giving help about using the computers.
  • Getting or giving help about solving minor syntax errors.
  • High level discussions of course material for better understanding.
  • Discussing the code that we give out on the assignment.
  • Discussing the assignments to better understand them.
  • Providing assistance with the language, class library,and tools.

We will not condone cheating.

Due Dates/ Deadlines

  • Projects
  • The due date for projects is the last in-class day available for students to work. The time (i.e. end of day at 11:59pm or end of school day at 2:30) will be specified in Google Classroom for each particular assignment.
  • Students will not be given class time to work on projects after the due date and are expected to come in outside of class to work if they need more time to submit prior to the deadline.
  • Submitting a project after the due date but before the deadline will result in a 10% deduction.
  • Students who have spent any time working on coursework for a different class or otherwise using the class time provided on non-class tasks forfeit the right to turn in an assignment after the due date and forfeit the opportunity to work in any of our computer labs during non-class time.
  • Any project not submitted by the deadline will result in a score of zero.
  • Homework
  • The due date for homework is 7am on the day during which the assignment is due.
  • The deadline for homework is the same as the due date. No late homework will be accepted for credit. Any homework submitted after the due date/deadline will result in a score of zero.

Reteaching / Reassessment

Reteaching occurs when the teacher or student determines that students are not meeting learning goals. Reassessment opportunities are identified by the teacher before the original task/assessment and occur within an instructional unit. Only one reassessment opportunity is offered per task/assessment. Reassessment opportunities will be offered in every course. When tasks/assignments are reassessed, they may be reassessed partially, entirely, or in a different format, as determined by the teacher.

The following assessments/tasks that indicate a final measure of learning may not be reassessed:

  • End of course semester exams
  • Assessments that end an instructional unit or period of study
  • Final research papers, reports, or essays
  • Culminating projects or performances

When reassessment is offered, all students may be reassessed, regardless of grade on original task/assessment if they meet the following requirements: complete the original task or assessment, completed required assignments, and complete reteaching/relearning activities as determined by the teacher.

The reassessment grade replaces the original grade

Other Expectations

  • Students are expected to spend class time focused on the materials for this class. This includes materials found online.
  • This classroom is a place where all students should feel comfortable and secure. No hate speech of any kind will be tolerated.
  • Students are expected to attend class in a timely manner.

Absences

  • Students who are absent (excused) on the day of a quiz or test are expected to email or speak with me on the day they are absent or the morning before school when they return.
  • Students who are absent (excused) on a due date are expected to turn in an assignment the next day they are in school. If the student has missed several work days, s/he must email or speak with me on the day they are absent or the morning before school when they return to work out an amended due date.

Availability

I am available to stay after school by appointment made at least one day in advance (i.e. the day before) on Thursday. Please note: I don’t stick around if I don’t know a student is coming.

On days when I do not have a duty during lunch, find me for help (in 105 or the Tech Department office 109B).

I am also happy to answer questions sent via email if you are working on something while not in the lab with me.

1 | Page