Please enable JavaScript.
Coggle requires JavaScript to display documents.
Data Management - Coggle Diagram
Data Management
4.2 Overview of Data Management
4.2.1 The Hierarchy of Data
Bit: Binary digit representing circuit on or off state
Byte: Conventionally comprising eight bits
Character: Fundamental unit of information representing letters, digits, or symbols
Field: Name, number, or combination describing a business object or activity
Record: Cluster of interrelated data fields
File: Compendium of interlinked records or tables
Database: Apex of hierarchy encompassing integrated and interconnected files
4.2.2 Data Entities, Attributes, and Keys
Entity: Broad category for which data is collected
Attribute: Specific characteristics of an entity
Data Item: Actual value of an attribute
FBI Next Generation Identification: Database housing digital facial, fingerprint, and palm images
Primary Key: Field or set of fields that uniquely distinguishes a record
Secondary Key: Field used to speed up finding a specific record
4.2.3 Traditional Approach vs Database Approach
Shared resource example: Federal databases including DNA test results for criminals
Database approach: Multiple application programs share a common pool of data
Traditional approach: Individual data files created and maintained for each application
COMPARATIVE LINK: Traditional Approach vs Database Approach
4.1 Introduction
Database Definition and Value
Albuquerque database: Water bills, crime statistics, and campaign contributions
OPEC, IEA, and UN database: Overseeing global oil supply
Tom Cruise movie database: Actor roles, productions, and endorsements
Definition: Structured repository of data
Database Environment and Governance
Database Management System (DBMS): Suite of programs to manipulate databases
Database Administrator (DBA): IS professional overseeing environment and security
Security breach case: Ivy League college data exposure
Data accuracy error: UK payroll failure affecting 400,000 individuals
IDC digital universe projection: 281 exabytes to 1.8 zettabytes by 2011
4.3 Data Modeling
Database Design Phases
Logical Design: Abstract model identifying relationships and information needs
Physical Design: Refinement for optimal performance, storage, and cost efficiency
Planned data redundancy: Duplicating attributes to enhance query performance
Enterprise Data Modeling: Organizational level analysis of data requirements
COMPARATIVE LINK: Logical Design vs Physical Design
Entity-Relationship (ER) Diagrams
Graphical representation: Boxes represent entities, diamonds represent relationships
Crow's-foot symbol: Denotes one-to-many relationships
Order database example: Salesperson, customer, order, line item, and product relationships
4.4 The Relational Database Model
Tabular Architecture and Domains
Tabular format: Two-dimensional tables called relations
Rows: Represent data entities or records
Columns: Represent attributes or fields
Predefined Domain: Limits permissible values to ensure data accuracy
Market platforms: IBM DB2, Oracle, Sybase, Microsoft SQL Server, Access, and MySQL
Oracle market share: Commands approximately half of the multibillion-dollar industry
Relational Data Manipulation Operations
Selecting: Filtering rows based on specific criteria
Projecting: Reducing the number of columns in a table
Joining: Merging two or more tables via common data attributes
Common data attributes: Department number and Manager SSN linking tables
Real-world application: Travel reservation systems handling millions of daily queries
COMPARATIVE LINK: Selecting vs Projecting vs Joining