FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
-
Upload
santhosh-nani -
Category
Documents
-
view
216 -
download
0
Transcript of FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
1/28
Unit III
Life Cycle Testing Approach
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
2/28
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.
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
3/28
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
4/28
OBJECTIVES
Determine that the requirements fairly represent what the userneeds
Determine that the needs have been defined and documented
Verify that a cost/benefit study has been performed and that itis reasonable
Determine that thebusiness problem has been solved
Verify that the control requirements have been specified
Verify that a reasonable process was followed in developingthe business solution
Verify that a reasonable alternative was selected among themost probable alternative solution
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
5/28
CONCERNS
Take Higher-caliber person to perform the test
Requires new testing methods
Continue until requirements are complete
Management review occur after requirement
phase is complete(senior management).
Recommended test process outlined on the 15requirements phase test factor and the test
concerns for each factor
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
6/28
WORKBENCH
DO CHECK
REWORK
Task 1
Task 2
Task 3
Prepare RiskMatrix
Perform Test
Factor Analysis
Conduct a Req.
Walkthrough
Req. accurate
&
complete
Project
Deliverables
DefiningReq.
Req. Gathering
Process
Test Report
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
7/28
INPUT
Business problem is well defined
Requirement phase : Initiated by management request,
and should conclude with a proposal to management onthe recommended solution
Develops a series of solutions
Requirement team should select a preferred solution
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
8/28
Deliverables needed by testers
Proposal to management describing the problem, the
alternatives and proposing a solution
Cost/benefit study describing the economics of the
proposed solution Detailed description of the recommendedsolution
List ofsystemassumptions such as life of the
project,the value of money, the average skill of the
user, and so on
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
9/28
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
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
10/28
Task 1. Prepare a Risk Matrix
Identification of risks and steps to be taken for each risks
Starts in the requirements phase and is expanded andcompleted in the design phase
Five step process Identify Risk Team
Identify Risks
Establish control objectives
Identify controls in each system segment
Determine adequacy of controls
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
11/28
1.1. Identify Risk Team
( 3 to 6 members)
Risk team may be part of requirement team or test team
Following Skills needed Knowledge of user application
Understanding of risk concepts
Ability to identify controls Familiarity with both application and information service risks
Understanding of information services concepts and system design
Understanding of computer operations procedures
Risk Team Members
User area Internal auditor
Risk consultant
Data processor
Security officer
Computer operations manager
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
12/28
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
13/28
1.3.Establish Control Objectives
Adequacy ofcontrol cannot be tested until the
acceptable level of loss from each risk has been
defined
After control objectives defined, the requirements
can be tested to determine whether those objectives
are achievable
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
14/28
Risk matrix Eg(requirement)
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
15/28
1.4. Identify controls in each system
segment
Origination
Data entry-transfer to machine readable media
Communication-manual or electronic Processing-system logic to date
Storage
Output-translation of data from computer mediato media
Use-satisfication of the business need through
the results of system processing
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
16/28
Risk matrix eg(design)
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
17/28
1.5. Determine adequacy of controls
Controls are adequate to reduce each of the
identified risks to the acceptable level
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
18/28
Task 2. Perform a Test factor Analysis for
the Requirement Phase
1. Requirements Comply with Methodology
(Methodology Test Factor)
2. Functional specifications Defined (CorrectnessTest Factor)
3. Usability specifications Determined (Ease-of-Use
Test Factor)
4. Maintenance specifications Determined
(Maintainable Test Factor)
5. Portability Needs Determined (Portable Test
Factor)
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
19/28
Test Team make one of the following four
judgments
Very adequate
Adequate evaluation
Inadequate assessment Not applicable
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
20/28
Task 3. Conduct a Requirements
Walkthrough
Create a situation in which a team of skilled individuals canhelp the project team in the development of the projectsolutions
Amount of time for each steps depend upon the size of theapplication being reviewed and the degree of assistance.
Five Step process
1. Establish Ground Rules
2. Select team/Notify Participants
3. Project Presentation
4. Questions/Recommendations
5. Final Report
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
21/28
1. Establish Ground Rules
Size and makeup of the walkthrough team
Responsibility of the walkthrough team
Obligation of the project team to answer
Approximate length, time, and location
Confidentiality of information
Aspects of the system that are not challengeable or
discussible Who will receive the results of the walkthrough?
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
22/28
2. Select team/Notify Participants
Information services project manager / system
analyst
Senior management with responsibility over thecomputerized area
Operations management
User management
Consultants possessing needed expertise
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
23/28
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
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
24/28
4. Questions/Recommendations
Evoke discussion
Recorder
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
25/28
5. Final Report
Entire walkthrough team should agree on the
contents of the report
Recorder may prove valuable information indeveloping the report
Report should be issued within five days of the
conclusion of the walkthrough
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
26/28
Output
Report indicating requirement deficiencies
Indicate where requirements are not accurate and/or
complete
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
27/28
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.
-
7/27/2019 FALLSEM2013 14 CP0600 03 Sep 2013 RM01 1 Requirement Testing
28/28
Properties are
Requirements
Requirements Based Testing
SW High-Level
Reqs. Development
Software
Model
SW Integration
(Executable Code Production)
Desired Model
Properties
Cover the
Properties!