1 / 37

eSusu Project

eSusu Project. Pete Bohman Dennis Horvath Omkar Lele Jinseuk Park Jaswini Vijayakumar. Introduction. Poster Work Products Requirements Analysis Design Implementation Project Management Future Direction Demo Future Direction. Poster. Business Problem. Online

john-ross
Download Presentation

eSusu Project

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. eSusu Project Pete Bohman Dennis Horvath Omkar Lele Jinseuk Park Jaswini Vijayakumar

  2. Introduction • Poster • Work Products • Requirements • Analysis • Design • Implementation • Project Management • Future Direction • Demo • Future Direction

  3. Poster • Business Problem • Online • Diminishes geographical boundaries. Extends customer base • Transaction Management • Automated transfer of funds. Personal account management. • Social Networking • Builds trust and fosters growth. • Access to Capital • Peer to Peer lending. • Security • Peace of mind. Created and Owned by Denis Rhoden

  4. Poster Challenges and Methods Requirements • Functional • Core functionality, security, transaction management, social networking • Statistical • Leverage functional requirements. Value add of the product to stake holders. • Feel Good • Convenience and style Architecture

  5. Poster: Results Documentation is a big accomplishment. • Requirements, Analysis, Design, Implementation, Project Management, and Future Directions. • Architecture as well as rationale. • A good start on the application. • A working framework. • Create Susu, Messaging, and Enrollment.

  6. Poster: Value added What the stakeholders have gained from our progress: eSusu End Users • The Features: finished and future. Us • Experience: technical, social, business, and academic. Our Sponsor • A Sharper Vision: technical, tangible, and stable. Future Teams • A Paved Road: documentation, and framework.

  7. Business Case “The goal of the C2C Microfinance Application is to create an online experience which successfully merges people capital and democratizes access to capital online for mobile and internet users. This is achieved by creating, distributing and managing consumer-to-consumer financial transaction platforms on behalf of individuals, neighborhoods, organizations. By leveraging people capital to achieve high levels of trust along with secure and flexible online functionality, eSusu is committed to equitable, user-guided creation and sustaining of opportunity and transparency for their core financial transactions.” Ack: Denis Rhoden

  8. Problem Statement “In order to provide the functionality of an online SUSU, a web application that employs social networking concepts such as the formation of online communities (in the form of susus) and member interaction will be developed.  The system will enable geographically diverse users to search for and participate in susus, which satisfy their individual needs.  By keeping track of the user’s transactions, the system will provide an opportunity for user’s to build their credit score by making regular payments and hence trust amongst other members.”

  9. Project Scope • Transition from offline to online • Convenience of a web application • Access from anywhere • Can develop to mobile • Design to cultivate trust among members (Social Networking)

  10. Background • Susu meaning “society” in Spanish • Peer to peer lending • Collect funds from all members and redistribute to one chosen member on a fixed time scale • Used by people who can foresee the need for funds • Not a “lender of last resort” Ack: Denis Rhoden

  11. System Purpose • Who: People in small communities to enterprise owners • Where: Place online; Accessible worldwide • Why: Leverage trust of offline susu with flexibility of technology; Expand the reach

  12. Functional Requirements - Core • Tier 1 (Core Functionality)  • Login / Logout • Alerts (Errors, Information, Leading - Lagging) • Profile Updating • Visitor – Create Account • Create Susu – Sponsor • Confirm Susu (Begin Transactions – Automatic withdrawal and deposit) • Susu search / Bot Functionality • Invite / Apply (Also related management) • View Susu (Partial/Complete) • Messages (Backbone functionality – User viewable logs, invites, error messages) • Transaction Security (SSL)

  13. Functional Requirements – Statistical and Feel Good • Tier 2  • Credit Score • Joining Fee – Tip, Insurance, Security • Automatic user up-gradation to Sponsor • Detailed Server Logs • UI with some Jazz – attracts people • Tutorials – Video, downloadable(pdf, picture sequences) • Password Management (Eg: Vidoop) • Security Signing – Verisign, McAfee Scanned

  14. Non functional Requirements • Compatible with common internet browsers. • Mobile devices • Security

  15. Analysis • Object Interaction Diagrams • Enrollment • Create Susu • Join Susu • Messages • State Models • User States • Susu States • Susu Membership States

  16. OID - Enrollment

  17. OID – Create Susu

  18. OID – Join Susu

  19. OID - Messages

  20. Analysis • User States

  21. Analysis • Susu States

  22. Analysis • Susu Membership States

  23. Design – System Architecture

  24. Design - Security • Need – Client Server communication contains sensitive information. • OpenSSL – Certificate and Key Generation • Https – Encrypted Communication • Handshake protocol • Exchange of public and private keys • Impossible to deduce private key using the public key Ref: Authorize.net

  25. Design – Environment and Technology • MySql – Database Server • Open Source Database • Runs on more than 20 platforms • Web Browser • Firefox 1.0 + • MS IE 5.0 + • Other popular browsers • Ruby on Rails – Development Platform • Quick, • Supports Security Implementation Frameworks • Gateway Interfacing • WeBrick - Web Server • Compatible with RoR • Supports SSL • Free • MySql • RoR – Binaries and IDE • Web Browsers • Web Server (WeBrick) • Security Key Generation • Gateway Interfacing Web Browser • Firefox 1.0 + • MS IE 5.0 + • Other popular browsers • Paid • Payment Gateway Accounts • Merchant Accounts • Password Management Utilities

  26. Design – ER Diagram

  27. Design • Functional Specifications • Create Susu • Add User to Susu • Enrollment Process • Messaging

  28. Implementation • Development Environment • Tools • Libraries

  29. Project Management • Development Process • Meeting Minutes • Issue Tracking • Gantt Chart

  30. Development Process • Rational Unified Process • Agility

  31. Meeting Minutes • Detailed accounts of all meetings have been kept • Plenty of requirements discussed • Valuable resource for the next team to pick up from where we left off

  32. Issue Tracking • Code freeze few days before • Errors/ Bugs found over the last few days have been logged for the convenience of the next team • Bugs can be found at http://code.google.com/p/cse758/issues/list

  33. Gantt Chart

  34. Demo • http://Cl112dnat.cse.ohio-state.edu • https://esusu.dyndns.org

  35. Future Directions • Statistics and Dynamics • White Label Service • Undershot Opportunities • Credit Score • eSusu Credit Score • Credit Karma Linkning • Password Management and User Tutorials • Vidoop • User Tutorials • Susu Toolbar • Susu Creation Process and Insurance

  36. Questions?

More Related