Database Design
As a team, choose one of the 3 variants that you will implement throughout the project. This initial step is crucial as it will define the context for all subsequent tasks. Discuss as a team and select the variant that best matches your interests and learning goals.
Project Milestones
MVP (Minimum Viable Product)
The MVP milestone represents the essential functionality that must be implemented. Completing the MVP is sufficient to pass the project, and it ensures you understand the core database concepts. Focus on building a solid foundation with the minimum set of features required for your chosen variant.
For your chosen variant, you must:
- Design and implement the basic tables and relationships as described in the variant.
- Ensure the core functionality is present, such as the ability to add, update, and retrieve essential records.
- Write simple queries and implement basic CRUD (Create, Read, Update, Delete) operations for each table.
- Develop a minimal but functional data model that accurately represents the requirements.
Final Version (Enhanced Learning)
The final version is recommended for teams wanting to maximize their learning experience. It includes advanced features and demonstrates mastery of database concepts. This version should go beyond the basics and showcase your ability to design robust, scalable, and well-documented database solutions.
Additional features include:
- Implementing all described functionality from the variant, including advanced and optional features.
- Adding data validation and integrity checks to ensure data quality and consistency.
- Providing comprehensive documentation for your database design, including explanations of design choices and usage instructions.
Tasks
For your chosen variant, complete the following:
- Create an ER (Entity-Relationship) diagram that visually represents the structure of your database, including entities, relationships, and key attributes.
- You may use tools such as DB Designer, DB Designer app, or any other tool of your choice, as long as the output is clear and shareable.
- Submit the ER diagram as a PDF or image file.
- Ensure that your diagrams and schema are clear, well-organized, and easy to understand by others.
Add a note on the ER diagram / schema mentioning which team members were responsible for what parts of the diagram. This helps clarify individual contributions and responsibilities.
Clearly mark in your diagrams which parts belong to MVP and which are for the final version. Use color coding, labels, or other visual cues to distinguish between the two.
On top of the code and documentation deliverables, each team member must record a short video (approximately 2 minutes per person) describing the part of the solution they were responsible for. The video should briefly explain your contribution, the challenges you faced, and how you addressed them. The free version of Zoom allows recording of videos during a conference call, making it easy for teams to collaborate and record together. Once recorded, the video can be uploaded to Google Drive or YouTube (as an unlisted video), and the link should be provided as part of the graded material.