CS122B Spring 2017: Projects in Databases and Web Applications

Time: T/Th 9:30 am – 10:50 pm (Check UCI Calendar for holiday information)
Location: Engineering Hall, Room 1200.

  • Instructor: Chen Li chenli AT
  • Staff Member: Chen Luo, cluo8 AT
  • Staff Member: Phanwadee Sinthong,psinthonAT
  • Staff Member: Hao Chen, haoc13 AT
  • Staff Member: Yoshitomo Matsubara,yoshitomAT

Office hours

Name Time Office
Chen Luo Monday, 4:30pm - 5:30pm ICS 424
Instructor: Chen Li Tuesday, 11am - noon DBH 2092
Yoshitomo Matsubara Wednesday,1pm- 2pm ICS 424
Phanwadee Sinthong Thursday, 4:30pm - 5:30pm ICS 424
Hao Chen Friday, 1pm - 2pm ICS 424

Online Discussion


  • Quiz 1: Thursday, April 20th, 2017, in-class, closed-book, closed-notes.
  • Quiz 2: Tuesday, May 16th, 2017, in-class, closed-book, closed-notes.
  • Quiz 3: Thursday, June 8th, 2017, in-class, closed-book, closed-notes.

Projects (Subject to change)

Group Signup Sheet

Project Topic Days Due Date Proportions Grading Grading Staff
Project 1 MySQL creation, JDBC, Tomcat, AWS 8 days 4/12/2017, Wednesday, 11:45pm 12% checklist Chen Luo, Phanwadee Sinthong
Project 2 Developing Fablix Web site An earlier demo 19 days 5/1/2017, Monday, 11:45pm 28% checklist Hao Chen, Yoshitomo Matsubara
Project 3 reCaptcha, HTTPS, Stored Procedure, XML Parsing 14 days 5/15/2017, Monday, 11:45pm 21% checklist Chen Luo, Phanwadee Sinthong
Project 4 Ajax, Search, UDF, and Android 14 days 5/29/2017, Monday, 11:45pm 24% checklist Hao Chen, Yoshitomo Matsubara
Project 5 Scaling Fabflix 11 days 6/9/2017, Friday, 11:45pm 15% checklist Chen Luo, Phanwadee Sinthong


No. Date Notes
01 04/04/17, Tu Introduction, Project 1,
02 04/06/17, Th AWS, Sample JDBC Programs
03 04/11/17, Tu ODBC, MySQL Logging, Project 2, Install Tomcat
04 04/13/17, Th TomcatTest Example, Tomcat Logging, Form Example
05 04/18/17, Tu Servlet Session Example, "Cookie Idea" in Movie Memento, Shopping cart
06 04/20/17, Th Pagination, Caching, Project 2 Step-By-Step, 1st quiz
07 04/25/17, Tu "Browsing", "Searching", Open a Window Using Javascript, Javascript debugging, JSP, ASP
08 04/27/17, Th Web Application Architectures, Domain registration
09 05/02/17, Tu Project 2 demos, Project 3, reCaptcha (PPT)
10 05/04/17, Th HTTPS, Stored Procedures
11 05/09/17, Tu XML
12 05/11/17, Th Sample Employee XML File, SAX Parser,, DOM Parser, AutoCommit, Batch Insert, Load data file
13 05/16/17, Tu XML, Project 4, 2nd Quiz
14 05/18/17, Th MySQL Full-Text Search, Ajax Example
15 05/23/17, Tu Android Programming, Android Activity, Android Activity Lifecycle
16 05/25/17, Th edit distance, UDF, Inverted Index
17 05/30/17, Tu Project 5: MySQL Replication
18 06/01/17, Th Project 5: Load Balancing
19 06/06/17, Tu Project 5: Connection Pooling, Jmeter
20 06/08/17, Th AsterixDB, Cloudberry, TextDB, Course wrap up, Quiz 3

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.

Working in Groups

Working together on projects is strongly encouraged. You can form groups of no more than 3 (three) 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.


We will give out the following awards at the end of the quarter:

  • We will announce the top 3 students based on their overall performance in the class (projects and quizzes). They will have a lunch with the professor and TAs :-)
  • 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.

Topic Overview

Last modified 5 years ago Last modified on Jun 8, 2017 8:51:38 AM

Attachments (14)