Milestones
Milestone One
List of Criteria: A list that our group had created to help us narrow down slightly as to what we want our design to accomplishÂ
Need Statement: After identifying an end-user, we created a Need Statement to identify exactly who the product was for, what the product was and why they needed.Â
Preliminary List of Ideas: This was used to quickly brainstorm possible solutions we could derive from the need statement that we had created
Milestone Two
Concept Sketch: Prior to meeting altogether, each team member was asked to create at least 3 preliminary idea sketches for the selected end-user.Â
Design Flowchart: This was created for each concept sketch. It was a way to better understand the concept sketch. Essentially, it outlined the way the device was to intake input and its process of displaying output.
Go, No-Go Screening: Upon meeting up as a group, certain ideas (such as the least practical ones) were eliminated and in the end, we had narrowed down the number to about 7 designs. The Go, No-Go Screening aided to understand how well each device performed next to a standard, commonly used and already-existed wearable medical device.
Decision Matrix: This matrix helped to better understand how well each device pertained to our need statement the best. Our team had finalized on the back EMG patch.
Milestone Three
Parts List: This is simply a list of the parts that we were to request in order to complete the final project
Support Frame Sketches: One of my teammates and I are responsible for the solid modelling of this project using Autodesk Inventor. These were the sketches that are to hold the GPIO Break Board, the Bread Board, the Raspberry Pi and the sensors themselves. One thing to note, these items are too heavy and bulky to put on the actual prototype, these are simply to represent as proof of concept.
Flowchart: This flowchart is to represent how the final code is supposed to function, everything from understanding input, processing and showcase a final output.
Test Plan: This is simply a plan to test if the code runs as planned in later stages.
Milestone Four
Preliminary Design Review Feedback: This milestone consisted of our team meeting with two professional and explaining our idea to them. The reason for this was to gain insightful feedback on our design as well as address any concerns/questions we may have to better improve the device or clear any ambiguity.
