Scribd
Upload
20 views2 pages

Guidelines for Database Project

The document outlines guidelines for a database project, covering objectives, design, implementation, testing, and documentation. It emphasizes the creation of an Entity-Relationship Diagram, schema mapping, and the selection of a suitable database management system. Additionally, it details the importance of data integrity, functional testing, and comprehensive documentation of the database design and SQL scripts.

Uploaded by

guyoboru12345
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
20 views2 pages

Guidelines for Database Project

The document outlines guidelines for a database project, covering objectives, design, implementation, testing, and documentation. It emphasizes the creation of an Entity-Relationship Diagram, schema mapping, and the selection of a suitable database management system. Additionally, it details the importance of data integrity, functional testing, and comprehensive documentation of the database design and SQL scripts.

Uploaded by

guyoboru12345
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/ 2

Guidelines for Database Project

1. Introduction

1.1. Objective of the project

2. Database Design

a. Conceptual Design:

 Entity-Relationship Diagram (ERD): Create an ERD to visually represent the


entities (objects) and their relationships within the system.
o Identify entities.
o Define the relationships, like one-to-many or many-to-many.

b. Logical Design:

 Mapping Database Schema


 Normalization

3. Implementation(Physical database design )

a. Database Platform Selection

 Choose a suitable database management system (DBMS) based on your project


requirements. Common DBMS options include:
o Relational DBMS: MySQL, or Sql server

b. Schema Creation:

 Implement the schema defined in the logical design in your chosen DBMS. Create
tables, define relationships, primary keys, foreign keys, and constraints.

c. Data Entry:

 Populate the database with sample data, ensuring it accurately reflects real-world
scenarios.
 Use INSERT statements to add initial records.

d. SQL Queries:
 Write SQL queries for various functions (e.g., retrieving, updating, deleting data).
o For example, retrieve a list of all customers who placed orders in the last
month.
 Implement stored procedures, triggers, or views if necessary, based on project
requirements.

4. Testing and Validation

a. Data Integrity:

 Ensure that all relationships between tables are enforced and that there is no
inconsistent or erroneous data in the system.
 Test for referential integrity (e.g., no orphan records in the Mysql table if a Customer
is deleted).

b. Functional Testing:

 Test whether all required functionalities (queries, reports, CRUD operations) are
working as expected.
 Verify the system behaves correctly under normal and edge-case conditions..

5. Documentation

a. Database Design Documentation:

 Document your ERD, schema, table definitions, relationships, and any special design
considerations.
 Include descriptions for each table, column, and relationship.

b. SQL Scripts:

 Provide the SQL scripts for creating the database, inserting sample data, and
performing operations like queries or updates.
 Include stored procedures, triggers, or views if applicable

You might also like