DCIT24 Flashcards

1
Q

it is concerned with the nature and use of data

A

data analysis

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

in practice, go directly from fact finding to implementation dependent data analysis

A

systems analysts

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

establishing the nature of data

A

data analysis

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

establishing the use of data

A

functional analysis

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

the designer creates a written specification in words for the database system to be built

A

database study

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

conceptual, logical, and physical design steps in taking specifications to physical implementable designs

A

database design

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

it is quite possible that the database is to run on a machine which as yet does not have a database management system running on it

A

implementation and loading

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

the database, once implemented, must be tested against the specification supplied by the client

A

testing and evaluation

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

the system is actually in real usage by the company

A

operation

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

designers rarely get everything perfect first time

A

maintenance and evolution

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

often referred to as the three-level model

A

three-level database model

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

the design moves from a written specification taken from the real-world requirements to a physically implementable design

A

three-level database model

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

three levels of database model

A
  • conceptual design
  • data model mapping
  • physical design
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

takes the requirements and produces a high-level data model of the database structure

A

conceptual design phase

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

the conceptual schema is converted into database internal structures

A

physical design phase

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

process of creating a visual representation of either a whole
information system or parts of it to communicate connections between data points and structures

A

data modeling

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

built around business needs

A

data models

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

can be modeled at various levels of abstraction

A

data

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

types of data models

A
  • conceptual data models
  • logical data models
  • physical data models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

also referred to as domain models

A

conceptual data models

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

offer a big-picture view of what the system will contain, how it will be organized, and which business rules are involved

A

conceptual data models

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

less abstract and provide greater detail about the concepts and relationships in the domain

A

logical data models

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

provide a schema for how the data will be physically stored within a database

A

physical data models

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

they’re the least abstract of all

A

physical data models

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
data modeling techniques
- hierarchical data modeling - network data modeling - relational data modeling - entity-relationship data modeling - dimensional data modeling - object-oriented data modeling - graph data modeling
26
organize data in a treelike arrangement of parent and child records
hierarchical data modeling
27
similar hierarchical method is also used today
XML or extensible markup language
28
a popular data modeling option in mainframe databases that isn't used as much now
network data modeling
29
allowing child records to be connected to multiple parent records
network data modeling
30
a more flexible alternative to hierarchical and network ones
relational data modeling
31
visually map entities, their attributes and the relationships between different entities
entity-relationship data modeling
32
primarily used in data warehouses and data marts that support business intelligence applications
dimensional data modeling
33
similar to the ER method, but it abstracts entities into objects
object-oriented data modeling
34
a more modern offshoot of network and hierarchical models
graph data modeling
35
steps of data modeling
- define an entity - define key properties for each entity - identify relationships between entities - mapping properties to entities - reduce redundance in performance requirements - complete and validate the data model
36
benefits of data modeling
- internal agreement on data definitions and standards - increased involvement in data management by business users - more efficient database design at a lower cost - better use of available data assets
37
the constraints, policies, and logic that govern how your data behaves and relates to each other
business rules
38
business rules
- identify the sources - define the scope - express the rules - implement the rules
39
a collection of tasks or processes that enhance the designing, development, implementation, and maintenance of enterprise data management system
database design
40
it is not an important discussion that has to be taken forward in this article because we are focused on the database design
life cycle
41
this stage is concerned with planning the entire DDLC (Database Development Life Cycle)
planning
42
this stage covers the boundaries and scopes of the proper database after planning
system definition
43
concerned with the practices and implementations of the logical model
physical model
44
concerned with developing a model based on the proposed requirements
logical model
45
used to import and convert data from the old to the new system
data conversion and loading
46
concerned with error identification in the newly implemented system
testing
47
a crucial step because it checks the database directly and compares the requirement specifications
testing
48
process of determining the logical data structures that are required to support information resources within an organization
logical database design
49
critical to the implementation of a corporate database
logical design
50
represents the database as a collection of relations
relational model
51
properties which define a relation
attributes
52
stored along with its entities
table
53
it represents records
rows
54
it represents attributes
column
55
a single row of a table, which contains a single record
tuple
56
represents the name of the relation with its attributes
relation schema
57
total number of attributes which in the relation
degree
58
total number of rows present in the table
cardinality
59
it represents the set of values for a specific attribute
column
60
a finite set of tuples in the RDBMS system
relation instance
61
every row has one, two or multiple attributes
relation key
62
every attribute has some pre-defined value and scope
attribute domain
63
conditions which must be present for a valid relation
relational integrity constraints
64
can be violated if an attribute value is not appearing in the corresponding domain or it is not of the appropriate data type
domain constraints
65
an attribute that can uniquely identify a tuple in a relation
key of the table
66
based on the concept of Foreign Keys
referential integrity constraints
67
an important attribute of a relation
foreign key
68
a type of flowchart that illustrates how “entities” relate to each other within a system
entity relationship (ER) diagram
69
a definable thing that can have data stored about it
entity
70
group of definable things
entity type
71
same as an entity type, but defined at a particular point in time
entity set
72
an attribute that uniquely defines an entity in an entity set
entity keys
73
set of attributes (one or more) that together define an entity in an entity set
super key
74
minimal super key, it has the least possible number of attributes
candidate key
75
a candidate key chosen by the database designer to uniquely identify the entity set
primary key
76
how entities act upon each other or are associated with each other
relationship
77
same entity participates more than once in the relationship
recursive relationship
78
property or characteristic of an entity
attribute
79
property or characteristic of a relationship
descriptive attribute
80
the attribute value is atomic and can’t be further divided
simple
81
sub-attributes spring from an attribute
composite
82
attributed is calculated or otherwise derived from another attribute
derived
83
more than one attribute value is denoted
multi-value
84
just one attribute value
single value
85
cardinality can be shown as look-across or same-side
cardinality views
86
minimum or maximum numbers that apply to a relationship
cardinality constraints
87
highest level in a data flow diagram // a tool popular among business analysts
context diagram
88
first drawn in the middle of the chart // usually a circle shape that represents a conceptual boundary
context bubble
89
represents all the external components that may interact with the system
system context diagram