Scribd
Upload
4 views

Project_DB

The document outlines the requirements for a Database Systems project for BS (IT) students at GC University, Faisalabad. It details the steps for designing a database schema, including problem definition, requirements gathering, conceptual and logical design, normalization, physical design, SQL implementation, testing, and documentation. The project aims to provide students with a comprehensive understanding of database design and implementation.

Uploaded by

ayeshanoor777325
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views

Project_DB

The document outlines the requirements for a Database Systems project for BS (IT) students at GC University, Faisalabad. It details the steps for designing a database schema, including problem definition, requirements gathering, conceptual and logical design, normalization, physical design, SQL implementation, testing, and documentation. The project aims to provide students with a comprehensive understanding of database design and implementation.

Uploaded by

ayeshanoor777325
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Department of Information Technology, Division of Physical Science

GC University, Faisalabad

Project of Database Systems

Class: BS (IT) Semester: 2nd


Date: 12/05/2025 Submission: 30th May, 2025
Subject: Database Systems Course Code: CCC-304
Max Marks: 10 Instructor: Prof. Dr. Mariam Rehman

Requirements for Designing a Database Schema Project


1. Problem Definition & Scope

 Clearly state the domain (e.g., Hospital Management, Library System, Online Store).
 Define the purpose of the database.
 Identify the users and their interactions (e.g., Admin, Customer, Staff).

2. Requirements Gathering

 Identify functional requirements:


o What data should be stored?
o What operations should be supported (CRUD: Create, Read, Update, Delete)?
 Identify non-functional requirements (optional for beginners):
o Performance, scalability, security, etc.
 Identify Business Rules

3. Conceptual Design

 Use an ER Diagram (Entity-Relationship Diagram) to model:


o Entities and their attributes
o Relationships between entities
o Cardinalities (one-to-one, one-to-many, many-to-many)
o Generalization, specialization, if applicable
 Optionally include UML Class Diagrams

4. Logical Design

 Convert the ER model to Relational Schema:


o Define tables, columns, data types
o Define Primary Keys (PK) and Foreign Keys (FK)
o Maintain referential integrity
5. Normalization

 Apply normal forms:


o Ensure 1NF (atomic attributes)
o 2NF (remove partial dependencies)
o 3NF (remove transitive dependencies)
 Optionally mention if and why denormalization is done

6. Physical Design

 Choose appropriate data types


 Decide on indexes for performance
 Estimate storage needs
 Design for data integrity constraints (e.g., NOT NULL, UNIQUE)

7. SQL Implementation

 Write SQL DDL (Data Definition Language) to create tables


 Write SQL DML (Data Manipulation Language) for sample inserts
 Optionally add:
o Views
o Stored procedures
o Triggers
o Constraints

8. Sample Queries

 Write useful queries to demonstrate database functionality:


o Search, filter, aggregate data
o Joins across multiple tables
o Data updates or deletes

9. Testing and Validation

 Populate tables with sample data


 Run queries to ensure correctness
 Handle edge cases (e.g., NULLs, empty results, duplicates)

10. Documentation & Presentation

 Prepare a well-organized report or presentation:


o Introduction and goals
o ER Diagram and schema explanation
o SQL scripts
o Sample data and queries
o Screenshots (if a frontend or tool like MySQL Workbench is used)

 Best of Luck 

You might also like