Validation and Verification of System Requirements

As the name suggests, Validation and Verification of System Requirements is to validate and verify whether the system is adhered to the user’s need and functional requirements of the system. This is quite handy in #202206201159.

There could be a discrepancy between the end-user access patterns and the test data gathered by the developers. Notice their differences, and study how and why they differ from each other.

#202206201159 recommends to do both Validation and Verification and 202206201428 as early as possible.

Links to this page

Usability Testing

Usability Testing aims to test the usability of the software, that is about the user interface and user experience (UI/UX) while using the program from the end-user point of view under real environment. As the testing is done regarding the user, it puts most of the concerns in terms of human factors rather than relying on synthetic data collected elsewhere, which by some sense quite similar to 202206201346. #202206201159 recommends doing them as early as possible.
Test Driven Development (TDD)

Hunt et al. recommends that both Validation and Verification of System Requirements# and Usability Testing# should be done as early as possible. And that Regression Testing# to be incorporated into the build system in order to compare it to the previous build.

Unit Testing# is the foundation of this whole practice. That being said, other testing such as Integration Testing#, Validation and Verification of System Requirements#, Environmental Testing#, Performance Testing#, Usability Testing# and Runtime Diagnostics# should not be underestimated. All test cases should honour its contract where we can check whether the code meet the contract of the contract means what we think it means.

#test