What is Requirements Testing Technique

Functional system testing ensures that the system requirements and specifications are achieved. The process normally involves creating test conditions for use in evaluating the correctness of the application.

Requirements testing must verify that the system can perform its function correctly 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.

What are the objectives of Requirements Testing Technique ?

Successfully implementing user requirements is only one aspect of requirements testing. The responsible user is normally only one of many groups having an interest in the application system. The objectives that need to be addressed in requirements testing are:
  1. Implement user requirements
  2. Maintain correctness over extended processing periods
  3. Ensure that application processing complies with the organization’s policies and procedures
Secondary user needs have been included, such as:
  1. Security officer
  2. Database administrator
  3. Internal auditors
  4. Records retention
  5. Comptroller
  6. System processes accounting information in accordance with generally accepted accounting procedures.
  7. Application systems process information in accordance with governmental regulations.
How to Use Requirements Testing ?

Requirements’ testing is primarily performed through the creation of test conditions and functional checklists. Test conditions are generalized during requirements, and become more specific as the SDLC progresses, leading to the creation of test data for use in evaluating the implemented application system.

Functional testing is more effective when the test conditions are created directly from user requirements. 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, defects introduced into the documentation will be detected.

Where to use Requirements Testing Technique ?

  1. Creating a test matrix to prove that the systems requirements as documented are the requirements desired by the user.
  2. Using a checklist prepared specifically for the application to verify the application’s compliance to organizational policies and governmental regulations.
  3. Determining that the system meets the requirements established by the organization’s department of internal auditors.
When to Use Requirements Testing ?

Every application should be requirements tested. The process should begin in the requirements phase, and continue through every phase of the life cycle into operations and maintenance. It is not a question as to whether requirements must be tested but, rather, the extent and methods used in requirements testing.(134.1)

Related Posts

UNIT TESTING

UNIT TESTING PART ONE

UNIT TESTING PART TWO

UNIT TESTING PART THREE

GUI TESTING

WINDOWS COMPLIANCE GUI TESTING PART ONE

WINDOWS COMPLIANCE GUI TESTING PART TWO

WINDOWS COMPLIANCE GUI TESTING PART THREE

WINDOWS COMPLIANCE GUI TESTING PART FOUR VALIDATION TESTING

WINDOWS COMPLIANCE GUI TESTING PART FIVE CONDITION TESTING

WINDOWS COMPLIANCE GUI TESTING PART SIX GENERAL CONDITION TESTING


No comments:

Post a Comment