Exam 1-Chapter 2 Flashcards

1
Q

Model

A

An abstraction of a real-world object or event; useful in understanding complexities of the real world environment

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

Data Models

A

Relatively simple representations of complex real-world data structures (often graphical); data modeling is iterative and progressive)

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

Importance of Data Models

A

Facilitate interaction among the designer, the applications programmer, and the end user
End users have different views and needs for data
Data model organizes data for various users
Data model is an abstraction (cannot draw required data out of the data model)

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

Entity

A

Anything about which data are to be collected and stored

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

Attribute

A

Describes an association among entities
One-to-many (1:M) relationship
Many-to-many (M:N or M:M) relationship
One-to-one (1:1) relationship

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

Constraint

A

A restriction placed on the data

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

Business Rules

A

Descriptions of policies, procedures, or principles within a specific organization (apply to any organization that stores and used data to generate information); Description of operations to create/enforce actions within an organization’s environment (must be in writing and kept up to date;must be easy to understand and widely disseminated);describe characteristics of data as viewed by the company

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

Sources of Business Rules

A
Company managers
Policy makers
department managers
Written documentation (procedures;standards; operations manuals)
Direct interviews with end users
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Importance of Documenting Business Rules

A
  • Standardize company’s views of data
  • Communications tool between users and designers
  • Allow designer to understand the nature, role, and scope of data
  • Allow designer to understand business processes
  • Allow designer to understand business processes
  • Allow designer to develop appropriate relationship participation rules and constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

The Hierarchical Model

A

The hierarchical model was developed in the 1960s to manage large amounts of data for manufacturing projects
Basic logical structure is represented by an upside-down “tree” with levels or segments
Higher layer=parent
Lower layer=child
1:1, 1:M

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

Network Model

A

The network model was created to represent complex data relationships more effectively than the hierarchical model (improves database performance)
Network database=collection of records in 1:M and M:M relationships

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

Owner

A

Equivalent to the hierarchical model’s parent

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

Member

A

Equivalent to the hierarchical model’s child

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

Schema

A

Conceptual organization of entire database as viewed by the database administrator

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

Subschema

A

Database portion “seen” by the application programs

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

Data Management Language (DML)

A

Defines the environment in which data can be managed

17
Q

Data Definition Language (DDL)

A

Enables the administrator to define the schema components

18
Q

Disadvantages of the Network Model

A

Became too cumbersome for larger, more complex data sets
Lack of ad hoc query capability placed burden on programmers to generate code for reports
Structural change in the database could produce havoc in all application programs

19
Q

Relational Database Management System (RDBMS)

A

Hides complexity from the user by managing all the physical details and allowing the user to work at the logical level
How the data is physically stored in the database is of no concern to the user or the designer
Relational table stores collection of related entities
Tables are related through common attributes

20
Q

Relational Diagram

A

Representation of entities, attributes, and relationships

21
Q

Entity Relationship Model

A

Graphical representation of entities and their relationships in a database structure
Entity is represented in ERD by a rectangle
Mapped to a relational type

22
Q

Entity Relationship Diagram (ERD)

A

Uses graphic representations to model database components

Entity is mapped to a relational table

23
Q

Chen Notation

A

Relationships are represented by a diamond with the relationship name written inside it
Connectivities written next to entity boxes

24
Q

Crow’s Foot Notation

A

Connectivities represented by symbols

25
Q

Object-Oriented (OO) Model

A

OODM (Object-Oriented Data Model) is the basis for OODBMS
Both data and relationships are contained in a single structure known as an object
An object also contains all operations that can be performed on it

26
Q

Classes

A
Objects that share similar characteristics (attributes and methods) 
Organized in a class hierarchy
27
Q

Inheritance

A

Object inherits methods and attributes or parent class

28
Q

Unified Modeling Language (UML)

A

Based on OO concepts that describe diagrams and symbols (used to graphically model a system, UML class diagrams used to represent data and relationships

29
Q

Extended Relational Data Model (ERDM)

A

Semantic data model developed in response to increasing complexity of applications
Includes many of OO model’s best features
Often described as an object/relational database management system (O/RDBMS)
Primarily geared to business applications

30
Q

Extensible Markup Language (XML)

A

The Internet revolution created the potential to exchange critical business information
Emerged as the de facto standard
Current databases support XML (XML: the standard protocol for data exchange among systems and Internet services

31
Q

Big Data

A
  • Find new and better ways to manage large amounts of Web-generated data and derive business insight from it
  • Simultaneously provides high performance and scalability at a reasonable cost
  • Relational approach does not always match the needs of organizations with Big Data Challenges
32
Q

NoSQL Databases

A
  • Not based on the relational model, hence the name NoSQL
  • Supports distributed database architectures
  • Provides high scalability, high availability, and fault tolerance
  • Supports very large amounts of sparse data (number of attributes is very large; number of actual data instances is low)
  • Geared toward performance rather than transaction consistency
33
Q

External Schema

A

Specific representation of an external view, Includes:

  • Entities
  • Relationships
  • Processes
  • Constraints
34
Q

The Conceptual Model

A

Represents global view of the entire database
All external views integrated into single global view: conceptual model or schema
-ERD graphically represents the conceptual schema (logical model)
-Provides a relatively easily understood macro level view of data environment
-Independent of both software and hardware

35
Q

THey Physical Model

A
  • Operates at lowest level of abstraction
  • Requires the definition of physical storage and data access methods
  • Physical independence: when changes in physical model do not affect internal model