Section 3 Introduction To SQL

This document provides an overview of testing databases. It discusses unit testing individual components, such as validating that columns contain the correct data type. A variety of tests should be carried out, including testing columns, constraints, and random samples rather than every element in large databases. Test cases should be designed upfront with expected results documented. Then the tests can be run and the actual results recorded to validate that the database is functioning as intended.

Uploaded by

Oka

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

53 views

Section 3 Introduction To SQL

Uploaded by

Oka

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 7

SECTION 3 LESSON 1

Introduction to Oracle Application Express

Objectives
This lesson covers the following objectives:
• Log-in to the Oracle Application Express practice environment
• Create a table using a script in Oracle Application Express
• Enter sample data into the table created
• Execute a defined query on the table to validate successful data insertion

Purpose
You have drawn the plans for your dream house and then transformed it into a physical design for
the house. The next step is to actually build the house. You will need tools to do this.
Oracle Application Express (OAE) is a tool that will allow you to build tables in an Oracle database.

Summary
In this lesson, you should have learned how to:
• Log-in to the Oracle Application Express practice environment
• Create a table using a script in Oracle Application Express
• Enter sample data into the table created
• Execute a defined query on the table to validate successful data insertion
SECTION 3 LESSON 2

SQL Introduction: Querying the Database

Objectives
This lesson covers the following objectives:
• Apply the rules of SQL to display all columns and a subset of columns specified by criteria
• Add new data with a different value in the “type” column
• Refine the SQL query to display only those rows that have data with the new type

Purpose
What if you had to take out all of your clothes from every dresser and closet in your whole house
every time you looked for clothes to wear that day? You might be late for school and you would
certainly have a lot to clean up! Accessing data in a database is a similar process if you don’t limit
what you’re looking for.
When retrieving information from a database, you will often have to find a subset of the data based
on specific search criteria. Becoming familiar with SQL will help you more quickly find the
information that you need.

DESCRIBE Command
The DESCRIBE command displays the structure of the table. The syntax is:

Basic SELECT Statement

The SELECT * command returns all the rows in a table. The syntax is:

Select Statement with a Condition

To return a subset of the data, modify the SELECT statement. The syntax is:

Inserting Data
Using the INSERT command, you can add a row of data to the table. The syntax is:

Terminology
Key terms used in this lesson included:
• Modification
• Subset
• Syntax

Summary
In this lesson, you should have learned how to:
• Apply the rules of SQL to display all columns and a subset of columns specified by criteria
• Add new data with a different value in the “type” column
• Refine the SQL query to display only those rows that have data with the new type
SECTION 3 LESSON 3

System Development Life Cycle

Objectives
This lesson covers the following objectives:
• List and describe the different stages of the system development life cycle (SDLC)
• Identify the role of data modeling in the system development life cycle
• Relate the project tasks to the different stages of the system development life cycle

Purpose
When you build a house, you draw up the plans before you start construction. During construction,
you lay the foundation before you start putting up walls. You finish all the major construction before
you start decorating. The architect, the builder, and the decorator coordinate their efforts so that
they do their jobs at the appropriate times.
A knowledge of the tasks associated with each stage of the system-development life cycle will help
you better plan a project and be a productive member of the team

System Development Life Cycle

Strategy and Analysis

Study and analyze the business requirements. Interview users and managers to identify the
information requirements. Incorporate the enterprise and application mission statements as well as
any future system specifications.

Build conceptual models of the system. Transfer the business narrative into a graphical
representation of business-information needs and rules. Confirm and refine the model with the
analysts and experts
Design

Build
Write and execute the commands to create the tables and supporting objects for the database.
Populate the tables with data.
Develop user documentation, help text, and operations manuals to support the use and operation of
the system.

Transition and Production

Transition
Conduct user-acceptance testing. Convert existing data and parallel operations. Make any
modifications required.
Production
Roll out the system to the users. Operate the production system. Monitor its performance and
enhance and refine the system.

Terminology
Key terms used in this lesson included:
• Parallel operations
• Populate
• System development life cycle
• User acceptance testing

Summary
In this lesson, you should have learned how to:
• List and describe the different stages of the system development life cycle (SDLC)
• Identify the role of data modeling in the system development life cycle
• Relate the project tasks to the different stages of the system development life cycle
SECTION 3 LESSON 4

Testing

Objectives
This lesson covers the following objectives:
• Develop and apply a strategy for testing that a database functions as designed

Purpose
Most people, when they buy a car, wish to know that it is reliable and will not break down.

So the manufacturers will put the car through a number of tests before it is available to be sold.

The same is true of a database; before it is sold to a customer, it is tested to verify that it meets the
business requirements.

Unit Testing
If two things are tested at once and the test fails, it is difficult or impossible to work out what has
caused the failure. So it is important to test only one thing at a time. This is commonly referred to
as unit testing.

What Could Be Tested?

When testing a database, a variety of things need to be tested.
For example:
 Columns should be tested that they contain the correct data type.
 Columns should be tested that they can accommodate the largest amount of data that might be
entered.
 Constraints should be checked that they only constrain or limit data that they are supposed to—
no more and no less.

What Should Be Tested?

It is frequently unrealistic to test every column and every constraint in every table in a database if it
is a large database. A random spread of tests, that check some columns and some constraints,
should be carried out.

Designing Tests
Before you carry out a test, you should have a good idea of what result you expect to see if the
database is working as expected. This should be documented before you carry out the test in a table
similar to the one shown:
Running Tests
Once you have designed your test, you can run it and record your results.

Summary
In this lesson, you should have learned how to:
• Develop and apply a strategy for testing that a database functions as designed