Week 9 UAS Flashcards Preview

Database Systems > Week 9 UAS > Flashcards

Flashcards in Week 9 UAS Deck (20)
Loading flashcards...
1
Q

Stages of the Database System Development Lifecycle?

A
  1. Database planning
  2. System definition
  3. Requirements collection and analysis
  4. Database design
  5. DBMS selection
  6. Application design
  7. Prototyping (optional)
  8. Implementation
  9. Data conversion and loading
  10. Testing
  11. Operational maintenance
2
Q

Criteria to produce an Optimal Data Model?

A
  1. Structural validity
  2. Simplicity
  3. Expressibility
  4. Nonredundancy
  5. Shareability
  6. Extensibility
  7. Integrity
  8. Diagrammatic representation
3
Q

Three phases of database design

A
  1. conceptual database design, process of constructing a model of the data used in an enterprise, independent of all physical considerations.
  2. logical database design, process of constructing a model of the data used in an enterprise based on a specific data model, but independent of a particular DBMS and other physical considerations.
  3. physical database design, process of producing a description of the database implementation on secondary storage
4
Q

Database planning?

A

management activities that allow stages of database system development lifecycle to be realized as efficiently and effectively as possible

5
Q

System definition?

A

describes scope and boundaries of database system and the major user views.

6
Q

Requirements collection and analysis?

A

Process of collecting and analyzing information about the part of organization to be supported by the database system, and using this information to identify users’ requirements of new system.

3 main approaches:

  1. centralized approach
  2. view integration approach
  3. combination of both approaches
7
Q

Database design?

A

Process of creating a design for a database that will support the enterprise’s mission statement and mission objectives for the required database system.

Main approaches include:

  1. Top-down
  2. Bottom-up
  3. Inside-out
  4. Mixed
8
Q

DBMS selection?

A

Selection of an appropriate DBMS to support the database system.

9
Q

Application design?

A

Design of user interface and application programs that use and process the database.

two important activities:

  1. transaction design
  2. user interface design
10
Q

Prototyping?

A

Building working model of a database system.

11
Q

Implementation?

A

The physical realization of the database and application designs.

12
Q

Data conversion and loading?

A

Transferring any existing data into new database and converting any existing applications to run on new database.

13
Q

Testing

A

The process of running the database system with intent of finding errors.

14
Q

Operational maintenance?

A

The process of monitoring and maintaining database system following installation.

15
Q

CASE tools benefits?

A
  1. Standards;
  2. Integration;
  3. Support for standard methods;
  4. Consistency;
  5. Automation .
16
Q

The Difference between Data Administrator and Database Admisnistrator?

A

The Data Administrator (DA) and Database Administrator (DBA) are responsible for managing and controlling the corporate data and corporate database, respectively.

DA is more concerned with early stages of database system development lifecycle and DBA is more concerned with later stages.

17
Q

Tugas Data Administrator?

A

Management of data resource including:

  • database planning,
  • development and maintenance of standards, policies and procedures, and conceptual and logical database design.
18
Q

Tugas Database Administrator?

A

Management of physical realization of a database system including:

  • physical database design and implementation,
  • setting security and integrity controls,
  • monitoring system performance, and reorganizing the database.
19
Q

several fact-finding techniques?

A
  1. examining documentation
  2. interviewing
  3. observing the organization in operation
  4. research
  5. questionnaires
20
Q

Why using fact-finding techniques?

A

It is critical to capture the necessary facts to build the required database application.
Enables developer to learn about the terminology, problems, opportunities, constraints, requirements, and priorities of the organization and the users of the system.