7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

1/13

DESIGN PHASE TESTING

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

2/13

Design Testing

Overview

User and system designer work as partners to develop

not only an efficient application system, but also one

that is acceptable to the user.

Objective

Test process recommends scoring the design success

factor, conducting a design review; and inspecting

design deliverables

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

3/13

Concerns

Produces more effective testing.

Test process to be more productive

Create a more professional image

Develop more meaningful findings and

recommendations

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

4/13

WORKBENCH

DO CHECK

REWORK

Task 1

Task 2

Task 3

Score Success

Factors

Analysis Design

Factors

Conduct Design

Review

Design accurate

&

complete

Design process

Design phase

Deliverables

Test Report

Task 4Inspect Design

Deliverables

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

5/13

Input

The sooner the project team become aware of

potential defects, the cheaper it is to correct

those defects

When defects are found, the corrective process

can be so time-consuming and painful that it

may appear cheaper to live with the defects

than to correct them

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

6/13

Design Phase Deliverables

Input specification

Processing specification

File specification

Output specification

Control specification

System flowcharts

Hardware and software requirements

Manual operating procedure specifications

Data retention policies

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

7/13

Task 1: Score Success Factors

Scoring is a predictive tool that utilizes previous systemsexperience.

Existing systems are analyzed to determine the attributes

of those systems and their correlation to the success orfailure of that particular application.

When attributes that correlate to success or failure canbe identified, they can be used to predict the behavior ofsystems under development.

The more heavily the user is involved, the higher theprobability that system will be successful

Election

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

8/13

Scoring Process

Scoring Criteria (Attributes)

Sampling

High positive correlation

Ease of use Develop risk score

Scoring test tool

Project leader assessment

Test team assessment

Conclusion

Estimate extent of testing

Identify area of test

Identify composition of test team

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

9/13

Task 2: Analyze test factors

Data integrity controls designed

Authorization rules designed

File integrity controls designed

Audit trail designed

Contingency plan designed Method to achieve service level designed

Access procedures defined

Design complies with methodology

Design conforms with requirements

Design facilitates use Design is maintainable

Design is portable

Interface design is complete

Design achieves criteria

Needs communicated to operations

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

10/13

Task 3: Conduct Design Review

Conducted by team of individual

knowledgeable in the design process

Follow predetermined review process Project personnel

Independent review team

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

11/13

Guidelines

Select the review team

Train the review team member

Notify the project team

Allot adequate time

Document the review facts

Review the facts with the project team

Develop review recommendations

Review recommendation with project team

Prepare formal report

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

12/13

Task 4: Inspect Design Deliverables

Inspection is a process by which completed butuntested design products are evaluated as towhether the specified changes were installed

correctly 3 types of defects

Errors, the change has not been made correctly

Missing, something that should have been changed ,but

was not changed

Extra, something not intended was changed or added

7/27/2019 FALLSEM2013 14 CP0600 06 Sep 2013 RM01 2 Design Phase Testing

13/13

Output

Deficiencies uncovered in the design review

Defects and assessment produced by theinspection process

Results from deliverables inspection

No defects found

Minor work required

Major rework required

Training & product quality - enhance benefits of formalinspection