Introduction to Database and Transactions Flashcards
(73 cards)
1
Q
Organized collection of logically related data
A
Database
2
Q
Stored representations of meaningful objects and events
A
Data
3
Q
Two Classifications of Data
A
- Structured
2. Unstructured
4
Q
Classification of data that are numbers, text, dates
A
Structured
5
Q
Classification of data that are images, video, documents
A
Unstructured
6
Q
Data processed to increase knowledge in the person using the data
A
Information
7
Q
Data that describes the properties and context of user data
A
Metadata
8
Q
Turn data into useful information that managers can use for decision making and interpretation
A
Graphical Displays
9
Q
What are the 5 Disadvantages of File Processing?
A
- Program-Data Dependence
- Duplication of Data
- Limited Data Sharing
- Lengthy Development Times
- Excessive Program Maintenance
10
Q
All programs maintain metadata for each file they use
A
Program-Data Dependence
11
Q
Different systems/programs have separate copies of the same data
A
Duplication of Data
12
Q
No centralized control of data
A
Limited Data Sharing
13
Q
Programmers must design their own file formats
A
Lengthy Development Times
14
Q
80% of information systems budget
A
Excessive Program Maintenance
15
Q
- Waste of space to have duplicate data
- Causes more maintenance headaches
A
Problems with Data Redundancy
16
Q
What is the iggest problem of Problems with Data Redundancy?
A
- Data changes in one file could cause inconsistencies
- Compromises in data integrity
17
Q
What is the solution for Problems with Data Redundancy?
A
Database Approach
18
Q
- Central repository of shared data
- Data is managed by a controlling agent
- Stored in a standardized, convenient form
A
Database Approach
19
Q
What is required in Database Approach?
A
Database Management System (DBMS)
20
Q
A software system that is used to create, maintain, and provide controlled access to user databases
A
Database Management System
21
Q
Contains employee,
order, inventory,
pricing, and
customer data
A
Central Database
22
Q
What are the 10 Advantages of the Database Approach?
A
- Program-data Independence
- Planned Data Redundancy
- Improved Data Consistency
- Improved Data Sharing
- Increased Application Development Productivity
- Enforcement of Standards
- Improved Data Quality
- Improved Data Accessibility and Responsiveness
- Reduced Program Maintenance
- Improved Decision Support
23
Q
What are the 5 Costs and Risks of the Database Approach?
A
- New, specialized personnel
- Installation and Management Cost and Complexity
- Conversion Costs
- Need for Explicit Backup and Recovery
- Organizational Conflict
24
Q
What are the 4 Elements of the Database Approach?
A
- Data Models
- Entities
- Relationships
- Relational Databases
25
Graphical system capturing nature and relationship of data.
Data Models
26
Two Classifications of Data Models
1. Enterprise Data Model
| 2. Project Data Model
27
Classification of data model that has a high-level entities and relationships for the organization.
Enterprise Data Model
28
Classification of data model that has more detailed view, matching data structure in database or data warehouse.
Project Data Model
29
- Noun form describing a person, place, object, event, or concept
- Composed of attributes
Entities
30
- Between entities
| - Usually one-to-many (1:M) or many-to-many (M:N)
Relationships
31
Database technology involving tables (relations) representing entities and primary/foreign keys representing relationships.
Relational Databases
32
9 Components of the Database Environment
1. CASE Tools
2. Repository
3. Database Management System (DBMS)
4. Database
5. Application Programs
6. User Interface
7. Data/Database Administrators
8. System Developers
9. End Users
33
Computer-aided software engineering
CASE Tools
34
Centralized storehouse of metadata
Repository
35
Software for managing the database
Database Management System (DBMS)
36
Storehouse of the data
Database
37
Software using the data
Application Programs
38
Text and graphical displays to users
User Interface
39
Personnel responsible for maintaining the database
Data/Database Administrators
40
Personnel responsible for designing databases and software
System Developers
41
People who use the applications and databases
End Users
42
- First step in the database development process
- Specifies scope and general content
- Overall picture of organizational data at high level of abstraction
- Entity-relationship diagram
- Descriptions of entity types
- Relationships between entities
- Business rules
Enterprise Model
43
Two Approaches to Database and IS Development
1. SDLC
| 2. Prototyping
44
- Detailed, well-planned development process
- Time-consuming, but comprehensive
- Long development cycle
SDLC (System Development Life Cycle)
45
- Cursory attempt at conceptual data modeling
- Define database during development of initial prototype
- Repeat implementation and maintenance activities with new prototype versions
Prototyping with the use of Rapid Application Development (RAD)
46
Part in Systems Development Life Cycle
Purpose: preliminary understanding
Deliverable: request for study
Database Activity: enterprise modeling and early conceptual data modeling
Planning
47
Part in Systems Development Life Cycle
Purpose: thorough requirements analysis and structuring
Deliverable: functional system specifications
Database Activity: thorough and integrated conceptual data modeling
Analysis
48
Part in Systems Development Life Cycle
Purpose: information requirements elicitation and structure
Deliverable: detailed design specifications
Database Activity: logical database design (transactions, forms, displays, views, data integrity and security)
Logical Design
49
Part in Systems Development Life Cycle
Purpose: develop technology and organizational specifications
Deliverable: program/data structures, technology purchases, organization redesigns
Database Activity: physical database design (define database to DBMS, physical data organization, database processing programs)
Physical Design
50
Part in Systems Development Life Cycle
Purpose: programming, testing, training, installation, documenting
Deliverable: operational programs, documentation, training materials
Database Activity: database implementation, including coded programs, documentation, installation and conversion
Implementation
51
Part in Systems Development Life Cycle
Purpose: monitor, repair, enhance
Deliverable: periodic audits
Database Activity: database maintenance, performance analysis and tuning, error corrections
Maintenance
52
Prototyping Database Methodology:
- Analyze requirements
- Develop preliminary data model
Conceptual Data Modeling
53
Prototyping Database Methodology:
- Analyze requirements in detail
- Integrate database views into conceptual data model
Logical Database Design
54
Prototyping Database Methodology:
- Define new database contents to DBMS
- Decide on physical organization for new data
- Design database processing programs
Physical Database Design and Definition
55
Prototyping Database Methodology:
- Code database processing
- Install new database contents, usually from existing data sources
Database Implementation
56
Prototyping Database Methodology:
- Analyze database to ensure it meets application needs
- Fix errors in database
Database Maintenance
57
Prototyping Database Methodology:
- Analyze database for improved performance
- Fix errors in database
Database Maintenance
58
3 Database Schema
1. External Schema
2. Conceptual Schema
3. Internal Schema
59
Classification of Database Schema:
- User Views
- Subsets of Conceptual Schema
- Can be determined from business-function/data entity matrices
- DBA determines schema for different users
External Schema
60
Classification of Database Schema:
- E-R models
Conceptual Schema
61
Classification of Database Schema:
- Logical structures
- Physical structures
Internal Schema
62
2 Structures of Internal Schema
1. Logical Structures
| 2. Physical Structures
63
A planned undertaking of related activities to reach an objective that has a beginning and an end
Project
64
Who are involved in managing projects? (9)
1. Business Analysts
2. Systems Analysts
3. Database Analysts and Data Modelers
4. Users
5. Programmers
6. Database Architects
7. Data Administrators
8. Project Managers
9. Other technical experts
65
Evolution of Database Systems is driven by Four Main Objectives:
1. Need for program-data independence -> reduced maintenance
2. Desire to manage more complex data types and structures
3. Ease of data access for less technical personnel
4. Need for more powerful decision support platforms
66
2 Enterprise Applications
1. Enterprise Resource Planning (ERP)
| 2. Data Warehousing Implementations
67
Three-tiered Client/Server Database Architecture:
- Database of vendors, purchase orders, vendor invoices
Accounts Payable Processing Browser
68
Three-tiered Client/Server Database Architecture:
- Database of customer receipts and our payments to vendors
Cash Flow Analyst Browser
69
Three-tiered Client/Server Database Architecture:
- No local database
Customer Service Representative Browser
70
Three-tiered Client/Server Database Architecture:
- A/P, A/R, order processing, inventory control, and so forth; access and connectivity to DBMS, Dynamic Web pages; management of session
Application/Web Server
71
Three-tiered Client/Server Database Architecture:
- Transaction databases containing all organizational data or summarizes of data on department servers
Enterprise Server with DBMS
72
Enterprise database application that integrate all enterprise functions (manufacturing, finance, sales, marketing, inventory, accounting, human resources)
Enterprise Resource Planning (ERP)
73
Enterprise database application that Integrated decision support system derived from various operational databases.
Data Warehouse
