Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 1
Learning Objectives
What is software testing and why it is so hard? Error, Fault, Failure, Incident Test Cases Testing Process Limitations of Testing No absolute proof of correctness Overview of Graph Theory
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 2
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 4
Definition
Process that Establishes the S/W is working satisfactorily as per the users requirements. Proves the product is free of errors. Certifies that the product is ready to be used.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 5
In Practice
Testing is a task of locating errors. Includes running / examining the S/W product with the intent of making it fail. By Glen Myers Testing is the process of executing a program with the intent of finding errors Objective The basic idea is to make sure that the errors are tracked and submitted for rectification before the product is finally delivered.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 6
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Basic Questions
When to test? Cost and time factors What to test? What is Software How to test? Automated or manual Who should test? Does the developer qualify
U1. 7
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
When to Test
Phased Process => Errors at one stage would propagate to the next unless checked in time. Later an error is found, the more it costs to fix. Thus, it is important to: Prevent occurrence of errors. Detect errors in the same phase as they are introduced and prevent their migration across phases of development. Thus, in order to minimize costs we need to test right from the stage one where requirements are being gathered .
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 8
How to Test
Laying down processes Considerations behind Automation Analysis of tools available in terms of Suitability Economic feasibility In-time procurement User Training Portability Interoperability Available support
U1. 9
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
S/W Failure
Error, Fault, Failure, Incident Errors due to: Commission Omission Could lead to deviation from user requirements or requirement specifications.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 11
S/W Failure
A common cause behind failures is that we can pay attention to the wrong conditions. But we can't pay attention to all the conditions The phenomenon of blindness due to inattention Humans (often) don't see what they don't pay attention to. Programs (always) don't see what they haven't been told to pay attention to. (Programs are more precise and less flexible.)
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 12
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Intended inputs
Configuration and system resources From other cooperating processes, clients or servers
Monitored outputs
Impacts on connected devices / system resources To other cooperating processes, clients or servers
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 13
Testing
A technical investigation done to expose quality-related information about the product under test
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 14
Explanation
A technical
We use technical means, including experimentation, logic, mathematics, models, tools (testing-support programs), and tools (measuring instruments, event generators, etc.)
investigation
An organized and thorough search for information. This is an active process of inquiry. We ask hard questions (aka run hard test cases) and look carefully at the results.
done to expose quality-related information
Discussed next
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 15
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 16
Challenges
What are various possible conditions in which it is expected to work. Does the S/W function as it is expected to under those conditions. How to generate those conditions. Convey the findings in a positive manner. Testing time and resources are generally limited. Deciding when to stop testing
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 17
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 18
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Limitations of testing
The objective of testing is to show presence of errors. What it definitely cant do is prove absence of errors. One can never find the last bug in an application, no matter how hard he tries as: Domain of possible inputs is too large. The program has a number of possible paths. The challenge is to achieve maximum coverage through minimum test cases. It is rightly said that testing process is only as efficient as the test data.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 19
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 20
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 22
Few Directions
Use testing for Quality Assurance rather than Quality Control Always remember the customers perspective Keep redesigning the tests to address untested areas Remember that the principle proposed by Myers that the probability of existence of an error in a part of code is proportional to the number of errors already found Should know when to stop testing
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 24
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 25
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 26
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 27
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
Conclusion
What is software testing and why it is so hard? Error, Fault, Failure, Incident Test Cases Testing Process Limitations of Testing No absolute proof of correctness Overview of Graph Theory: Students Presentation
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 28
Objectives
Life cycle testing Verification Validation V Model W Model 11 Steps of Testing: W. Perry
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 29
Life-Cycle Testing
What it is: Implies continuous testing of solution even after plans are complete and tested system is implemented. Objective: Identify defects at earliest possible time Requirements: Formally developed processes A well defined Test Plan Structured Methodologies. Features: Development and Testing processes start at the same time (with the project) with the same information
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 30
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
10
Life-Cycle Testing
Responsibilities Development team defines and documents the requirements, carries out development related activities Test team formulates test plans and runs compliance tests to uncover defects
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 31
Verification
Verification: Are we building the product right? Static and proactive in nature (QA). Checks if product (result of a particular phase of SDLC) conforms with its specifications. Is static in nature. Involves manual checking, doesnt include execution of code. The target documents are Req. Specs., HLD, DB Design The methods used are Inspection, Walkthrough etc.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 33
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
11
Validation
Validation: Are we building the right product? Dynamic and reactive in nature (QC). Checks the software to insure it meets customers requirements. Is dynamic in nature. Involves execution of code. The target could be a component, module, a set of integrated modules or system as a whole. The methods used are Black box, white box testing etc.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 34
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 36
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
12
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 37
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 38
V Model
The V-model is a software development process which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 39
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
13
V Model
The V-model deploys a well-structured method where each phase can be implemented by the detailed documentation of the previous phase. Testing activities like test designing start at the beginning of the project well before coding and therefore Saves a huge amount of the project time and thus helps in cost reduction Assures better validation Assures involvement of people with appropriate skills.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 40
V Model
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 41
V Model
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 42
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
14
V Model
The V-Model further promotes the notion of early test preparation. finds faults in baselines and is an effective way of detecting faults early The V-model promotes the idea that the dynamic test stages (on the right hand side of the model) use the documentation identified on the left hand side as baselines for testing.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 43
V Model: Problems
Derivative of Waterfall model => no provision for increments V Model focuses on specific dynamic test stages And has no mention of the effectiveness of static tests such as reviews, inspections, static code analysis and so on. This is a major omission and the V-Model does not support the broader view of testing as a constantly prominent activity throughout the development lifecycle.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 44
V Model: Problems
No mention of important activities like: Planning Post implementation maintenance Testing Quality Control
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 45
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
15
Modified V
Addresses the parallelism in S/W development and accommodates incremental development. Introduces concept where development products go through phases of testing Each unit/component/module is given an entry / exit criteria to go through a testing stage The components that satisfy the entry criteria are moved into the corresponding testing phase The components that satisfy the exit criteria are moved out of the current testing phase
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 46
W Model
W-Model focuses on the development products themselves and utilizes static testing techniques to verify intermediate deliverables. Essentially, every development activity that produces a work product is shadowed by a test activity.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 47
W Model
The purpose of the test activity specifically is to determine whether the objectives of a development activity have been met and the deliverable meets its requirements. The W-Model of testing focuses specifically on the product risks of concern at the point where testing can be most effective.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 48
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
16
W Model
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 49
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 50
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
17
Step1 Assess Development P lan and Status Step2 Develop the test P lan Step3 Test Software requirements
Build Software
Step4 Test Software design Step5 Program Phase Design Step6 Execute and record result Step7 Acceptance Test Step8 Report Test Results Step9 Test Software Installation Step10 Test Software Changes Step11 Evaluate Test effectiveness
Install Software
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 52
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 53
Testers can challenge the completeness and correctness of the development plan Potential problem areas could be: An inaccurate estimate Choice of inadequate development tools / procedures
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 54
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
18
ensuring
Potential problems areas in ensuring proper execution of Test Plan: Lack of training / test tools / management support / time / user involvement
U1. 55
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 56
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 57
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
19
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 58
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 59
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 60
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
20
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 61
Acceptance Test
Describes procedures for identifying acceptance criteria for interim life cycle products Final acceptance acknowledges: Software product meets users requirements Adequacy of development process Responsibilities of user: Ensure involvement in developing system requirements and acceptance criteria Identify interim and final products for acceptance Plan, schedule and delegate responsibilities for acceptance activities Act according to the plan and acceptance decision for each product
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 62
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
21
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 64
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
22
Conclusion
Life cycle testing Verification Validation V Model W Model 11 Steps of Testing: W. Perry Detailed Discussion
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 67
Verification Techniques
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 68
Objectives
Verification Techniques Inspection Walkthrough Pass-around Desk Checks Pair Programming
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 69
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
23
Recall
There are two basic types of testing Execution-based testing Non-execution-based testing V & V Verification Determine if the workflow was completed correctly Validation Determine if the product as a whole satisfies its requirements Remember The terms verify / review are also used for all non-executionbased testing
U1. 70
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 71
Reviews
A review is any activity in which a work product is distributed / presented to reviewers who examine it and give feedback. In execution-based testing, one defect may mask another so several executions might be required. On the other hand, many different defects may be discovered in a single review. Because of the reuse of domain and programming knowledge, reviewers are likely to have seen the types of error that commonly arise In a peer review, co-workers of a person who created a software work product examine that product to identify defects and correct shortcomings
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 72
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
24
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 73
Objective of Review
Verify whether the work product Correctly satisfies the specifications found in any predecessor work product. Adheres to standards. Suggest improvement opportunities to the author. Gain consensus amongst the project team members. Secure approval from stakeholders. Promote the exchange of techniques and education of the participants.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 74
Review: Categories
Technical Ensure conformance to specifications. Check if development is in accordance to plans, standards and guidelines. Ensure changes to software elements are implemented properly. Managerial Check if project making progress as per plan. Identify and evaluate alternatives. Maintain global control through adequate resource allocation.
U1. 75
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
25
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 78
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
26
Verification Techniques
Inspections
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 79
Participants
In general, a work product should be reviewed by: The author of any predecessor document or specification Someone who must base their subsequent work on the work product Peers of the author Anyone responsible for a component to which the work product interfaces Attendance by anyone with supervisory authority over the author is by invitation of the author only.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 80
Roles - Responsibilities
Author: Creator or maintainer of the work product to be inspected. Initiates the inspection process by asking the peer review coordinator to assign a moderator. States his objectives for the inspection. Delivers work product and its specification or predecessor document to moderator. Works with moderator to select inspectors and assign roles. Addresses items on the Issue Log. Reports rework time and defect counts to moderator.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 81
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
27
Roles - Responsibilities
Moderator Plans, schedules, and leads the inspection events. Works with author to select inspectors and assign roles. Assembles inspection package and delivers it to inspectors at least 3 days prior to the inspection meeting. Determines whether preparation is sufficient to hold the meeting. If not, reschedules the meeting
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 82
Roles - Responsibilities
Moderator (Contd.) Facilitates inspection meeting. Corrects any inappropriate behavior. Solicits input from inspectors as reader presents each section of the work product. Records any action items or side issues that arise during the inspection. Leads inspection team in determining the work product appraisal. Serves as verifier or delegates this responsibility to someone else. Delivers completed Inspection Summary Report to the organizations peer review coordinator.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 83
Roles - Responsibilities
Reader Presents portions of the work product to the inspection team to elicit comments, issues, or questions from inspectors. Recorder Records and classifies issues raised during inspection meeting.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 84
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
28
Roles - Responsibilities
Inspector Examines work product prior to the inspection meeting to find defects and prepare for contributing to the meeting. Records preparation time. Participates during the meeting to identify defects, raise issues, and suggest improvements. Verifier Performs follow-up to determine whether rework has been performed appropriately and correctly.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 85
Roles - Responsibilities
Peer Review Coordinator Custodian of the organizations inspection metrics database. Maintains records of inspections conducted and data from the Inspection Summary Report for each inspection. Generates reports on inspection data for management, process improvement team, and peer review process owner.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 86
Entry Criteria
The author selected inspection as the approach for the product being reviewed. All necessary supporting documentation is available The author has stated his objectives for this inspection. Reviewers are trained in the peer review process. Documents to be inspected are identified with a version number. All pages are numbered and line numbers are displayed. The documents have been spell-checked.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 87
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
29
Entry Criteria
Source code to be inspected is identified with a version number. Listings have line numbers and page numbers. Code compiles with no errors or warning messages using the projects standard compiler switches. Errors found using code analyzer tools have been corrected. For a re-inspection, all issues from the previous inspection were resolved. Any additional entry criteria defined for the specific type of work product are also satisfied.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 88
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 89
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 90
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
30
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 91
Preparation
Ask individual inspectors to prepare with specific objectives in mind, such as: checking for interface errors; checking traceability to, and consistency with, predecessor specifications; or checking conformance to standards. Moderator and Author Examine the work product, to understand it, find defects, and raise questions about it. Use the appropriate defect checklist to focus attention on defects commonly found in the type of product being inspected. Use other analysis methods to look for defects as appropriate. Inspectors Log minor defects found, such as typographical errors or style inconsistencies, on the Typo List. Deliver this to the author at or prior to the inspection meeting. Inspectors
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 92
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
31
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Severity
Location
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
32
Accept Defects must be corrected, and the changes must be Conditionally verified by the individual named on the Inspection Summary Report. Re-inspect Following Rework Inspection Not Completed A substantial portion of the product must be modified, or there are many changes to make. A second inspection is required after the author has completed rework. A significant fraction of the planned material was not inspected, or the inspection was terminated for some reason.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 97
Rework
Task Responsib le Correct defects and typos found, resolve issues raised, and Author modify work product accordingly. Mark issues list to indicate action taken. Correct any other project documents based on defects identified in the inspected work product. Record any uncorrected defects in the projects defect tracking system. If rework verification is not needed, report the number of major and minor defects found and corrected and the actual rework effort to the moderator. Record the actual rework effort on the Inspection Summary Report. Author Author Author
Moderator
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 98
Follow-Up
Task Responsible Confirm that the author has addressed every item on the Verifier Issue Log. Determine whether the author made appropriate decisions as to which defects not to correct and which improvement suggestions not to implement. Examine the modified work product to judge whether the Verifier rework has been performed correctly. Report any findings to the author, so rework can be declared complete, incorrect rework can be redone, or items that were not originally pursued can be addressed. Report the number of major and minor defects found and corrected and the actual rework effort to the moderator. Author
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 99
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
33
Follow-Up
Task Responsible
Check whether the exit criteria for the inspection and for the Moderator peer review process have been satisfied. If so, the inspection is complete. Check the baselined work product into the projects configuration management system. Author
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 100
Rules to be followed
Inspection should be carried out by 3-6 participants All participants can act as an inspector The author shall not act as inspection leader The author should not act as reader or recorder Roles may be shared among the team members Individual participant may act in more than one role
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 101
Deliverables
1. 2. 3. 4. 5. Baselined work product Completed Inspection Summary Report Completed Issue Log Completed Typo Lists Counts of defects found and defects corrected
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 102
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
34
Exit-Criteria
All of the authors inspection objectives are satisfied. Issues raised during the inspection are tracked to closure. All major defects are corrected. Uncorrected defects are logged in the projects defect tracking system. The modified work product is checked into the projects configuration management system. Moderator has collected and recorded the inspection data.
U1. 103
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Exit-Criteria
If changes were required in earlier project deliverables, those deliverables have been correctly modified, checked into the projects configuration management system, and any necessary regression tests were passed. Moderator has delivered the completed Inspection Summary Report and defect counts to the peer review coordinator
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 104
Measurements
The moderator shall collect the data items from each inspection. These data items are used to calculate the process metrics and to monitor and improve the inspection process. The moderator shall record the data items in the appropriate spaces on the Inspection Summary Report and Issue Log and report them to the organizations peer review coordinator. The peer review coordinator shall maintain these metrics in a repository and produce periodic reports of summary data for practitioners and managers
U1. 105
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
35
Data to be Collected
Data Item Effort: Planning Definition total labor hours spent by the moderator and author in planning, scheduling meetings, assembling, duplicating, and distributing materials, and any other related tasks total labor hours spent by the participants in an overview meeting, if one was held total labor hours spent by the inspectors and author preparing for the inspection total labor hours the author spent correcting defects in the initial deliverable and making other improvements; include verification time from the follow-up stage duration of the inspection meeting in hours
U1. 106
Time: Meeting
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Data to be Collected
Data Item Defects Found: Major, Minor Definition total number of major and minor defects found by the inspection team; do not include non-defect issues raised, such as questions, requests for clarification, points of style, or items from the Typo Lists
Defects Corrected: total number of major and minor defects corrected Major, Minor during rework Size: Planned, Actual total physical lines of code (not including comments and blank lines) or number of document pages that were planned for inspection and that were actually inspected number of active participants in the inspection meeting inspection teams decision about disposition of the inspected work product (accepted as is, accepted conditionally, re-inspect following rework)
U1. 107
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Rework.per.Defect
Effort.Rework / Defects.Corrected.Total
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 108
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
36
Defects Corrected: Defects. Corrected.Major + Defects. Total Corrected.Minor Effort: Inspection Effort.Planning + Effort.Overview + Effort.Preparation + Effort.Meeting + Effort.Rework Number.of.Inspectors * Time.Meeting Effort.Inspection / Defects.Found.Total
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
A Sample Form
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal U1. 110
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 111
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
37
Review Techniques
Walkthrough
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 112
Walkthroughs
A walkthrough is an informal way of presenting a technical document in a meeting. The author runs the walkthrough: calling the meeting, inviting the reviewers, soliciting comments and ensuring that everyone present understands the work product. After the meeting, the author should follow up with individual attendees who may have had additional information or insights. The walkthrough is preceded by preparation by designers/developers Lists of items Items not understood Items that appear to be incorrect
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 113
Managing walkthroughs
Document driven Person responsible for document walks the reviewers through the document Reviewers interrupt with comments triggered by the presentation Interactive process Not to be used for the evaluation of participants
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 114
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
38
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 115
Author Author
Reviewers Author
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 116
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 117
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
39
Inspection
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
Verification Techniques
Passaround
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 119
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
40
Notify reviewers that work product is available and indicate Author the date by which review comments are to be provided. Either hand-write comments directly on the work product, or enter comments into the work product file, using a revision marks convention or an annotation feature of the tool being used. If working with an individual copy of the work product, deliver the work product with comments to the author after completing the review. Reviewers
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 121
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 122
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 123
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
41
Verification Techniques
Code Review
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 124
Code Review
A code review is a special kind of inspection in which the team examines a sample of code and fixes any defects in it. In a code review, a defect is a block of code which does not properly implement its requirements, or does not function as the programmer intended, or is not incorrect but could be improved For example, it could be made more readable or its performance could be improved
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 125
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
42
Input/output
OPEN statements correct? Format specification correct? End-of-file case handled?
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 127
Verification Techniques
Deskchecks
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 128
Deskchecks
A deskcheck is a simple review in which the author of a work product distributes it to one or more reviewers. The author sends a copy of the work product to selected project team members. The team members read it, and then write up defects and comments to send back to the author.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 129
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
43
Deskchecks
Unlike an inspection, a deskcheck does not produce written logs which can be archived with the document for later reference. Deskchecks can be used as predecessors to inspections. In many cases, having an author of a work product pass his work to a peer for an informal review will significantly reduce the amount of effort involved in the inspection.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 130
Verification Techniques
Pair Programming
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 131
Pair Programming
Pair programming is a technique in which two programmers work simultaneously at a single computer and continuously review each others work. Although many programmers were introduced to pair programming as a part of Extreme Programming, it is a practice that can be valuable in any development environment. Pair programming improves the organization by ensuring that at least two programmers are able to maintain any piece of the software.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 132
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
44
Pair Programming
In pair programming, two programmers sit at one computer to write code. Generally, one programmer will take control and write code, while the other watches and advises. Some teams have found that pair programming works best for them if the pairs are constantly rotated; this helps diffuse the shared knowledge throughout the organization. Others prefer to pair a more junior person with a more senior for knowledge sharing.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 133
Pair Programming
The project manager should not try to force pair programming on the team; it helps to introduce the change slowly, and where it will meet the least resistance. It is difficult to implement pair programming in an organization where the programmers do not share the same nine-to-five (or ten-to-six) work schedule. Some people do not work well in pairs, and some pairs do not work well together.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 134
Conclusion
Inspection Walkthrough Pass-around Desk Checks Pair Programming
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 135
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
45
References
1. Beizer, B., Software Testing Techniques. New York: Van Nostrand, 1983 2. Howden, W. E, A Functional Approach to Program Testing & Analysis, New York: McGraw-Hill, 1987 3. Howden, W. E, Functional Program Testing and Analysis, IEEE Trans. Software Eng SE-12, 10 (Oct. 1986), 997-1005 4. Paul C. Jorgensen, Software Testing, A Craftsmans Approach, CRC Press, 2002 5. William Perry, Effective Methods for Software Testing, John Wiley & Sons, New York, 1995.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 136
1. 2. 3. 4.
Bharati Vidyapeeths Institute of Computer Applications and Management, New Delhi-63, by Shalini Singh Jaspal
U1. 138
Bharati Vidyapeeths Institute of Computer Applications & Management, by Shalini Singh Jaspal
46
This document was created with Win2PDF available at http://www.win2pdf.com. The unregistered version of Win2PDF is for evaluation or non-commercial use only. This page will not be added after purchasing Win2PDF.