Databases Chptr 2 Rob/coronel 8

Front 1

Attribute

Back 1

Characteristic of an entity

Front 2

Entity

Back 2

Anything, person, place, thing, event, about which data are to be collected and stored

Front 3

Relationship

Back 3

Association among entities

Front 4

Many to many relationship

Back 4

M:M

Front 5

One to many relationship

Back 5

1:M

Front 6

One to many

Back 6

One painter...many paintings

Painter=1
Paintings=many
Painter paints painting=
1:M

Front 7

Many to many relationship

Back 7

M:N

Student takes many classes
Each class taken by many students
M:N = student take class

Front 8

One to One relationship

Back 8

Each store managed by one employee

Manager, is an employee manages only one store

Front 9

Relationships

Back 9

Multidirectional

Front 10

Constraint

Back 10

Restriction placed on data

Front 11

Data model

Back 11

Relatively simple representation, usually graphical

Front 12

Model

Back 12

Abstraction of real world event or bject

Front 13

Business rules

Back 13

Breif, precise, unambiguous description of policy procedure, or principle w/in an organization

Front 14

Business rules

Back 14

Must be in writing and updwated

Front 15

Properly written business rules

Back 15

Define entities, attributes, relationships and constraints

Front 16

Business rules descri,be

Back 16

Distinguishing characteristics of data as viewed by the company

Front 17

Not all business rules can be modeled

Back 17

Such rules can be enforced w/ software

Front 18

Noun

Back 18

Will translate into entity in model

Front 19

Verb

Back 19

Will translate into relationship among entities

Front 20

Properly identify relationship type

Back 20

How many instances of B
Related to one instance of A

Front 21

Identify relationship

Back 21

How many instances of A related to B

Front 22

Hierarchy.al model

Back 22

1960s

Front 23

Heirarchial model

Back 23

Manage large amounts of data for complex projects
1960s

Front 24

Segment

Back 24

Equivalent of a file systems record type

Front 25

Hierarchical system

Back 25

Fundation of current models

Front 26

Network model

Back 26

Created to represent complex data relationships more effectively than heirarchical models

Front 27

Conference on data systems
Languages CODASYL

Back 27

Created database task group DBTG
1960s

Front 28

dBTG report

Back 28

Schema
Conctional organization of entire database

Front 29

DBTG

Back 29

Subschema
Portion of database "seen"

Front 30

DBTG

Back 30

Data management language DML
Defines environment in which data can be managed

Front 31

Data definition language DDL

Back 31

Enables database admin to define schematic components

Front 32

Relational model

Back 32

1970s

Front 33

Relational model foundation

Back 33

Math concept known as relation

Front 34

Relation

Back 34

Table

Front 35

Relation/table

Back 35

Matrix of intersecting rows and columns

Front 36

Row

Back 36

Tuple

Front 37

Column

Back 37

Represents attribute

Front 38

Relational database management system
RDBMS

Back 38

Same functions as heirarchal and network but easier o implement and understand

Front 39

Relational diagram

Back 39

Representation of relational database entities, attributes within entities nd relationships between entities

Front 40

Structured query language SQL

Back 40

Allows user to specify what must be done without specifying how it must be done

Front 41

RDBMS

Back 41

Uses SQL

Front 42

End user SQL

Back 42

Three parts
User interface
Set of tables
Engine

Front 43

End user interface

Back 43

Allows end user to interact with data

Front 44

Collection of tables stored in database

Back 44

Relational database, all data perceived to be stored in tables

Front 45

SQL engine

Back 45

Largly hidden from end user
SQL engine executes queries or data requests

Front 46

Entity relationship model ERM

Back 46

Graphical tool for data mod"ing

Front 47

Chen

Back 47

ERM data Odell 1976

Front 48

Er models

Back 48

Normally represented as
Entity relationship diagram
ERD

Front 49

ER model based upon

Back 49

Entity and relationships

Front 50

Connectivity

Back 50

Labels relationship parts

Front 51

Entity instance

Back 51

Entity occurrence
Row in relational table

Front 52

Chen notation

Back 52

Original

Front 53

Crows feet notation

Back 53

More current

Front 54

Crows feet

Back 54

Three part symbol to represent the many side of relationship

Front 55

Chen notation

Back 55

Relationships represented by a diamond connected to related entities through relationship line

Name written inside diamond

Front 56

Object oriented model OODM

Back 56

Dats and relationship contained in single structure known as
Object

Front 57

OODMDATS

Back 57

Basis for object oriented database management system
OODBMS

Front 58

OODMDATS

Back 58

Semantic data model
Smanic indicates meaning

Front 59

Object oriented
oo

Back 59

Object described by factual content

Front 60

Unlike an entity

Back 60

Object excludes information about relationships between facts within an object
+
Information about its relationship w/ other objects

Front 61

object

Back 61

abstraction of real world entity

Front 62

object represents

Back 62

only one occurence of an entity

Front 63

attributes

Back 63

describe properties of an object

Front 64

objects w/ similar characteristics

Back 64

grouped as class

Front 65

class

Back 65

collection of similar objects
shared structure(attributes)
shared behavior(methods)

Front 66

class

Back 66

different from entity set
contains set of procedures(methods)

Front 67

method

Back 67

represent real world actions
(finding, changing)
equivalent to procedures

Front 68

oo methods

Back 68

define objects behavior

Front 69

class organized

Back 69

class heirarcy
upside down tree... each class one parent

Front 70

inheritance

Back 70

ability of an object w/i class heirarchy to inherit attributes and methods of class above it

Front 71

uml
unified model language

Back 71

oo
based on diagrams and symbols
used to graphically model system

Front 72

class diagrams

Back 72

represent data and their relationships w/i larger uml

Front 73

another semantic model

Back 73

ERDM
extended relational data model
4 complex applications

Front 74

DBMS

Back 74

BASED ON ERDM
DESCRIBED AS
object/relational database systems

Front 75

internet

Back 75

changed role and scope of database market

Front 76

ANSI/SPARC
ANSI
american national standards institute

Back 76

three levels of data abstraction
external
conceptual
internal

Front 77

external model

Back 77

end users view of data environment

Front 78

external schema

Back 78

specific representation of an external view

Front 79

conceptual model

Back 79

represents global view of entire database as viewed by entire org.

Front 80

conceptual model integrates

Back 80

all external views
entities, relationships, constraints, processes
into single global view of entire database

conceptual schema

Front 81

software independence

Back 81

model does not depend on dbms software

Front 82

hardware independence

Back 82

model does not depend on hardware

Front 83

logical design

Back 83

task of crating conceptual data model could be implemented in any dbms

Front 84

internal model

Back 84

database as seen by dbms

Front 85

internal schema

Back 85

specific representation of internal model using database constructs

Front 86

software dependent

Back 86

internal model depends on specific software

Front 87

logical independence

Back 87

can change internal model w/o affecting conceptual model

Front 88

physical model

Back 88

lowest level of abstraction
describes how data is saved

Front 89

physical independence

Back 89

can change physical model w/o affecting internal model

Front 90

data model

Back 90

abstraction of complex real world data environment

Front 91

heirarchial and network models

Back 91

early models no longer used

Front 92

relational model

Back 92

current database implementation standard

Front 93

object oriented data model
oodm

Back 93

uses objects as basic modeling structure

Front 94

relational model

Back 94

adopted oo
becomes
extended relational data model

Front 95

data modeling requirements

Back 95

function of different data views
and
level of abstraction