Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Databases > Databases > Flashcards

Databases Flashcards

Study for CP2404 final exam

1
Q

attribute

A

A characteristic of an entity or object. An attribute has a name and data type.

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

binary relationship

A

An ER term for an association (relationship) between two entities. For example PROFESSOR teaches COURSE.

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

business rule

A

A description of a policy, procedure or principle within an organisation. For example, a pilot cannot be on duty for more than 10 hours during a 24-hour period, or a professor may teach up to four classes during a semester.

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

candidate key

A

A minimal superkey; that is, a key that does not contain a subset of attributes that is itself a superkey.

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

cardinality

A

A property that assigns a specific value to connectivity and expresses the range of allowed entity occurrences associated with a single occurrence of the related entity.

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

class diagram notation

A

The set of symbols used in the creation of class diagrams.

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

closure

A

A property of relational operators that permits the use of relational algebra operators on existing tables (relations) to produce new relations.

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

completeness constraint

A

A constraint that specifies whether each entity supertype occurrence must also be a member of at least one subtype. The completeness constraint can be partial or total. Partial completeness means that some supertype occurrences might not be members of nay subtype. Total completeness means that every supertype occurrence must be a member of at least one subtype.

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

composite attribute

A

An attribute that can be further subdivided to yield additional attributes. For example, a phone number such a 6158982368 may be divided into an area code (615), an exchange number (898), and a four digit code (2368). Compare to simple attribute

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

composite entity

A

An entity designed to transform an M:N relationship to two 1:M relationships. The composite entity’s primary key comprises at least the primary keys of the entities that it connects. Also known as bridge entity. See also linking table.

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

composite identifier

A

In ER modeling, a key composed of more than one attribute.

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

composite key

A

A multiple attribute key.

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

conceptual model

A

The output of the conceptual design process. The conceptual model provides a global view of an entire database and describes the main data objects, avoiding details

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

conceptual schema

A

A representation of the conceptual model, usually expressed graphically.

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

connectivity

A

The classification of the relationship between entities. Classifications include 1:1, 1:M, and M:N.

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

constraint

A

A restriction placed on data usually the form of rules. For example, “A student’s GPA must be between 0.00 and 4.00.” Constraints are important because they help to ensure data integrity.

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

crow’s foot notation

A

A representation of the entity relationship diagram that uses a three-pronged symbol to represent te “many” sides of the relationship.

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

data dictionary

A

A DBMS component that stores metadata–data about data. Thus, the data dictionary contains the data definition as well as their characteristics and relationships. A data dictionary may also include data that are external to the DBMS. Also know as an information resource dictionary.

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

data redundancy

A

A condition in which the data environment contains redundant (unnecessarily duplicated) data.

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

database system

A

An organisation of components that defines and regulates the collection, storage, management, and use of data in a database environment.

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

dependent

A

An attribute whose value is determined by another attribute.

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

derived attribute

A

An attribute that does not physically exist within the entity and is derived via an algorithm. For example, the Age attribute might be derived by subtracting the birth date from the current date.

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

design trap

A

A problem that occurs when a relationship is improperly or incompletely identified and is therefore represented in a way that is not consistent with the real world. The fan trap is the most common design trap.

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

determinant

A

Any attribute in a specific row whose value directly determines other values in that row.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
determination
The role of a key. In the context of a database table the statement "A determines B" indicates that knowing the value of attribute A means that the value of attribute B can be looked up.
26
difference
Difference is a relational set operator that yields all rows in one table that are not found in the other table; that is, it subtracts one table from the other table which eliminates duplicates. Tables must be union compatible.
27
disjoint subtype
In a specialisation hierarchy, a unique and nonoverlapping subtype entity set.
28
Domain
In data modelling to construct used organise and describe an attribute's set of possible values
29
Entity
person place thing concept or events for which data can be stored
30
Entity Cluster
a virtual entity type used to represent multiple entities and relationships in the ERD. An entity cluster is formed by combining multiple interrelated entities into a simple single abstract entity object. An entity cluster is considered virtual abstract because it is not really an entity in the final ERD.
31
Entity instance
in ER modelling a specific table row also known as an entity occurrence.
32
entity integrity
the property of a relational table that guarantees each entity has unique value in primary key and that the key has no null values.
33
entity relationship diagram
A diagram that depicts an entity relationship model's entities, attributes, and relations.
34
entity subtype
in a generalisation specialisation hierarchy a subset of an entity super-type the entity super-type contains the common characteristics and the subtypes contained the unique characteristics of each entity
35
entity supertype
in a generalisation specialisation hierarchy a generic entity chance it contains the common characteristics of entity sometimes.
36
existence dependent
A property of an entity his existence depends on when I’m on the entities in such an environment the existence of independent table must be created and loaded first because the existence dependent he cannot reference the table that does not yet exist.
37
existence independent
A property of an entity that can exist apart from one or more related entities. Such a table must be created first one referencing in an existence dependent table.
38
external model
the application program is view of the data environment. Given its business focus, and external model works with the data subset of the global database schema.
39
external schema
the specific representation of an external view; the end users you of the daughter environment.
40
Fan trap
A design error that occurs when one entity is in one to many relationships with other entities that produces an association among the other entities that is not expressed in the model.
41
Foreign key
That should be like to be in one table Israelis much my last match the primary key in another table or he says must be now
42
Full functional dependence
A condition in which actually dysfunctionally dependent on a composite key but not on any subset
43
Functional dependence
With in relation are and actually be functionally dependent on actually a if and only if the given value of actually a determined exactly one day about you beingThe relationship quite B is depending on a unquote is equivalent toQuite a determine the unquote and is written as baby
44
Generalisation
In a specialisation hierarchy the grouping of common actually into a super type entity
45
Hardware Independence
Condition in which a model does not depend on hardly used in the models implementation therefore changes in the hardware will have no effect on the database design conceptualLevel
46
Hierarchical model
An early database model is basic concepts and characteristics formed the basis of subsequent database development. This model is based on upside down tree structure in which each record is called the segmentWill stopTop record is the root segment each segment has a one to many relationship to segment directly below it.
47
Identifiers
In an ER and unique name to be gently instant. In the relational model, such identifiers are up to primary keys and tables.
48
Inheritance
Any object oriented garden model, the ability of an object to inherit the dey destruction and methods of classes are bothered in the class hierarchy.
49
Internal model
In database modelling, I level of the abstraction that DAT conceptual model to a specific DBMS model to implementation.Internal model is the representation of the database as clay scene" by the DBMS. In other words, the internal model requires a designer to match the conceptual models characteristics and constraints today to the selected implementation model.
50
Internal schema
A representation of an internal model using database contract constructs supported by the chosen database.
51
key
An entity identify a based on the concept of functional dependents; please maybe classified in several ways. Examples include super keys candidate keys firing key secondary keys phone keysForeign please
52
Key attributes
That attributes that form the primary key
53
Logical design
I stay in a stage in the design phase that matches the conceptual design to the requirements of the selected DBMS it is therefore software independentLogical design and used to translate the conceptual design into the internal model for a selected database management systemThat is DVT SQL Server Oracle IMs Informix access for ingress
54
Logical independence
A condition in which the internal model can be changed without affecting the conceptual model.(The internal model is hardly independent because it is unaffected by the computer on which the software installed. Therefore, changing storage devices operating systems, in fact affects the internal model.)
55
Mandatory participation
Relationship England in which one and two parents must have a corresponding parenting another entity for example, an employee works in a division,(a person can't be an employee without being signed to a company's division.)
56
M:N
Association among Kilmartin to which one of parents of an empty is associated with many occurrences ever related entity and one parents of the related entities associated with many occurrences of the firstAnd 13
57
Multi-valued attribute
And actually that can have many values for a single entity parents for example thenAnd degree actually it might store the string BBA MBA PhD to indicate three different degrees hell
58
Natural key (natural identifier)
They generally accepted identifies the real world Objects. As its name implies, financial keys familiar to end users and forms partly day-to-day business vocabulary.
59
Network model
I don't model standards created in the late 1960s the represented dad is a collection of record types and relationships predefined sex with an own record type and a member record type in a one to many relationship
60
1:M
Associations among two more interviews that are used by Donna models in a one to many relationship finding to the incentive associated with many instances of the related
61
1:1
Associations 12 or more interviews that are used by data models in a one to one relationship one entity incident is associated with only one instance of the related entity
62
Optional attribute
In the ER modelling and actually that does not require a value; therefore, it can be left empty.
63
Optional participation
In ER modelling, a condition in which wanted to your parents does not require a corresponding entity occurrence in particular relationship.
64
Overlapping subtype
In a specialisation hierarchy, a condition in which each entity instance or road of the super tight canopy in more than one subtype.
65
Partial completeness
In a generalisation hierarchy, a condition in which some super-type occurrences might not be members of any subtype.
66
Participants
And ER term to entities that participate in a relationship for example in the relationship professor teachers class teachers relationship is based on the participant professor and class
67
Physical model
A model in which physical characteristics such as vacation, path, and format described for the data. The physical model is both hardware and software dependent
68
Primary key
In the relational model, and identify a composed of one on my Chevy is that uniquely identifies a row. Also, I can make key selected as a new unique entity identifier.
69
Recursive relationship
Relationship found within A single entity type. For example, an employee is married to an employee for our part is a component of another part.
70
Referential integrity
A condition by Richard depend on tables foreign key must have either no entry or a matching entry in a related table. Even though anchovies may not have a corresponding actually it is impossible to have an invalid entry.
71
Regular entity
An entity that is existent independent that is it can exist apart from all of its related entities. Also called a strong entity
72
Relation
In a relational database model, an entity set. Relations are implemented as tables relations are related to each other through the sharing of common entity characteristic(Everywhen:).
73
Relational diagram
A graphical representation of a relational databases entities actually to them then entities and relationships among the entities.
74
Relational model
Developed by ES kind of IBM in 1970 it represents a major breakthrough thing uses and designers because of its conceptual simplicityRelational model is based on mathematical set theory and represents dad is independent relations each relation(table) is conceptually represented as a matrix of intersecting rows and columns. The relations are related to each other through the sharing of common entity characteristics(values and columns).
75
Relational schema
The organisation of a relational database as described by the database administrator.
76
Relationship
An association among entities
77
Relationship degree
The number of entities or participants associated with the relationship. A relationship degree can be you merry by Mary turn aerial higher
78
Relvar
Short for relation variable, a variable that holds the relation. Rollbar is a container(variable) the holding relation dad are not the relation itself
79
Required attributes
In ER modelling, I naturally that must have a value. In other words, it cannot be left empty.
80
Schema
A magical grouping of database objects, such as tables, indexes, views, and queries, that I related to each other.Usually, as email belongs to a single user or application.
81
Secondary key
A key you strictly forgot a retrieval purposes. For example, customers are not likely to know the customer number(primary key), but the combination of theirLast name, first name, middle initial, and telephone number will probably match the appropriate table rate.
82
Segments
In the hierarchical got a model, the equivalent of a filesystems record type.
83
Simple attribute
Attributes that cannot be further subdivided into meaningful components.
84
Single-valued attributes
Attributes that have only one value
85
Software independence
A property of any model application that does not depend on the software used to be implemented.
86
Specialisation
In a specialisation hierarchy, the grouping of unique attributes into a subtype entity.
87
Specialisation hierarchy
A hierarchy based on the top down process of identifying lower level, more specific entity subtypes from a higher level entity super-type. Specialisation is based on grouping unique characteristics and relationships of the subtypes.
88
Strong relationship
A relationship that occurs when two entities are existence-dependent; from a database design perspective, this relationship exists whenever the primary key of the related entity contains the primary key in the parent entity.
89
Subschema
In the network model, proportion of the database "seen" by the application programs that produce the desired information from the data in the database.
90
Subtype
An entity that contains unique characteristics (attributes) in a more broadly defined entity known as the super-type. In a generalisation hierarchy a subtype is an entity below a parent entity. For example pilot could be some type of the super-type employee.
91
Subtype discriminator
An attribute in the super-type entity that determines to which entity subtype each super-type occurrence is related.
92
Super key
An attribute or attributes that uniquely identify each entity in a table.
93
Surrogate key
A system assigned primary key generally numeric and auto-incremented.
94
System catalogue
A detailed system data dictionary that describes all objects in a database
95
Table
A matrix composed of intersecting rows (entities) and columns (attributes) that represents an entity set in the relational model.
96
Ternary relationship
An ER term used to describe an association (relationship) between three entities
97
Time variant data
Data whose values are a function of times.
98
tuple
In the relational model, a table row.
99
Unary relationship
An ER term used to describe an association with in an entity. For example, a course might be a prerequisite to another course.
100
Unique index
An index in which the index key can have only one associated pointer value (row).
101
Weak entity
An entity that displays existence dependence and inherits the primary key of its parent entity. For example a dependent requires the existence of an employee.
102
Weak relationship
a relationship in which the primary key of the related entity does not contain a primary key component of the parent entity.

Databases (3 decks)

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