|CPSC 329||Software Development||Fall 2016|
You are expected to be familiar with the course policies stated below. Ignorance of a policy is not an excuse for violating a policy or being surprised when it is applied to you, and will not exempt you from its penalties.
On this page:
You are expected to regularly check your HWS email and the course web page (especially the syllabus page). Assignments, handouts, and other information relevant to the class as a whole will be posted on the course web page. Email will be used in the case of a particularly time-sensitive announcement (e.g. an announcement about a homework which is due in the next class meeting) or for matters which are only relevant to a few people in the class.
You are expected to be on task during class - web surfing, texting, playing games, doing assignments for other courses, etc. are not acceptable. Except in the case of an emergency, leaving the classroom during class is not acceptable. (Take care of any necessary business before or after class!) Also, please do not use headphones during lab - you may miss important announcements to the class about assignments, and it makes it difficult to interact with you about the assignment.
|Assignments and Evaluation||
Readings: Readings are to be completed for the class period where they are listed on the syllabus page.
Class Prep Assignments: Sometimes there may be a small assignment to be completed before class in order to set the stage the the day's discussion. These assignments are due in class and will be graded primarily on having made a serious effort to consider the questions.
Projects: This is a course about software development, so most of your time will be spent developing software. There will be a series of smaller projects focusing on particular topics in the first two-thirds of the course and a substantial final project in which you will cover the full process from specification to functional software in the last third of the course. All projects will be group projects and all members of a group will receive the same grade.
Labs: Lab sessions will be held on Tuesdays in the Rosenberg 009 computer lab. Labs will be an opportunity for hands-on activities and working on group projects.
Exam: There will be one take-home exam (or "individual assessment") following Thanksgiving break.
Participation: "Participation" covers a number of aspects of engagement in the course: attendance, completion of assigned preparatory work (readings, class prep assignments), meaningful contributions to class discussions, and pulling your weight on group assignments.
Grades: Grades in this course will be computed as follows:
Following reasonable conventions is important for readability of your code. The course coding standards specify the particular conventions you should use in this course; not following these standards can result in points lost on assignments.
You are expected to attend and be on time for all class and lab sessions and to be present for the full class period. Attendance is especially important in this course because there is no textbook to help you catch up on missed material, and because not all of the material is black-and-white - discussions with others are valuable in building your ability to make good choices. In addition, announcements are made at the beginning of class and late arrivals may miss important information.
Because attending and participating in class and lab is an important part of your experience in this course, any unexcused absence after the first two absences (whether excused or unexcused) will result in a 5% deduction from your final grade. It is your responsibility to make sure that you sign the attendance sheet each day; a few slip-ups will be allowed but repeatedly forgetting to sign in may result in the accumulation of unexcused absences.
Excused absences include absences due to sports competitions, official Colleges activities such as musical performances or debate competitions, academically-related events such as attending a conference, religious observances, illness, or personal or family emergencies. A reason must be provided in order for such an absence to be counted as an excused absence. (Note that providing a reason does not automatically make an absence excused - it must also be one of the reasons listed above.)
Missing class for other reasons - such as being too busy, oversleeping, or leaving early for a vacation - is considered to be an unexcused absence. Any absence for which no reason is provided is automatically considered to be unexcused.
|Making Up Work||
You are responsible for acquiring any notes, handouts, assignments, and other material missed as the result of an absence, whether excused or unexcused. This should be done promptly to avoid falling behind.
Every effort should be made to hand assignments in on time, even if you are absent from class that day. If a last-minute emergency prevents you from handing in completed work on time, the assignment will be accepted late without penalty only if arrangements are made as soon as possible to get the assignment handed in. If you need more time to complete the assignment, then you need an extension (see below).
|Late Policy and Extensions||
Work will not generally be accepted late - planning your efforts (and how much you take on) so as to meet deadlines even in the case of unexpected surprises is an important component of software development. In addition, aspects of projects may be discussed in class shortly after the due date.
Exceptions are expected to be rare but may be granted in special circumstances. Any requests for extensions must be discussed with me as far in advance of the deadline as possible. Note that leaving early for a vacation, being busy, having a bunch of assignments due at the same time, and computer failures are not considered reasons for extensions - schedule your time carefully, save often, and make backups of your files.
The final exam timeslot will be used for final project presentations. This group activity will be difficult to reschedule, however, if one of the Colleges-approved reasons for rescheduling the final exam (religious observance, post-season athletic competition, or three or more final exams scheduled on the same day) applies, speak to me as soon as possible to determine what arrangements can be made.
No work will be accepted after the end of the Registrar-scheduled final exam time slot.
|Working Together and Academic Integrity||
The HWS Principle of Academic Integrity governs all of the work completed in this course. Specifically:
For all assignments, copying part or all of someone else's solution is expressly prohibited and it is never acceptable to be in possession of someone else's program or solution before you have handed in your own. Decompiling or reverse-engineering someone else's code (including provided code) is also prohibited.
Failure to acknowledge help received will generally result in a warning the first time, and point deductions for subsequent offenses. Submitting work which is unreasonably similar to another person's work and/or not being able to explain any part of your solution will result in a minimum penalty of a 0 on the assignment. A second such offense is grounds for failure in the course. Plagiarism offenses may also be referred to the Committee on Standards.
There are no exceptions to this policy; ignorance of the policy and desperation ("It was the night before it was due and there wasn't anyone else to ask!") are specifically not excuses for violating the policy. If you are having trouble with the course material, come to the instructor! - it is never advantageous to "borrow" someone else's solution, and the time spent trying to disguise this "borrowing" is far better spent getting help.
From the HWS Catalogue: (available online at http://www.hws.edu/catalogue/policies.aspx)
|Plagiarism in Programs and on Problem Sets||
As with papers, verbatim copying of programs and problem solutions constitutes plagiarism. Also as with papers, plagiarism is not limited to verbatim copying - copying the significant ideas and structure of someone else's program/problem solution also constitutes plagiarism.
But aren't all programs which solve the same task/solutions to the same
problem pretty much the same, so won't my program/solution look like everyone
else's even if I worked by myself?
Programming/problem solving techniques are often explained via examples -
what's the difference between using an example and "copying the
significant ideas and structure"?
OK, then, so I can't use any examples because that constitutes
Using "examples" (as defined above) is generally OK but using "solutions" is not.
There's a fuzzy middle ground here, and I'm still not sure exactly
what is OK and what isn't.
|Being Successful and Getting Help||
There is a steady schedule of assignments and the course material is cumulative - don't fall behind! It is important that you budget your time and start on assignments early so that you have time to think about problems and deal with unexpected surprises.
The primary resources for this course are your group (for group assignments), other students in the course (when allowed), and the instructor - during lab, during office hours, and dropping by or scheduling a meeting outside of office hours.
For more general help, such as with writing, study skills, or time management, you are encouraged to check out the Center for Teaching and Learning (CTL).
If you are a student with a disability for which you may need accommodations, you should self-identify, provide appropriate documentation of your disability, and register for services with the Coordinator of Disability Services at the Center for Teaching and Learning (CTL). Disability related accommodations and services generally will not be provided until the registration and documentation process is complete. The guidelines for documenting disabilities can be found at the following website: http://www.hws.edu/academics/ctl/disability_services.aspx
Please direct questions about this process or Disability Services at HWS to David Silver, Coordinator of Disability Services, at firstname.lastname@example.org or x3351.