Customer Handoff & Final Project Documentation
Table of Contents
Team Vision for Final Demo and HandoffWhat did your team plan to do during this phase?
During the Customer Handoff and Final Project Documentation phase, the team planned on wrapping up the project, and making sure everything was ready to be handed over top the customer. First, the test plans for the phase were made, and the team worked together to see if anything could be done separately, as every class is still online. Second, the test results summery was laid out, and the results were compared to the engineering requirements. Next, the final drafts of the paper, poster, and lightning talk were planned to be completed. The risk assessments and problem tracking were also planned to be updated and completed, such that the work throughout the year could be seen. During the phase, the team planned to have one team member run the system from their home and see how the system operates. Once the system ran into bugs, the team planned on discussing how to move forward via Zoom and seeing how to move forward with the testing. Lastly, the team planned to add all final project documentation to the EDGE page, and complete demo materials for the final presentation, which will also be added to the EDGE page.
What did your team actually accomplish during this phase?
During the phase, the team focused on completing the final project documentation, so that the next team and customer new exactly were the team had left the system. The team focused on the paper, poster, and lightning talk, such that it could be updated and revised many times. The testing of the system at home ran into problems, as the Linux operating system was needed to be sued to run the code. As the team could not meet to get the Linux operating system running properly, the testing of the code was not successful, and the only code that was able to be tested was from previous phases. The team than moved onto test plans and test results, along with finishing up the design vs requirements file. Next, the Gantt chart was finalized and posted on the EDGE page, so that the process of the phases could be seen. The risk assessments were looked over, but since not much was done for testing during this phase, the team did not update the risk assessments file from the previous phase. The problem tracking and demo materials were then finished, and lastly the team prepared for the final customer handoff and wrap-up for the system.
Test Results SummaryThe 2019-2020 COVID-19 Global Pandemic halted our progress on our test results. Therefore, our test results are very similar to the previous phase.
Summary of Test Plans: test results
- Use previous team's Imagine RIT Demonstration to gather live-time sensor data via terminal
- Send live-time data to an excel spreadsheet or CSV file
- Read file and write data to the SD Card to gather live-time data of sensors
Inputs & Source
- Accelerometer - Acceleration data must be within 5% of the expected value on bench test.
- Vibration and Torture Testing of System and Enclosure - System must be able to withstand volatile in-car environment
- Mounting Bracket Design and Production - Brackets must be manufactured/adaptable to the various mounting locations within the vehicle.
- Lap Time Acquisition - Configuration of timer module to pair to GPS data for timestamps
- All sensors must acquire data within 5% tolerance.
- Device is able to store at least one hour of data to an external storage device 32GB in size without overwriting buffer
Outputs & Destination
- 5% tolerance of all sensors
- Gain a greater understanding of the source code to move forward and create greater progress
Risk and Problem TrackingRevised Risk Assessment Seen Below:
Final Project DocumentationLink to Technical Paper Below:
Link to Poster Below:
Link to Lightning Talk Powerpoint Presentation Below:
Work Breakdown: By Topic
|Project Management||Design Tools||Design Documentation||Implementation||Validation|
Functional Demo MaterialsLink to Powerpoint Presentation Below:
Plans for Wrap-upAs a team, what do you need to do to conclude your project?
To conclude the project, the team must make sure everything is prepared to hand off to the customer, so that the next team to work on the system knows where we left off, and how we would advise to move forward with the testing and debugging. First, the team needs to make sure the code is easy to understand, such that the next team does not take much time to see how the code is operating the system. This can be done by continuing to add comments to the code until the system is fully moved over to the customer. Another thing to conclude the project will be to organize everything that was done over the course of senior design, so that the next team can see how we moved in our design each step of the way. Finally, all the manuals, drawings, and schematics used should be commented on, so that the next team can see how the team edited or changed anything from the previous team’s work. In all, the team must make sure the next group to work on the system does not waste time understanding what was done, and can continue to move the system forward with what they think should be tested, along with what is suggested from our team to move forward.