Information Technology Reference
In-Depth Information
First, if there are any process documents detailing the business practices of the
organization are available, they would be studied to capture the gaps between the
product and the business practices. Then, product demos would be conducted with
the concerned functional executives to see how many gaps need product cus-
tomization and how many business practices can be modified by the organization.
Once this is carried out the project requirements would be ready.
It may sometimes happen that there is little or no useful process documentation
available. In such cases, personal interviews and product demos would be the
methods to capture the project requirements.
Perhaps, this is the only scenario, in which project requirements are captured by
demonstrating the product itself!
3.6 Elicitation and Gathering in Testing Projects
Testing projects differ from other types of partial life cycle projects. In partial life
cycle projects, the aim to produce working and defect-free code starts at some
point in the software development life cycle. But in the case of testing projects, the
software is already developed. The objective of the project could be different for
each testing project. The objectives of testing are:
1. To uncover all lurking defects
2. To certify a product as defect-free, virus-free, or malware-free and so on
3. To benchmark a product vis-a-vis other comparable products
4. To accept software from a vendor and start using it
The testing that is carried out concurrently while developing the software is
normally referred to as embedded testing. The testing carried out at the end of
software development on the final product is normally referred to as product
testing. Embedded testing is carried out by the organization which is developing
the software. Product testing is sometimes outsourced. Besides unit testing, inte-
gration testing, system testing and user acceptance testing there are umpteen
variety of tests that are conducted. These include stress testing, load testing,
parallel testing, concurrent testing, end to end testing, negative testing, intuitive
testing and so on. A testing project could include any combination of those tests.
However, when the testing project is initiated, one thing is certain and that is, the
code is ready and working. Perhaps, if it was a process-driven project, the
requirements and design documents also would also be available.
So what sort of requirements would be needed for a testing project? We can
enumerate them below:
1. The type of tests to be conducted as part of the testing project
2. Information for planning the specified tests
3. Information for designing the test cases
4. Information for pass/fail decisions
 
Search WWH ::




Custom Search