Information Technology Reference
In-Depth Information
The first step ensures that everyone is informed of the tests. This allows all team
members to bring up any valid and significant points they may have concerning the
system. Also, by informing all members of the development team of the inspection
they will be aware and not feel as if they are personally being targeted. A strong
understanding of the document is crucial to the following steps. If it is not com-
prehensible it must go back to the design team to rework it until it is under-
standable. If the document is intelligible the next step provides the testers with a
group execution, as the testers move through all possibilities and analyzes the
outcomes. This walkthrough should be thorough and ideas should be shared among
all members, but precautions should be made to avoid group think. Some sug-
gestions are as follows:
• Have all team members write down (and not cross out ideas) before they bring
them up with the group.
• Create a friendly and conductive environment, by not prohibiting some off topic
ideas as long as it is not the main activity at the meeting.
• Make sure that team meetings are not directly proceeding holidays or incon-
venient times. If the members do not wish to be there, their mind will be
elsewhere.
The person that knows the document or section of the document under review
will be the one the one that wrote it. Allowing that person to address the issues in
the final report will be the most efficient as they are the most familiar with the
issues. It is important however that they should not feel as if they are being
blamed, but that they are just making corrections to the document as are the rest of
the team. This promotes corrections are implemented correctly and efficiently.
Finally, once the group moderator has deemed that all issues have been addressed
and resolved then the group may dissolve.
10.5 Things to be Tested
Execution based testing is a process of inferring certain behavioral properties of a
product based, in part, on the results of executing the product in a known envi-
ronment with selected inputs. This has three implications:
1. First, the definition states that testing is an inferential process. The tester takes
the product, runs it with known input data, and examines the output. The tester
has to infer what, if anything is wrong with the product.
2. A problem with definition is the phrase ''known environment''. We never really
can know our environment, either the hardware or the software.
3. Another worrisome phrase is ''with selected inputs''. In the case of real-time
system, frequently no control is possible over the inputs to the system.
