Introduction
This class provides an introduction to the development of Web-based applications using PHP, MySQL/MariaDB, and Apache. The course will focus on the PHP programming language.
This class has no required textbooks. The course coordinator is Nelson Padua-Perez.
Grading
Final grades will be computed according the following weights:
| Projects | 65% |
|---|---|
| Final Exam | 35% |
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 11:30 pm on the specified day in the project description. You have until 11:30 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. For example, if a project is due on Wednesday at 11:30 pm, you have until Thursday at 11:30 pm to submit a late project with a 12% penalty. Any submission after Thursday 11:30 pm will receive 0 pts.
- Submit Server - You need to use the submit server for project submissions. Notice we will grade the last submission you provide and there will be no testing support in the submit server. If you submit both an on-time and a late submission, we will only grade the late submission (after applying a 12% penalty). No assignment will be accepted after the one-day late period. Assignment are to be submitted electronically by uploading a zip file.
- 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. 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 on-time/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.
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. Feel free to use the submit server as a backup tool by submitting often. You can also use tools like git, cvs, etc. If you use online systems (e.g., GitHub) make sure your work is not accessible to everyone.
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.
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 GitHub, Pastebin, etc.
- 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.
- 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. Notice that posting of your projects in a private repository where only selected people (e.g., potential employers) can see them is OK.
- Notice we constantly monitor online sites/resources.
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. Also feel free to provide suggestions during the semester.
- 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.