CS122B Spring 2018: Projects in Databases and Web Applications

Time: T/Th 3:30 pm – 4:50 pm (Check the UCI Calendar for holiday information)
Location: PCB 1100.

Name Office Hours Place Email
Instructor: Chen Li Thursdays 2:15 - 3:15 pm DBH 2092 chenli AT
Assistant: Avinash Kumar Tuesday 12:30 - 1:30 pm ICS 464C avinask1 AT
Assistant: Qiushi Bai Wednesday 9:30 - 10:30 am, Friday 9:30 - 10:30 am ICS 464C qbai1 AT
Assistant: Zuozhi Wang Monday 4:00 - 5:00 pm ICS 464C zuozhiw AT
Assistant: Matthew Wo hwo AT
Assistant: Yicong Huang yicongh1 AT


No. Date Notes
01 04/03/18, Tu Introduction, Course Overview, MySQL, JDBC, AWS, Setup Scripts
02 04/05/18, Th Git Overview Using Github in CS122B, Sample JDBC Programs
03 04/10/18, Tu ODBC, Install Tomcat on AWS, Tomcat Example, Tomcat Logging
04 04/12/18, Th MySQL Logging, Project 2 Overview, Form Example
05 04/17/18, Tu HTTP GET/POST, "Cookie Idea" in Movie Memento, Servlet Session Example
06 04/19/18, Th Shopping cart, ​Pagination, Searching/Browsing
07 04/24/18, Tu JSP, ASP, Frontend/Backend Seperation (Example, Slides)
08 04/26/18, Th Web architectures, Quiz 1
09 05/01/18, Tu project2-login-example, Remote Access to AWS MySQL, Domain registration
10 05/03/18, Th reCAPTCHA (Code, PPT), HTTPS, Password encryption, Stored Procedures
11 05/08/18, Tu Ditto
12 05/10/18, Th XML SAX/DOM Parsers
13 05/15/18, Tu Transactions, AutoCommit, Batch Insert (Prepared statement), Load data file
14 05/17/18, Th XML, Project 4: Normal Search, MySQL Full-Text Search
15 05/22/18, Tu AutoComplete Example, Quiz 2
16 05/24/18, Th Android Programming
17 05/29/18, Tu Android Activity, Android Activity Lifecycle, edit distance, UDF, UDF Example
18 05/31/18, Th Project 5: Connection Pooling, MySQL Replication
19 06/05/18, Tu Load balancing, Google Cloud Platform
20 06/07/18, Th JMeter, Course Wrapup, Quiz 3

Online Discussion

Please signup on Gradescope as a student using your UCI id and use the code sent through EEE to enroll into the course.

Projects (Subject to change)

Project Topic Days Due Date Weight Grading Rubrics Demo Signup
Project 1 MySQL creation, JDBC, Tomcat, AWS 12 days Week 3 Monday, 04/16 14% P1 Rubric P1 Demo Signup
Project 2 Developing Fablix Web site An earlier demo 18 days Week 5 Friday, 05/04 30% P2 Rubric P2 Demo Signup
Project 3 reCaptcha, HTTPS, Stored Procedure, XML Parsing 13 days Week 7 Thursday, 05/17 18% P3 Rubric P3 Demo Signup
Project 4 Ajax, Search, UDF, and Android 15 days Week 9 Friday, 06/01 22% P4 Rubric P4 Demo Signup
Project 5 Scaling Fabflix 9 days Week 10 Sunday, 06/10 16% P5 Rubric

The project grading percentages add up to 100%, all projects worth 88% out of the total grade.


  • Quiz 1: 04/26/18, Th
  • Quiz 2: 05/22/18, Tu
  • Quiz 3: 06/07/18, Th

Course Information


This course exposes students to advanced programming concepts and provides students with a greater focus on using DBMS techniques to build Web-based applications. It is intended for two purposes: (1) It introduces students to the modern data management techniques including database connectivity, Web application development, extending database functions, database administration, and XML. (2) It teaches students how to use these technologies to build real-world applications. The course builds on CS122A, which introduces students to the classical relational databases and SQL programming.

Using Cloud Services

We will heavily use cloud services (Amazon AWS and Google Cloud Platform) in the course. You are expected to launch instances on AWS to deploy some of the projects you are developing. AWS provides free-tier 64-bit Ubuntu instances! In addition, you are welcome to participate in the AWS Educate program, which can provide $100 AWS credits per student. We will provide more instructions about how to use their services to deploy your projects. We will also use Google Cloud Platform (GCP) as well, which provides $300 free trial credits at Google Cloud Free Trial.


You should have taken CS122A or an equivalent course. In addition, you should have a reasonable understanding of core computer science concepts, good familiarity with relational databases (equivalent of CS122A), good programming skills in Java, skills to learn other programming languages, and familiarity with basic undergraduate-level operating system concepts. Above all, you need to have a positive attitude towards learning, no inhibitions about working in groups and learning from each other. If you are not sure whether you meet requirements, do talk to the instructor after the first lecture to make sure you are ready to take this course.

Grading Breakdown

Projects: 88%
In-class Quizzes: 11%
Participation in EEE Class Evaluation: 1%

For all the graded projects and exams, if you disagree with the grading, you can discuss with us within two weeks after they are returned. After that, all the grades will be finalized.

For each project demo, we assume each group can provide their own computing environment (either a laptop or a remote desktop) to show the demo. If you cannot provide such an environment, please let us know before the demo, so that we can find a solution.


Many online tutorials.

Using Other Domains

Our main projects are using the movie domain, with provided schemas, data, and required functionalities. Students are encouraged to choose another domain you are familiar with, and use this domain to develop the projects. If you make this choice, the projects can be more fun! At the same time, it also requires additional effort to come up with schemas (comparable to the movie database), sample data, and similar features. Since later projects rely on earlier ones, you cannot change the domain in the middle of the quarter. As a reward, we will give 5% extra credit to each of the five projects. Please specify this decision clearly in your first submission. Students need to make the complexity of their proposed projects comparable to Fabflix. Otherwise, we reserve the rights to deduct points. Also please make sure NOT to do the project for other non-CS122B obligations. You are highly recommended to talk to us before deciding the domain to use.

Using Github

You are required to use Github to manage your source code. Here are the instructions.

Working in Groups

Working together on projects is strongly encouraged. You can form groups of no more than 2 (two) students and submit one homework solution per group making sure that the names of all the group members appear on the first page. Work in groups will be graded on a per group basis.

Students may leave their existing group in the quarter. But they cannot join any new group after the end of the second week. For each group splitting, the group members should tell the instructor at least two weeks before the corresponding project/homework deadline. From the previous quarters, we saw quite a few students who worked alone first but found out the workload was much higher than they initially expected. Thus, please seize the opportunity of the first two weeks to find good teammates to work together.


The top 2 students who made the most contributions to Piazza (e.g., providing high-quality answers, decided by the staff) will receive 1% extra credit each on the overall grade.

Project Late Policy

  • The official due date for each assignment is listed here on the wiki, and it is expected that students will turn the work in on or before that date.
  • We will offer a 24-hour grace period for each assignment, and will therefore accept submissions turned in within 24 hours of the due date, with a 10-point penalty. It's 10 points, not 10 percent. For example, if your late project got 87 points, then your real score will be 87-10=77 points. Notice that EEE will only keep the latest submission. If so you submit or resubmit the project after the deadline, it will be considered as a late submission.
  • Late assignments will NOT be accepted beyond the grace period, so do always aim to be on time! Please don't even ask, as this is what the 1-day grace period is intended for.

Policy on Academic Honesty

All students will be expected to adhere to the UCI and ICS Academic Honesty policies (see read their details). Any student found to be involved in cheating or aiding others in doing so will be academically prosecuted to the maximum extent possible: that means you will fail this course. Just say no to cheating!

In case you reuse another party's source code for certain generic tasks (e.g., JDBC access) make sure you explicitly comment on its origin in your source code.

Project Overview

Last modified 3 years ago Last modified on Jun 9, 2018 4:38:54 PM

Attachments (16)