Projects

Projects in COP 5725 mirror the work a junior data engineer does in industry:

• Pick a real dataset. A letter rule assigns your dataset family; you choose the slice within it.
• Build it up over the semester. Each project iterates on the same data.
• Ship to a GitHub repo. Submissions are git tags on a personal repository.
• Document like onboarding. Each repo’s README should let a new engineer load and run your work.

Projects are individual. Each student creates a private GitHub repository on their own account named exactly cop5725fa26-project, and adds cegme (instructor) and rkc8626 (TA, Ray Chen) as Admins so the TA and instructor can review.

The repo URL becomes your project handle; you register it once in Project 0 (P/F) and use the same repo through the Final Project.

Projects may include a peer grading aspect; details arrive with each project’s release.

---

Project Schedule

Project weights grow with scope; each builds on the same dataset.

Project	Weight	Released	Due	Topic
Project 0	P/F	Fri, Aug 21	Fri, Sep 4	Setup + dataset selection + initial load
Project 1	4%	Wed, Sep 2	Fri, Sep 25	Schema design + SQL ETL + basic queries
Project 2	6%	Mon, Sep 21	Fri, Oct 23	Advanced SQL analytics on your dataset
Project 3	10%	Mon, Oct 19	Fri, Nov 13	Indexing and query optimization investigation
Final Project	15%	Mon, Nov 16	Wed, Dec 9	Capstone — full database-backed solution

---

back