Professional Documents
Culture Documents
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
Concerns
Produces more effective testing. Test process to be more productive Create a more professional image Develop more meaningful findings and recommendations
WORKBENCH
DO
REWORK
Design process
CHECK
Task 1
Score Success Factors
Task 2
Analysis Design Factors
Test Report
Task 3
Design phase Deliverables
Conduct Design Review
Task 4
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
Input specification Processing specification File specification Output specification Control specification System flowcharts Hardware and software requirements Manual operating procedure specifications Data retention policies
Scoring is a predictive tool that utilizes previous systems experience. Existing systems are analyzed to determine the attributes of those systems and their correlation to the success or failure of that particular application. When attributes that correlate to success or failure can be identified, they can be used to predict the behavior of systems under development. The more heavily the user is involved, the higher the probability that system will be successful
Election
Scoring Process
Sampling High positive correlation Ease of use Develop risk score Project leader assessment Test team assessment Estimate extent of testing Identify area of test Identify composition of test team
Conclusion
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
Conducted by team of individual knowledgeable in the design process Follow predetermined review process
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
Inspection is a process by which completed but untested design products are evaluated as to whether 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
Output
Deficiencies uncovered in the design review Defects and assessment produced by the inspection process