Final Demo :: ECE 445 - Senior Design Laboratory

Final Demo

Description

The Final Demo is the single most important measure (and assignment) for the success of your project. The evaluation is holistic, focused on whether your project is completed, well-designed, reliable, and usable. You will demo your project to your professor, at least one TA, and a few peer reviewers. Other guests (e.g. alumni, high school students, sponsors, or other department affiliates) may also be present.

Requirements and Grading

Students must be able to demonstrate the full functionality of their project by proving that all the requirements in their Requirements and Verification (RV) table are met. Students must bring a printed out version of their block diagram, high level requirements, and RV table. Credit will not be given for feature which cannot be demonstrated.

For tests that are lengthy or require equipment not available at the time of demo, students should have their lab notebooks or printouts ready to show testing data. For any portion of the project which does not function as specified, students should have hypotehses (and supporting evidence) of what is causing the problem. If your demo needs to happen somewhere that is not the Senior Design Lab, you must communicate this with your TA!

The design team should be ready to justify design decisions and discuss any technical aspect of the project or its performance (not just one's own responsibilities). Quantitative results are expected wherever applicable. The demo grade depends on the following general areas: See the Demo Grading Rubric for specific details, but in general, show the following:

  1. Completion: The project has been entirely completed.
  2. Integration: The project is well-integrated, looking more like a final product than a prototype.
  3. Performance: Performance is completely verified, and operation is reliable.
  4. Understanding: Everyone on the project team must must be able to demonstrate understanding of his/her technical work and show that all members have contributed significantly.
  5. Polish & Attention to Detail: The project is well-polished with the user in mind. Good attention to detail is afforded to useability, presentation, and packaging.

 

Submission and Deadlines

Signing-up for a demo time is handled through the PACE system. Again, remember to sign up for a peer review as well.

Wireless IntraNetwork

Daniel Gardner, Jeeth Suresh

Wireless IntraNetwork

Featured Project

There is a drastic lack of networking infrastructure in unstable or remote areas, where businesses don’t think they can reliably recoup the large initial cost of construction. Our goal is to bring the internet to these areas. We will use a network of extremely affordable (<$20, made possible by IoT technology) solar-powered nodes that communicate via Wi-Fi with one another and personal devices, donated through organizations such as OLPC, creating an intranet. Each node covers an area approximately 600-800ft in every direction with 4MB/s access and 16GB of cached data, saving valuable bandwidth. Internal communication applications will be provided, minimizing expensive and slow global internet connections. Several solutions exist, but all have failed due to costs of over $200/node or the lack of networking capability.

To connect to the internet at large, a more powerful “server” may be added. This server hooks into the network like other nodes, but contains a cellular connection to connect to the global internet. Any device on the network will be able to access the web via the server’s connection, effectively spreading the cost of a single cellular data plan (which is too expensive for individuals in rural areas). The server also contains a continually-updated several-terabyte cache of educational data and programs, such as Wikipedia and Project Gutenberg. This data gives students and educators high-speed access to resources. Working in harmony, these two components foster economic growth and education, while significantly reducing the costs of adding future infrastructure.