• No results found

SOFTWARE QUALITY ASSURANCE_4

N/A
N/A
Protected

Academic year: 2020

Share "SOFTWARE QUALITY ASSURANCE_4"

Copied!
24
0
0

Loading.... (view fulltext now)

Full text

(1)

TEST PLAN

LECTURE 4 : WEEK 4

SEN 460

: FALL 2016

(2)
(3)

Concerns

 Not enough training.

 Us-versus-them mentality.  Lack of testing tools.

 Lack of management understanding/support of testing  Lack of customer and user involvement

 Not enough time for testing. This is common complaint.  Over-reliance on independent testers

(4)

Inputs

Two inputs are used in developing the test plan:

Project plan.

This plan should address the totality of activities required to implement the project and control that implementation. The plan should also include testing.

Project plan assessment and status report.

(5)

DO PROCEDURES

The following six tasks should be completed during the execution of this step:

1. Profile the software project.

2. Understand the software project’s risks. 3. Select a testing technique.

4. Plan unit testing and analysis. 5. Build the test plan.

(6)

TASK1:PROFILE THE SOFTWARE PROJECT

This task can be divided into the following two subtasks:

1. Conduct a walkthrough of the customer/user areas.

1. Because testers represent the customer/users, they should have access to

the users of the system.

2. Two main purpose

1. to give an overview of the totality of activities users perform 2. to gain an appreciation of the how the software will be used

2. Develop a profile of the software project.

3. The primary objective of understanding the business responsibilities of

(7)

DEVELOPING A PROFILE OF THE

SOFTWARE PROJECT

The following is the profile information that is helpful

1. Project objectives

2. Development process 3. Customer/users

4. Project deliverables 5. Cost/schedule

6. Project constraints

7. Developmental staff competency 8. Legal/industry issues

9. Implementation technology 10. Databases built/used

(8)

TASK 2: UNDERSTAND THE

PROJECT RISKS

Reliability

Authorization

File integrity

Audit trial

Continuity of processing

Service level

(9)

Methodology

Correctness

Ease of use

Maintainable

Portable

Coupling

Performance

Ease of operation

(10)

RELIABILITY

Assurance that the application will perform its

intended function with the required precision

over an extended period of time. The

correctness of processing deals with the

ability of the system to process valid

transactions correctly, while reliability relates

to the system’s being able to perform

(11)

 The level of accuracy and completeness expected in the

operational environment is established.

 Data integrity controls are implemented in accordance with

the design.

 Manual, regression, and functional tests are performed to

ensure the data integrity controls work.

 The completeness of the system installation is verified.

 The accuracy requirements are maintained as the

applications are updated.

(12)

AUTHORIZATION

 Assurance that data is processed in accordance

with the intents of management

.

In an application system, there is both general and specific

authorization for the processing of transactions

.

 General authorization governs the authority to

conduct different types of business, whereas

(13)

 The rules governing the authorization of transactions are defined.

 The application is designed to identify and

 enforce the authorization rules.

 The application implements the authorization rules.

 Unauthorized data changes are prohibited during the installation process.

 The method and rules for authorization are preserved during maintenance.

(14)

File Integrity

Assurance that the data entered into the application

(15)

File Integrity

Requirements for file integrity are defined.

The design provides for the controls to ensure

the integrity of the file.

The specified file integrity controls are

implemented.

The file integrity functions are tested to ensure

they perform properly.

The integrity of the files is preserved during the

(16)

Audit Trial

The capability to substantiate the

processing that has occurred. The

processing of

data

can be supported

through the retention of sufficient

evidential matter to substantiate the

accuracy, completeness, timeliness,

and authorization

of data. The process of

(17)

Audit Trial

The requirements to reconstruct processing are defined.

The audit trail requirements are incorporated

into the system.

The audit trail functions are tested to ensure the

appropriate data is saved.

The audit trail of installation events is recorded.

The audit trail requirements are updated during

(18)

Continuity of Processing

The ability to sustain processing in the

event problems occur. Continuity of

processing ensures that the necessary

procedures and backup information are

available to recover operations should

integrity be lost.

Continuity of processing includes the

timeliness of recovery operations and the

ability to maintain processing periods when

(19)

Continuity of Processing

The impact of each system failure is defined.

The contingency plan and procedures have been

written.

Recovery testing verifies that the contingency

plan functions properly.

The integrity of the previous systems is ensured

until the integrity of the new system is verified.

The contingency plan is updated and tested as

(20)

Service level

Assurance that the desired results will be available

within a time frame acceptable to the user.

To achieve the desired service level, it is

necessary to match user requirements with

available resources.

Resources include input/output capabilities,

(21)

Service level

The desired service level for all aspects of the system

The method to achieve the predefined service levels

The programs and manual systems are designed to

Stress testing is conducted to ensure that the system

service level when both normal and above normal

A fail-safe plan is used during installation to ensure

The predefined service level is preserved as the

(22)

Access Control

 Assurance that the application system resources will be

protected against accidental and intentional

modification, destruction, misuse, and disclosure.

(23)

Access Control

 Access to the system is defined.

 The procedures to enforce the access rules are designed.  The defined security procedures are implemented.

 Compliance tests are utilized to ensure that the security

procedures function in a production environment.

 Access to the computer resources is controlled during

installation.

 The procedures controlling access are preserved as the

(24)

Any Questions !!!

END OF LECTURE

References

Related documents

(R) The capacitance of an air filled plane parallel (3) Increases if the capacitor is maintained plate capacitor on insertion of dielectric at constant

The results show that using high strength material for high flex- ural moment capacity has lower cost than low stretch concrete since doubly rein- forced design is not an

It handles client requests, creates and mutates the directory and file structure on their behalf, refers clients to chunk servers, and manages the over- all health of the file

93 / 42 / EEC Medical devices, class IIb (European Directive for Medical Devices), 97/ 23 / EC (Pressure Equipment Directive), 2006 / 42 / EC (Machinery Directive) ; EN 13060

If a file is checked out, this command is available to bring revisions from the local working copy to the server while leaving the file checked out.. Refresh

$ ./a.out <in.dat >out.dat scanf() will read data inputs from the file.. “in.dat”, and printf() will output results on the file “

For Photo Supreme, the truth is in the database, and all the files that are displayed on screen are catalog entries that do or don’t point the existing physical files on disk..

[r]