Dr. Bae Preliminary Feedback - lydia-wu/cadence GitHub Wiki

Hunter Alloway 09/17/2021

• The client requirements are the one's that we must nail down, because if we have to modify them later, this will impact the system requirements.
• Clearly state the solution data set input/output and what the intentions of each requirement are. Prognostic testing for example is a main objective and all the system requirements should be able to trace back to this requirement, meaning one system requirement can satisfy multiple stakeholder requirements
• We can show that relationship between system and stakeholder requirements on the right-most column in Decision gate Two
• Dr. Bae reccomends identifying the exact requirement, the exaCT DEFINITION OF WHAT IS BEING REQUIRED be it a hardware component or software. Make sure that he is able to clearly identify "this is exactly what the client wants come the end of the capstone project.
• The deliverable should be the deliverable in a sense
• In our case, if the client says "this is not what I want". We should be able to go back to the stakeholder requirements and make a clear argument on the teams behalf stating clearly "this is what you were expecting and we have noted this in both system and stakeholder requirements"