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.
Project Summary | Project Information |
|---|---|
All template text on this page must be removed from this page prior to your Week 3 Problem Definition Review One or two paragraphs that provide a general description of the project in terms of background, motivation(s), customer(s), and overall objective(s). Use your creative talents to include photos, short video clips, or other information to quickly and effectively help prospective student team members learn what the project is all about, and how they would be able to contribute. | Project Name/Title: Project Number: PXXXXX Project Family (if relevant): Start Term: 2XXX End Term: 2XXX Faculty Guide: Primary Customer(s): Sponsor (financial support): Don't include people's email/phone # without their consent |
Team Members
| Member | Major | Role | Contact |
|---|---|---|---|
| name | major | role | |
| name | major | role | |
| name | major | role | |
| name | major | role | |
| name | major | role |
Information
Content Guidelines: Use these links below to guide you in populating your website. A few points to consider:
- Be aware of any information that your sponsor might not want publicly available. You can use the directory for this information, and it will be available only to those users with Guest access to your site.
- Do not post any files on your site that are not yours, unless you are certain that they are in the public domain or you have received permission to post them. Examples of files that you should avoid posting are copies of published papers, standards documents, textbook chapters/excerpts, or copyrighted images. If you have received a .pdf of a paper through Interlibrary Loan, or purchased an ASTM or ISO standard, you may post it in the private directory, where only your team and guide will have access to it.
- If you are including contact information for people that would otherwise not be publicly available, make sure you have their permission. For example, your faculty advisor's email address and office phone number are already publicly available on the KGCOE website, and is fine to post. However, if he or she has provided a cell phone number to the team, that is most likely not public information and should not be posted without explicit permission.
- Comment out this text once you've read it.
Work Breakdown: By Phase
MSD I & II | MSD I | MSD II |
|---|---|---|
Integrated System Build & Test Customer Handoff & Final Project Documentation (Verification & Validation) |
Work Breakdown: By Topic
Use this space to link to live/final documents throughout the project. Your team should customize this as-needed, with input from your guide and customer. The example below will address most of what most teams need to capture.
Project Management | Design Tools | Design Documentation | Implementation | Validation | Presentation & Dissemination |
|---|---|---|---|---|---|
PRP Requirements Schedule Cost Risk Management Problem Management Communication & Minutes | Use Cases Benchmarking Functional Decomposition Morphological Chart Pugh Concept Selection | BOM Mechanical Drawings Electrical Schematics Software Diagrams Facility Layout Manuals | Mockups Test Fixtures Prototyping Test Plans | Analysis Results Simulations Test Results | Design Review Documents Technical Paper Poster Imagine RIT Exhibit |
Acknowledgements
- Be sure to include any relevant sponsor acknowledgement throughout your site.
- Acknowledge any other support you have received from people at RIT or elsewhere.