Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Fundamentals of Database Systems > Module 2: Database Architecture, Models and Diagram > Flashcards

Module 2: Database Architecture, Models and Diagram Flashcards

(65 cards)

Start Studying
1
Q

A Good Data Name Is:

A
  • related to business, not technical, characteristics
  • meaningful and self-documenting
  • unique
  • readable
  • composed of words from an approved list
  • repeatable
  • written in standard syntax
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

word or phrase with specific meaning

A

Term

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

association between two or more terms

A

Fact

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Guidelines for Good Data Definition

A
  • A concise description of essential data meaning
  • Gathered in conjunction with systems requirements
  • Accompanied by diagrams
  • Achieved by consensus, and iteratively
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

person, place, object, event, concept (often corresponds to a row in a table)

A

Entity Instance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

collection of entities (often corresponds to a table)

A

Entity Type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

link between entities (corresponds to primary key-foreign key equivalences in related tables)

A

Relationship Instance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

category of relationship… link between entity types

A

Relationship Type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

properties or characteristics of an entity or relationship type (often corresponds to a field in a table)

A

Attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

a special entity that is also a relationship

A

Associative

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

specify number of entity types involved

A

Relationship Degrees

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

specify how many of each entity type is allowed

A

Relationship Cardinalities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  • are statements that define or constrain some aspect of the business
  • are derived from policies, procedures, events, functions
A

Business Rules

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Business rules assert _____.

A

business structure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Business rules are automated through _____.

A

DBMS software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

A Good Business Rule

A
  • declarative
  • precise
  • atomic
  • consistent
  • expressible
  • distinct
  • business-oriented
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

what, not how

A

Declarative

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

clear, agreed-upon meaning

A

Precise

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

one statement

A

Atomic

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

internally and externally

A

Consistent

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

structured, natural language

A

Expressible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

non-redundant

A

Distinct

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

understood by business people

A

Business-oriented

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

a person, a place, an object, an event, or a concept in the user environment about which the organization wishes to maintain data

A

Entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
a collection of entities that share common properties or characteristics
Entity Type
26
a single occurence of an entity type
Entity Instance
27
- exists independently of other types of entities | - has its own unique identifier
Strong Entity
28
Strong entity has its own unique identifier underline with _____.
single line
29
- dependent on a strong entity (identifying owner)... cannot exist on its own - does not have a unique identifier (only a partial identifier)
Weak Entity
30
Weak entity box and partial identifier have _____.
double lines
31
Identifier is also primary called _____/
Primary Key
32
links strong entities to weak entities
Identifying Relationship
33
property or characteristic of an entity or relationship type
Attribute
34
Classification of Attrubutes
- Required vs Optional Attributes - Simple vs Composite Attribute - Single-Valued vs Multivalued Attribute - Stored vs Derived Attributes - Identifier Attributes
35
must have a value for every entity (or relationship) instance with which it is associated
Required
36
may not have a value for every entity (or relationship) instance with which it is associated
Optional
37
an attribute that has meaningful component parts (attributes)
Composite Attribute
38
may take on more than one value for a given entity (or relationship) instance
Multivalued
39
values can be calculated from related attribute values (not physically stored in the database)
Derived
40
is saved into the database
Multivalued Attributes
41
is not saved into the database because its values may change over time
Derived Attributes
42
an attribute (or combination of attributes) that uniquely identifies individual instances of an entity type
Identifier (Key)
43
an attribute that could be a key... satisfies the requirements for being an identifier
Candidate Identifier
44
one attribute only
Simple Identifier
45
two or more identifier attributes
Composite Identifier
46
Standard Format for Naming Attributes
[Entity type name {]Qualifier]}] Class
47
is modeled as lines between entity types
Relationship Type
48
two entities can have more than one type of relationship between them
Multiple Relationships
49
combination of relationship and entity
Associative Entity
50
the instance is between specific entity instances
Relationship Instance
51
is the number of entity types that participate in it
Degree of a Relationship
52
one entity related to another of the same entity type
Unary
53
entities of two different types related to each other
Binary
54
entities of three different types related to each other
Ternary
55
each entity in the relationship will have exactly one related entity
One-to-One
56
an entity on one side of the relationship can have many related entities, but an entity on the other side will have a maximum of one related entity
One-to-Many
57
entities on both sides of the relationship can have many related entities on the other side
Many-to-Many
58
can have attributes of its own
A Relationship
59
the number of instances of one entity that can or must be associated with each instance of another entity
Cardinality Constraints
60
Minimum cardinality if zero
Optional
61
Minimum cardinality if one or more
Mandatory
62
Maximum cardinality
the maximum number
63
- an entity that has attributes | - a relationship that link entities together
Associative Entities
64
is like a relationship with an attribute, but it is also considered to be an entity in its own right
Associative Entity
65
a time value that is associated with a data value, often indicating when some event occurred that affected the data value
Time Stamp

Fundamentals of Database Systems (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions