Database System Final Project
Database System Final Project
1. Project Title:
2. Project Description:
Provide a brief overview of the project, including its purpose and objectives. Describe what
the database system is intended to manage or solve, and the main functionalities it will offer.
3. Scope:
Define the key features and boundaries of the project. List the major functionalities that the
database system will support. Specify any limitations or exclusions to clarify what is within
the project's scope.
4. Stakeholders:
Identify the individuals or groups who will interact with or benefit from the database system.
Include:
● Entities: List the main entities that will be part of the database. For each entity,
describe its purpose and relevance to the system. ERD should contain a maximum of
8-10 entities.
● Relationships: Describe how entities are related, including the type of relationship
(e.g., one-to-one, one-to-many, many-to-many) and any relevant constraints or rules.
6. Schema Design:
● Tables: Define the tables that will be included in the database schema.
● Columns: List the columns for each table, including data types and constraints.
● Primary Keys: Identify the primary key for each table.
● Foreign Keys: Define the foreign keys that establish relationships between tables.
● Candidate Keys: Define the candidate keys that establish relationships between tables.
Normalization: The database should be normalized and all the details of this
process have to be documented at the end of the project.
Front-End Requirements:
● Responsive Design: The website should fully support different screen sizes (desktop,
tablet, mobile).
● Navigation: Implement an intuitive navigation structure (e.g., side menu or
navigation bar) to allow users to switch between different features easily.
● Form Inputs: Provide forms for data input, validation, and submission, such as
creating, updating, and deleting records.
● Feedback & Alerts: Include visual feedback (e.g., success/failure messages) for user
actions such as submitting a form, invalid inputs, or system errors.
● Data Display: Design data display screens using widgets such as tables, lists, and
cards to show information retrieved from the database in an organized way.
User Roles and Access
● Role-Based Access Control: Define different user roles (e.g., Admin, Editor, Viewer)
to limit access to specific functionalities. The UI should change dynamically based
on the logged-in user's permissions.
● Admin Panel: Provide an interface for system administrators to manage users,
settings, and the database structure (if applicable).
Documentation:
General Instructions
GOOD LUCK!