Mizan-Tepi University

School of Informatics & Computing

Individual Assignment of Fundamental of database
Department of IT
2nd Year 1st semester

Name. Alemu tadele ID: 4704/16

Submitted to Mrs.Tsige A.

1
 Submit on 20/03/2017 E.C

Table
Contents
1. File system vs. DEMS.......................................................................................... 3
2. Data Storage and Management.............................................................................. 3
3. Data Access and Retrieval......................................................................................4
4.Data Integrity........................................................................................................... 5
5. Concurrency and Multi-user Access...................................................................... 5
6. Security................................................................................................................... 6
7. Scalability............................................................................................................... 6
8. Backup and Recovery.............................................................................................7
9. Data Redundancy....................................................................................................7
10.Applications............................................................................................................8
2. Type of data model in database.......................................................................... 9
11.Hierarchical Data Model........................................................................................ 9
12.Network Data Model............................................................................................ 10
13.Relational Data Model..........................................................................................11
14.Object-Oriented Data Model................................................................................ 11
6. Document Data Model......................................................................................... 12
8. Column-Family Data Model................................................................................ 13
9. Graph Data Model................................................................................................ 14

2
1. File system vs. DEMS
The key differences between a File System and a Database
Management System (DBMS) revolve around how data is
stored, managed, and accessed. Here’s a comparison of the two:

1.Data Storage and

Management File System:

 Data is stored as files (e.g., text
files, CSV, images).
 Files are typically managed at the
operating system level.
 There is no centralized management; each file is handled
independently.
 The structure is usually flat, with little to no
relationship between different files unless manually
defined.
DBMS:
 Data is stored in tables with rows and columns, which
are organized into databases.
 It provides a more complex, structured storage model
(e.g., relational, hierarchical).
3
 A DBMS manages data relationships and enforces data
integrity, providing mechanisms for querying, indexing,
and accessing data efficiently.

2. Data Access and Retrieval

File System:
 Data retrival is typically done sequntially or by
searching the file directly.
There is no standardized query
language ;access is
usually thrugh file handling methods of low level
commands.
DBMS:
 A DBMS allows complex queries using structured
query language (SQL) or other query languages.
It provides efficient mechanism for searching, filtering,
and sorting data based on various criteria.

4
3.Data Integrity
File System:

There is no inherent data integrity enforcement; it is up
to the application to ensure the correctness of the data.
DBMS:

A DBMS provides data integrity features like
constraints, normalization, and ACID (Atomicity,
Consistency, Isolation, Durability) properties to ensure
that data is consistent and reliable.

4. Concurrency and Multi-user Access

File System:
 Access control is typically managed by the operating
system, and concurrent access to files can lead to data
inconsistency or corruption if not handled properly.
DBMS:
 A DBMS supports concurrent access by multiple users,
ensuring that transactions are handled safely and that
users can access and modify data without conflicts

5
 through features like locking and transaction
management.

5. Security
File System:
 Security is managed by the operating system, usually
through file permissions and user access control.
DBMS:
 A DBMS offers advanced security features, including
user roles, encryption, authentication, and fine-
grained access control to data, ensuring that only
authorized users can perform certain operations.

6. Scalability
File System:
 Scaling the file system typically involves manually
managing more storage and directories, which can
become complex as the volume of data increases.
DBMS:
 A DBMS is designed to handle large volumes of data
efficiently. It includes mechanisms like indexing,

6
 normalization, and distributed databases to ensure
scalability.

7. Backup and Recovery

File System:
 Backup and recovery procedures are generally
handled at the file level, requiring manual intervention
to ensure data safety.
DBMS:
 A DBMS provides built-in backup and recovery
features, which can automate data backup and
recovery processes,
 ensuring minimal downtime and data loss.

8. Data Redundancy
File System:
 Data redundancy is common, as files can be duplicated
across the system or stored in different formats.
DBMS:
 A DBMS reduces data redundancy through
normalization, ensuring that data is stored efficiently

7
 and that relationships between data are maintained
without unnecessary duplication.

9. Applications
File System:
 Typically used for simpler, unstructured data storage
needs such as documents, images, and other
multimedia files.
DBMS:
 Used for managing large, structured datasets in
applications that require complex querying, reporting,
or data relationships, such as finance, e-commerce,
and enterprise systems.

Summary Table:
In summary, a DBMS provides advanced tools for
managing large, complex datasets, ensuring data
integrity, and supporting concurrent access, whereas a
file system is simpler, more suitable for unstructured
data, and lacks the advanced management features of a

8
DBMS.
 In database systems, a data model defines how data is
structured, stored, and related to each other. There
are several types of data models, each serving
different purposes and offering different ways to
represent and manipulate data.

2. Type of data model in database

Below are the main types of data models used in
databases:

1. Hierarchical Data Model

 Structure: Data is organized in a tree-like structure
where each record has a single parent (except the
root), and each parent can have multiple children.
Example: A company’s organizational structure (CEO ->
Manager -> Employee).
Advantages:

9
 Simple and easy to navigate if data follows a strict
hierarchy.

Disadvantages:
 Difficult to model many-to-many relationships.
 Data redundancy and lack of flexibility.
Example of Use: Early IBM mainframe systems, such as
IMS (Information Management System).

2. Network Data Model

 Structure: Data is organized in a graph structure where
each record can have multiple parent and child
records. Unlike the hierarchical model, records can
have multiple relationships.
Example: A network of cities connected by various roads,
where each city can be connected to multiple other cities.
Advantages:
 More flexible than the hierarchical model and can
handle many-to-many relationships.

10
Disadvantages:
 Complex to design and manage.
 Lack of standardization in representing relationships.
 Example of Use: CODASYL (Conference on Data Systems Languages)
database model.

3. Relational Data Model

 Structure: Data is stored in tables (also called
relations), which consist of rows (records) and
columns (attributes). Relationships between tables are
established using foreign keys.
Example: A student database where "Students" is a table
and "Courses" is another, linked via a relationship table.
 Use Case: Widely used in modern databases like
MySQL, PostgreSQL, Oracle, and SQL Server.

4. Object-Oriented Data Model

 Structure: Data is represented as objects, similar to
how data is represented in object-oriented
programming languages (e.g., Java, C++).

11
Example: An object representing a "Car" with attributes
like make, model, and year, and methods like
"startEngine()".
 Use Case: Suitable for applications requiring complex
data types and relationships, such as CAD systems,
multimedia applications, and systems modeling real-
world objects.

5. Entity-Relationship Model (ER Model)

 Structure: Uses entities (objects or things) and
relationships between them to represent data. ER
diagrams are often used to model database structures
visually.
Example: A university system where "Student" and
"Course" are entities, and the "enrolls" relationship links
them.
 Use Case: Primarily used in the design phase of a
database.

6. Document Data Model

 Structure: Data is represented as documents, typically
in formats like JSON, BSON, or XML. Each document is
a self-contained unit of data.

12
Example: A collection of JSON objects where each
document represents a product in an e-commerce
system.
 Use Case: Used in NoSQL databases like MongoDB,
where flexible, semi-structured data is handled.
7. Key-Value Data Model
 Structure: Data is stored as key-value pairs, where
each key is unique and points to a value (which can be
a simple data type or complex data).
Example: A dictionary or hash map in programming,
where a key (e.g., "user123") maps to a value (e.g., user's
data).
 Use Case: Used in NoSQL databases like Redis and
DynamoDB, ideal for fast look ups and caching systems.

8. Column-Family Data Model

 Structure: Data is stored in columns rather than rows,
and columns are grouped into column families. This
model is efficient for reading and writing large
amounts of data.
Example: A "User" column family may have columns like
"name", "email", and "birthdate".

13
 Use Case: Used in NoSQL databases like Cassandra and
HBase for large-scale, distributed storage.

9. Graph Data Model

 Structure: Data is stored as nodes (entities) and edges
(relationships), suitable for representing complex,
interconnected data.
Example: A social network where users are nodes, and
their connections (friends, followers) are edges.
 Use Case: Used in graph databases like Neo4j and
Amazon Neptune, ideal for social networks,
recommendation engines, and semantic web
applications.
 Each of these data models is suited for specific types
of applications, and the choice of a data model
depends on the complexity of the data and the
operations needed.

14