1 / 10

Rock O’ The Range ListenUP

Rock O’ The Range ListenUP. Advisor Dr. Vegdahl, Dr. Ward Industry Representative Mr. Jason Favors, Eric West, Owen Nichols, Ben Foran Flashlight Engineering. Team Paul Imel Takeshi Horie Joe Lyons Jonathon Loo. Overview. Introduction Scorecard Additional Accomplishments Plans

mark-wood
Télécharger la présentation

Rock O’ The Range ListenUP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Rock O’ The RangeListenUP • Advisor • Dr. Vegdahl, Dr. Ward • Industry Representative • Mr. Jason Favors, Eric West, Owen Nichols, Ben Foran • Flashlight Engineering Team Paul Imel Takeshi Horie Joe Lyons Jonathon Loo University of Portland School of Engineering

  2. Overview • Introduction • Scorecard • Additional Accomplishments • Plans • Issues/Concerns • Conclusions University of Portland School of Engineering

  3. Introduction • Visual Music Creator • Visually rich • Musically simple • Creatively inspirational University of Portland School of Engineering

  4. Scorecard • Finished Theory of Operations 1.0 • Merge the two parts of our program together. • Merged Successfully • Create music library and finish play functionality. • Plays Beautifully • Have testers(other teams) test our program. • Not done yet University of Portland School of Engineering

  5. Additional Accomplishments • Demo-able program • Very close to being completely, successfully done University of Portland School of Engineering

  6. Plans • Test the program thoroughly ourselves • Every use case and test case • Have testers(other teams) test our program • Complete program • Perform dry run • Present on Founder’s Day • Finish Final Report University of Portland School of Engineering

  7. Milestones University of Portland School of Engineering

  8. Concerns/Issues • Authority to save/load on school computers • Considering secondary functionality • Time vs. Easy Implementation • Finding all the bugs • Making it look as good as it can • Coloring it well • Finding the right music University of Portland School of Engineering

  9. Conclusions • What we’ve done • Program that functions well. • Only finishing touches needed yet. • Need to show it off well. University of Portland School of Engineering

  10. Any Questions? University of Portland School of Engineering

More Related