Course OverviewThis class provides an introduction to the internet/web capabilities and trends, and to computer programming in the context of building full-featured web sites. Intended for students with no previous programming experience who wish to understand the technologies making web sites possible, this course will provide a set of practical problem solving skills necessary for the development of dynamic client-side web content. This class provides non-majors with a basic skill set for leveraging web technologies within their own majors and research interests and an appreciation of both the potential and limits of such resources. This course covers:
Visit this link to find the prerequisites and restrictions for this course. The course Piazza page is your best source for getting course information. TA office hours, additional resources and essential course information will appear on Piazza, and all course-related questions will also be answered on Piazza to ensure all students have equal access to the information.
Course TopicsFollowing topics will be covered in this course (subject to change).
- History of the Web/Internet
- Internet and Society
- Web/Internet Fundamentals
- HTML/CSS for dynamic web sites
- Web authoring tools
- Design (pseudocode)
- Web Page Evaluation
- Instructor: Dr. Ilchul Yoon (Office: IRB1248)
- Semester period: August 26 (Monday), 2019 - December 9 (Monday), 2019
- Lecture hours:
- Section 0101: MWF 1:00pm - 1:50pm (Room: CSI 1115)
- HTML and CSS: Design and Build Websites (Author: Jon Duckett, ISBN-13: 978-1118008188)
- HTML and XHTML Pocket Reference, 3rd Edition (Author: Jennifer Niederst Robbins, ISBN-13: 978-0596527273)
- CSS Pocket Reference: Visual Presentation for the Web, 4th Edition (Author: Eric A. Meyer, ISBN-13: 978-1449399030)
Clicker (or App)
Clicker questions may often be introduced in lectures. You can purchase the Clicker device at bookstore or you can install the Clicker app on your handheld device. The license is free. You can find out how to register here. Clicker points are extra. The points will not be added to your total when an initial letter grade is assigned based on your other points. No makeup point will be given for Clicker points.
Additional Notes on Projects
- Deadlines - All projects are due at 8 pm on the specified day in the project description. You have until 8 pm of the next day to submit your project with a 10% penalty. Notice that after the late period, you will not receive any points for your project. For example, if a project is due on Wednesday at 8 pm, you have until Thursday at 8 pm to submit a late project with a 10% penalty (10% of the assigned points to the project, not your earned points). Any submission after Thursday 8 pm will receive 0 pts.
- Submit Server - You need to use the submit server for project submissions. We will not accept projects submitted otherwise (e.g., e-mail, etc.).
- Which Project Gets Graded - Your grade for an project will be based on the last submission.
- Good Faith Attempt - You must satisfy a minimum set of requirements for each project (Good Faith Attempt) otherwise you will not pass the course (automatic grade of F). Each project defines its own good faith attempt criteria and a deadline to provide an implementation that satisfies it. If you start a project on time, and look for assistance (if required) you should have no problems satisfying the Good Faith Attempt. The Good Faith Attempt guarantees you have at least the mimimum level of skills expected from this course. Notice that you will not receive extra points for completing the good faith attempt. The grade you obtain for a project will be based on your ontime/late submission.
- Closed Projects - All assignments in this course are to be written individually (unless explicitly indicated otherwise). Cooperation between students is a violation of the Code of Academic Integrity. Remember the purpose of projects is for you to learn the class material and do well in projects.
- Do not post your work on the assignments online (e.g., GitHub) where it can be seen by others. Making your work accessible to others can lead to academic integrity violations. Even if the course is over, do not make your work available to others.
- As you work on a project, submit your project often even if you have not finished. We monitor submit server submissions and can provide assistance based on submit server results.
Note that academic dishonesty includes not only cheating, fabrication, and plagiarism, but also includes helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. In short, all submitted work must be your own.
Cases of academic dishonesty will be pursued to the fullest extent
possible as stipulated by the Office
of Student Conduct.
It is very important for you to be aware of the consequences of cheating, fabrication, facilitation, and plagiarism. If the student is found to be responsible of academic dishonesty, the typical sanction results in a special grade "XF", indicating that the course was failed due to academic dishonesty. If you have any doubt as to whether an act of yours might constitute academic dishonesty, please contact your TA or the course coordinator.
On any graded project or lab, you are NOT allowed to collaborate or exchange code. We compare each student's code with every other student's code to check for similarities. Every semester, we catch an embarrassingly high number of students that engage in cheating and we have to take them to the Honor Council.
GroupMe/ Other Group Chats
We encourage students to talk about course material and help each other out in group chats. However, this does NOT include graded assignments. Talking about release tests is NOT okay.
There have been a couple instances in the past where students have posted pictures/source files of their code, or earlier sections have given away exam questions to later sections. Not only did this lower the curve for the earlier section because the later one will do better, the WHOLE group chat had to pay a visit to the Honor Council. It was an extremely ugly business.
You may post your project code to private Github (or similar service) repos only. As a student, you can make a private repo for free. Just remember that your free premium subscription has an expiry date, and your code becomes public once it expires. The Honor Council can retroactively give an XF (even to students who have already graduated) if your code is then used by another student to cheat. So just be careful. Posting graded code to a public repo will give you a free ticket to the Honor Council.
Creating collaborative study guides on Google docs is OK. Encouraged, even. Just do this before the exam, and don't bring the study guide to the exam. Don't add exam questions to the study guide after the early section's midterm.
PRACTICE Exams/ Worksheets/ Lecture examples/ Ungraded Lab examples
Totally cool. Highly encouraged to co-create and share (with same caveats as study guides).
Additional examples of Academic Integrity Violations
The following are a few examples of academic integrity violations:
- Hardcoding of results in a project assignment. Hardcoding refers to attempting to make a program appear as if it works correctly (e.g., printing expected results for a test).
- Using any work available on the internet/web or any other source. For example, using work from Sourceforge or GitHub.
- Hiring any online service to complete an assignment for you.
- Discussing project implementations (everything beyond clarifications) with your classmates.
- Sharing your work with any student.
- Providing ideas/suggestions on how to solve/implement a programming assignment.
- Looking at another student's work.
- Using online forums to ask for help regarding our assignments.
Additional information can be found in the sections titled "Academic Integrity" and "Code of Student Conduct" available at Course Related Policies.
Disabilities Support Accommodations
In case academic accommodations are needed, you must provide a letter of accommodation from the Office of Accessibility and Disability Services (ADS) within the first TWO weeks of the semester. For details, see the section titled "Accessibility" available at Course Related Policies.
The university allows for self-documentation for some absences.
If you need to be excused for an absence from a single
lecture, due to your illness (or other reasons), you shall make
a reasonable attempt to report prior to the class. Send me an
email if you have a medical problem. All other planned,
execusable absences must be reported using the absence report
feature in the grade server).
Upon returning to the class, present with a self-signed note attesting to the date of your illness (or other reasons). Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(i) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.
Self-documentation may NOT be used for the midterm and the final exam, and it may only be used for only 1 class meeting (or more, if you choose) during the semester. Any student who needs to be excused for a prolonged absence (2 or more consecutive class meetings), or for the exams, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment, clearly recomment the student to be off from all school work and indicate the time frame that the student was unable to meet academic responsibilities. In addition, it must contain the name and phone number of the medical service provider to be used if verification is needed. No diagnostic information will ever be requested. Note that the "Medical Discharge Summary" from the Health Center will NOT be accepted as evidence of doctor's recommendation for your absence.
For additional details, see the section titled "Attendance, Absences, or Missed Assignments" available at Course Related Policies
The department and faculty take student feedback seriously. At the end of the course visit https://www.courseevalum.umd.edu/ to complete your course evaluations.
- Please bring your laptop to lectures. If you don't have a laptop, we will pair you up with a classmate.
- If you are experiencing difficulties in keeping up with the academic demands of this course, you may contact the Learning Assistance Service located at 1101 Shoemaker Building.
- UMD Course related policies can be found at http://www.ugst.umd.edu/courserelatedpolicies.html
- Although every effort has been made to be complete and accurate, unforeseen circumstances arising during the semester could require the adjustment of any material given here. Consequently, given due notice to students, the instructor reserves the right to change any information on this syllabus or in other course materials.
All course materials are copyright UMCP, Department of Computer Science © 2019. All rights reserved. Students are permitted to use course materials for their own personal use only. Course materials may not be distributed publicly or provided to others (excepting other students in the course), in any way or format. Although every effort has been made to be complete and accurate, unforeseen circumstances arising during the semester could require the adjustment of any material given here. Consequently, given due notice to students, the instructor reserves the right to change any information on this syllabus or in other course materials.