Documente Academic
Documente Profesional
Documente Cultură
Requirement Testing
The most cost effective phase in which to detect a
system flaw.
Testing the system requirement increase the probability
that the requirement will be good one.
Requirement are properly recorded
Correctly interpreted by the information services
project team.
Recorded in accordance with the departments
guidelines, standards and procedure.
OBJECTIVES
Determine that the requirements fairly represent what the user
needs
Determine that the needs have been defined and documented
Verify that a cost/benefit study has been performed and that it
is reasonable
Determine that the business problem has been solved
Verify that the control requirements have been specified
Verify that a reasonable process was followed in developing
the business solution
Verify that a reasonable alternative was selected among the
most probable alternative solution
CONCERNS
WORKBENCH
DO
CHECK
REWORK
Project
Deliverables
Defining
Req.
Task 1
Prepare Risk
Matrix
Task 2
Perform Test
Factor Analysis
Task 3
Req. Gathering
Process
Conduct a Req.
Walkthrough
Req. accurate
&
complete
Test Report
INPUT
Business problem is well defined
Requirement phase : Initiated by management request,
and should conclude with a proposal to management on
the recommended solution
Develops a series of solutions
Requirement team should select a preferred solution
Do Procedures
Task 1. Prepare a risk matrix
Task 2. Perform a Test factor Analysis for the
Requirement Phase
Task 3. Conduct a Requirements Walkthrough
User area
Internal auditor
Risk consultant
Data processor
Security officer
Computer operations manager
1.2.Identify Risks
1.Risk analysis scenario brainstorms the potential application risks using their
experience, judgment, and knowledge
2. Risk checklist
Category : Uncontrolled System Access
Category : Ineffective security practices for the Application(repeat
payment to the same party )
Category : Procedural errors at the information services facility(files
destroyed during DB reorganization)
Category : Program Errors(records deleted from sensitive files without
guarantee that deleted record can be reconstructed)
Category : Communication system failure
Origination
Data entry-transfer to machine readable media
Communication-manual or electronic
Processing-system logic to date
Storage
Output-translation of data from computer media
to media
Use-satisfication of the business need through
the results of system processing
3.Project Presentation
Statement of the goals and objectives of the
project
Background information
List of any exceptions made by the project team
Discussions of alternatives
Using representative transactions as a basis
4. Questions/Recommendations
Evoke discussion
Recorder (member of project team)
5. Final Report
Entire walkthrough team should agree on the
contents of the report
Recorder may prove valuable information in
developing the report
Report should be issued within five days of the
conclusion of the walkthrough
Output
Report indicating requirement deficiencies
Indicate where requirements are not accurate and/or
complete
Conclusion
Testers should perform the following steps
during requirements phase testing:
1. Prepare a risk matrix.
2. Perform a test factor analysis.
3. Conduct a requirements walkthrough.
4. Perform requirements testing.
5. Ensure requirements are testable.
Desired Model
Properties
Software
Model
Cover the
Properties!
SW Integration
(Executable Code Production)
Properties are
Requirements