March 17, 2025

University of Saint Thomas of

Mozambique

The Evolution of File

Systems in Data Processing

STUDENTS: EILAN AQUILA & OSSAMA BOUABID

TEACHER: ANTONIO SIMBINE
Table of Content
Introduction…………………………………………………………………………..1

1. Manual File Systems…………………………………………………………..2

2. Computerized File Systems…………………………………………………...2
3. File System Redux: Modern End-User Productivity Tools…………………3
4. Structural Dependence………………………………………………………..4
5. Data Dependence: An Advancement on Database Systems………………...4
6. Data Redundancy……………………………………………………………...6
7. Poor Database Design and Data Modeling…………………………………..7
8. Conclusion……………………………………………………………………..8
The Evolution of File Systems in Data
Processing
Introduction
File systems have been a fundamental component of data processing, evolving to meet the
increasing demands of storage, accessibility, and security. From early manual storage methods
like punched cards to modern cloud-based and distributed file systems, their development
reflects technological advancements and the growing complexity of data management. As
computing needs expanded, file systems adapted to support faster access, multi-user
environments, and large-scale data processing. This evolution has played a critical role in
shaping how organizations and individuals store, retrieve, and manage digital information
efficiently.
1. Manual File Systems
A manual file system refers to a paper-based method of storing and managing records.
Organizations historically relied on this method for record-keeping before the advent of
computers.

Advantages of Manual File Systems

1. Simplicity – Requires no technical knowledge or expensive software.

2. No Electronic Dependency – Useful in areas with no electricity or digital infrastructure.
3. Security – Physical records are less vulnerable to cyber threats, though they can be lost
or stolen.

Disadvantages of Manual File Systems

1. Inefficiency – Searching for records is time-consuming compared to digital databases.

2. Lack of Backup – Paper records can be destroyed by fire, water damage, or loss.
3. Limited Accessibility – Records can only be accessed in one location, making remote
work difficult.

2. Computerized File Systems

A computerized file system is a digital method of organizing, storing, and retrieving data using a
structured approach. Over time, database management systems (DBMS) have evolved as a more
advanced alternative to traditional computerized file systems.

Advantages of Computerized File Systems

1. Faster Access – Compared to manual systems, computerized file systems allow quick
data retrieval.
2. Storage Efficiency – Digital storage reduces physical space requirements.
3. Improved Organization – Files can be categorized and indexed for better management.

Limitations of Computerized File Systems

1. Data Redundancy – The same data may be stored in multiple files, leading to
duplication.
2. Limited Data Integrity – No structured enforcement of data consistency.
3. Security Risks – Files may lack strong authentication and encryption mechanisms.
4. Scalability Issues – As data grows, retrieval becomes inefficient without advanced
indexing.
3. File System Redux: Modern End-User Productivity Tools
The evolution of data management has transitioned from manual file systems to advanced
database management systems (DBMS). However, the widespread use of personal productivity
tools, particularly spreadsheet applications like Microsoft Excel, has reintroduced challenges
reminiscent of early file systems. This phenomenon, termed "File System Redux," highlights the
resurgence of data redundancy, inconsistency, and security issues in modern contexts.

Challenges of Using Spreadsheets as Databases

Utilizing spreadsheets as de facto databases introduces several issues:

1. Data Redundancy and Inconsistency: Multiple versions of the same data can exist
across various spreadsheets, leading to discrepancies and errors.
2. Lack of Data Integrity: Spreadsheets lack robust mechanisms to enforce data validation
rules, increasing the risk of inaccurate data entry.
3. Security Vulnerabilities: Sensitive information stored in spreadsheets may not be
adequately protected, making it susceptible to unauthorized access.
4. Collaboration Limitations: Concurrent access by multiple users is challenging, often
resulting in version control issues.

Modern Database Tools for End-Users

To counter spreadsheet limitations, structured database tools like Kexi, Database Workbench,
and DBeaver offer secure, scalable, and user-friendly data management.

By adopting proper database solutions, organizations can ensure efficient, secure, and scalable
data management in an increasingly data-driven world.

Structural Dependence and Data Dependence in DBMS

Structural dependence and data dependence are key concepts in database management systems
(DBMS). They describe how a database’s structure and its data interact, as well as how changes
in one aspect affect the other.
4. Structural Dependence
Structural dependence refers to the tight coupling between a database’s structure (e.g., tables,
fields, and relationships) and the way data is stored and accessed. In systems with structural
dependence, any changes to the database structure require modifications to the application
programs that interact with the data.

Example:

If a column is added or removed from a table, the application that retrieves or processes this data
must be updated to accommodate the change.

Problems with Structural Dependence:

 Lack of flexibility: Any structural change requires reworking existing applications,

which can be costly and time-consuming.
 Maintenance challenges: As databases grow, frequent structural changes make it
difficult to maintain both the application and the database.

5. Data Dependence: An Advancement on Database Systems

Data dependence refers to how closely an application is tied to the physical storage format of the
data. In systems with high data dependence, changes in the way data is stored (e.g., file format or
storage location) directly impact how applications retrieve, update, or manipulate the data.

Example:

In traditional file systems, if the format or storage method of data changes, the application must
also be modified to maintain access.

Problems with Data Dependence:

 Rigid data access: Applications are tightly bound to the data storage format, making
modifications difficult.
 Lack of abstraction: Any changes to the physical storage require updates to the
applications, increasing maintenance efforts and costs.
Impact on Modern DBMS

Modern Database Management System (DBMS) aim to eliminate structural and data dependence
by introducing abstraction layers that separate application logic from data structure and storage.
It is a structured approach to handling data, offering better efficiency, integrity, and security than
simple file storage.

Unlike computerized file systems, DBMS ensures centralized data management and allows
multiple users to access and manipulate data concurrently. Examples include MySQL,
PostgreSQL, and Microsoft SQL Server.

Advantages of Database Systems over File Systems

1. Data Integrity – Ensures accuracy and consistency through normalization.

2. Reduced Redundancy – Centralized data storage minimizes unnecessary duplication.
3. Enhanced Security – Encryption, authentication, and access controls protect sensitive
data.
4. Flexibility: Changes to the database structure do not require modifications to application
programs.
5. Easier maintenance: Applications and databases can evolve independently.
6. Efficient Query Processing – SQL and NoSQL databases allow fast, structured
searches.
7. Scalability – Databases can manage large volumes of data efficiently without affecting
existing systems.

Contributions from Coronel, Morris, & Rob (9th Edition)

The ninth edition of Database Systems: Design, Implementation, & Management emphasizes the
transition from traditional file systems to modern DBMS by highlighting:

 The need for data independence, where logical data structures are separated from
physical storage mechanisms.
 The role of metadata management in organizing and maintaining large data
repositories.
 The advantages of multi-user database environments, supporting simultaneous access
while maintaining consistency through ACID (Atomicity, Consistency, Isolation,
Durability) properties.
6. Data Redundancy
Data redundancy refers to the unnecessary repetition or duplication of data within a database or
storage system. It occurs when the same piece of data is stored in more than one location, leading
to inefficiency and wasted storage space.

Causes of Data Redundancy:

1. Lack of Normalization – Poor database structuring results in similar information or data

being stored in multiple places.
2. Multiple Systems or Departments – Different departments may store identical data
independently, leading to redundancy such as customer details in both sales and
marketing databases.
3. Manual Data Entry – When data is manually entered across different systems, there is a
higher chance duplication can occur.

Problems with Data Redundancy:

1. Wasted Storage – Unnecessary data duplication consumes disk space and system
resources.
2. Inconsistent Data – Updating redundant data in one place but not another can create
inconsistencies or errors across systems.
3. Increased Maintenance Costs – When managing multiple copies of the same data, more
resources are required to maintain, back up and update them which consequently
increases the complexity and cost.
4. Slower Performance – Excessive data in a system can slow down queries and system
processing especially if it needs to be processed repeatedly.

In general, while redundancy should be minimized in database design to improve efficiency and
consistency, it is sometimes necessary for backup and fault tolerance purposes (reliability and
availability).
 7. Poor Database Design and Data Modeling
Lack of proper design and data modeling skills in database development can lead to significant
issues such as inefficiency, inconsistency, and high maintenance costs. Here are some points that
should be avoided:

Problems from Poor Database Design:

1. Data Redundancy – Improper modeling results in redundant data, increasing storage

needs and inconsistency risks.
2. Data Inconsistency – Poorly structured databases lead to conflicting versions of the
same data which happens when updates are not properly managed or enforced.
3. Poor Data Integrity – Weak relationships and constraints make data unreliable,
becoming harder to maintain accurate and valid data.
4. Scalability Issues – Improper designs lead to inefficient databases that struggle with
performance as data volume increases, leading to slow performance and difficulties
handling larger volumes of data.
5. Complex Maintenance – Poor design make maintaining it harder. Updates, migrations,
and even simple queries become difficult to manage.
6. Inefficient Queries – Because of lack of indexing and normalization, queries results are
slow and resource-intensive.
7. Increased Costs – Fixing poor designs is expensive and time-consuming especially if the
system has already been built.

And for points that should be integrated more:

Importance of Proper Database Design:

1. Normalization – Reduces redundancy and improves data organization.

2. Clear Relationships – Defines entity relationships for easier querying and maintaining.
3. Integrity Constraints – Ensures rule following, data consistency and accuracy.
4. Scalability – Allows efficient handling of growing data volumes and system loads.
5. Optimized Performance – Enhances speed and performance with indexing and
structured queries.
8. Conclusion
Poor database design, data redundancy, and structural and data dependence contribute to
inefficiency, inconsistencies, and high maintenance costs in database management. The
evolution of file systems, from manual paper-based storage to advanced cloud-based solutions,
has significantly improved data handling. However, challenges persist, particularly with the
misuse of spreadsheets as databases, which reintroduces redundancy, security risks, and
inefficiencies.

Modern database management systems (DBMS) address these issues by implementing best
practices such as normalization, indexing, and data independence. These approaches ensure
scalability, flexibility, and optimized performance while maintaining data accuracy and security.
Moving forward, organizations must adopt robust database strategies to enhance accessibility,
streamline maintenance, and support efficient, structured, and secure data management in an
evolving digital landscape.
References
 Coronel, C., Morris, S., & Rob, P. (2011). Database Systems: Design, Implementation, &
Management (9th ed.). Cengage Learning.
 Silberschatz, A., Galvin, P. B., & Gagne, G. (2018). Operating System Concepts (10th
ed.). Wiley.
 Tanenbaum, A. S., & Bos, H. (2014). Modern Operating Systems (4th ed.). Pearson.
 Ghemawat, S., Gobioff, H., & Leung, S. T. (2003). "The Google File System." ACM
Symposium on Operating Systems Principles (SOSP).
 Shvachko, K., Kuang, H., Radia, S., & Chansler, R. (2010). "The Hadoop Distributed
File System." IEEE 26th Symposium on Mass Storage Systems and Technologies (MSST).
 Date, C. J. (2019). An Introduction to Database Systems. Pearson.
 Coronel, C., Morris, S., & Rob, P. (2022). Database Systems: Design, Implementation, &
Management. Cengage Learning.
 KDE UserBase Wiki: "Kexi"
 Calligra Suite: "Kexi"
 KDE.news: "Kexi 3.1 Brings Database Application Building to Windows"
 W3Schools. (n.d.). DSA - Introduction. W3Schools.
https://www.w3schools.com/dsa/dsa_intro.php