Database Management 3845 Ch1-5

Front 1

Constraint

Back 1

Rule that can't be violated by database user

Front 2

Metadata

Back 2

Data that describe properties of end-user data and the context of that data

Front 3

Repostitory

Back 3

Centralized knowledge base of all data definitions, relationships, screen and report formats, and other system components

Front 4

Entity

Back 4

Person,place,object,event, or concept in the user environment grouped into a single abstract entity type.

Front 5

Data Independence

Back 5

Separation of data descriptions from the application programs that use the data

Front 6

Conceptual Scheme

Back 6

Detailed, technology-independent specification of the overall structure of organizational data.

Front 7

Logical Data model

Back 7

Representation of a database for a particular data management technology.

Front 8

Prototyping

Back 8

Iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analyst and users.

Front 9

System Development life cycle vs prototyping

Back 9

Used to develop, maintain, and replace information systems vs. requirements that are continually revised through close work between analyst and users.

Front 10

Internal Scheme

Back 10

Consists of logical scheme and physical scheme. Logical is representation of data for a type of data management technology while physical scheme describes how data are to be represented and stored in secondary storage.

Front 11

Data vs. Information

Back 11

Data - stored representations of objects and events that have meaning and importance in the users environment.

Data that have been processed in such a way as to increase the knowledge of the person who uses the data.

Front 12

Repository vs. Database

Back 12

Repository - centralize knowledgebase of all data definitions, data relationships, screen and report formats,

Database - Organized collection of logically related data.

Front 13

Data dependence vs. independence

Back 13

Data independence - separation of data descriptions from the application programs that use the data

Data dependence - no seperation

Front 14

5 major components in database system.

Back 14

CASE tools
Repository
DBMS
Database
Application Programs
User interface
Data and database administrators
System developers
End users

Front 15

What are client, application, and enterprise tiers

Back 15

Client tier - desktop or laptop computer which concentrates on managing the user-system interface and localized data

Application tier- Processes HTTP protocol, scripting tasks, performs calculations, and provides access to data

Enterprise tier - Performs sophisticated calculations and manages the merging of data from multiple sources across the organization.

Front 16

Internal Scheme vs. conceptual scheme

Back 16

Internal schema is the end result, conceptual scheme is view of data architect or data administrator.

Front 17

Information Engineering and the difference between it and systems development life cycle

Back 17

Info Engineering - emphasizes the importance of understanding relevant data when creating and maintaining information systems.

System development life cycle - Used to develop, maintain, and replace information systems

Front 18

Attribute

Back 18

Property or characteristic of an entity type that is of interest to the org.

Front 19

Derived attribute

Back 19

Attribute whose values can be calculated from related attribute values.

Front 20

Cardinality

Back 20

Number of instances of one entity that can be associated with each instance of another entity

Front 21

Binary relationship

Back 21

Relationship between the instances of 2 entities

Front 22

Entity-relationship model(E-R model)

Back 22

Logical representation of the data for an organization or for a business area.

Front 23

Multivalued attribute

Back 23

May take on more than one value for a given entity instance.

Front 24

Entity Instance

Back 24

Single occurance of an entity type.

Front 25

Strong entity vs. weak entity

Back 25

Strong - exists independently of other entity types.
Weak - existence depends on some other entity

Front 26

Entity type vs. relationship type

Back 26

Entity type - Collection of entities that share common properties.
Relationship type - meaningful association between entity type.s

Front 27

Business Rule

Back 27

Statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control the behavior of the business.

Front 28

Subtype

Back 28

Subgrouping of entities in an entity type that is meaningful to the organization and that shares common attributes distinct from other subgroupings

Front 29

Supertype

Back 29

Generic entity that has a relationship with one or more subtypes.

Front 30

Action assertions

Back 30

Statement of constraint or control on the actions of the organization.

Front 31

Completeness constraint

Back 31

Type of constraint that address the question whether an instance of a supertype must also be a member of at least one subtype.

Front 32

What is attribute inheritance?

Back 32

Property by which subtype entities inherit values of all attributes of the super type.

Front 33

Relation

Back 33

Named 2d table of data

Front 34

Primary Key

Back 34

Attribute or combination of attributes that uniquely identifies each row in a relation.

Front 35

Data Integrity

Back 35

built into the physical structure of the fields and controls enforced by the DBMS on those fields.

Front 36

Referential Integrity

Back 36

Integrity constraint specifying that the value of an attribute in one relation depends on the value of a primary key in the same or another relation.

Front 37

Normalization

Back 37

Process of decomposing relations with anonmalies to produce smaller; well-structured relations.

Front 38

Candidate Key

Back 38

Attribute or combination of attributes that uniquely identifies a row in a relation.

Front 39

Synonym

Back 39

Two or more attributes having different names but the same meaning, as when they describe the same characteristic of an entity.

Front 40

Transitive dependency

Back 40

Functional dependency between two or more non-key attributes.

Front 41

Determinant

Back 41

Attribute on the left-hand side of the arrow in a functional dependency.

Front 42

Recursive foreign key

Back 42

Foreign key in a relation that references the primary key values of that same relation.

Front 43

Partial dependency vs transitive dependency

Back 43

Partial - one or more attributes dependent on part but not all of primary key
Transitive - two or more non-key attributes are dependent on each other.

Front 44

Foreign key vs. primary key

Back 44

Foreign - serves as the primary key of another relation in the same database
Primary - Uniquely identifies each row in a relation.

Front 45

Normal form vs. normalization

Back 45

Normal form - state of a relation that results from applying simple rules regarding functional dependencies to that relation.
Normalization - Process of decomposing relations with anomalies to produce smaller, well-structured relations.