Information Systems, Information Types, and Database Foundations
Information in a Business Environment
Continuous Data Generation:
Organizations continuously generate information through daily operations.
Data is produced by customer interactions, sales, bookings, registrations, payments, and service activities.
Information systems capture and process this raw data to support ongoing business operations and executive decision-making.
Detailed Example: Supermarket Transactions:
A supermarket processes customer transactions throughout the day via a structured sequence:
Customers select items from store shelves.
Items are brought to the point-of-sale (POS) terminal.
Items are recorded and priced by system scanners.
The financial transaction is completed.
Transaction details are saved in the organization's central database.
By the end of the operating day, accumulated transaction data can be processed to reveal:
Specific items sold.
Exact quantities sold per product.
Total monetary value of sales.
Current stock balances remaining on shelves and in inventory.
Identification of products running low on stock.
Overall daily operational and financial performance of the business.
Domain-Specific Transaction Systems:
Ticket-booking systems
Flight-reservation systems
Course-registration systems
Point-of-sale (POS) systems
Inventory-management systems
Categories of Information Generated by Organizations
Classification Framework:
Information generated within business environments is categorized based on the level and type of organizational decision it supports:
Operational information
Tactical information
Strategic information
Statutory information
Interconnected Nature of Information Categories:
Categories are directly linked in a hierarchical relationship.
Operational information originates from raw day-to-day transactions.
Operational data is subsequently aggregated, summarized, and analyzed to form tactical and strategic information.
Operational Information and Transaction Systems
Definition and Characteristics of Operational Information:
Definition: Operational information is the detailed data required to execute, monitor, and manage the routine, daily activities of an organization.
Characteristics:
Generated continuously on an ongoing basis.
Characterized by high volume.
Tightly tied to routine operational transactions.
Used directly by front-line operational employees and first-line supervisors.
Focused on current real-time events or short historical operational windows.
Domain Examples of Operational Information:
Supermarket Environment:
Individual item sales records.
Items scanned at the point of sale.
Daily sales totals.
Real-time inventory level records.
Customer purchase receipts.
Supplier delivery manifests.
Cash register logs.
University Environment:
Daily student attendance logs.
Individual student course registration records.
Examination grade entries.
Fee payment transaction records.
Unit enrollment listings.
Transaction Processing Systems (TPS):
Definition: Computer systems designed to record, process, and track high-volume, structured, routine business transactions as they occur.
Routine Transaction Types Recorded:
Purchasing products
Booking flights
Registering for academic courses
Paying tuition or service fees
Checking into service facilities
Logging attendance entries
Core Operational Functions of a TPS:
Captures transaction data at the source.
Validates and checks data against predefined rules.
Stores transaction details securely.
Updates primary database records.
Generates transaction receipts or operational output reports.
Workflow Example (Course Registration):
System identifies the requesting student.
System checks and identifies the requested course.
System validates eligibility and permissions.
System logs and records the registration.
System updates the student's official academic transcript and record.
Online Transaction Processing (OLTP):
Operational transaction systems hosted online to handle electronic inputs immediately upon entry.
Examples of OLTP:
Online course registration platforms.
Online flight booking engines.
Online banking systems.
E-commerce purchasing portals.
Tactical Information
Definition and Core Role:
Definition: Tactical information consists of analytical, summarized data used by management to make short-term or medium-range decisions regarding effective resource allocation and operational control.
Primary Users: Middle-level managers, departmental heads, and supervisors.
Derivation: Formed by filtering, aggregating, and analyzing raw operational transaction data.
Detailed Industry Scenarios:
Supermarket Inventory Decision:
Operational level: POS system logs thousands of individual item sales.
Tactical analysis: System aggregates sales and detects that a specific product's stock is depleting rapidly and will run out shortly.
Tactical output: Automated warning alerting the manager to initiate a short-term stock reorder from the supplier.
University Class Management:
Operational level: Daily class attendance logs recorded.
Tactical analysis: Academic managers evaluate aggregated attendance and discover a class size exceeds room capacity.
Tactical output: Management divides the class into two sections, assigns an additional lecturer, adjusts the timetable, and reallocates a larger facility.
Key Characteristics of Tactical Information:
Derived directly from processed operational data.
Presented in structured summary reports.
Directly supports departmental and short-range decisions.
Assists managers in allocating personnel, budget, and physical resources.
Identifies operational bottlenecks, resource shortages, and immediate inefficiencies.
Exhibits significantly higher analytical value than raw transaction records.
Strategic Information
Definition and Organizational Scope:
Definition: Strategic information consists of long-term performance summaries, market analyses, and trend forecasts used to establish organizational goals, long-range planning, expansion, and corporate vision.
Primary Users: Senior executives, board members, Chief Executive Officers (CEOs), and Vice Chancellors.
Scope and Impact: Evaluates multi-year performance, incurs substantial financial commitments, and defines the future path of the entity.
Strategic Decision Frameworks:
Establishing physical branches in new regions or foreign countries.
Introducing major new product lines, academic degree programs, or core services.
Reallocating corporate capital investments.
Entering new commercial or geographic markets.
Expanding corporate infrastructure and facilities.
Restructuring long-term corporate business models.
Data Requirements for Strategic Information:
Requires extensive historical data archives.
Synthesizes long-term internal sales trends, financial results, customer demographic behavior, and macro-environmental trends.
Relationship Among Operational, Tactical, and Strategic Information
Hierarchical Interdependence:
Level 1 (Operational Information): Captures detailed, real-time, daily transactions.
Level 2 (Tactical Information): Summarizes operational data into actionable short-term management reports.
Level 3 (Strategic Information): Aggregates historical tactical summaries and external data to drive long-term strategic decisions.
Integrated Multi-Level Example:
Operational: An individual sales receipt logged at a checkout counter.
Tactical: A monthly analytics report indicating sustained 20% sales growth for a specific store department.
Strategic: A corporate board decision to build a new regional distribution center based on multi-year sustained regional sales growth.
Statutory Information
Definition and Legal Mandatory Role:
Definition: Statutory information consists of mandatory records, financial statements, and administrative reports that an organization is legally bound to compile and submit to governmental authorities and regulatory bodies.
Purpose: Compliance with public law, tax statutes, and industry regulations (rather than internal management control).
Detailed Example: Corporate Tax Returns:
Statutory tax filings require strict reporting of specific financial figures:
Gross revenue
Total operating expenses
Net accounting profits
Calculated taxable income
Total tax collected from customers
Total tax paid to authorities
Characteristics of Statutory Information:
Mandated by federal, state, or municipal legislation.
Must adhere to strictly standardized formats and schedules.
Submitted to external legal regulators and authorities.
Requires complete precision, accuracy, and auditability.
Derived from internal operational, accounting, and financial databases.
Organizational Structure and Information Needs
Organizational Hierarchy Framework:
Organizations structure authority and operational responsibilities across explicit managerial levels:
Chancellor / Governing Board / Board of Directors
Vice Chancellor / Chief Executive Officer (CEO)
Deputy Vice Chancellors / Executive Vice Presidents
Registrars / Senior Administrative Officers
Deans / School Directors
Heads of Academic or Operational Departments
Lecturers, Administrative Staff, and Front-line Operational Personnel
Information Alignment Across Hierarchy Levels:
Senior Management:
Role: Long-term vision, institutional policy, corporate strategy.
Information Needs: Highly summarized strategic reports, long-term trends, global performance summaries, growth forecasts.
Middle Management:
Role: Departmental administration, staff control, resource allocation.
Information Needs: Tactical reports, departmental performance metrics, staffing levels, variance analyses.
Operational Staff:
Role: Executing routine daily tasks and transactions.
Information Needs: Real-time operational data, daily duty schedules, individual task logs, transactional records.
Information Flow and Aggregation Dynamics:
Data originates at the base of the hierarchy through daily operational activities.
As information flows upward through management levels, it is continuously filtered, structured, and summarized.
Higher levels of authority receive progressively more summarized, broad-scope, long-term strategic information.
Fundamentals of Information Systems
Definition of an Information System (IS):
An Information System is an integrated, coordinated arrangement of people, processes, data, and technology designed to collect, store, process, analyze, and output information to support organizational operations, management, and decision-making.
An IS encompasses the complete organizational infrastructure—not merely software code or isolated database files.
The Four Core Components of an Information System:
People: System users and stakeholders, including operational employees, middle managers, executive leaders, system administrators, technical support staff, customers, and regulatory agents.
Processes: Standardized procedures, business workflows, and operational routines (e.g., executing sales, processing course registrations, booking tickets, taking attendance, reordering inventory).
Data: Unprocessed facts, metrics, and recorded observations (e.g., student IDs, product SKUs, prices, attendance timestamps, transaction volumes).
Technology: Physical hardware, network infrastructure, and software applications (e.g., servers, POS hardware terminals, local and wide-area networks, application engines, relational database software).
Primary Strategic Objectives of an Information System:
Optimize day-to-day operational execution.
Maximize administrative and business process efficiency.
Log, monitor, and audit corporate activities.
Supply actionable data to operational personnel.
Support tactical management planning.
Facilitate long-term strategic analysis.
Ensure compliance with legal and statutory reporting mandates.
Key Types of Information Systems
Transaction Processing Systems (TPS):
Operates at the bottom of the information hierarchy.
Automates high-volume, structured operational transactions.
Primary objective: High-speed recording, accuracy, and basic record updating.
Management Information Systems (MIS):
Converts underlying transaction data into structured, scheduled management reports.
Provides middle managers with tactical insight into routine performance.
Core Administrative Functions Supported:
Activity planning and scheduling
Departmental resource organization
Employee and process performance evaluation
Operational oversight and direction
Inventory control and monitoring
Periodic sales revenue review
Standard Output Reports Generated:
Inventory status reports
Daily and weekly sales summaries
Departmental efficiency reports
Staffing and payroll summaries
Resource utilization analyses
Decision Support Systems (DSS):
Interactive computer systems designed to support analytical evaluation of semi-structured and unstructured problems.
Categorization of Problem Complexity:
Structured Problem: Solvable using fixed, automated rules or algorithms.
Semi-Structured Problem: Partially automated, but requires critical human interpretation and contextual judgement.
Unstructured Problem: Complex, non-routine scenario lacking predefined algorithms or standard solutions.
Core Capabilities of DSS:
Multi-variable analytical data modeling.
Comparative scenario analysis ("What-If" scenarios).
Trend projection and pattern identification.
Evaluation of alternative financial or operational strategies.
Key Distinctions:
Unlike TPS, a DSS focuses on analytical modeling rather than routine transaction processing.
Unlike MIS, which generates standardized, fixed reports, a DSS allows ad-hoc interactive manipulation of complex variables.
Interrelationship Between Systems and Information Types
System-to-Information Mapping:
Transaction Processing Systems (TPS):
Handles structured transactions.
Produces operational data and operational reports.
Serves front-line workers and operational supervisors.
Management Information Systems (MIS):
Processes structured operational data.
Produces structured summary reports and tactical information.
Serves middle managers and department heads.
Decision Support Systems (DSS):
Processes complex semi-structured and unstructured problems.
Produces analytical evaluations, predictive models, and strategic insights.
Serves middle and senior executive managers.
Data, Processing, and Information
Fundamental Definitions:
Data: Raw, unorganized facts, symbols, and uninterpreted observations (e.g., a stock number, an attendance mark, a sale amount, a student name).
Processing: The transformation phase wherein operations clean, organize, calculate, structure, and filter raw data.
Information: Data that has been successfully processed, structured, contextualized, and presented in a meaningful form that delivers utility to a decision-maker.
Operations Included in Data Processing:
Sorting items alphanumerically or chronologically.
Calculating mathematical totals, averages, and margins.
Classifying data into relevant categories.
Summarizing large data sets into totals.
Comparing metrics against benchmarks.
Filtering out unnecessary fields or parameters.
Combining data sets from disparate operational units.
Formatting outputs into readable reports.
Mathematical Representation of Information Generation:
The Role of a Database in an Information System
Definition of a Database:
A database is a central, organized repository designed to store, manage, secure, and retrieve linked organizational data efficiently.
Essential Database Management Operations:
Collection: Gathering raw operational transactions at the point of origin (e.g., POS checkouts, course registration forms, fee payments).
Storage: Persisting digital records reliably in physical memory and media.
Organization: Structuring data into logical tables, schemas, and fields for indexation.
Access: Enforcing security protocols to allow authorized applications and users to query data.
Manipulation: Performing CRUD operations (Create, Read, Update, Delete), alongside sorting, filtering, and joining data sets.
Relationship Management: Defining relational links between entities across the organization (e.g., mapping Students to Courses, Products to Suppliers, Customers to Receipts, Employees to Departments).
End-to-End Operational Lifecycle of Data in a Database:
Organizational operations execute and generate raw data.
The database receives, indexes, and stores raw data.
Application systems extract and process stored data.
Information systems produce reports, dashboards, and analytical outputs.
Decision-makers use the generated information to drive actions.
Evolution of Data Storage
1. Manual Filing Systems:
Predated digital computer infrastructure.
Relied on physical paper records stored in folders, registers, and metal filing cabinets.
Severe Drawbacks: Extremely slow access, prone to physical destruction, high storage footprint, difficult cross-referencing, zero concurrent user sharing.
2. File-Based Computer Systems:
Early computerized approach attempting to digitize paper files.
Each functional application program managed its own separate, dedicated data files independently.
Example: A university maintaining separate software applications with isolated files for Student Registration, Financial Accounting, and Library Services.
3. Database Management Systems (DBMS):
Modern centralized database architectures developed to solve the architectural flaws and inefficiencies of legacy file-based systems.
File-Based Systems and Their Limitations
Application Control in File-Based Systems:
In a file-based architecture, each application program is responsible for:
Defining data structures within program code.
Entering and validating raw inputs.
Maintaining and modifying physical file contents.
Updating local records.
Generating a predefined, rigid set of hardcoded reports.
Institutional Scenario (University File-Based System):
School of Science, School of Business, and School of Education run isolated registration applications with local files.
A student taking courses across multiple schools is re-entered into three separate data files.
Severe Technical Limitations of File-Based Systems:
Data Redundancy:
Definition: Unnecessary, duplicate storage of identical data across multiple isolated storage files.
Consequences: Consumes excessive digital storage, mandates duplicated manual data entry, increases human error, causes data maintenance overhead.
Data Inconsistency:
Definition: Occurs when conflicting versions of identical data exist in different files across the organization.
Scenario: Student name recorded as "Jon." in Science, "Jones." in Business, and "J-O-N." in Education.
Causes: Lack of centralized validation, failure to update all copy locations simultaneously when changes occur, differing naming standards.
Data Isolation:
Definition: Storage of data in detached, incompatible files that prevent integration or cross-departmental analysis.
Consequences: Inability to compile holistic organizational reports without manually extracting and rekeying data.
Difficulty Accessing Data:
Retrieving unprogrammed reports requires custom software programming, specialized technical skills, or manual file processing.
Limited Reporting Flexibility:
Fixed application code limits reporting to built-in formats. Ad-hoc query generation across departmental data sets is impossible without recoding applications.
Data Integrity Problems:
Data Integrity: The overall correctness, completeness, consistency, and reliability of stored data.
Impact: Disparate validation rules lead to invalid data entries across systems, destroying trust in executive decisions.
Program-Data Dependence:
Definition: The tight structural coupling between the physical file layout and the underlying application source code.
Program-Data Dependence vs. Program-Data Independence
Mechanism of Program-Data Dependence:
Application source code explicitly hardcodes structural file assumptions:
Names of underlying storage files
Explicit field names and field order
Exact physical byte sizes of fields
Data types (e.g., Integer, String, Float)
Inter-file structural relationships
Concrete Impact: If a database administrator adds a new field (e.g., "Email Address") or changes a field length in a file, the application program crashes unless its source code is rewritten and recompiled.
Consequences of Program-Data Dependence:
Exorbitant software maintenance costs.
Extreme difficulty implementing business system changes.
System downtime and high error rates during field updates.
Total organizational dependence on custom software developers.
Program-Data Independence in Database Systems:
Definition: The structural separation of physical data definitions from application programs.
Database management systems store structural metadata centrally in a data dictionary.
Fields, tables, and physical layouts can be modified without breaking or requiring modifications to existing application programs.
Comparative Summary: File-Based vs. Database Systems:
File-Based System:
Decentralized file management per application.
Tight program-data coupling (Program-Data Dependence).
High data redundancy and risk of data inconsistency.
Isolated files prevent cross-functional reporting.
Difficult system maintenance and expansion.
Database System:
Centralized management via DBMS software.
Structural separation (Program-Data Independence).
Minimizes redundant storage and enforces global data consistency.
Shared relational access across all organizational divisions.
Flexible, ad-hoc reporting capabilities.
End-to-End Information Flow in Organizations
Complete Organizational Information Lifecycle:
Operational staff perform real-world business activities.
Standardized processes govern how operational activities execute.
Executed activities produce unorganized raw data.
Transaction Processing Systems (TPS) record and validate raw transactional inputs.
The centralized Database indexes, links, and stores data securely.
Application systems process stored records.
Management Information Systems (MIS) aggregate data to output structured tactical performance reports.
Decision Support Systems (DSS) evaluate complex scenarios to assist tactical and strategic decision-making.
Organizational managers utilize processed information to direct daily tasks, make tactical adjustments, and define long-term strategic plans.
Financial and operational databases feed required statutory records directly to government authorities to meet legal regulatory requirements.