Chapter 3 - Database Planning
Step 7 of Database Design Life Cycle
Create the DB and DB application prototypes
A data model is usually created during this phase of the Database Design Life Cycle
Creating a database strategy
This step will help the DB designer to determine the needs that the DB will be designed to meet
Creating a database strategy
These statements represent the transaction functionality built into the application programs.
DML statements
involves defining the users of the database and its corresponding application
Defining the scope
Step 9 of Database Design Life Cycle
Implementation
Step 8 of Database Design Life Cycle
Test the DB and DB application
T/F Many database management systems include functionality that helps convert legacy data into the new format.
True
T/F The database's design must support the needs of the organization
True
T/F The functionality required by the user must be built into the database application
True
Black-box testing comes before or after white-box testing?
after
Failure to ascertain all the requirements of a database system can lead to
an inadequate or incomplete system
Database/prototype testing happens in two places:
before implementing the database and after the system goes live
This individual must test the user's point of view, including all areas of user input, user interface, and data output areas
black-box testers
which tester has no knowledge of the code, or any predetermined notions of how the application is supposed to perform
black-box testers
The database design phase usually occurs in three stages:
conceptual, logical and physical
this is the stage when those carefully planned processes should be carried out.
conversion
Step 10 of Database Design Life Cycle
convert legacy data and load new data
Step 3 of Database Design Life Cycle
create a database requirements document
Step 1 of Database Design Life Cycle
create database strategy
used as a blueprint from which the database design is derived
database requirements document
A mission statement
declares the specific purpose of the database in broad terms without defining specific tasks pertinent to the implementation of the database
Step 2 of Database Design Life Cycle
define the scope of database application
Step 4 of Database Design Life Cycle
design the database
Step 6 of Database Design Life Cycle
design the database application
T/F Monitoring a database and its application is not an ongoing activity.
false
Testing should also demonstrate that the database and its application are
functioning within database requirements
For the database, this will typically include executing DDL statements to create the tables of the database.
implementation
This phase can occur with or without the aforementioned prototyping, but will usually run more smoothly if the prototyping occurs
implementation
This phase includes implementing the necessary programming constructs to create the database and its application
implementing the DB and DB application
Testing is performed to ______ & ___ errors that may be present in both the database and the database's application
locate; fix
Step 11 of Database Life Cycle
maintain the DB and DB application
As long as the system is in use, it must be...
maintained
This stage includes the monitoring of the system to ensure that it properly and efficiently carries out its designated tasks.
maintenance
once a database and an application have been deployed, ___________ testing should be conducted
post-deployment
The application programs are implemented in the designated ___________ _____________.
programming language
Testing should be performed with carefully designed testing strategies with ____ ___ so that the entire system is thoroughly tested
real data
The loading of legacy data is only necessary if the database system is
replacing an old system
Step 5 of Database Design Life Cycle
select a DBMS
who performs white-box testing on database systems?
someone other that the database designer or developer
a database requirements document contains...
the specifications for the database & info about required features
which testers have direct access to the code, and may be authorized to make changes to the code
white box testers
The use of internal knowledge of the code for an application when conducting tests.
white box testing (glass box)
