1 / 12

eyeWeb & eyeData

eyeWeb & eyeData. G Li Jason Klym Xiaying Peng Jason Hamilton-Smith. 0. Index. Synopsis Versions Features Architecture QA Bugs Feedback Post-Mortem. 1. Synopsis. eyeWeb

lucas-french
Download Presentation

eyeWeb & eyeData

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. eyeWeb & eyeData G Li Jason Klym XiayingPeng Jason Hamilton-Smith

  2. 0. Index • Synopsis • Versions • Features • Architecture • QA • Bugs • Feedback • Post-Mortem

  3. 1. Synopsis eyeWeb • A streamlined, high accessibility web-browser, for the iPhone device, designed with mildly vision-impaired users in mind. eyeData • A data storage, computation and display website for demonstrating user preferences to research and commercial interests.

  4. 2. Versions • Version 1: • eyeWeb application - basic web browsing • Testing of individual functions • Version 2: • Integration of eyeWeb user preference uploading with eyeData server • Testing of integrated systems • Version 3: • Password protection, bug fixing, and feature addition/removal • Testing of users

  5. 3. Features • Features video intermission! • YouTube: http://www.youtube.com/watch?v=RXKt1-BL3kU

  6. 4. Architecture

  7. 5. QA

  8. 5. QA

  9. 6. Bugs • eyeWeb will not load the default Home Page when it’s first loaded—program must be exited and restarted. • eyeWeb Setting’s Menu keyboard will not close after entering an URL. • eyeWeb bookmarking was intended but removed as an implementation that was acceptable was not reached by our deadline.

  10. 7. Feedback • “Changing the text color is AMAZING!” • “Simple and easy to navigate the Internet with.” • “Nice icon!” • “With the larger text, I don’t really need my glasses for reading.” • “It has a plain interface, but I like it.”

  11. 8. Post-Mortem • The Bottom-Up approach of project management, delegating each person to his or her duties and then integrating the project as a team. • Allowed for avoidance of scheduling conflicts and excessive overhead. • Researching available software packages and interfaces was the largest technical hurdle. • Technical problems were overshadowed by team scheduling times. • If the project were reprised, more feasibility studies would be completed prior to a requirements document being produced.

  12. 8. Post-Mortem • Keeping project complexity to a minimum allowed for much refinement and QA. • Advice for next year: “Through me you pass into the city of woe; Through me you pass into eternal pain; Through me among the people lost for aye. Justice the founder of my fabric mov’d; To rear me was the task of power divine, Supremest wisdom, and primeval love. Before me things create were none, save things Eternal, and eternal I endure. All hope abandon ye who enter here.”

More Related