CMSC389N (Fall 2019)
Single Page Web Application Development With JavaScript


Introduction

This course provides an introduction to the development of single page Web-based applications (SPA's) using JavaScript for both the front end client and back-end api/service. We will be devleoping applications using a micro-service architecture pattern and discussing throughout the evolution of web application architectures and current trends.


Prerequisites

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


Administrative Information


Textbooks

None.


Course Topics (Subject to Change)


Classroom

Please bring your laptop to lectures. If you don't have a laptop, we will pair you up with a classmate.

TA Room/Office Hours

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.


Grading

Your grades will be computed according the following weights:

Evaluation Components Percentage
Projects / Exercises 50%
Midterms 1 (Date: October 3, Thursday) 15%
Midterms 2 (Date: November 7, Thursday) 15%
Final Exam (Date: December 16 1:30-3:30pm, CSI 1115) 20%

Projects


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

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.


Projects/Labs

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.


Github

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.


Study Guides

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:

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.


Excused Absences

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 recommend 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. For additional details, see the section titled "Attendance, Absences, or Missed Assignments" available at Course Related Policies


Course Evaluations

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.


Miscellaneous


Copyright

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.


Web Accessibility