What do you mean by managing data resource? Outline the advantages of a Database Management Approach to manage the Data Resource of Business compared with a File Processing Approach.
20 marks · directive: Outline
The core of a good answer
Managing the data resource means treating data as a shared organisational asset, planned, stored, secured and governed through data administration and database technology; compared with separate application files, the database approach cuts redundancy and inconsistency, enables sharing and ad hoc queries, enforces integrity and security, and gives program-data independence.
An outline written by upsc.help, not an official UPSC answer; every fact checked by a separate review. How we work
What the question asks
5 marks for the meaning of data resource management (data as an asset, data administration, DBMS, data warehouses and governance); 15 marks for a structured comparison: the problems of the file processing approach and the advantages a DBMS brings for each.
Answer outline
Introduction
Data resource management is the managerial activity that applies information technology and policies to manage an organisation's data as a strategic resource, so that accurate, consistent and secure data is available to all authorised users.
Meaning of managing data resource
- Data planning: enterprise data models and standards (common definitions of customer, product, employee).
- Data administration and database administration: ownership, quality, access rights, backup and recovery.
- Technologies: DBMS, data dictionary, data warehouses and data marts, data mining and analytics.
- Data governance, privacy and security compliance.
File processing approach and its problems
- Each application (payroll, billing, inventory) keeps its own files, written in programs tied to the file structure.
- Data redundancy: the same data is stored many times.
- Data inconsistency: updates in one file are not reflected in others.
- Program-data dependence: changing a file format means changing every program that uses it.
- Poor sharing and integration across departments; ad hoc queries need new programs.
- Weak security, integrity and concurrency controls; high maintenance cost.
Advantages of the database management approach
- Reduced redundancy and better consistency through a single integrated database.
- Data sharing among many applications and users with a common view of the business.
- Program-data independence: schema changes do not require rewriting applications.
- Data integrity through constraints and validation rules defined once in the DBMS.
- Centralised security: user authorisation, views, encryption and audit trails.
- Ad hoc querying and reporting with query languages such as SQL; faster decision support.
- Concurrency control, backup and recovery for multi-user transaction processing.
- Standardisation through a data dictionary; lower application development and maintenance cost.
- Foundation for data warehousing, analytics and ERP systems.
Limitations to note
- Higher initial cost of DBMS software, hardware and skilled staff.
- Complexity; a central database is a single point of failure unless backed up and secured.
- Organisational resistance and need for data governance.
Conclusion
The database approach turns scattered application data into a managed corporate resource; its costs are justified where data is shared widely and decisions depend on consistent information.
Examples and data to cite
- Edgar F. Codd of IBM described the relational model of data (main paper 1970); SQL was pushed as the standard language for relational databases.
- A bank's customer database shared by savings, loan and card systems avoids the inconsistent addresses typical of separate files.
Facts to remember
- DBMS functions: data definition, update, retrieval and administration (security, integrity, concurrency control, recovery), with a data dictionary of metadata.
- Three-level architecture: external, conceptual and internal levels; changes at one level should not affect the levels above (data independence).
- ACID properties of transactions: atomicity, consistency, isolation, durability.
- Database administrators define data structures, set storage and security parameters, tune performance and manage backup and restore.