IMNT Exam 2

Application Programs

The software that processes data, handles tasks like recording sales or generating reports

Application/system Programmers

People who write and maintain application programs

Attribute

Specific piece of information describing an entity, like a name or address

Big Data

Huge, complex datasets from many sources (sensors, social media) that traditional databases can't handle easily

Binary Relationship

A connection between two different entities, like between Customer and Sale.

Business Analytics Mindset

Using data to analyze past performance, spot trends, and make better business decisions.

Candidate Keys

Attributes that could be used as the unique identifier for a table because they are different for every record.

Cardinalities

Rules that define how many instances of one entity relate to another (like "one customer has many orders").

Cardinality Constraints

The specific minimum and maximum numbers that define a relationship.

Composite Attribute

An attribute made of smaller parts, like Address being made of Street, City, State, and Zip.

Conceptual Data Model

A high-level picture or map of important business "things" (entities) and how they relate.

Conceptual Modeling Steps

The process of creating that map: understand the business, identify entities, find relationships, add cardinalities.

Data Control Language

Commands used to control who can access and change the database (security and permissions).

Data Definition Language

Commands used to create and modify the structure of the database, like building tables.

Data Dictionary

A central catalog that describes all data in the database, including field names, types, and security rules.

Data Lake

A storage repository that holds vast amounts of raw data in its original format, without needing structure first.

Data Manipulation Language

Commands used to work with data inside tables, like adding, updating, or deleting records.

Data Query Demands

Commands used to ask questions and search for specific data (like SQL).

Database Administrators

The people responsible for managing and maintaining the database system.

Database Management Systems

The software that lets you create, manage, and interact with a database (like MySQL or Oracle).

Database Tables

The actual structures that hold data, organized into rows (records) and columns (fields).

Data-oriented Processing

An approach where many applications share a central database, reducing redundancy and keeping data consistent.

Data Mart

A smaller, focused version of a data warehouse for a specific department or team.

Data Mining

Using software to analyze large datasets and find hidden patterns and relationships.

Data Warehouse

A huge central database that stores historical data from many sources, used for analysis and reporting.

Degree of Relationship

The number of entity types involved in a relationship (like binary for two entities).

Derivable Attributes

Information that can be calculated from other data already in the database, so it doesn't need to be stored.

End Users

The people who use the database and applications to do their jobs (sales reps, accountants, etc.).

Entity

A person, place, thing, event, or concept you need to track (like CUSTOMER, PRODUCT, or SALE).

Entity-relationship Diagram

The drawing used for the conceptual data model, with rectangles for entities and lines showing relationships.

Field

A single piece of data in a database table; a column (like "Customer Name").

File-oriented Processing

An older approach where each application has its own separate data files, leading to duplication.

Foreign Keys

A field in one table that is the primary key of another table, used to create a link between them.

Forms Generators

Tools in a DBMS that make it easy to design data entry screens for users.

Hierarchical Databases

An older database model that organizes data in a tree-like structure with parent-child relationships.

Instances

A single occurrence of an entity. If "Customer" is the entity, then "Customer #1001" is one instance.

Legacy Systems

Old computer systems and technologies that an organization still uses.

Logical

Focuses on how data should be structured from a user's perspective, not technical storage details.

Logical Data Design

The blueprint for the database, showing tables, keys, and how they link together.

Logical Data Design Steps

The process of creating the blueprint: turn entities into tables, pick primary keys, link tables, add attributes.

Logical View/Schemas

A specific way of looking at data for a particular user. A "schema" is the overall database structure.

Mandatory Relationship

A relationship that must exist (a sale must be linked to at least one product).

Maximum Cardinality

The most instances that can be related (a product can be on "many" sales orders).

Minimum Cardinality

The fewest instances that can be related (a new customer could have "zero" sales orders).

Multivalued Attribute

An attribute that can have several values for one entity (an employee can have multiple skills).

Network Logistical Structures

An older database model that is more flexible than hierarchical, allowing complex relationships.

No SQL Database

A database that doesn't use traditional table structures, designed for large-scale or unstructured data.

Normal Form (Normalization)

Organizing data to reduce redundancy and ensure each table only describes one thing.

Object Oriented Logical Structures

A database that stores data and the code that acts on it together as an "object."

Object and Object Oriented

An "object" is a package containing both data and the instructions for what you can do with that data.

Online Analytical Processing

Software for analyzing data from multiple perspectives (by product, region, time, etc.).

Optional Relationships

A relationship that doesn't have to exist (a product may have zero sales orders yet).

Primary Key

A unique identifier for each record in a database table (like Customer ID)

Query by Example

A user-friendly way to search a database by filling in an example of the data you want.

Record

A complete set of information about one instance; a row in a table.

Record Layout

A document showing the structure of a file or table, listing each field, its type, and size.

Relation

The formal term for a table in a relational database; a structure of rows and columns.

Relational Logical Structures

The most common database type, organizing data into tables linked by common fields.

Relationships

The logical connections or associations between different entities.

Report Generators

Tools in a DBMS that help users design and create formatted reports from data.

Schema

The overall structure or blueprint for a database, defining tables, fields, and relationships.

Schema on Read

Applying a structure to data when you read or analyze it, not when you store it.

Schema on Write

Applying a structure to data before storing it in the database (how traditional databases work).

Structures Query Language

The standard programming language used to communicate with relational databases.

Structures, Semi-structured, and Unstructured Data

Categories: structured fits neatly in tables; semi-structured has some tags (like JSON); unstructured has no format (like images).

Ternary Relationship

A relationship involving three different entities at the same time.

Unary Relationship

A relationship an entity has with itself (an Employee manages other Employees).

User Interface

What the user sees and interacts with on screen—menus, buttons, and forms.