Scribd
Upload
8 views

1801198_Tutorial 1_Matthew Lewis Database Design

The document provides an overview of Database Management Systems (DBMS), highlighting their role in managing data, ensuring integrity, and facilitating efficient querying. It differentiates between databases and DBMS, outlines strategic database planning, and details the Database Development Life Cycle (DDLC) tasks. Additionally, it defines key concepts such as entities, attributes, and relationships, and illustrates examples of entities and their relationships in a database context.

Uploaded by

Matthew Lewis
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
8 views

1801198_Tutorial 1_Matthew Lewis Database Design

The document provides an overview of Database Management Systems (DBMS), highlighting their role in managing data, ensuring integrity, and facilitating efficient querying. It differentiates between databases and DBMS, outlines strategic database planning, and details the Database Development Life Cycle (DDLC) tasks. Additionally, it defines key concepts such as entities, attributes, and relationships, and illustrates examples of entities and their relationships in a database context.

Uploaded by

Matthew Lewis
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/ 5

1.

Database Management System (DBMS):


A Database Management System is software that allows users to interact with a database. It
provides a set of tools and mechanisms for creating, retrieving, updating, and managing data in a
database. It also ensures data integrity, security, and facilitates efficient querying.

2. Database vs Database Management System (DBMS):

A database is an organized collection of data, typically stored electronically in a computer


system. It can be as simple as a text file or as complex as a relational database with multiple
interrelated tables.
A DBMS, on the other hand, is a software application that provides an interface for users and
applications to interact with the database. It manages the storage, retrieval, and manipulation of
data in the database.
3. Strategic Database Planning:
Strategic Database Planning involves the process of defining long-term objectives for managing
an organization's data resources. It includes identifying data requirements, ensuring data quality,
and aligning data management with the organization's overall business goals.

(a) Tasks in Database Development Life Cycle (DDLC):


i) Estimating operating costs - Feasibility Study
ii) Writing and testing database application programs - Implementation
iii) Determining technical qualifications - Feasibility Study
iv) Specifying conceptual structure - Conceptual Design
v) Determining files for a report - Requirements Analysis
vi) Entering data - Implementation
vii) Identifying needed information - Requirements Analysis
4. Definitions:
Entity: A distinct object, concept, or thing about which data can be stored. For example, in a
database of students, each student is an entity.
Relationship: Describes how entities are related to each other. It defines connections and
associations between entities.
Attribute: A characteristic or property of an entity. For example, in a "Person" entity, attributes
could be name, age, and address.
Atomic Attribute: An attribute that cannot be further subdivided. For example, a person's age is
an atomic attribute.
Derived Attribute: An attribute whose value is derived from other attributes or data in the
database. For example, the age of a person can be derived from their birthdate.
Multi-Valued Attribute: An attribute that can have multiple values for a single entity. For
instance, a person may have multiple phone numbers.
Composite Attribute: An attribute that can be further divided into sub-attributes. For example, an
address attribute can be broken down into street, city, and zip code.
Examples:

5.
Entity: Person
Name (Atomic Attribute)
Date of Birth (Atomic Attribute)
Contact Numbers (Multi-Valued Attribute)
Address (Composite Attribute: Street, City, Zip Code)
6.
Entities:

Customer

Attributes: CustomerID (Primary Key), Name, Address, Phone


Car
Attributes: CarID (Primary Key), Make, Model, Year, VIN (Vehicle Identification Number)
Accident
Attributes: AccidentID (Primary Key), Date, Location, Description
Insurance Policy
Attributes: PolicyID (Primary Key), PolicyNumber, StartDate, EndDate, CoverageAmount
Premium Payment
Attributes: PaymentID (Primary Key), Amount, DueDate, PaymentDate

Relationships:
Customer owns Car

Type: One-to-Many (A customer can own multiple cars, but a car is owned by one customer)
Foreign Key: CustomerID in Car entity
Car has Accidents

Type: Zero-to-Many (A car can have zero or more accidents)


Foreign Key: CarID in Accident entity
Policy covers Car

Type: Many-to-Many (A policy can cover multiple cars, and a car can be covered by multiple
policies)
Associative Entity: CoveredBy
Attributes in CoveredBy: CoverageID (Primary Key), PolicyID (Foreign Key), CarID (Foreign
Key)
Policy has Premium Payments

Type: One-to-Many (A policy can have multiple premium payments)


Foreign Key: PolicyID in Premium Payment entity
The ER diagram will visually represent these entities, their attributes, and the relationships
between them. Each entity will be represented by a rectangle, and the relationships will be
represented by lines connecting the relevant entities with cardinality indicators (e.g., 1:M, M:N,
etc.).
Remember to label each entity, attribute, and relationship appropriately, and indicate primary
and foreign keys where applicable.

You might also like