Database Design and Prototype Development
Main contact
Timeline
-
September 24, 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, 2025User Acceptance Testing (UAT) & Refinement Report
-
December 3, 2025Experience end
Timeline
-
September 24, 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 TABLEstatements), 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, 2025User Acceptance Testing (UAT) & Refinement Report
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, 2025Final Project Submission & Presentation
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 3, 2025Experience end
Experience scope
Categories
Software development Machine learning Artificial intelligence Databases Cloud technologiesSkills
operational efficiency prototype development database architecture business requirements business logic database schema database design user interface (ui) data management prototypingThis experience focuses on empowering learners to design robust database schemas and develop functional prototypes tailored to meet specific business needs. Participants in this program will apply their skills to create efficient data collection systems for implementing business logic that aligns with real-world company objectives. By collaborating with industry professionals, learners will gain practical insights and deliver solutions that enhance data management and operational efficiency.
Learners
- Comprehensive database schema designs tailored to specific business requirements
- Functional prototype applications demonstrating data collection and fundamental processing capabilities
- Documentation of database architecture and business logic implementation as well as recommendations for optimization if applicable
- User interface mockups for data entry and retrieval processes
Project timeline
-
September 24, 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, 2025User Acceptance Testing (UAT) & Refinement Report
-
December 3, 2025Experience end
Timeline
-
September 24, 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 TABLEstatements), 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, 2025User Acceptance Testing (UAT) & Refinement Report
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, 2025Final Project Submission & Presentation
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 3, 2025Experience end
Project examples
- Designing a customer relationship management (CRM) database for a small or mid-sized business
- Developing a prototype inventory management system for a retail company
- Creating a database solution for tracking employee performance metrics
- Building a prototype for a data-driven marketing campaign management tool
- Designing a database for a healthcare provider to manage patient records
- Developing a prototype for a financial reporting system for a mid-sized company
- Creating a database solution for a logistics company to track shipments
- Creating a database solution for a training company to provide training plan and customer management
- Building a prototype application for managing event registrations and feedback
Additional company criteria
Companies must answer the following questions to submit a match request to this experience:
Main contact
Timeline
-
September 24, 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, 2025User Acceptance Testing (UAT) & Refinement Report
-
December 3, 2025Experience end
Timeline
-
September 24, 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 TABLEstatements), 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, 2025User Acceptance Testing (UAT) & Refinement Report
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, 2025Final Project Submission & Presentation
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 3, 2025Experience end