1 / 18

Design and Planning University of California, Los Angeles CS 130, Spring 2009 Prof. Rupak

uKuda. Design and Planning University of California, Los Angeles CS 130, Spring 2009 Prof. Rupak. Design Details. uKuda will utilize HTTP and HTTPs protocols Challenge: obtaining a Secure Sockets Layer (SSL) certificate for free Our toolkit: CakePHP, MySQL, JavaScript, CSS, HTML

inga
Download Presentation

Design and Planning University of California, Los Angeles CS 130, Spring 2009 Prof. Rupak

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. uKuda Design and Planning University of California, Los Angeles CS 130, Spring 2009 Prof. Rupak Michelle Auyoung - Borys Boyko - Kin Chung Chu - Brian Geffon - Brian Hou - Christopher Oentojo - Zev Solomon

  2. Design Details • uKuda will utilize HTTP and HTTPs protocols • Challenge: obtaining a Secure Sockets Layer (SSL) certificate for free • Our toolkit: CakePHP, MySQL, JavaScript, CSS, HTML • Risk: can we develop everything we want within the given deadline? • Functionality over aesthetics

  3. The Plan • Establish framework, develop key features first • Beautify later (aesthetically pleasing UI, Web 2.0) • 1) Database • Controls whole backend • What tables are needed, what they represent, how are they connected? • 2) User accounts • HTTPs and SSL • 3) Location database • Importing – how to get 2.7 million entries into a database from a .txt file …

  4. The Plan (continued) • 4) User profiles • Google Maps API • Friends • Comments system • “Where I’ve been” • 5) Location profiles • Google Maps API • Rating system • “Who’s been here” • 6) Stories • Integration with locations and user profiles …

  5. The Plan (continued) • 7) Homepage Layout and Design • Story feed • Top 10 lists • Google Maps API • 8) Templates • Search bar • Quick login • Navigation tabs • 9) Photo Upload Feature • 10) Web 2.0 • Aesthetics • Fluid GUI • Split into multiple builds

  6. The Plan (continued) • Build 1 (= prototype) • User Accounts – Brian Geffon • User Profiles – Brian Hou, Chris Oentojo, Zev Solomon • Location Profiles – Michelle Auyoung, Borys Boyko, Kin Chung Chu • Build 2 • Stories – Brian Hou, Chris Oentojo, Zev Solomon • Home Page – Michelle Auyoung, King Chung Chu, Brian Geffon • Website Template – Borys Boyko • Build 3 • Photo Upload Feature – Michelle Auyoung, Kin Chung Chu, Brian Geffon • Web 2.0 – Borys Boyko, Brian Hou, Chris Oentojo, Zev Solomon

  7. System Architecture • Based around an SQL database hierarchy • Database will contain several interacting tables • Tables will have entries (ex: an entry in a “Users” table is a single “User”) • All interaction between components occurs at the database level due to database table relationships

  8. System Architecture: Continued… Database Table Structure

  9. System Architecture: Continued… User Registration Procedure

  10. System Architecture: Continued… User Login Procedure

  11. System Architecture: Continued… User Information Retrieval Procedure

  12. System Architecture (continued) • Clearly, there is a pattern for accepting user input:

  13. System Architecture (continued) • Adding user input to database table(s): • Verifying user input via database table(s):

  14. Testing Plan • Unit testing for each module during development • User Accounts • User Profile • Registration/Login • Location pages • Stories • Google Maps API • Mostly manual, possibly with customer involvement

  15. Testing Plan (continued) • Integration testing for module groupings • Location databases • Search function • User account • Login • User / location interaction • Story • Regression testing for each module intergration

  16. Testing Plan (continued) • System testing for whole system • Non-user actions • User actions • GUI testing • Load testing • Security testing • Regression testing, one more time • Have all requirements been met?

  17. Milestones • Repository has been up since the first week of group meetings (current build number is in the 90s, mostly due to document edits) • Basic database structure has been established • World country, region, and city data has been located (over 2.7 million entries!) • Domain names and web space has been purchased

  18. Thank You! www.ukuda.com Coming Spring 2009

More Related