INF2603
Assignment 02
(QUIZ & ANSWERS)
Due Date 13 June 2025
, INF2603
Assignment 02
(QUIZ & ANSWERS)
Due Date 13 June 2025
Reconciling Conflicting Goals in Real-World Database Design
Introduction
Real-world database design is an intricate exercise in balancing the theoretical purity of
conceptual models with the pragmatic exigencies of implementation. While the relational
model, a cornerstone of structured data management, offers a robust framework for
ensuring data integrity and consistency, its strict adherence can often clash with critical
non-functional requirements such as performance, operational flexibility, long-term
maintainability, and business agility. This essay delves into the inherent conflicts that
frequently arise in relational database design, illustrates these tensions with concrete
real-world examples, and critically evaluates various strategies employed to reconcile
these divergent objectives. The ultimate goal is to illuminate how database designers
navigate these complexities to construct systems that are both theoretically sound and
practically effective.
4.1 Conflicting Goals in Relational Database Design
Relational database design, despite its foundational strengths in data organization,
inherently faces several conflicting goals that stem from optimizing for different system
attributes:
1. Data Integrity vs. Performance:
o Conflict: The pursuit of high data integrity is typically achieved through
normalization, a process that decomposes large tables into smaller, well-
structured ones to eliminate data redundancy and anomalies (Elmasri &
Navathe, 2016). While normalization significantly enhances data
consistency and reduces storage requirements, it concurrently increases
the number of joins required during data retrieval. Each join operation
Assignment 02
(QUIZ & ANSWERS)
Due Date 13 June 2025
, INF2603
Assignment 02
(QUIZ & ANSWERS)
Due Date 13 June 2025
Reconciling Conflicting Goals in Real-World Database Design
Introduction
Real-world database design is an intricate exercise in balancing the theoretical purity of
conceptual models with the pragmatic exigencies of implementation. While the relational
model, a cornerstone of structured data management, offers a robust framework for
ensuring data integrity and consistency, its strict adherence can often clash with critical
non-functional requirements such as performance, operational flexibility, long-term
maintainability, and business agility. This essay delves into the inherent conflicts that
frequently arise in relational database design, illustrates these tensions with concrete
real-world examples, and critically evaluates various strategies employed to reconcile
these divergent objectives. The ultimate goal is to illuminate how database designers
navigate these complexities to construct systems that are both theoretically sound and
practically effective.
4.1 Conflicting Goals in Relational Database Design
Relational database design, despite its foundational strengths in data organization,
inherently faces several conflicting goals that stem from optimizing for different system
attributes:
1. Data Integrity vs. Performance:
o Conflict: The pursuit of high data integrity is typically achieved through
normalization, a process that decomposes large tables into smaller, well-
structured ones to eliminate data redundancy and anomalies (Elmasri &
Navathe, 2016). While normalization significantly enhances data
consistency and reduces storage requirements, it concurrently increases
the number of joins required during data retrieval. Each join operation
