CMSC389N (Fall 2018) - Introduction to PHP & Javascript

Syllabus

This course provides an introduction to the development of Web-based applications using PHP, JavaScript, MySQL/MariaDB, and Apache. The course covers fundamental programming language constructs of both PHP and JavaScript, forms, sessions, interation with MySQL/MariaDB via PHP, DOM, and JavaScript event-handling. In addition, popular JavaScript libraries (e.g., JQuery) will be overviewed.

Prerequisite → C- or better in CMSC 216 and CMSC 250
Credits → 3

None.

Credit granted for only 389J and 389P OR 389N.

• HTML5 overview
• Installing Apache, PHP, and MySQL
• Forms
• PHP
  • Variables, data types, expressions, operators
  • Conditional, iteration, statements
  • Functions
  • Arrays
  • PHP Object Model
  • Files and Directories
  • Interacting with MySQL using PHP
  • Sessions
• JavaScript
  • Variables, data types, expressions, operators
  • Conditional, iteration, statements
  • Functions
  • Arrays
  • DOM, Events, Events Handling
  • Client-side Persistance
  • Object-Oriented JS
  • Ajax
• Overview of JavaScript Libraries/Frameworks
• Miscellaneous

Once we have graded any class material (e.g., exams, projects, etc.) we will make an announcement at the beginning of the next class. In the event a regrade is necessary due to grading error, please contact the instructor as soon as possible either via Slack or by email.

• Deadlines - All projects are due at 11:59 pm on the specified day in the project description. You have until 11:59 pm of the next day to submit your project with a 12% penalty. Notice that after the late period, you will not receive any points for your project, even though you still need to satisfy the good faith attempt (see information below). For example, if a project is due on Thursday at 11:59 pm, you have until Friday at 11:59 pm to submit a late project with a 12% penalty. Any submission after Friday 11:59 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 submission with the highest score after the late penalty (if any) has been applied.
• 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 the skills necessary for upper-level courses. 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 programming 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.

• Do not post your assignments' implementation online (e.g., GitHub, PasteBin) where they can be seen by others. Making your code accessible to others can lead to academic integrity violations.
• Posting of your projects in a private repository where only selected people (e.g., potential employers) can see them is OK. Just make sure is not a public site.
• Even if the course is over, do not make your code publicly available to others.
• We constantly monitor online sources.

Office hours get extremely busy the day before a project deadline. Therefore do not wait to start your projects. Regarding office hours and the TA Room:

• Once you have been helped by a TA please leave the TA room. We have a large number of students in all of our classes and the TA room is really crowded.
• If there is a line of students waiting, a TA should spent at most 5 minutes with a student. Please remind TAs about this rule.

You need to keep backups of your projects as you develop them. No extensions will be granted because you accidentally erased your project. Feel free to use the submit server as a backup tool by submitting often. You can also use tools like git, etc. Do not post code in any online system that is accessible to others (e.g., GitHub).

We will be using (Slack) for class communication.

See the section titled "Attendance, Absences, or Missed Assignments" available at Course Related Policies.

See the section titled "Accessibility" available at Course Related Policies .

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. For more information on the Code of Academic Integrity or the Student Honor Council, please visit http://www.shc.umd.edu.

The CS Department takes academic integrity seriously. Information on how the CS Department views and handle academic integrity matters can be found at Academic Integrity.

The following are 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 code available on the internet/web or any other source. For example, using code from Sourceforge.
• Hiring any online service to complete an assignment for you.
• Sharing your code or your student tests with any student.
• Using online forums (other than Slack) in order 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.

• At the end of the semester visit (www.courseevalum.umd.edu) to complete your course evaluations.
• If you are experiencing difficulties in keeping up with the academic demands of this course, you may contact the Learning Assistance Service located at 2202 Shoemaker Building.
• UMD Course related policies can be found at http://www.ugst.umd.edu/courserelatedpolicies.html

All course materials are copyright UMCP, Department of Computer Science © 2018. 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.

Web Accessibility