Term
|
Definition
| storage structure that provides mechanisms for recording, manipulating, and retrieving data. |
|
|
Term
| DBMS (database management system) |
|
Definition
| Used to create and maintain the structure of a database, and then to enter, manipulate, and retrieve the data it stores. |
|
|
Term
|
Definition
| Basic unit of data, and it can be a letter, number, or a special symbol |
|
|
Term
|
Definition
| Group of related characters / Column |
|
|
Term
|
Definition
| Collection of fields about one customer / Row |
|
|
Term
|
Definition
| Group of records about the same type of entity / Table |
|
|
Term
| System Development Life Cycle (SDLC) |
|
Definition
| Design and development process to determine the most appropriate structure of fields, records, and files in a database |
|
|
Term
| What are the steps of SDLC? |
|
Definition
1. Systems Investigation: Understanding the problem
2. System Analysis: Understanding the solution to the previously identified problem
3. System Design: Defining the logical and physical components
4. System Implementation: Creating the system
5. System Integration and Testing: Placing the system into operation for testing
6. System Deployment: Placing the system into production
7. System Maintenance and Review: Evaluating the implemented system |
|
|
Term
|
Definition
| any person, place, or thing with characteristics or attributes that will be included in the system. |
|
|
Term
|
Definition
| diagram that identifies the entities (customers, books, orders and such) in the database, and it shows how the entities are related to one another. |
|
|
Term
| Solid line connecting two entities |
|
Definition
| Relationship is mandatory |
|
|
Term
| Dashed line connecting two entities |
|
Definition
|
|
Term
|
Definition
Process used to create a design that reduces or eliminates data redundancy and, therefore, avoids anomalies.
It helps database designers determine which attributes, or fields, belong to each entity. |
|
|
Term
|
Definition
| Data that hasn't been designed by using a normalization process. |
|
|
Term
|
Definition
| field that identifies each record uniquely. |
|
|
Term
|
Definition
| indicates that all values of the columns contain no repeating values. |
|
|
Term
|
Definition
| When more than one field is used as the primary key for a table |
|
|
Term
|
Definition
| Problem that can occur when the primary key consists of more than one field. Fields contained in a record (row) depend on only one portion of the primary key. |
|
|
Term
|
Definition
| The second step in the normalization process, in which partial dependencies are removed from database records by breaking a composite primary key into two parts, each representing a separate table. |
|
|
Term
|
Definition
| at least one value in the record isn't dependent on the primary key but on another field in the record |
|
|
Term
|
Definition
| The third step in the normalization process, in which transitive dependencies are removed from database records. |
|
|
Term
|
Definition
| Connection between two tables |
|
|
Term
|
Definition
| When a common field exists in two tables being joined, it's called a primary key in one table and a foreign key in the second table. Foreign key appears on the "many" side of one-to-many relationship |
|
|
Term
|
Definition
| Placed between the original entities and serves as a "filter" for the data |
|
|
Term
|
Definition
| Common description for the table referenced in a foreign key relationship. |
|
|
Term
| SQL (Structured Query Language) |
|
Definition
| Data sub-language with commands focused on creating database objects and manipulating data stored in a database. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Create or modify data values |
|
|
Term
|
Definition
|
|
Term
|
Definition
| Save or undo data value modifications |
|
|
Term
|
Definition
| Set permissions to access database structures |
|
|
Term
|
Definition
| Analyzing historical sales data and other information stored in an organizations database |
|
|
