RIT will permanently shut down the RIT Wiki (Confluence wiki) on February 2, 2024. Review the Wiki Shut Down Overview for information on alternative tools, exporting content from the wiki, and other FAQs.
Document Owner: Jeffrey Seamon
Date Updated: 10/7/2020
Date
Monday 10/5/2020 - 12:45 to 2:15 pm - Zoom Meeting
Pre-Read
Team: 21363 Automated Player Piano V
Since our Problem Definition Review, we have refined our understanding of the problem, and what our customer is looking for. The focus of our design remains a semi-autonomous player piano device capable of assisting a human pianist in playing a piece, with a user interface, full autonomous support, among other requirements.
Over the course of this meeting, we will be going through the topics listed in the agenda above. This will begin with a review of our current progress and show the updates based on feedback from our previous review. We will address the functionality we will include to achieve the corresponding customer/engineering requirements, and show how we arrived at our concept proposal, including selection criteria, benchmarking, test design, and feasibility. This system design proposal is subject to change based on our testing results, further risk assessment, and your feedback. We will be sending along an outline of our functional composition and concept proposal, any initial feedback you have regarding these documents before the meeting would be appreciated. Listed here is the link to the system level design section of the wiki page for your reference:
https://wiki.rit.edu/display/P21363/System+Level+Design
Attendees
- Nick Besley
- David Anthony
- Josiah Martuscello
- Steven Petrick
- Jeffrey Seamon
- Jerry Adamski (Guide)
Ron Dufort (Customer)
Goals
- Revisit action items from PDR
- Discuss concept development
- Discuss selection criteria, system concepts, and system selection
- Layout final concept selection
- Discuss feasibility, system architecture, risk assessment
- Show our tentative upcoming schedule
- Discuss next steps, answer questions, ask for approval
Agenda and discussion notes
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Action Items from PDR | Steven Petrick | Customer gives OK on action items |
| 5 min | Functional Decomposition | Steven Petrick | Notes/discussion here |
| 5 min | Benchmarking | David Anthony | N/A |
| 5 min | Morphological Chart | David Anthony | Discussion of camera concept, good job coming up w/ a lot of ideas |
| 5 min | Selection Criteria | Jeffrey Seamon | N/A |
| 5 min | Pugh Chart | Jeffrey Seamon | Be explicit w/ metrics used; develop a "Concept F" w/ best qualities from other concepts & compare |
| 5 min | Final Concept Selection | Josiah Martuscello | N/A |
| 5 min | Feasibility | Josiah Martuscello | N/A |
| 5 min | System Architecture | Josiah Martuscello | Feedback sys. will create MIDI to playback, send off to teacher, etc. |
| 5 min | Risk Assessment | Nick Besley | Develop risk mitigation plan |
| 5 min | Plans for Next Phase | Nick Besley | Very modest budget past few years, develop BOM and then propose budget |
| 5 min | Thank you, Questions, Approval | Nick Besley | Customer gives approval to proceed; be sure to collaborate w/ client |
Presentation
The following link leads to the presentation given for the Problem Definition Review: System Level Design Review Presentation. A PDF version is available here.
Issues Raised
- Keep risk management in mind (not just risk assessment)
Decisions Made
- Approval given on action items from PDR
- Evaluate inventory, develop BOM, and then propose budget (if none given, more money needed)
- Approval given to proceed to Preliminary Detailed Design Phase
Action items
- Team will complete peer evaluations.