Requirements testing must verify that the system can perform its function corectly and that the correctness can be sustained over a continuous period of time. Unless the system can function correctly over an extended period of time, management will not be able to rely upon the system. The system can be tested for correctness throughout the life cycle, but it is difficult to test the reliability until the program becomes operational.

Objectives
Sucessfully implementing user requirements is only one aspect of requirements testing. The responsible user is normally onle one of many groups having an interest in the application system. The objectives that need to be addressed requirements testing are:

* Implement user requirements.
* Maintain correctness over extended processing periods.
* Ensure that application processing complies with the organization's policies and procedures.

Secondary user needs have been included, such as:
* Security officer
* Database administrator
* Internal auditors
* Records retention
* Comptroller
* System processes accounting information in accordance with generally accepted accounting procedures.
* Application system process information in accordance with governmental regulation.

How to Use Requirements Testing
Reauirements' Testing is promarily through the creation of test conditions and functional checklists. Test conditions are generakized during requiremnts, and become more specific as the SDLC progresses, leading to the creation of test data for use in evaluating the impleneted application system.

When test conditions are created from the system documentation, defects in that documentation will  not be detected through testing. When the test conditions are created from other than the system documentation will be detected.

Requirement Testing Techniques