Planning & Execution
All files related to planning and execution can be found in the Project Management directory, which can be accessed by this link.
Intellectual Property ConsiderationsAny intellectual property developed in the course of this project will be available to be licensed to RIT and the Al Sigl Community of Agencies at no charge in perpetuity for purposes of research and development of effective access technologies, devices and systems.
Therefore, whoever is active in the project at the time of laying an IP claim will have equal rights for the IP. “Active” is defined as being engaged in group conversation and in the emailing list for weekly project updates.
Our IP Statement is subject to change based on unknown circumstances that we may encounter over the course of the project.
Risk Assessment and Growth Curves
This is a link to the Risk Management Spreadsheet
Project Plans & Schedules
This is a link to the LiveAbility Lab Gantt Chart
Plans for next phase
Team Goal for Weeks 4-7
- Our team goal for Phase 2 is to have a completed system design for the LiveAbility Lab Project. This will include all customer requirements, how to connect our sensors to software which will display and analyze the data, and prototypes for some parts of the project.
Individual Responsibilities to Achieve Team Goals
- Martine Bosch
- Assist Lead Engineers with research on sensors, waterproofing techniques, and possible materials to use. (6 hours)
- Design sensor attachments. (4 hours)
- Draft initial top-level design. (3 hours)
- Nick Petreikis
- Research Texas Instrument force sensors and beacons (2 hours).
- Contact Texas Instruments about sponsoring the team (1 hour).
- Draw up mock budgeting plan (5 hours).
- Matthew Devic
- Sketch ~20 design solutions of the overall system to generate and rank team ideas(1-2 hours).
- Research rechargeable batteries for life, weight, and dimensions (1-2 hours).
- Research and determine what types of microcontrollers could work for system design (2-3 hours).
- Patrick Mylott
- Create a stakeholder matrix with contact information and the power and influence of each stakeholder. This is so all of our contact information will be in one place. (1 hour).
- Continue to update the gantt chart for the project, which lays out tasks and their owners. (2 hours)
- Assist team with coming up with design ideas for sensors, batteries, triangulation system, and more. (at least 6 hours)
- Help Nicholas with the budget and possibly turning it into a time phased budget to help us predict the spending of the project team. (4 hours)
- Begin to develop prototype ideas and gather materials with the team. (8 hours)
- John Lebrun
- Research and develop battery solutions for the sensor device (6 Hours)
- Determine the method communication transfer from sensor to “server.” (2 Hours)
- Get donuts for the team (30 Minutes)
- Continue on with the weekly State-of-the-Project emails
- Research the two previous attempts at making something similar to our project and extract useful findings from their projects for use in our design. (2 Hours)
- Erik Brown
- Brainstorm options for sensor attachment without affecting gait of individual. (2 hours)
- Benchmarking analysis. (2 hours)
- Assist lead engineers in developing test plan. (4 hours)
- Hrishikesh Moholkar
- Research the MCU and IDE to use for developing the firmware for sensor.
- Add more cases and improve the UML diagram for the sensor software.
- Help team in research.
Other Team ResourcesYour team may have other resource requirements. With your customer and guide, your team should identify:
- Planned meeting space (default is MSD Design Center)
- Planned build & test space (e.g., Design Center, EE Senior Design Lab, CE Projects Lab, ME Machine Shop, Brinkman Lab, other faculty lab on campus, onsite at customer location, etc.)
- Any RIT or customer safety training required to use
- RIT Training may include, for example: lab/studio safety, fire safety, laser safety, hazardous waste management, radiation safety, gas cylinder training, shop safety
- Full list of available RIT courses is available here. If you have an external customer, they may require additional training.
Meeting Minutes, Notes, & ActionsMSD I & II. Maintain a record of team/guide meetings. This includes discussion, action items, decisions made, and work assigned.
PurposeProvide feedback that enables improvements in effectiveness and efficiency of individuals and the whole team.
- Instructions and EXAMPLE must be deleted before the Problem Definition Review.
- Identify an owner for this document.
- Each team member will assess each of their team mate per the criteria established in the Values and Norms section.
- Each member will acknowledge excellent behaviors of their fellow team members and provide constructive recommendations to improve the team effectiveness and/or efficiency. (plus/delta recommendations)
- Considering the purpose, the team should anticipate potential failure modes associated with construction and use of this document.
Inputs and Source
- Team members.
- Template and Example.
- Reference doc.
Outputs and DestinationReview form that is shared with Guide at the end of each cycle. All peer reviews are done using the myCourses peer2peer tool, and teams will discuss the results with their guide after each phase.
- To be completed at a later date.
- Establish customer point of contact
- Establish preferred method of communication
- Establish expected frequency of communication
- Determine customer availability for each of the 5 reviews
- Identify a team member to handle customer
- Establish team expectations for cc on customer emails
- Set expectations for how/when pre-read documentation will be shared with customer
- Establish expectations for within-team communication
- Establish preferred method of communication
- Establish expectations for how/when to include guide in communication
- Establish team expectations for cc on within-team messages