IT 233: Business Information Systems
By the end of this chapter, you will be able to:
Before databases, every application stored its own data in separate files.
A modern approach that creates a centralized, shared repository of data.
The goal is to create a "single source of truth" for the entire organization.
A logically coherent collection of related data.
The software that manages and controls access to the database.
Examples of DBMS: MySQL, Oracle, Microsoft SQL Server, PostgreSQL
Applications and users don't touch the data directly. They go through the DBMS.
Data is stored once. An update in one place is an update for everyone.
This creates a "Single Source of Truth", ensuring all departments use the same, correct data.
Centralized data is easy to share across departments, providing a holistic view of the business.
The DBMS provides a sophisticated security framework.
The DBMS can enforce rules to ensure data quality.
Example Rule: An `order_quantity` field must be a positive number. The DBMS will reject any attempt to enter a negative value.
The most popular database model. Data is organized into tables (relations).
A collection of rows and columns.
Represents a single item or entity (e.g., one customer).
Represents a characteristic of that entity (e.g., customer name).
Example: A `Customers` Table
CustomerID | FirstName | LastName | City
-----------|-----------|-----------|-----------
101 | Ram | Thapa | Kathmandu
102 | Sita | Sharma | Pokhara
Tables are linked together using special columns called keys.
A unique identifier for each row in a table. No two rows can have the same PK.
Example: `CustomerID` in the `Customers` table.
A primary key from one table that is placed in another table to create a link.
Example: `CustomerID` in the `Orders` table.
This link allows us to see all orders placed by a specific customer!
Before building, you must design. This is done with a data model.
Data Model: An abstract diagram that illustrates the data structure and relationships between different pieces of data.
A common tool for this is the Entity-Relationship Diagram (ERD).
ERDs visually represent the database structure using three main components:
The "things" we store data about.
e.g., Customer, Product, Order
The properties or characteristics of an entity.
e.g., CustomerName, ProductPrice
How entities are connected to each other.
e.g., A Customer `places` an Order.
The database approach is the backbone of modern digital services.
A central database stores `Products`, `Customers`, and `Orders`. This single source of truth ensures your cart is accurate and sellers know what to ship.
Your `UserID` (Primary Key) links your account to all your `Transactions`. The DBMS ensures security and data integrity for every payment.
A national database links `Vehicle` information to `Owner` information using keys, helping manage taxes ("blue book") and ownership records efficiently.
Any questions?
Next Up: Unit 3.4 - Introduction to SQL