Lesson 3 Flashcards

(36 cards)

1
Q

automated tools used to design
databases and application programs

A

Data modeling and design tools

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

centralized storehouse
of metadata

A

Repository

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

software for managing the
database

A

Database Management System
(DBMS)

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

storehouse of the data

A

Database

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

software using the data

A

Application Programs

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

text, graphical displays, menus, etc. for user

A

User Interface

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

personnel responsible for maintaining the database

A

Data/Database Administrators

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

personnel responsible for designing databases and software

A

System Developers

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

people who use the applications and databases

A

End Users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  • First step in the database development process
  • Specifies scope and general content
  • Overall picture of organizational data
    at high level of abstraction:
    a. Entity - relationship diagram
    (ERD)
    b. Descriptions of entity types
    c. Relationships between entities
    d. Business rules
A

Enterprise Data Model

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

Approaches to Database and IS
Development

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

● Detailed, well-planned development
process
● Time-consuming, but comprehensive
● Long development cycle

A

SDLC (System Development Life Cycle)

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

● Rapid application development
(RAD)
● Cursory attempt at conceptual data
modeling
● Define database during development
of initial prototype
● Repeat implementation and
maintenance activities with new
prototype versions

A

Prototyping

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q
  • Waterfall approach
  • The output from one phase to the
    next
A

System Development Life Cycle

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

● Purpose: Preliminary understanding
● Deliverable: Request for study
● Database Activity: Enterprise
modeling and early conceptual data
modeling

A

Planning

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

● Purpose: Thorough requirements
analysis and structuring
● Deliverable: Functional system
specifications
● Database Activity: Thorough and
integrated conceptual data modelling

17
Q

● Purpose: Information requirements
elicitation
● Deliverable: Detailed design
specifications
● Database Activity: Logical
database design (Transactions,
Forms, display, views, data integrity
and security)

A

Logical Design

18
Q

● 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)

A

Physical Design

19
Q

● Purpose: Programming, testing,
training, installation, documentation
● Deliverable: Operational programs,
documentation, training materials
● Database Activity: Database
implementation (Coded programs,
documentation, installation and
conversion)

A

Implementation

20
Q

● Purpose: Monitor, repair, enhance
● Deliverable: Periodic audits
● Database Activity: Database
maintenance, performance analysis
and tuning, error corrections

21
Q

● A classical Rapid Application
Development (RAD) approach.
● One of the most popular RAD
methods is prototyping, which is an
● iterative process of systems
development in which requirements
are converted to a working system
that is continually revised through
close work between analysts and
users.

A

Prototyping Database Methodology

22
Q

Conceptual Data Modelling
● Analyze requirements
● Develop preliminary data model

A

Identify problem

23
Q

Logical Database Design
● Analyze requirements in detail
● Integrate database views into
conceptual data model

A

Develop initial prototype

24
Q

● Define new database contents to
DBMS
● Decide on physical organization for
new data
● Design database processing
programs

A

Physical Database Design and Definition

25
● Code database processing ● Install new database contents, usually from existing data sources 3. Revise and enhance prototype 4. Implement and use prototype
Database Implementation
26
● Analyze database to ensure it meets application needs ● Fix errors in database
Database Maintenance
27
Database Maintenance ● Tune database for improved performance ● Fix errors in database
Convert to operational system
28
Different people have different views of the database
external schema
29
view of the data architect and data administrator
conceptual schema
30
underlying design and implementation
internal schema
31
● Can be determined from business-function/data entity matrices ● Enterprise model + User Views ● During the Analysis and Logical Design phases
External Schema
32
● E-R models ● A single, coherent definition of enterprise's data ● The view of data architect or data admin ● During the Analysis phase
Conceptual Schema
33
● Logical structures ● Physical structures
Internal Schema
34
a planned undertaking of related activities to reach an objective that has a beginning and an end.
Project
35
Managing Projects: People Involved
● Business analysts ● Systems analysts ● Database analysts and data modelers ● Users ● Programmers ● Database architects ● Data administrators ● Project managers ● Other technical experts
36
● Personal databases ● Two-tier and N-tier Client/Server databases ● Enterprise applications ○ Enterprise resource planning (ERP) systems ○ Data warehousing implementations
Range of Database Applications