Syllabus

Course Description

From the catalog:

Covers key software development concepts and tools not in introductory courses. Concepts of lower-level programming (C/C++) and explicit memory management; techniques and tools for individual and group software development; design, implementation, and testing strategies. Intended for non-majors. Cannot be taken for credit if credit received for CSE 333. Prerequisite: CSE 143.

This is a very practical, skills-oriented course. The goal is to gain exposure to a wide variety of useful concepts and tools.

By the end, you will:

(Rough) Course outline

Grading and Exams

In principal, all homeworks contribute equally to the 60%, but larger programming projects will be weighed somewhat more than others. Percentages are tentative and may be adjusted.

Extra credit

Not doing extra credit will not lower your grade. The extra credit will not be worth as much as it should be based on how difficult it is, and will have no chance for partial credit. Extra credit isn’t valid unless the rest of the assignment is completed.

Late days

Deadlines are strict. For the entire quarter, you may have four free “late days”. You are strongly advised to save them for emergencies. You may not use more than two for the same assignment. On group projects you may only use late days if all members of the group have them available, and all members of the group will be charged for each late day used. They must be used in 24-hour (integer) chunks. This policy may not be the same as in your other classes. You are responsible for understanding it if you choose to submit late work.


Fine print details

Academic Conduct

We encourage collaboration, but there is a fine line between collaboration and cheating. We can learn from working with each other, but remember the goal is for YOU to learn the material so that YOU will be prepared for the exams, for job interviews, etc.

Cheating consists of sharing code or solutions to assignments by either copying, retyping, looking at, or supplying a copy of a file. Examples include:

Coaching a friend to arrive at a solution by simply following your instructions (i.e. no thinking involved). An example is helping a friend write a program line-by-line. Copying code from a similar course at another university or using solutions/code on the web, including GitHub. Communicating your solution with another student via electronic or non-electronic means.

You are responsible for understanding and applying the department’s Academic Misconduct Policy. If you are in doubt about what might constitute cheating, send the instructor an email describing the situation and we will be happy to clarify it for you.

Inclusion

Our code and our projects are made better by considering a variety of viewpoints. Your course staff is committed to the values outlined in department’s inclusiveness statement, and you are expected to uphold a supportive and inclusive learning environment.

If, at any point, you are made to feel uncomfortable, disrespected, or excluded by a staff member or fellow student, please report the incident so that we may address the issue. Should you feel uncomfortable bringing up an issue with a staff member directly, consider sending anonymous feedback or contacting the Office of the Ombud.

Disability Resources

The Disability Resources for Students (DRS) is a unit within the Division of Student Life and is dedicated to ensuring access and inclusion for all students with disabilities on the Seattle campus. They offer a wide range of services for students with disabilities that are individually designed and remove the need to reveal sensitive medical information to the course staff. If you have a medical need for accommodations, these will only be granted through official documentation from DRS. Browse to this link to start the process as soon as possible to avoid delays.

Religious Accommodations

Washington state law requires that UW develop a policy for accommodation of student absences or significant hardship due to reasons of faith or conscience, or for organized religious activities. The UW’s policy, including more information about how to request an accommodation, is available at Religious Accommodations Policy. Accommodations must be requested within the first two weeks of this course using the Religious Accommodations Request form.

Extenuating Circumstances

We recognize that our students come from varied backgrounds and can have widely-varying circumstances. If you have any unforeseen or extenuating circumstance that arise during the course, please do not hesitate to contact the instructor (eg, in office hours or via email) to discuss your situation. The sooner we are aware, the more easily these situations can be resolved.

Extenuating circumstances include work/school balance, familial responsibilities, military duties, unexpected travel, or anything else beyond your control that may negatively impact your performance in the class.