COMP5112 Chap.10 Database Systems and Data Independence
Database Systems and Data Independence
Shared data needs a management layer
A DBMS gives applications a controlled way to store and query organisational data while centralising integrity, concurrency, recovery and access. The chapter diagnoses redundancy and update anomalies in file-based processing, compares hierarchical, network, relational and object-oriented models, and develops physical and logical data independence through layered schemas.
Each feature is tied to the file problem it solves.
Separate application files often repeat the same fact in different formats. When an address changes, every copy must be found and updated consistently. Missing one creates an update anomaly. A new customer may be impossible to record before an order exists, and deleting a final order may erase the only customer details.
These insertion and deletion anomalies show that independent facts have been tied to an unrelated event.
A database management system centralises description and control. A schema records structure and constraints, a query interface retrieves selected data, and transaction facilities coordinate multi-step changes.
Integrity checks reject invalid states; authorisation controls permitted actions; recovery restores committed expectations after failure; concurrency control prevents harmful interleavings. Each facility answers a different risk, so a sound explanation begins with the failure scenario and then names the relevant mechanism.
Transactions form logical units of work.
Atomicity prevents a partial operation from remaining visible, consistency requires declared rules to hold, isolation addresses interference among concurrent actions, and durability protects committed results. These properties should not be treated as interchangeable slogans.
For example, preventing a negative balance is an integrity question, while hiding a salary attribute is a confidentiality question and recording who changed it is an audit question.
Data models organise structure and access differently. Hierarchical systems emphasise parent-child paths, network systems permit richer linked navigation, and relational systems describe data through relations and declarative operations.
Object and object-relational approaches support complex values and behaviour in other ways. Compare models using the same workload, representation needs, query style, standards and dependence on physical navigation rather than merely listing them chronologically.
The three-schema view separates external user views, a shared conceptual design and internal storage.
Physical data independence means changing files, pages or indexes without forcing conceptual and application changes. Logical data independence means revising the conceptual organisation while preserving appropriate external interfaces.
Logical change is often harder because user meanings can be affected, but the distinction clarifies what a DBMS shields from programs.
Views can present selected rows or attributes to a group and stabilise an interface, yet they do not automatically enforce every security or integrity need. Indexes improve particular access patterns but add storage and update cost.
The recurring design method is to identify a concrete requirement, locate the layer responsible for it, and state both benefit and trade-off. This avoids attributing every desirable database property to one undifferentiated management layer.
What this chapter covers
- 01
Database, query and DBMS
- 02
File-processing redundancy
- 03
Integrity and transactions
- 04
Concurrency and recovery
- 05
Database model comparison
- 06
Physical and logical independence
Worked example · free
Remove a duplicated borrower fact
- 2Name the repeated fact and inconsistency.
- 3Choose one authoritative record.
- 3Connect dependent records by key.
Key terms
- Database
- A managed collection of useful organisational data.
- Query
- A request that retrieves or transforms selected database data.
- DBMS
- Software managing storage, queries, control and recovery for a database.
- Data Independence
- Protection of higher interfaces from lower representation changes.
Database Systems and Data Independence FAQ
What is the main problem with duplicated files?
One real fact gains several stored versions that can disagree after an update. The result is an update anomaly, not merely wasted storage, and applications can no longer know which copy is authoritative.
What does physical data independence protect?
It allows storage structures such as file organisation and indexes to change while preserving the logical schema and application queries, so performance tuning does not force costly interface rewrites for users.
Why is logical data independence harder?
Applications depend directly on the meaning and structure of the data they see, so changing logical entities or attributes is harder to hide behind stable views without semantic compromises.
Exam move
For every DBMS feature, write the file-processing failure it addresses. Then classify proposed changes as view, logical or physical before claiming independence. Create short scenarios for update, insertion and deletion anomalies and identify the duplicated fact in each. Separate integrity, confidentiality, concurrency, recovery and auditing in a mechanism table.
When comparing data models, apply one common workload and judge representation, navigation, standards and change isolation using the same criteria.
Working through Database Systems and Data Independence in COMP5112? Sia is AskSia’s AI Computer Science tutor — ask any COMP5112 Database Systems and Data Independence question and get a clear, step-by-step explanation grounded in how COMP5112 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
