This week’s discussion reminds me a lot of what we had to learn in our capstone design class senior year. The three biggest deliverables for that class other than our powerpoint presentations were the two documents that we had to turn in: business requirements document and the test plan document. The business requirements document was a direct representation of the customer needs. We met with our customer, asked what he wanted his device to have and the constraints, and then we determined how to create a device that fulfilled all these requirements. This document was long and was to specifically list every single aspect of the device and be so detailed that if carrying out and following every requirement, the device can be made perfectly every time.

The test plan document is a supplement to the business requirement document. The test plan is meant to take all the requirements and introduce a test architecture to determine whether all the values in the requirements represent the device.

It is common for a device to go through all these steps before it can be mass produced and sold. Everything has to be perfect because of that and the constant trial and error of making it is difficult and takes a decent amount of time.