CS 5610 - Web Development

Fall 2019

Discusses Web development for sites that are dynamic, data driven, and interactive. Focuses on the software development issues of integrating multiple languages, assorted data technologies, and Web interaction. Requires each student to deploy individually designed Web experiments that illustrate the Web technologies and at least one major integrative Web site project. Each student or team must also create extensive documentation of their goals, plans, design decisions, accomplishments, and user guidelines.

Essential Resources

Sections

Section Location Time
01 FR 129 9:50-11:30pm TuFr

Office Hours

Name Location Hours Email
Nat Tuck NI 132 E Tu 5:30-6:30pm; We 2-3pm ntuck ⚓ ccs.neu.edu
Abhishek Ahuja KA 204 Th 6:00-8:00pm ahuja.a ⚓ husky.neu.edu
Sangeetha Chandrashekar EV 008 We 3:00-5:00pm chandrashekar.s ⚓ husky.neu.edu

Schedule

This is an initial schedule, subject to revision as the semester progresses.

Assignments will frequently be due at 11:59pm Thursday.

Week Starts Topics Work Due
1 (+) Sep 2 Intro: Dev on the Web, Server Setup -
2 Sep 9 JS & DOM; Elixir & Phoenix Intro HW01: Dev & Server Setup
3 Sep 16 Webpack & React; In-browser State HW02,HW03: Warm Up
4 Sep 23 Sockets & Channels; Server-side State HW04: Client-Side Game
5 Sep 30 OTP: GenServers, Agents, Supervisors HW05: Client-Server Game
6 Oct 7 Canvas, WebGL, Web Assembly -
7 Oct 14 Resources, REST, Ecto; Rels & RDBMSes -
8 Oct 21 JSON Resources & AJAX ; Passwords Proj1: Multi-Player Game
9 Oct 28 SPAs; Redux HW06: Simple CRUD App
10 Nov 4 Using Web APIs; Oauth2 HW07: Single Page App
11 Nov 11 Security and Performance -
12 Nov 18 NoSQL ; Distributed Elixir -
13 (+) Nov 25 Semester Wrap-Up Project 2: Final Project
14 Dec 2 Project Presentations -
15 Dec 9 Project Presentations -

(+) One Lecture Weeks: Start, Thanksgiving

Required Supplies

There is no required textbook for this course. Your primary resource should be the official documentation for the languages, libraries, tools, and frameworks we use in the class.

Each student must have virtual private server and a domain name, accessible from the public internet. Getting these will be part of the first homework assignment. This will cost around $30 for the semester.

Domain Registrars: joker, gandi, namecheap.

VPS Providers: vultr, linode, digital ocean

Your VPS should have Debian 10 and at least 1 GB of RAM. Either your domain registrar or your VPS provider should provide DNS hosting.

You may not use a cloud server (e.g. Amazon EC2, Google Compute, Azure) in place of a VPS.

Library, Framework, Tool, and Language Documentation

Prof Rasala’s Web Dev Links: Web Dev Links

Editors

We will be writing code in several languages. Programming is much easier with editor support, so you must find and configure an editor that supports the languages we are using. Most editors will do HTML / CSS / JS well out of the box. Elixir is supported less broadly - these editors should work well:

Submitted code with indentation that shows that you aren’t using an editor with automatic indentation support (and using it successfully) will be penalized harshly.

Grading

Letter Grades

The number to letter mapping will be as follows:

95+ = A, 90+ = A-, 85+ = B+, 80+ = B, 75+ = B-, 70+ = C+, 65+ = C, 60+ = C-, 50+ = D, else = F

There may be a curve or scale applied to any assignment or the final grades, in either direction.

Homework

Most weeks there will be a homework assignment due. You’ll have to do some web design, programming, system administration, database manipulation, etc.

In order to learn the material in this class you must submit the homework. If at any point you have three unexcused zero grades for assignment that have been graded you will fail the course.

If you fall behind on the course work for any reason, please come to the professor’s office hours to discuss how you can catch up.

Projects

Your projects will exercise many of the techniques and technologies covered in the homework to create a significant web application from scratch.

Late Work

Late submissions will be penalized by 1% per hour late.

Project 2 may not be submitted after presentations begin.

Policies

Contesting Grades

Homework and project grades will be posted on Bottlenose. If you think your work was graded incorrectly, you can challenge your grade through the following process:

First, go to the office hours of the course staff member who graded your work. If you can convince them that they made a concrete error in grading, they will fix it for you.

If the grader doesn’t agree that the grade was wrong, you can issue a formal grade challenge. This follows a variant of the “coaches challenge” procedure used in the NFL.

Here’s the procedure:

Special Accomodations

Students needing disability accommodations should visit the Disability Resource Center (DRC).

If you have been granted special accomodations either through the DRC or as a student athlete, let me know as soon as possible.

Code Copying & Collabaration Policy

Copying code and submitting it without proper attribution is strictly prohibited in this class. This is plagiarism, which is a serious violation of academic integrity.

Details:

Non-Code Work

Obviously, written text for something like a project report can also be plagarized. The standard rules for writing apply.

Lecture Notes

Lecture notes are not starter code, and should not be copied without attribution. As long as attribution is provided, there is no penalty for appropriately using code from the lecture notes.

Collaboration and Attribution:

Since it’s not plagiarism if you provide attribution, as a special exception to these rules, any code sharing with attribution will not be treated as a major offense.

There is no penalty for copying small snippets of code (a couple of lines) with attribution as long as this code doesn’t significantly remove the intended challenge of the assignment. This should be in a comment above these lines clearly indicating the source (including author name and URL, if any).

If you copy a large amount of code with attribution, you won’t recieve credit for having completed that portion of the assignment, but there will be no further penalty. The attribution must be obvious and clearly indicate both which code it applies to and where it came from.

Penalty for Plagarism

First offense:

Avoid copying code if you can. If you’re looking at an example, understand what it does, type something similar that is appropriate to your program, and provide attribution. If you must copy code, put in the attribution immediately, every time or you will fail the course over what feels like a minor mistake.