Course Policy (Fall 2015)
Nate Chambers, , Room 366, Phone x3-6838
Joni Pepin, , Room 319, Phone x3-5251
Internet & World Wide Web: How to Program, Fifth Edition, P. J. Deitel, H. M. Deitel, A. Deitel; Prentice Hall, 2012.
Yes, we will actually read this!
At the end of the course students should be able to:
- To be familiar with and understand the importance of web standards. (Supports student outcome IT-m)
- To be able to design and develop interactive, client-side web applications. (Supports student outcome IT-l)
- To be able to design and develop server-side web applications. (Supports student outcome IT-l)
- To be able to explain how the client-server model of Internet programming works.
- To be able to describe and apply human-computer interaction principles such as affordances, conceptual model, and feedback to design and implementation of a web-based application
- To be able to describe sources of accessibility guidelines and standards, and the impact of these guidelines on designing computer-based applications.
- To be able to evaluate ethical issues involving web privacy. (Supports student outcomes e and g)
- To be able to successfully complete team-based projects.
- (e) An understanding of ethical responsibilities (social); (Supported by learning objective 7)
- (g) An ability to analyze the local and global impact of computing on organizations and society; (Supported by learning objective 7)
- (IT-l) An ability to effectively integrate IT-based solutions into the user environment; (Supported by learning objectives 2 and 3)
- (IT-m) An understanding of best practices and standards and their application; (Supported by learning objective 1)
Students are responsible for obtaining any material missed due to an absence. Additionally, students must ensure that their work is submitted by the deadline regardless of other commitments, i.e. duty, sick call, movement orders. Should bona fide emergencies arise, it is the responsibility of the student to coordinate with the instructor IN ADVANCE (emergency leave, hospitalization, SIR, etc.).
Labs: You may collaborate on laboratory assignments to the following extent: collaborative conversations with regard to syntax, strategies and methods for accomplishing the goal of the labs are encouraged; however design and implementation must be the work of the individual student handing in the final product. Sharing or copying of code is never permitted. In addition, you must identify all those that you collaborate with (give or receive help) on your assignment cover sheet. Consult your instructor if you need further clarification.
Team Projects: The only collaboration allowed is among members of the same team. A midshipman may give no assistance whatsoever to any person not on their assigned team and may receive no assistance whatsoever from anyone outside the team, except from the instructor.
Exams/Quizzes: Exams will be open notes, but closed book, unless otherwise specified. Quizzes are closed book/notes. All work on exams/quizzes must be your own in accordance with USNAINST 1610.3F, USNAINST 1531.53, and COMPSCIDEPTINST1531C. These references can be found at http://www.usna.edu/cs/resources/honor.php.
Homeworks: Collaboration is allowed on homework. The final code or written submission must be entirely your own, but you may discuss approaches and algorithms with your classmates. You may never look at another student's written answers. This restriction also prohibits "checking your answers" by comparing answers side by side.
Online Resources: You can use online resources to assist your learning. These often contain code examples. You must identify in your final code every instance of code you adapted from an outside source. Using external code without citing it is an honor offense. Write a comment block with the citation above the portion of your code that you adapted from an online resource.
Extra Instruction (EI) is available and encouraged when your own attempts to understand the subject matter are unsuccessful. However, you must come prepared with specific questions or areas to be discussed (i.e. have read the assigned readings). If you have missed class, get the notes from a classmate. EI is normally available during weekdays by appointment; see the course web page (URL above) for hours of non-availability. Students may also show up at the instructor's office without appointment, however no expectation of instructor availability should be assumed. Asking questions over e-mail is strongly encouraged, though the reply might request in-person EI as the most effective solution.
The section leader will call the class to order and record absences and tardiness. If the instructor is absent, do not dismiss class. Instead, contact the department office and lead the class in productive review.
Preparation for Lab
Each student must have their personal lecture notes with them for every class session that meets in the lab. Students without their own notes are unprepared and must retrieve them before they can begin work.
Students are expected to uphold all professional standards while in class. Proper uniforms shall be worn, and proper language shall be used. Sleeping in class is prohibited. Stand in the back of the room if you are falling asleep. No food is permitted. Beverages are permitted in closed containers only.
|6-Week Grade||12-Week Grade||Final Grade|
For the Final Project, pairs of students will independently investigate an approved topic, and build a significant system that learns and solves an open NLP problem. Grades will be based on depth of content, coding challenge, and experimental results. Both students might not receive the same grade.
The 6 and 12-week exams will primarily focus on the recent material. The final exam will be comprehensive. If a make-up exam is required, inform the instructor at least 1 week in advance. Expect the exams to challenge your understanding of the underlying principles involved. Exam questions will not be simple rewrites of earlier homework assignments, but will instead be entirely different questions that require in-depth understanding to solve.
Late Assignments and Floating Grace Days
Unless otherwise specified, assignments are due one minute before lab or class on the due date (electronically and paper). Assignments with paper copies must be turned in at the start of lab/class on the due date. If the paper copy is later than this, then the whole assignment will be treated as if submitted when the paper copy arrives.
Weekend days count as full late days. An assignment due on Friday is 3 days late if turned in on Monday.
You are encouraged to turn everything in on time like the responsible adult that you are. However, unexpected events do happen, so you have 5 floating grace days to use during the semester. You may spread these out over any number of labs (up to 4 grace days for any single lab). For instance, you may use 3 grace days on one lab, and 2 grace days on another. After using all of your grace days, you will receive a 0 (zero) on any late assignment thereafter. Weekend days count as full late days.
Please note: grace days are intended to flexibly handle things like illnesses, injuries, and stressful circumstances. You shouldn't have to worry when these things happen. This is your safety net. However, if you use up your 5 days for "trivial" reasons, and then you fall ill, please consider what you're asking before pleading for extra late time.
|Electronic Submission Time||Penalty Days|
|By the due date and time||None|
|One minute after due time||1 day|
|23 hours and 59 minutes after due time||1 day|
|24 hours and 1 second after due time||2 days|
Course Coordinator Assistant Professor Nate Chambers