Through an analysis of Trace to Requirements and Trace to Modules sections, the system defined and the system tested almost fully match. Excluding hard to test components of the system, edge coverage of system inputs was tested. \\
GIF manipulation was tested through auto manipulation of a GIF and comparisons to the expected output. This solution provided a guaranteed way to validate output with what a user should expect. However, due to the system depending on user interaction, most testing had to go through a manual test plan for system validation and verification. All possible input types are tested within the test plan, which verifies full edge coverage of user inputs to the system. However not all sequences could be tested manually due to the immense time it would take to complete this task. Thus the system is tested on an edge coverage basis, not a path coverage basis. \\
Finally, hard to test requirements such as non-functional requirement 3.2.1 is relative to specific test groups not available during this development time. Having a person of age MIN\_USE\_AGE (10) test the system was not present during the development phase, thus remains unverified. Furthermore, non-functional requirement 3.3.1 would require a testing of an extreme amount of GIF images to validate the speed requirement is met. Few other examples of hard to test requirements exist, thus passing the system as valid is a safe assumption.
