CMSC389N

Syllabus

Introduction (Spring 2017)

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.

Prerequisites

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

Regarding Credits

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

Course Coordinator

Name	Office
Nelson Padua-Perez	AVW 1203

For office hours and other contact information, visit the staff link.

Textbooks

None.

Course Topics (Subject to Change)

• 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

Grading

Final grades will be computed according the following weights:

25%	Individual Projects
15%	Group Project
30%	Midterms (2, 15% each)
30%	Final Exam

Once we have graded any class material (e.g., exams, projects, etc.) we will post an announcement and a deadline by which you must submit any regrade request (if necessary). It is your responsibility to submit regrade requests by the specified deadline; no regrade requests will be processed afterwards.

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 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 Wednesday at 8 pm, you have until Thursday at 8 pm to submit a late project with a 12% penalty. 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 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.

Regarding Online Posting of Project Implementations

• 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.
• Notice we constantly monitor online sources.

TA Room/Office Hours

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.

Backups

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).

Academic Integrity

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.

Computer Science Department Academic Integrity Information

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

Examples of Academic Integrity Violations

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 Piazza) 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.

Piazza

We will be using (Piazza) for class communication. You will not be able to register to Piazza yourself. Your instructor will register you using the e-mail you have in the school system.

Excused Absence and Academic Accommodations

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

Disability Support Accommodations

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

Miscellaneous

• At the end of the course 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

Copyright

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

Schedule

Course Schedule

This schedule is tentative and subject to change. Keep in mind that the slides may not include all the material discussed in lecture. You are responsible for any material we present in lecture, even if it does not appear in the posted slides.

Staff

Coordinators

Name	Nelson Padua-Perez
Office	AVW 1203
Office Hours	Mon, Wed → 12:30 pm - 2:00 pm
E-Mail	nelson [AT] cs [DOT] umd [DOT] edu

Office Hours Information

Teaching Assistants

All TA office hours take place in AVW 1120 (Small TA Room, First Floor).

Name	E-mail	Pic
Jenish Kanani	jenishkanani1 [AT] gmail [DOT] com
Reed Trevelyan	reedtrevelyan [AT] gmail [DOT] com
Roozbeh Yousefzadeh	first name [AT] cs.umd [DOT] edu

Office Hours

Coordinators

Name	Nelson Padua-Perez
Office	AVW 1203
Office Hours	Mon, Wed → 12:30 pm - 2:00 pm
E-Mail	nelson [AT] cs [DOT] umd [DOT] edu

Office Hours Information

Teaching Assistants

All TA office hours take place in AVW 1120 (Small TA Room, First Floor).

Name	E-mail	Pic
Jenish Kanani	jenishkanani1 [AT] gmail [DOT] com
Reed Trevelyan	reedtrevelyan [AT] gmail [DOT] com
Roozbeh Yousefzadeh	first name [AT] cs.umd [DOT] edu

Lectures

Course Schedule

This schedule is tentative and subject to change. Keep in mind that the slides may not include all the material discussed in lecture. You are responsible for any material we present in lecture, even if it does not appear in the posted slides.

Good Faith Attempt

Good Faith Attempt Deadlines

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. Notice that you will not receive extra points for completing the good faith attempt. The grade you obtain in the project will be based on your ontime/late submission.

Project	Good Faith Attempt	Deadline
Project #3, Grades Submission	Processing (Going back and correcting grades)	May 1
Project #4, Application System	Submit and Review Application	May 3
Project #6, Utilities	Photoviewer "Slide Show" generates a sequential slide show, "Random Slide Show" generates a random slide show, Doubly-linked list was used to implement functionality, Photoviewer customer type defined. No Recorder implementation expected.	May 10

Regrades

Regrades Deadlines

After any class material is graded, you have a period to address any grading concerns. Unfortunately we will not be able to address any grading concerns after the specified deadline.

Class Material	Grading Concerns Deadline
Project #1	Wed Mar 8
Project #2	Wed Mar 15
Midterm #1	Fri Apr 7
Project #3	Fri Apr 14
Project #4	Wed Apr 26
Project #5	Mon May 8
Midterm #2	Wed May 10
Project #6	Fri May 12

Projects

Projects

The planned dates when projects will be handed out and due is given in the course schedule. Beware that the exact dates are subject to change, but we will try to give you fair notice of any changes.

Project Descriptions

Project	Deadline
Web Page (P1)	Wed Feb 15
Group Project	Thu Mar 2/ Mon May 8
Request Form (P2)	Wed Feb 22
Grades Submission (P3)	Fri Mar 3
ApplicationSystem (P4)	Thu Apr 6
DataValidation (P5)	Mon Apr 17
Utilities (P6)	Fri May 5

Exams

Exams

This page provides information regarding course exams.

Exam	Date
Midterm I	Tue Mar 7
Midterm II	Thu Apr 20
Final	Thu May 18

Links

Links

XAMPP(Apache, MySql, and PHP)

• XAMPP for Linux, Windows, Mac OS X, Solaris

PHP References

• PHP Net → http://www.php.net/
• PHP Manual → http://www.php.net/manual/en/
• PHP Function Index→ http://www.php.net/manual/en/indexes.php
• PHP Tutorials → http://www.thescripts.com/serversidescripting/php/index.html
• W3schools.com PHP Tutorial → http://www.w3schools.com/php/default.asp
• Onlamp → http://www.onlamp.com/
• http://www.phptherightway.com/

Drupal

• drupal.org
• Drupal Gardens
• Drupal Gardens Documentation
• Tutorials
• Drupal Mobile Theme
• JQuery Based Drupal Modules

Miscellaneous

• git tutorial
• How Web Servers Work

Hosting

• https://www.namecheap.com/, Additional Info
• http://www.hostmonster.com/
• PHP Hosting
  • http://www.inmotionhosting.com/
  • https://www.webhostinghub.com/
  • http://www.arvixe.com/

JavaScript

• JavaScript Reference
• JavaScript Debugging
• https://www.javascript.com/
• https://fivejs.codeschool.com/episodes
• ecmascript-6-complete-tutorial
• http://exploringjs.com/es6/
• Speedometer

Bootstrap

• Bootstrap Examples
  1. Example #1
  2. Example #2
  3. Example #3
  4. Example #4
  5. Example #5
• Tables
  1. http://mdbootstrap.com/css/tables/
  2. http://v4-alpha.getbootstrap.com/content/tables/
  3. Bootstrap Table Generator (and more)

jQuery

• Introduction to jQuery

Revalidate

Revalidate link is revalidate page.

Device Emulators(Check Page on iphone, ipad, etc.)

• http://quirktools.com/screenfly/

Other

• Safari Books Online
• Beautifier
• Tiny URL
• Learn CSS Layout
• http://lesscss.org/
• Google Fonts API
• Color Palette Generator
• Color Picker Tool
• http://www.colorhunt.co/
• Free Web Design Templates
• ECMAScript 2015 Language Specification
• ECMAScript examples (http://www.es6fiddle.net/ib6sflu9/)
• Favicon Generator
• Babel (JavaScript Compiler)
• https://examplewebpresence.wordpress.com/
• http://www.terpconnect.umd.edu/~nelsonp/csterpconnect/
• https://bitbucket.org/ (Git solution for professional teams)
• http://www.oswd.org/ (Open Source Web Design)
• sqlReview.pdf
• PHP_SELF exploits
• Gentle Explanation of this in JavaScript
• How to Create a Secure Login Script in PHP and MySQL
• Free Certificates
• Lecture Videos
• Building HTML email

Piazza

Piazza

We will be using (Piazza) for class communication. Regarding Piazza:

• We will use Piazza to communicate in lecture and to provide class announcements.
• Posting of code is not allowed is Piazza. Anyone posting any kind of code may receive an XF in the course.. Please carefully read the Piazza Guidelines.
• In Piazza you can see the class announcements by selecting "Resources", "Course Information".
• When we post an announcement we will select the Piazza option that allows you to receive an immediate e-mail. The e-mail will have a subject line that starts with "[Instr Note]." If you are filtering piazza messages make sure that those messages are not placed in the junk folder.
• You are responsible for checking class announcements.
• The prefered mechanism to address course questions (projects, lecture material, etc.) is during office hours, in lab, and lecture.
• Students' questions can only be answered by CS staff (TAs and instructors). Although we will try to check Piazza often, there is no guarantee we will respond to messages immediately.
• You will not be able to register to Piazza yourself. Your instructor will register you using the e-mail you have in the school system.. If you would like to use a different e-mail address see your teaching TA in lab.
• If you access the link provided for Piazza on the class web page and it asks for an access code, try the following:
  • Visit http://www.piazza.com
  • Click "log in" on the top right
  • Click "forgot password"
  • Enter the e-mail address registered to piazza (e-mail address registered with the school).
  • Access your e-mail account to receive a link that will bring you to the registration site.