DATA MODELING CONCEPT Flashcards

1
Q
  • High-level description of the data domain
  • Does not constrain how that description is mapped to an actual implementation in software
  • There may be many mappings
A

Conceptual Data Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  • Being the scope of a model, it helps to describe the semantics of a domain
A

Conceptual Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  • There are description of Tables, Columns, Object Oriented Classes, XML Tags, Document Structure
A

Logical Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  • This Model Cares about the actual physical structure to store the data, like the partitions, CPU Spaces, Replications, Shards etc
A

Physical Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  • Only addresses data and relationships. Classic, simplest. Best for deriving a sound table design. Many extensions/variations exist. Basis for most other modeling approaches
A

Entity-Relationship (E-R) Models

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  • Class models. Goes beyond data, also models behaviors
A

UML (Unified Modeling Language)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q
  • Technology independent. Contains more detail than the Conceptual Data Model. Considered by many to be just an expanded conceptual data model
A

Logical Data Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  • Documentation of the structure of the data. Used to communicate the design. Serve as the basis for data model implementation
A

Entity Relationship Model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  • effectively become tables
A

Entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  • describe entities and become fields (columns) in tables
A

Attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
  • link tables on a common attribute or “key” and become formal constraints (part of the business rules)
A

Relationships

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
  • maximum number of times an instance in one entity can be associated with instances in the related entity
A

Cardinality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  • minimum number of times an instance in one entity can be associated with instances in the related entity
A

Participation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q
  • Maximum number of times an instance of an entity can be associated with instances of a related entity
  • Can ONLY have values of 1 or many
  • Located closest to the entity in Crow’s Foot notation
A

Cardinality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  • Each row in a table should have an attribute that is a persistent, unique identifier
A

Primary Key

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

Indicates whether an instance of an entity MUST participate in the relationship. Can ONLY have the values of 0 or 1

A

Participation

16
Q
  • Tables represents both data and relationships. Multiple columns with unique names
  • Each record type defines a fixed number of fields, or attributes
  • Most widely used db
A

Relational Model

17
Q
  • Collection of basic objects called entities and its relationships
  • An entity is a real world thing or object
  • Distinguishable from other objects
  • Widely used in database design
A

ER Model

18
Q
  • OOP Languages- C++, Java, C#, etc .Need for Object Oriented data model
A

Object-Based Model

19
Q
  • Specification of data. Individual data items of the same type may have different sets of attributes. Using of 2 different language
A

Semistructured Data Model