IT Module 1

1. differentiate among terms used in Information Management; For example, fields, records, tables,
files, database and database management system.
Fields: A field is a single piece of data or attribute within a record that stores a specific type of information (such as
a name, date, or number).

Records: A record is a complete set of related fields that contains all the information about one entity or item in a
database.

Tables: A table is a collection of related records organized in rows and columns, where each row represents a
record and each column represents a field.

Files: A file is a collection of related records stored together, which can be organized in different ways such as
serial, sequential, indexed sequential, or random/direct.

Database: A database is an organized collection of related tables that stores data in a structured way to eliminate
redundancies and facilitate efficient data handling, processing, searching, and retrieval.

Database Management System (DBMS): A database management system is software that provides the tools and
functionality to create, manage, organize, store, retrieve, and manipulate data within a database while ensuring
data quality, integrity, and security.
DBMS ──manages──> DATABASE ──contains──> TABLES/FILES ──consist
of──> RECORDS ──made up of──> FIELDS
1950s - 1960s: Early Computing Era
Storage Devices:

● Punched Cards (1950s): Text-based data storage with holes representing binary data
● Magnetic Tape (1950s-1960s): Sequential access, storing text-based data
● Magnetic Drums (1950s): Early form of random access storage

Data Format: Primarily text-based (alphanumeric characters)

Volume: Kilobytes (KB) to low Megabytes (MB)

Access Method: Sequential access (slow, must read data in order)

Speed: Very slow - seconds to minutes for data retrieval

1970s: Disk Storage Revolution
Storage Devices:

● Floppy Disks (1971): Portable, removable storage (initially 8-inch, later 5.25-inch)
● Hard Disk Drives (HDD) (1970s): Fixed magnetic storage with better capacity

Data Format: Text-based with early structured data files

Volume: Hundreds of KB to low MB

Access Method: Direct/Random access becomes more common

Speed: Faster than tape - milliseconds to seconds

Compression: Minimal compression utilities available

1980s: Personal Computing Era
Storage Devices:

● 3.5-inch Floppy Disks (1980s): 1.44 MB capacity, widely adopted

● Hard Drives (expanding): 10-40 MB typical for PCs
● CD-ROM (late 1980s): 650-700 MB optical storage

Data Format: Text-based expanding to early graphics and simple multimedia

Volume: MB range (1-100 MB typical)

Access Method: Random access standard; indexed sequential file organization

Speed: Improved - HDDs with faster seek times

Compression: Early compression utilities emerge (e.g., PKZIP for files)

1990s: Multimedia Explosion
Storage Devices:

● CD-ROM (widespread): 650-700 MB for multimedia applications

● Hard Drives: 500 MB to several GB
● DVD (late 1990s): 4.7 GB (single layer), 8.5 GB (dual layer)
● Zip Drives (mid-1990s): 100-250 MB removable storage

Data Format: Full multimedia - text, graphics, audio, video, animations

Volume: GB range becoming standard

Access Method: Random/direct access; network access methods developing

Speed: Much faster - improved HDD rotation speeds (5400-7200 RPM)

Compression: Advanced compression utilities (WinZip, WinRAR); JPEG, MP3, MPEG for multimedia
2000s: Digital Media Era
Storage Devices:

● USB Flash Drives (early 2000s): 16 MB to 256 GB, highly portable

● External HDDs: Hundreds of GB to TB
● DVD-R/RW: Writable optical media
● Blu-ray (mid-2000s): 25-50 GB high-definition storage
● Memory Cards (SD, microSD): For cameras, phones

Data Format: High-resolution multimedia - HD video, high-quality audio, complex graphics

Volume: GB to TB range

Access Method: Fast random access; network-based retrieval (FTP, HTTP); cloud storage emerges

Speed: Significantly faster - 7200-10000 RPM HDDs; USB 2.0 transfer speeds

Compression: Sophisticated algorithms (7-Zip, lossless/lossy formats); streaming compression

2010s: Cloud and Solid State Era

Storage Devices:

● Solid State Drives (SSD): No moving parts, extremely fast (120 GB to 4 TB+)
● Cloud Storage: Online storage (Dropbox, Google Drive, OneDrive)
● Large Capacity HDDs: 1-10+ TB for archives
● High-capacity Flash: USB drives and SD cards up to 1 TB+

Data Format: Ultra-high-definition multimedia (4K video, lossless audio, 3D graphics, VR content)

Volume: TB to Petabytes (PB) in enterprise/cloud

Access Method:

● Direct access with SSDs (no seek time)

● Cloud-based access from anywhere
● Database management systems with complex queries

Speed: Extremely fast

● SSDs: Read/write speeds 500+ MB/s

● USB 3.0/3.1: Up to 10 Gbps
● Network speeds improving significantly

Compression:

● Real-time compression
● Advanced codecs (H.264, H.265)
● Cloud-based compression utilities
2020s - Present: Big Data and Beyond
Storage Devices:
● NVMe SSDs: Ultra-fast PCIe-based storage (read speeds 3000+ MB/s)
● Cloud Storage Platforms: Massive scalability (Amazon S3, Azure, Google Cloud)
● Large Capacity SSDs: 8-30+ TB
● Enterprise Storage Arrays: Petabyte-scale storage systems
Data Format:
● Massive multimedia files (8K video, 360° video, AR/VR)
● Big Data (structured, semi-structured, unstructured)
● IoT sensor data streams
● AI/Machine learning datasets
Volume: TB for personal use; PB to Exabytes (EB) for enterprises
Access Method:
● Instant access with NVMe technology
● Distributed cloud access
● Data warehouses and data lakes
● Real-time streaming and processing
Speed: Blazing fast
● NVMe SSDs: 3000-7000+ MB/s
● 5G networks for mobile
● Fiber optic connections for cloud
● USB 4.0 and Thunderbolt 4
Compression:
● AI-powered compression
● Automatic cloud optimization
● Real-time data deduplication
● Advanced video codecs (AV1, VP9)
 Key Changes Summary:
Aspect 1950s-1970s 1980s-1990s 2000s-2010s 2020s+

Format Text-based Text + graphics Multimedia Big Data + Ultra-HD

Volume KB - MB MB - GB GB - TB TB - PB - EB

Access Sequential Random/Direct Fast random + Network Instant + Cloud

Speed Seconds- Milliseconds-Seconds Very fast Near-instantaneous

Minutes

Devices Tape, Cards Floppy, HDD, CD DVD, Flash, External HDD SSD, NVMe, Cloud
3. explain the advantages of using a database approach compared to using traditional file processing; Advantages including speed,
efficiency, cost; data quality: completeness, validity, consistency, timeliness and accuracy; data handling, data processing.
 Aspect Traditional File Processing Database Approach Advantages of Database

SPEED

Data Slower - must search through entire Faster - optimized queries Up to 100x faster for
complex searches
Retrieval files sequentially or use complex retrieve specific data quickly
indexing using SQL

Search Linear search through files; time- Indexed searches; multiple Instant retrieval with
proper indexing
Operations consuming for large datasets access paths available

Multi-user Slow - file locking causes delays Fast - concurrent access with Simultaneous access
without bottlenecks
Access when multiple users access same file minimal locking
 Aspect Traditional File Processing Database Approach Advantages of
Database
Query Capability Limited - requires custom programming for each Powerful - SQL enables Ad-hoc queries possible
query complex queries easily

Data Manipulation Complex - requires procedural code Simple - declarative SQL Faster development
statements

Transaction Processing Risky - no guarantee of atomicity Reliable - ACID properties Guaranteed consistency
ensure data integrity

Reporting Difficult - custom report programs needed Easy - report generation tools Flexible reporting
integrated

Data Mining Nearly impossible - data scattered across files Feasible - centralized data Business intelligence capabilities
enables analysis

Sorting/Filtering Slow - must process entire files Fast - indexes enable efficient Optimized performance
operations

Data Aggregation Manual - requires programming to summarize Built-in - aggregate functions Instant summaries
readily available
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA HANDLING

Data Sharing Difficult - files not designed for Easy - multiple users and Promotes
sharing applications access same data collaboration

Data Integration Complex - requires custom Simple - queries join data from Seamless
programs to combine files multiple tables integration

Data Security Basic - file-level permissions Advanced - granular access Enhanced

only control (table, row, column security
level)

Backup/Recovery Manual - each file backed up Automated - centralized backup Reliable data
separately and recovery procedures protection

Data Independence Low - programs depend on file High - physical storage Flexible
structure independent of logical structure architecture

Concurrent Access Limited - file locking prevents Excellent - multiple users work Better
simultaneous access simultaneously productivity
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA QUALITY:
ACCURACY

Data Entry Errors Common - limited Reduced - validation Up to 90% fewer

validation in file rules catch errors at errors
systems entry

Calculation Accuracy Varies - different Consistent - Reliable

programs may calculations computations
calculate differently performed uniformly

Data Verification Manual - requires Automated - triggers Built-in accuracy

separate checking and constraints verify checks
processes data

Error Correction Difficult - must find Easy - correct once in Simplified error
and fix in multiple centralized location management
locations
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA QUALITY:
TIMELINESS

Real-time Updates Delayed - batch Immediate - Up-to-date

processing common; transactions information always
files updated committed in real-
periodically time

Data Freshness Stale - reports may Current - queries Real-time decision

use outdated file access latest data making
versions

Synchronization Manual - requires Automatic - single No synchronization

effort to sync multiple source of truth lag
files

Reporting Scheduled - reports On-demand - current Instant access to

generated at specific reports available latest data
intervals anytime
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA QUALITY:
CONSISTENCY

Data Updates Inconsistent - same Consistent - single Eliminates

data in multiple files update affects all contradictions
may not match references

Data Standards Vary by application - Uniform - database Standardized

no uniform approach enforces standards formats

Concurrent Updates Conflicts possible - no Controlled - Maintains integrity

coordination between transaction during multi-user
programs management updates
prevents conflicts

Data Anomalies Common - insertion, Rare - normalization Anomaly-free

deletion, update prevents anomalies operations
anomalies occur
Aspect Traditional File Processing Database Approach Advantages of
DATA QUALITY: Database
VALIDITY

Data Type Control Weak - programs Strong - data types Prevents type errors
may accept invalid strictly enforced at
data types database level

Value Validation Inconsistent - each Consistent - CHECK Guarantees valid

program implements constraints ensure data
own rules valid values

Referential Integrity Not enforced - Enforced - foreign Maintains data

orphaned records keys prevent invalid relationships
common references

Domain Constraints Difficult to implement Built-in - domain rules Ensures acceptable

across multiple files applied universally values
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA QUALITY:
COMPLETENESS

Required Fields Difficult to enforce - Easy to enforce - 100% completeness

each program constraints ensure all achievable
handles validation required data is
separately entered

Missing Data Common - no Rare - NOT NULL Eliminates gaps in

centralized control constraints prevent critical data
over data entry omissions

Data Coverage Incomplete - different Complete - relational Comprehensive data

files may have partial structure links all availability
information relevant data
 Aspect Traditional File Processing Database Approach Advantages of
COST Database

Initial Setup Lower - simple file Higher - DBMS Database pays off
systems are software and training long-term
inexpensive required

Maintenance Cost Higher - requires Lower - centralized 30-40% lower

more programmer maintenance reduces ongoing costs
time for updates labor

Storage Cost Higher - redundant Lower - efficient Reduced hardware

data requires more storage reduces investment
storage hardware hardware needs

Training Cost Lower initially - Higher initially - ROI achieved through

simpler concepts requires specialized efficiency
knowledge
 Aspect Traditional File Processing Database Approach Advantages of
Database
DATA QUALITY:
COMPLETENESS

Required Fields Difficult to enforce - Easy to enforce - 100% completeness

each program constraints ensure all achievable
handles validation required data is
separately entered

Missing Data Common - no Rare - NOT NULL Eliminates gaps in

centralized control constraints prevent critical data
over data entry omissions

Data Coverage Incomplete - different Complete - relational Comprehensive data

files may have partial structure links all availability
information relevant data
 Aspect Traditional File Processing Database Approach Advantages of
Database
COST

Initial Setup Lower - simple file Higher - DBMS software Database pays off long-
systems are and training required term
inexpensive

Maintenance Cost Higher - requires more Lower - centralized 30-40% lower ongoing
programmer time for maintenance reduces costs
updates labor

Storage Cost Higher - redundant data Lower - efficient storage Reduced hardware
requires more storage reduces hardware investment
hardware needs

Training Cost Lower initially - simpler Higher initially - requires ROI achieved through
concepts specialized knowledge efficiency

Long-term TCO Higher - accumulates Lower - efficiency gains 50-70% cost savings
due to inefficiencies compound over time over 5+ years
 Aspect Traditional File Processing Database Approach Advantages of
Database
EFFICIENCY

Data Redundancy High - same data Minimal - data stored Eliminates 60-80% redundancy
duplicated across once and referenced as
multiple files needed

Storage Utilization Inefficient - wasted space Efficient - normalized 30-50% less storage required
due to duplication structure reduces
storage needs

Program Maintenance Difficult - changes to file Easy - changes made in Saves development time
structure require one place; programs
modifying all programs remain unchanged

Development Time Long - each application Short - DBMS provides Reduces coding by 40-60%
needs custom file built-in functions
handling code

Resource Usage High - multiple programs Optimized - centralized Better CPU and memory utilization
access same data management of
differently resources
4. describe the different types and organisation of files and databases; File types including master and transaction files. File organisation including
serial,sequential, indexed sequential, random or direct; Database organisation including hierarchical, relational, network and object-oriented.
File Organization
Serial

● Definition: Records are stored one after another in the order they are received, with no particular sequence.
● Example: Log files recording system events in the exact order they occur.

Sequential

● Definition: Records are stored in a specific order based on a key field and must be accessed in that order.
● Example: Student records sorted alphabetically by last name and accessed from A to Z.

Indexed Sequential

● Definition: Records are stored sequentially but with an index that allows both sequential and direct access.
● Example: Library catalog with an index pointing to book locations, allowing quick searches while maintaining
alphabetical order.

Random/Direct

● Definition: Records can be accessed immediately using their address or key without reading previous records.
● Example: Bank ATM accessing a specific account balance directly using the account number.
File Types
Master File

● Definition: A permanent file containing relatively static data that is used as a reference for
processing transactions.
● Example: Employee records database containing all staff information including names, addresses,
and salary details.

Transaction File

● Definition: A temporary file containing records of day-to-day business activities that are used to
update master files.
● Example: Daily sales receipts waiting to update the master inventory file.
Database Organization
Hierarchical

● Definition: Data is organized in a tree-like structure with parent-child relationships where each child has only one parent.
● Example: Company organization chart showing CEO at the top, department managers below, then employees under each
manager.

Relational

● Definition: Data is organized in tables (relations) with rows and columns, linked through common fields (keys).
● Example: School database with separate tables for Students, Courses, and Enrollments connected through StudentID and
CourseID.

Network

● Definition: Data is organized in a graph structure where records can have multiple parent and child relationships.
● Example: Parts inventory system where one component can belong to multiple products and one product can contain
multiple components.

Object-Oriented

● Definition: Data is stored as objects that encapsulate both data attributes and methods (operations) together.
● Example: Multimedia database storing video objects that contain the video file, metadata, playback methods, and
compression algorithms as a single unit.
Hierarchical Database Organization
Parent Node - A record that has one or more dependent records (children) below it in the tree structure.

Child Node - A record that belongs to a parent record in the hierarchy; each child has only one parent.

Root Node - The topmost record in the hierarchical structure that has no parent.

Sibling Nodes - Records at the same level in the hierarchy that share the same parent.

Tree Structure - The overall organizational pattern resembling an inverted tree with the root at the top.

Path - The route followed from the root to access a specific record through parent-child links.

Level - The position of a record in the hierarchy, measured by its distance from the root.

One-to-Many Relationship - The relationship type where one parent can have multiple children, but each child
has only one parent.
Relational Database Organization
Table (Relation) - A two-dimensional structure consisting of rows and columns that stores data.

Row (Tuple/Record) - A single horizontal entry in a table representing one complete set of related data.

Column (Attribute/Field) - A vertical component of a table representing a specific characteristic or property.

Primary Key - A field or combination of fields that uniquely identifies each record in a table.

Foreign Key - A field in one table that refers to the primary key in another table, creating a link between tables.

Composite Key (Compound/Concatenated Key) - A primary key composed of two or more fields used together to uniquely identify records.

Candidate Key - Any field or combination of fields that could serve as a primary key.

Relationship - A logical connection between tables based on common fields.

One-to-One Relationship - A relationship where one record in a table relates to exactly one record in another table.

One-to-Many Relationship - A relationship where one record in a table can relate to multiple records in another table.

Many-to-Many Relationship - A relationship where multiple records in one table can relate to multiple records in another table.

Referential Integrity - A rule that maintains consistency between related tables by ensuring foreign keys match existing primary keys.

Entity - A distinct object or concept about which data is stored (represented as a table).

Schema - The structure or design of the database, including tables, fields, and relationships.

Query - A request for specific data from one or more tables based on defined criteria.
Network Database Organization
Node (Record Type) - A collection of related data fields representing an entity.

Set - A named relationship between two record types: an owner and a member.

Owner Record - The parent record in a set relationship that controls access to member records.

Member Record - The child record in a set relationship that belongs to an owner record.

Graph Structure - The overall organizational pattern where records are connected in a network allowing multiple pathways.

Many-to-Many Relationship - Records can have multiple parents and multiple children, creating complex interconnections.

Pointer - A reference that links one record to another, enabling navigation through the network.

Navigation - The process of traversing through the database by following pointers from record to record.

Set Occurrence - A specific instance of a set relationship connecting particular owner and member records.

Circular Link - A connection that allows navigation back to a previously accessed record.

Entry Point - A designated record from which database navigation typically begins.
Object-Oriented Database Organization

Object - A self-contained unit that combines data (attributes) and the operations (methods) that can be performed on that data.

Class - A template or blueprint that defines the structure and behavior of similar objects.

Instance - A specific occurrence or example of a class.

Attribute - A characteristic or property of an object (similar to fields in traditional databases).

Method - A function or procedure that defines the behavior or operations that can be performed on an object.

Encapsulation - The bundling of data and methods together within an object, hiding internal details from external access.

Inheritance - The mechanism by which one class can acquire properties and methods from another class.

Parent Class (Superclass) - A class from which other classes inherit attributes and methods.

Child Class (Subclass) - A class that inherits properties and methods from a parent class and can add its own unique features.

Polymorphism - The ability of different objects to respond to the same method call in different ways.

Object Identity (OID) - A unique identifier assigned to each object that remains constant throughout its lifetime.

Complex Object - An object that contains other objects as attributes, creating nested structures.

Persistent Object - An object whose data is stored permanently in the database and survives beyond program execution.

Transient Object - A temporary object that exists only during program execution and is not permanently stored.

Message Passing - The process by which objects communicate with each other by invoking methods.

Abstract Class - A class that serves as a template for other classes but cannot be instantiated directly.

Interface - A specification of methods that a class must implement, defining a contract for behavior.
5. explain how files and databases are used in organisations; Uses: including store, organise, search, retrieve;
eliminate redundancies; data mining, data marts and data warehouses.
1. Store

Files:

● Organizations use files to store data in a structured format on storage devices

● Example: A retail store saves daily transaction files containing sales records on their computer's hard drive
● Files provide permanent storage of business records such as customer information, product catalogs, and financial documents
● Different file types serve different purposes: master files store permanent data while transaction files store temporary operational data

Databases:

● Databases store large volumes of structured data in tables with defined relationships
● Example: A hospital database stores patient records, medical histories, appointment schedules, and billing information all in one
centralized system
● Data is stored once and can be accessed by multiple users and applications simultaneously
● Provides persistent storage with backup and recovery capabilities
2. Organize

Files:

● Files organize data using different methods: serial, sequential, indexed sequential, or direct/random organization
● Example: A school maintains student files organized sequentially by student ID number, making it easy to locate records in numerical
order
● File organization determines how efficiently data can be accessed and updated
● Records within files are structured with specific fields for consistent data organization

Databases:

● Databases organize data into logical structures (tables, hierarchies, networks, or objects) with defined relationships
● Example: A university database organizes information into related tables—Students, Courses, Enrollments, Instructors—with clear
relationships showing which students are enrolled in which courses
● Eliminates data fragmentation by consolidating related information
● Uses schemas to define the structure, ensuring consistent organization across the entire system
● Primary and foreign keys establish relationships between different data entities
3. Search

Files:

● Files can be searched using key fields or specific criteria, though search efficiency depends on file organization
● Example: A library searches its sequential book catalog file for all books by a specific author by reading through records alphabetically
● Sequential files require reading records in order; indexed files allow faster searches using an index
● Search capabilities are limited compared to databases

Databases:

● Databases provide powerful search capabilities through query languages like SQL
● Example: A customer service representative uses a database query to instantly find all orders placed by "John Smith" in the last 30 days
where the order total exceeds $100
● Can search across multiple tables simultaneously using joins
● Supports complex search criteria with multiple conditions (AND, OR, NOT operators)
● Allows searching by any field, not just key fields
● Much faster than file-based searches, especially with proper indexing
4. Retrieve

Files:

● Files retrieve data by accessing specific records based on their organization method
● Example: A bank's ATM system retrieves account balance information directly from a random access file using the account number as
the key
● Retrieval speed depends on file organization: direct access is fastest, serial is slowest
● Typically retrieves one record or a small set of records at a time

Databases:

● Databases retrieve data efficiently through queries that can extract exactly the information needed
● Example: A manager retrieves a report showing total sales by region for the last quarter by querying the sales database, pulling data
from Sales, Products, and Regional tables
● Can retrieve data from multiple related tables in a single operation
● Provides various output formats: individual records, summary reports, or aggregated data
● Supports views that present data in customized formats for different users
● Retrieval maintains data integrity through concurrency controls when multiple users access simultaneously
5. Eliminate Redundancies

Files:

● Traditional file systems often suffer from data redundancy (duplication)

● Example (Problem): A company maintains separate files for Sales, Accounting, and Shipping departments; customer name and address
appear in all three files, creating redundancy
● Updates must be made in multiple files, leading to inconsistency
● Wastes storage space with duplicate data
● Increases chance of data inconsistency if one file is updated but others are not

Databases:

● Databases eliminate redundancy through normalization and centralized data storage

● Example (Solution): The same company uses a relational database with a single Customer table; Sales, Accounting, and Shipping
modules all reference this one table using the CustomerID
● Data is stored once and referenced multiple times through relationships
● Benefits of eliminating redundancy:
○ Reduced storage costs: Data stored once saves disk space
○ Improved data integrity: Single source of truth means consistent data across the organization
○ Easier maintenance: Updates made in one place automatically reflect everywhere
○ Fewer errors: No risk of updating one copy but forgetting others
● Normalization process specifically targets redundancy removal while maintaining data relationships
6. Additional Uses: Data Mining, Data Marts, and Data Warehouses

Data Mining:

● Process of analyzing large databases to discover patterns, trends, and relationships

● Example: A supermarket chain analyzes purchase patterns to discover that customers who buy diapers often buy beer, leading to
strategic product placement

Data Marts:

● Subset of a data warehouse focused on a specific business area or department

● Example: A retail company creates a Sales Data Mart containing only sales-related data for the Sales department's analysis needs

Data Warehouses:

● Large, centralized repositories that consolidate data from multiple sources for analysis and reporting
● Example: A multinational corporation combines data from all regional offices into a data warehouse for global business intelligence and
strategic decision-making
● Supports historical data analysis and trend identification
● Optimized for query and analysis rather than transaction processing
Organizational Benefits
1. Efficiency: Faster data access and processing speeds up business operations
2. Data Quality: Eliminating redundancy ensures accuracy, completeness, and consistency
3. Cost Savings: Reduced storage needs and fewer errors save money
4. Better Decision-Making: Quick retrieval and analysis support informed decisions
5. Scalability: Databases grow with organizational needs without restructuring
6. Integration: Multiple departments access the same consistent data
7. Security: Centralized control allows better access management and data protection
7. explain how the growth of the Internet impacts data handling; Including the demands for information (by customers
and suppliers); data mining, data warehousing; interfacing websites and data processing; underlying databases.
1. Demands for Information (by Customers and Suppliers)

Customers:

● 24/7 Access: Customers expect instant, round-the-clock access to information from any device
○ Example: Online banking customers check balances and transfer funds anytime without visiting a branch
● Self-Service: Customers want to find information independently
○ Example: E-commerce customers track packages in real-time without contacting customer service
● Personalization: Customers expect customized information based on their history
○ Example: Netflix recommends shows based on viewing patterns

Data Handling Impact:

● Organizations need real-time databases, robust web servers, secure authentication, and responsive interfaces across devices

Suppliers:

● Supply Chain Integration: Suppliers need direct access to inventory and order data
○ Example: Auto parts suppliers view manufacturer inventory to trigger automatic reordering
● Real-Time Processing: EDI systems enable instant order placement and confirmation
○ Example: Supermarkets automatically send purchase orders when stock is low
● Collaborative Planning: Shared data improves forecasting
○ Example: Retailers share sales trends with suppliers for production planning

Data Handling Impact:

● Need B2B portals, system integration, standardized data formats (XML, JSON), and accurate, timely data sharing
2. Data Mining

Definition: Analyzing large data volumes to discover patterns, trends, and relationships for business decisions.

Internet Impact:

● Big Data Volume: Internet transactions generate massive amounts of analyzable data
○ Example: Amazon mines millions of daily purchases, searches, and reviews
● Real-Time Analysis: Immediate pattern detection as transactions occur
○ Example: Credit card companies detect fraud within seconds of suspicious purchases
● Customer Behavior: Analyzing clickstream data reveals navigation patterns and purchase influences
○ Example: Online bookstores analyze which recommendations customers click to improve marketing
● Predictive Analytics: Historical data predicts future trends
○ Example: Streaming services predict successful shows to guide content acquisition

Data Handling Impact:

● Require specialized mining software, data warehouses, high-performance computing, data scientists, and privacy controls
3. Data Warehousing

Definition: Centralized repository consolidating data from multiple sources for analysis and reporting.

Internet Impact:

● Web Data Integration: Warehouses must incorporate vast internet-generated data

○ Example: Telecom companies integrate billing, website interactions, app activity, and social media
● Scalability: Exponential internet data growth requires continuous expansion
○ Example: E-commerce platforms expand warehouse storage monthly for growing transactions
● Real-Time Updates: Shift from daily/weekly to near-real-time updates
○ Example: Airlines continuously update seat availability for dynamic pricing
● Cloud-Based: Internet enables flexible, cost-effective cloud storage
○ Example: Startups use AWS Redshift, avoiding massive infrastructure costs
● Multi-Channel Integration: Consolidating website, mobile, email, and social media data
○ Example: Banks integrate online banking, mobile apps, ATMs, and branches for complete customer views

Data Handling Impact:

● Need ETL processes, massive storage, data quality controls, metadata management, security measures, and backup systems
4. Interfacing Websites and Data Processing

Definition: How web applications connect to backend databases to retrieve, display, process, and store data.

Internet Impact:

● Dynamic Content: Real-time database queries display current information

○ Example: Real estate sites show updated property listings as agents add them
● Web Forms: Forms collect data directly into backend databases
○ Example: University application forms feed data into admissions databases
● APIs: Websites communicate with multiple systems simultaneously
○ Example: Travel sites coordinate data across airline, hotel, and payment systems
● Session Management: Tracking user state across multiple requests
○ Example: Shopping carts maintain items as customers browse different pages
● Load Balancing: Distributing queries across servers during high traffic
○ Example: E-commerce sites distribute Black Friday queries across multiple database servers
● Caching: Storing frequently accessed data to reduce database load
○ Example: News sites cache popular articles for faster repeated access

Data Handling Impact:

● Need middleware, connection pooling, transaction processing, scalable architecture, secure protocols (HTTPS), and error handling
5. Underlying Databases

Definition: Backend database management systems storing and managing data accessed through internet applications.

Internet Impact:

● Distributed Systems: Geographically distributed databases improve performance and redundancy

○ Example: Facebook maintains global data centers so users access nearby servers
● Scalability: Must handle millions of internet users
○ Example: Twitter's infrastructure handles 500 million tweets daily
● Concurrent Access: Processing thousands of simultaneous users
○ Example: Concert ticket databases prevent overselling during high-demand sales
● NoSQL Databases: Flexible structures for varied internet data
○ Example: E-commerce sites use MongoDB for product catalogs with varying attributes
● Replication: Data copied across servers ensures availability
○ Example: Gmail replicates emails across data centers for continuous access
● Performance Optimization: Indexes and query optimization for millisecond response times
○ Example: Auction sites optimize searches across millions of listings

Data Handling Impact:

● Need database clustering, indexing, sharding, continuous backups, monitoring tools, expert DBAs, and capacity planning
Key Changes:

1. Volume: Exponential data increase

2. Velocity: Real-time processing requirements
3. Variety: Diverse data types (text, images, video, sensor data)
4. Accessibility: 24/7 global access expectations
5. Integration: Multiple internet sources working together
6. Security: Stronger protection against threats
7. Architecture: Shift from centralized to distributed systems
8. explain how the absence of data quality, accuracy, and timeliness impacts organisations; Including loss of revenue,
sales, competitive advantage, customers; poor decision-making; missed opportunities; impact on problem solutions.
1. LOSS OF REVENUE
Chain 1.1: Absence of Data Quality → Loss of Revenue

Absence of data quality (incomplete, inconsistent data) → Incomplete customer records → Unable to complete transactions properly →
Failed sales conversions → Direct loss of transaction revenue → Loss of revenue

Chain 1.2: Absence of Data Accuracy → Loss of Revenue

Absence of data accuracy (incorrect pricing data) → Wrong prices charged to customers → Undercharging products/services → Revenue
leakage on each transaction → Cumulative financial losses → Loss of revenue

Chain 1.3: Absence of Timeliness → Loss of Revenue

Absence of timeliness (delayed financial data) → Late detection of payment defaults → Delayed debt collection efforts → Increased bad
debts written off → Cash flow problems → Loss of revenue
2. LOSS OF SALES
Chain 2.1: Absence of Data Quality → Loss of Sales

Absence of data quality (invalid customer preferences) → Ineffective product recommendations → Poor personalization of offers →
Customers not interested in products shown → Reduced purchase intent → Loss of sales

Chain 2.2: Absence of Data Accuracy → Loss of Sales

Absence of data accuracy (wrong inventory levels) → Stockouts of popular items → Customers unable to purchase desired products →
Customers buy from competitors instead → Immediate sales opportunity lost → Loss of sales

Chain 2.3: Absence of Timeliness → Loss of Sales

Absence of timeliness (outdated product availability data) → Customers see items as available when out of stock → Order placed but
cannot be fulfilled → Customer frustration and cancellations → Failed sales conversions → Loss of sales
3. LOSS OF COMPETITIVE ADVANTAGE
Chain 3.1: Absence of Data Quality → Loss of Competitive Advantage

Absence of data quality (fragmented market research data) → Incomplete understanding of market needs → Products don't fully meet
customer requirements → Competitors offer better-suited products → Market share shifts to competitors → Loss of competitive
advantage

Chain 3.2: Absence of Data Accuracy → Loss of Competitive Advantage

Absence of data accuracy (incorrect competitor pricing data) → Wrong competitive positioning decisions → Pricing strategy misaligned
with market → Either overpriced (lose customers) or underpriced (lose margin) → Weakened market position → Loss of competitive
advantage

Chain 3.3: Absence of Timeliness → Loss of Competitive Advantage

Absence of timeliness (delayed trend analysis) → Late identification of emerging customer preferences → Slow adaptation to market
changes → Competitors innovate and launch first → Organization seen as follower, not leader → Loss of competitive advantage
4. LOSS OF CUSTOMERS
Chain 4.1: Absence of Data Quality → Loss of Customers

Absence of data quality (inconsistent service history) → Customer service reps lack complete interaction records → Customers must
repeat information multiple times → Frustrating customer experience → Customers switch to competitors → Loss of customers

Chain 4.2: Absence of Data Accuracy → Loss of Customers

Absence of data accuracy (wrong contact information) → Communications sent to incorrect addresses → Important notifications never
received → Customers miss appointments/deliveries → Customer dissatisfaction escalates → Loss of customers (churn)

Chain 4.3: Absence of Timeliness → Loss of Customers

Absence of timeliness (delayed complaint resolution data) → Customer issues not addressed promptly → Problems remain unresolved for
extended periods → Customer trust and loyalty eroded → Customers actively seek alternatives → Loss of customers
5. POOR DECISION-MAKING
Chain 5.1: Absence of Data Quality → Poor Decision-Making

Absence of data quality (incomplete sales data) → Analysis missing critical variables → Incomplete picture of business performance →
Decisions made on partial information → Strategic plans based on flawed foundation → Poor decision-making

Chain 5.2: Absence of Data Accuracy → Poor Decision-Making

Absence of data accuracy (incorrect financial forecasts) → Misleading projections presented to management → Budget allocations based
on false assumptions → Resources committed to wrong priorities → Investments in non-viable projects → Poor decision-making

Chain 5.3: Absence of Timeliness → Poor Decision-Making

Absence of timeliness (outdated performance metrics) → Management reviews stale information → Decisions based on past, not current,
reality → Actions taken are irrelevant to current situation → Ineffective responses to actual conditions → Poor decision-making
6. MISSED OPPORTUNITIES
Chain 6.1: Absence of Data Quality → Missed Opportunities

Absence of data quality (fragmented customer data) → Unable to identify high-value customer segments → Cannot target lucrative
market niches → Potential expansion opportunities overlooked → Growth potential remains untapped → Missed opportunities

Chain 6.2: Absence of Data Accuracy → Missed Opportunities

Absence of data accuracy (wrong market size estimates) → Underestimation of potential market → Business case appears unviable →
Promising ventures rejected → Competitors enter market instead → Missed opportunities

Chain 6.3: Absence of Timeliness → Missed Opportunities

Absence of timeliness (delayed detection of market gaps) → Slow recognition of unmet customer needs → Window of opportunity passes
→ By the time action is taken, market is saturated → First-mover advantage lost → Missed opportunities
7. IMPACT ON PROBLEM SOLUTIONS
Chain 7.1: Absence of Data Quality → Impact on Problem Solutions

Absence of data quality (incomplete problem data) → Root cause analysis is flawed → Wrong problems identified as priorities →
Solutions address symptoms, not causes → Problems persist or recur → Negative impact on problem solutions

Chain 7.2: Absence of Data Accuracy → Impact on Problem Solutions

Absence of data accuracy (incorrect measurements) → Problem severity misjudged → Inadequate resources allocated to fix → Proposed
solution insufficient for actual problem → Implementation fails to resolve issue → Negative impact on problem solutions

Chain 7.3: Absence of Timeliness → Impact on Problem Solutions

Absence of timeliness (delayed problem detection) → Issues escalate before intervention → Simple problems become complex crises →
Much more expensive and difficult to resolve → Solutions become less effective → Negative impact on problem solutions