0% found this document useful (0 votes)
15 views9 pages

Database Presentation

Uploaded by

saniayasmeen004
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views9 pages

Database Presentation

Uploaded by

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

 DATABASE

BS-IT
2nd SEMISTER

GROUP-I members:
Areeba khan , Ajwa , Sania yasmeen , Sania
maqbool , Almas .
DATE: 23/7/2024
WHAT’S DATABASE ?
• A database is an electronically stored, systematic collection of data. It can contain
any type of data, including words, numbers, images, videos, and files. You can use
software called a database management system (DBMS) to store, retrieve, and edit
data.
Advantages of Databases :
• Minimum data redundancy.
• Improved data security.
• Increased consistency.
• Lower updating errors.
• Reduced costs of data entry, data storage, and data retrieval.
• Improved data access using host and query languages.
• Higher data integrity from application programs.
In the context of a database, these terms have specific meanings and are foundational concepts in the
relational database model:
• Relation: A relation is essentially a table in a database. It consists of rows and columns where
each row represents a unique record, and each column represents a field or attribute. In relational
database theory, a relation is a set of tuples that have the same attributes.
• Tuple: A tuple is a single row in a table, which represents a single record or instance of the entity
that the table describes. Each tuple is a set of attribute values. For example, in a table of employees, a
tuple would contain all the information about a single employee.
• Entities: An entity is an object or thing in the real world that is distinguishable from other objects. In
a database, an entity is typically represented by a table. For example, an "Employee" might be an
entity, and each employee in the company would be a record (or tuple) in the Employee table.
• Attribute: An attribute is a column in a table, representing a specific property or characteristic of
the entity. For example, in an Employee table, attributes might include EmployeeID, Name, Position,
and Salary. Each attribute holds values that describe the entity.
To summarize:
• Relation (Table): A set of tuples with the same attributes.
• Tuple (Row): A single record in a relation.
• Entity: An object or thing being described, typically represented by a relation.
• Attribute (Column): A property or characteristic of an entity.
Relationships in database:
• 1. One-to-One (1:1): In a one-to-one relationship, each instance of Entity A is associated
with exactly one instance of Entity B, and vice versa. o Example: A "Person" entity and a
"Passport" entity might have a one-to-one relationship if each person can only have one
passport and each passport is assigned to only one person.
• 2. One-to-Many (1): In a one-to-many relationship, each instance of Entity A can be
associated with multiple instances of Entity B, but each instance of Entity B is associated
with only one instance of Entity A. o Example: A "Department" entity and an "Employee"
entity where each department can have multiple employees, but each employee belongs
to only one department.
• 3. Many-to-One (N:1): In a many-to-one relationship, multiple instances of Entity A can
be associated with one instance of Entity B, but each instance of Entity B is associated
with only one instance of Entity A. o Example: An "Order" entity and a "Customer" entity
where each customer can place multiple orders, but each order is placed by only one
customer.
• 4. Many-to-Many (M): In a many-to-many relationship, multiple instances of Entity A can
be associated with multiple instances of Entity B. o Example: A "Student" entity and a
"Course" entity where students can enroll in multiple courses, and each course can have
multiple students enrolled.
College Management System
A College Management System (CMS) is an integrated software solution designed to
streamline and manage the various administrative and academic operations of a college or
university. This system typically encompasses a wide range of functionalities, including
student information management, course management, faculty management, fee
management, attendance tracking, examination management, and more.
Components of a College Management System
Student Management:
 Enrollment and registration
 Student profiles
 Attendance tracking
 Academic performance records
Course Management:
 Course creation and scheduling
 Syllabus management
 Class assignments
 Exam scheduling and grading
 Faculty Management:
 Faculty profiles
 Course assignments
 Attendance tracking
 Performance evaluation
 Fee Management:
 Fee structure setup
 Fee collection and tracking
 Financial reports
 Library Management:
 Book cataloging
 Issue/return tracking
 Membership management
 Hostel Management:
 Room allocation
 Hostel fee management
 Student tracking
ERD:
ERD stands for entity relationship diagram. People also call these types of diagrams ER diagrams and Entity Relationship
Models. An ERD visualizes the relationships between entities like people, things, or concepts in a database.
ERD OF COLLEGE BASE MANAGEMENT SYSTEM:
• to create an ERD (Entity-Relationship Diagram) for the provided database schema, we'll focus on five key entities and their
relationships:
• College
• Department
• UserAccounts
• Staff
• Student
• We will include additional entities as needed to illustrate the relationships. Here's how these entities relate to each other:
• College does not have direct relationships in the provided schema, so it will be standalone.
• Department has a relationship with Staff.
• UserAccounts is related to Staff and Student.
• Staff is related to Department and UserAccounts.
• Student is related to Class, Term, StudyScheme, and UserAccounts.
CollegeID
(PK) DepartmentName Role Status

College Department
has has UserAccounts

Belongs Username
to
CollegeName
UserID
FirstName Staff
DepartmentID
,UserID
teaches Phone
SalaryType Number
/ Address
Student
ClassID
FirstName / Gender
LastName
Address Enrollment
Date
THE END

You might also like