DBMS

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/79

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

80 Terms

1
New cards

Data

Stored representations of meaningful objects and events; raw unprocessed information that can be structured or unstructured.

2
New cards

Database

An organized collection of logically related data stored and accessed electronically.

3
New cards

Information

Data that has been processed to increase knowledge of a person using it.

4
New cards

Metadata

Data describing the properties and context of other data

5
New cards

Database Management System (DBMS)

Software used to create

6
New cards

Database System

Includes the database

7
New cards

Database Schema

Structure of the database defining how data is organized.

8
New cards

Table

Structure that holds related data.

9
New cards

Record

A row in a table representing a single data entry.

10
New cards

Field

A column in a table representing an attribute.

11
New cards

Key

Unique identifier for a record.

12
New cards

Program-Data Independence

Ability to change the schema without affecting application programs.

13
New cards

Data Redundancy

Unnecessary duplication of data in multiple locations.

14
New cards

Data Sharing

Improved access and sharing of data among users through centralized control.

15
New cards

Data Integrity

Accuracy and consistency of stored data.

16
New cards

Enterprise Resource Planning (ERP)

Integrates all enterprise functions like manufacturing

17
New cards

Data Warehouse

Integrated decision support system derived from operational databases.

18
New cards

Repository

Centralized storehouse of metadata.

19
New cards

CASE Tools

Computer-aided tools for software and database design.

20
New cards

End User

Person who uses database applications.

21
New cards

Data Modeling

Process of defining and organizing data structures for efficient management and retrieval.

22
New cards

Data Model

Abstract representation defining how data is structured and related.

23
New cards

Entity-Relationship (ER) Model

Visual tool showing entities

24
New cards

Normalization

Process of organizing data to minimize redundancy and dependency.

25
New cards

Relationship

Association between entities such as one-to-one or one-to-many.

26
New cards

Schema Design

Development of a conceptual schema based on business needs.

27
New cards

Business Rule

Statement defining or constraining business behavior.

28
New cards

Data Definition

Explanation of a term or fact with specific meaning.

29
New cards

Conceptual Data Model

High-level model describing data independent of DBMS; focuses on meaning and relationships.

30
New cards

Representational Data Model

Logical model showing data structure

31
New cards

Physical Data Model

Defines how data will be stored and accessed in a specific DBMS.

32
New cards

Relational Algebra

Procedural query language describing how to retrieve data.

33
New cards

Relational Calculus

Non-procedural query language describing what data to retrieve.

34
New cards

Multidimensional Model

Represents business data in terms of facts and dimensions for analysis (e.g.

35
New cards

Top-Down Modeling

Approach starting from high-level requirements down to database design.

36
New cards

Bottom-Up Modeling

Approach modifying existing databases starting from physical structures.

37
New cards

Entity Relationship Diagram (ERD)

Graphical representation of entities

38
New cards

Entity

Object or concept about which data is stored.

39
New cards

Strong Entity

Entity that exists independently and has its own unique identifier.

40
New cards

Weak Entity

Entity dependent on another for identification.

41
New cards

Associative Entity

Entity that arises from many-to-many relationships and holds attributes of the relationship.

42
New cards

Attribute

Characteristic or property of an entity or relationship.

43
New cards

Identifier (Key)

Attribute or set of attributes that uniquely identify entity instances.

44
New cards

Unary Relationship

Relationship within the same entity.

45
New cards

Binary Relationship

Relationship between two entities.

46
New cards

Ternary Relationship

Relationship involving three entities.

47
New cards

Cardinality

Defines the number of occurrences of one entity related to another.

48
New cards

Minimum Cardinality

Specifies whether a relationship is optional (0) or mandatory (1).

49
New cards

Maximum Cardinality

Specifies the maximum number of relationships (1 or many).

50
New cards

Primary Key

Unique identifier that cannot be null.

51
New cards

Foreign Key

Attribute linking one table to another.

52
New cards

Composite Attribute

Attribute made up of multiple parts (e.g.

53
New cards

Derived Attribute

Value calculated from other attributes (e.g.

54
New cards

Data Flow Diagram (DFD)

Visual model showing how data moves through a system.

55
New cards

System

Group of interrelated procedures for a specific business function.

56
New cards

Analysis

Process of breaking down a system into components.

57
New cards

Design

Process of constructing or creating a system plan.

58
New cards

Entity (DFD)

External data source or destination defining system boundaries.

59
New cards

Process

Transformation of data; shown as verb phrases.

60
New cards

Data Store

Resting place for data

61
New cards

Data Flow

Movement of data between processes

62
New cards

Context Diagram

High-level DFD showing system boundaries and major data flows.

63
New cards

Level 0 DFD

Expanded DFD showing major sub-processes.

64
New cards

Level 1 DFD

Further detailed breakdown of Level 0 processes.

65
New cards

Law of Conservation of Data

Data cannot be created or destroyed; it must move through processes.

66
New cards

SQL

Standard language for managing data in relational databases

67
New cards

Physical Level

Describes how data is stored on hardware.

68
New cards

Logical Level

Describes what data is stored and its relationships.

69
New cards

One (1:1) — Diagram: —|

One can have one of the other entity (min 1

70
New cards

Optional One (0 or 1) — Diagram: —O|

May have one related record or none (0 or 1). Example: A customer may have one loyalty card

71
New cards

Mandatory One (exactly 1) — Diagram: —||

Must have exactly one related relationship (1). Example: Each student must have exactly one ID card.

72
New cards

Many (0-n) — Diagram: —<

One can have many of the other entities (0-n). Example: A customer can place many orders.

73
New cards

Mandatory Many (1-n) — Diagram: —<|

Must have at least one or more related relationships (1-n). Example: Each department must have at least one employee.

74
New cards

Optional Many (0-n) — Diagram: —O<

May or may not have related records (0-n). Example: A teacher may have many advisees

75
New cards

  • database is directly available to the user for using it to store data

  • used for local application development, where programmers communicate directly with the database for quick response

76
New cards

2 tier DBMS

  • includes and application layer between the user and the DBMS which is responsible between the user’s request with the DBMS

  • application interface known as ODBC (Open Database Connectivity) provides an API that allow client-side program to call the DBMS

  • provides extra security as DBMS is not exposed to the end user directly

77
New cards

3 tier DBMS

  • most commonly used architecture for web applications

  • an additional Presentation or GUI Layer is added, which provides a graphical user interface for the End user to interact with the DBMS

  • for the end user, the GUI layer is the database system

  • ex: mySQL’s PhpMyAdmin

78
New cards

Hierarchical data model

oldest model, tree like structure, implements 1:1 and 1:n relationship

79
New cards

network data model

organizes records to one another thru links/pointers, directed graphs are used, implements 1:1, 1:n, and n:n relationships

80
New cards

Relational data model

uses table to store records, and relationships between tables are set using common fields

Explore top flashcards