Database Design and Prototype Development
Main contact
Timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
-
October 15, 2025Database Schema & Design Document
-
October 29, 2025Database Implementation & Initial Code
-
November 12, 2025UI Mockups & Initial Web Implementation
-
November 22, 2025Model Refinement & Iteration
-
December 4, 2025Experience end
Timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
Deliverable: A formal document submitted to the instruction team and the company. This should include a summary of the project's goals, a clear list of functional and non-functional requirements gathered from the company, and a proposed team plan for the remaining milestones.
Purpose: This milestone ensures that students have a solid understanding of the company's needs from the very beginning.
-
October 15, 2025Database Schema & Design Document
Deliverable: An Entity-Relationship Diagram (ERD) and a design document. This document should detail the tables, fields, relationships, and data types, as well as any proposed normalization or denormalization strategies.
Purpose: This is the core design phase. Feedback at this point is critical before any code is written.
-
October 29, 2025Database Implementation & Initial Code
Deliverable: The Data Definition Language (DDL) scripts to create the database (e.g., CREATE TABLE statements), along with a small sample of populated data, satisfying the business logic. Students should also provide a working prototype or a basic script that demonstrates a few key database operations with or without web UIs.
Purpose: This milestone shows that students can physically build the database and ensures the design is functional.
-
November 12, 2025UI Mockups & Initial Web Implementation
Deliverable: Students will submit mockups or wireframes for the user interface, along with the initial code for the front-end. This should demonstrate the basic layout and navigation of the application, connecting to the database created in the previous milestone.
Purpose: This milestone ensures that students begin building the user-facing part of the application early, allowing for feedback on the user experience.
-
November 22, 2025Model Refinement & Iteration
Deliverable: A report summarizing the testing process, including any issues found and how they were resolved. The students should also show the company a working, populated version of the database for their review and feedback.
Purpose: This phase is for validating the project against the initial requirements and making final adjustments based on company feedback.
-
December 3, 2025Deliverable Development
Deliverable: The complete and documented project, including all code, a final report, a user manual, and a short presentation for the company.
Purpose: This is the culmination of the project, where students deliver the final product and demonstrate their skills.
-
December 4, 2025Experience end
Experience scope
Categories
Website development Software development Databases Data modelling Data scienceSkills
prototype development data management prototyping computer systems database normalization database application document-oriented databases database architecture distributed relational database architecture (drda)The project aims to enhance the efficiency of the service application process by transitioning from a manual to a digital system. Currently, the process involves cumbersome paperwork and manual data entry, leading to delays, inconsistencies and potential errors negatively impacting community members seeking services. The goal is to create a seamless digital workflow that automates data collection and integrates it directly into the company's Client Management System (CMS). This will not only reduce processing time but also improve data accuracy and accessibility. The project will involve analyzing the current process, designing a digital form for data collection, and developing a method to automatically input this data into the CMS. By digitizing the application process, the company can improve service delivery and operational efficiency.
Learners
The project will deliver a fully functional digital application form that can be accessed online by individuals in the community seeking services. Additionally, a system will be developed to ensure that data collected through the form is automatically and accurately entered into the CMS. The deliverables will include a detailed process map of the new workflow, a prototype of the digital form, and a demonstration of the CMS integration. The team will also provide documentation outlining the implementation process and user guidelines.
Project timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
-
October 15, 2025Database Schema & Design Document
-
October 29, 2025Database Implementation & Initial Code
-
November 12, 2025UI Mockups & Initial Web Implementation
-
November 22, 2025Model Refinement & Iteration
-
December 4, 2025Experience end
Timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
Deliverable: A formal document submitted to the instruction team and the company. This should include a summary of the project's goals, a clear list of functional and non-functional requirements gathered from the company, and a proposed team plan for the remaining milestones.
Purpose: This milestone ensures that students have a solid understanding of the company's needs from the very beginning.
-
October 15, 2025Database Schema & Design Document
Deliverable: An Entity-Relationship Diagram (ERD) and a design document. This document should detail the tables, fields, relationships, and data types, as well as any proposed normalization or denormalization strategies.
Purpose: This is the core design phase. Feedback at this point is critical before any code is written.
-
October 29, 2025Database Implementation & Initial Code
Deliverable: The Data Definition Language (DDL) scripts to create the database (e.g., CREATE TABLE statements), along with a small sample of populated data, satisfying the business logic. Students should also provide a working prototype or a basic script that demonstrates a few key database operations with or without web UIs.
Purpose: This milestone shows that students can physically build the database and ensures the design is functional.
-
November 12, 2025UI Mockups & Initial Web Implementation
Deliverable: Students will submit mockups or wireframes for the user interface, along with the initial code for the front-end. This should demonstrate the basic layout and navigation of the application, connecting to the database created in the previous milestone.
Purpose: This milestone ensures that students begin building the user-facing part of the application early, allowing for feedback on the user experience.
-
November 22, 2025Model Refinement & Iteration
Deliverable: A report summarizing the testing process, including any issues found and how they were resolved. The students should also show the company a working, populated version of the database for their review and feedback.
Purpose: This phase is for validating the project against the initial requirements and making final adjustments based on company feedback.
-
December 3, 2025Deliverable Development
Deliverable: The complete and documented project, including all code, a final report, a user manual, and a short presentation for the company.
Purpose: This is the culmination of the project, where students deliver the final product and demonstrate their skills.
-
December 4, 2025Experience end
Project examples
Designing a relational database schema to support a business process.
Building ETL (Extract, Transform, Load) pipelines to integrate multiple data sources.
Migrating legacy data into a modern database or cloud-based system.
Developing SQL-based dashboards and reports for business decision-making.
Performing advanced query optimization for large datasets.
Creating OLAP cubes or data marts for analytical workloads.
Comparing performance between SQL and NoSQL solutions for a given dataset.
Designing a scalable solution using cloud platforms (e.g., AWS RDS, DynamoDB, or Google BigQuery).
Implementing data partitioning, sharding, or replication strategies.
Designing and implementing a database-backed web or mobile application.
Creating APIs to enable secure and scalable database access.
Implementing role-based access control and auditing mechanisms.
Designing metadata repositories to improve data discoverability.
Additional company criteria
Companies must answer the following questions to submit a match request to this experience:
Main contact
Timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
-
October 15, 2025Database Schema & Design Document
-
October 29, 2025Database Implementation & Initial Code
-
November 12, 2025UI Mockups & Initial Web Implementation
-
November 22, 2025Model Refinement & Iteration
-
December 4, 2025Experience end
Timeline
-
September 23, 2025Experience start
-
October 1, 2025Project Brief & Requirements Report
Deliverable: A formal document submitted to the instruction team and the company. This should include a summary of the project's goals, a clear list of functional and non-functional requirements gathered from the company, and a proposed team plan for the remaining milestones.
Purpose: This milestone ensures that students have a solid understanding of the company's needs from the very beginning.
-
October 15, 2025Database Schema & Design Document
Deliverable: An Entity-Relationship Diagram (ERD) and a design document. This document should detail the tables, fields, relationships, and data types, as well as any proposed normalization or denormalization strategies.
Purpose: This is the core design phase. Feedback at this point is critical before any code is written.
-
October 29, 2025Database Implementation & Initial Code
Deliverable: The Data Definition Language (DDL) scripts to create the database (e.g., CREATE TABLE statements), along with a small sample of populated data, satisfying the business logic. Students should also provide a working prototype or a basic script that demonstrates a few key database operations with or without web UIs.
Purpose: This milestone shows that students can physically build the database and ensures the design is functional.
-
November 12, 2025UI Mockups & Initial Web Implementation
Deliverable: Students will submit mockups or wireframes for the user interface, along with the initial code for the front-end. This should demonstrate the basic layout and navigation of the application, connecting to the database created in the previous milestone.
Purpose: This milestone ensures that students begin building the user-facing part of the application early, allowing for feedback on the user experience.
-
November 22, 2025Model Refinement & Iteration
Deliverable: A report summarizing the testing process, including any issues found and how they were resolved. The students should also show the company a working, populated version of the database for their review and feedback.
Purpose: This phase is for validating the project against the initial requirements and making final adjustments based on company feedback.
-
December 3, 2025Deliverable Development
Deliverable: The complete and documented project, including all code, a final report, a user manual, and a short presentation for the company.
Purpose: This is the culmination of the project, where students deliver the final product and demonstrate their skills.
-
December 4, 2025Experience end