|
Difference between Software Product and Project Software Product: These
are readymade software applications designed by company after
researching customer requirements. Once these application or software
are designed, they are sold to the customer after lot of advertisements. If
customer wants any changes in color, title, appearance and append extra
functions then company will customize the product and sell to the
customer. Here business requirements play important role. Examples: Windows 9X family, 2001-2003 professional and server are all
Product of Microsoft. Software Project:
Project, on contrary, are software that are designed on collecting
complete requirements from customer and build the product as per his
requirements. Here customer requirements play important role. Examples: If Nikita asks XYZ-Company to build Stock Management Software (Store-Keepin) than it would Software Project for XYZ-company. I hope you are clear with above description. Test Strategy and Test Plan Test Strategy: It’s a document that defines the required Testing Approach to be followed by
testing people to test software in each phase (component test, system test, or acceptance test). Further, it is a part of Test plan. - Testing process: The testing procedure described in this plan, given in terms of phases and activities.
- Requirements traceability:
Relate the testing to the requirements given in the SRS (this will be
strongly related to what you given in the test requirement
cross-reference matrix).
- Items or components tested: The items being tested; identify them as precisely as possible.
- Testing schedule and resources: The overall testing schedule and resource allocation.
- Test recording procedures:
How the results of the tests will be systematically recorded. It must
be possible for an outside agency to inspect the test plan, the test
cases, and the test results to determine that the testing process has
been carried out correctly.
- Hardware and software requirements: The software tools that are needed for running these tests as well as any hardware that will be needed.
- Constraints: Any constraints that will affect the testing process.
Test Plan: It’s a document that provides work allocation in terms of schedule. It
is the primary means by which software testers communicate to the
product/project development team what they intend to do. Its purpose is
to prescribe the scope, approach and schedule of the testing
activities. It
helps to identify items being tested, the features to be tested, the
testing task to be performed, the personnel responsibility for each
task and risk associated with the Test plan and Testing process. For
your better understanding, Test plan is by-product of detailed planning
process that is undertaken to create it. It only plans the matter and
not resulting document.
The Goal is to communicate with Software Test team’s intent, its
expectations and understanding the testing that has to be performed. Following Topics help to design the Test Plan: High level Expectation People, place and Things
Inter-Group responsibilities Test Phases Test Strategies Bug Reporting Matrices and
Statistics Risks and Issues
|