Ent money mind

309 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
309
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ent money mind

  1. 1. Service Computing & MoneyMind Mash-up
  2. 2. What is Service Computing?
  3. 3. Service Computing  Self-contained, platform-independent method of bridging the gap between business and IT  Businesses can find, utilise and create their own services and integrate them with others to create a tailored system to match their business needs  Technology includes: Web services, service-oriented architecture (SOA), cloud computing and many more
  4. 4. What are its impacts?
  5. 5. Global Impacts  Most obvious impact is between businesses globally and their interaction  Large companies like Microsoft putting cloud computing as a top priority  IBM spent $360 million on building a cloud computing software centre in NY  Estimated by 2014, 30% of Global 1000 companies will use two or more cloud services up from 5% today
  6. 6. Local Impacts  Less cost on businesses  Use PAYG (or subscription) based services  Flexibility for upgrade – providing “on-tap” IT capability for start-ups, spikes in workload, etc.  Integration of business and IT systems, allows businesses to easily interact with and upgrade where necessary
  7. 7. Personal Impacts  Mobile applications as web services  Capability to access web services from all locations – integration of systems  Increase in cross-platform capabilities  More rich applications where processing can be done server-side and the phone doesn’t need the processing power  HTML5 further enhances them with APIs such as Google Charts
  8. 8. What Web Services will be used in MoneyMind?
  9. 9. BPM – Business Process Model
  10. 10. BPM (contd.) - MoneyMind
  11. 11. BPM (contd.) - PayPal
  12. 12. BPM (contd.) - Proximiant
  13. 13. BPM (contd.) – Google Maps
  14. 14. BPM (contd.) – Google Charts
  15. 15. PayPal - Functionality  Both personal and business application  Personal - online banking, purchasing, account management  Business - manage business operations, take payments on your website or by invoice  The PayPal Adaptive Accounts API allows users to create applications with built-in account management features. Using the API developers can create a PayPal Business account, add a bank account or a credit card as funding sources for PayPal accounts and verify a PayPal account status.  Within MoneyMind, PayPal is used as the primary source of payment and account verification.
  16. 16. PayPal – Owners and providers  In 2002 PayPal became a subsidiary of eBay  Service is targeted towards online shoppers as it provides a simple, easy method of transferring money over the Internet PayPal - Constraints  Quality of service dependent on internet coverage. Additionally, if no access to internet, PayPal cannot be used.
  17. 17. PayPal – Pricing Factors  While there is no initial upfront cost or plan options to use the service, PayPal is an acquirer which means they have the option to charge a fee for receiving money, proportional to the amount received. PayPal – Legal Factors  Important to consider security factors within MoneyMind as this is a mobile application.  Two-factor authentication including a login and additional security key - precaution against fraud and prevents accounts being compromised by malicious third parties  Additionally possible to receive a Mobile Transaction Authentication Number via SMS to increase security.
  18. 18. PayPal – Legal Factors  Important to consider security factors within MoneyMind as this is a mobile application.  Two-factor authentication including a login and additional security key - precaution against fraud and prevents accounts being compromised by malicious third parties  Additionally possible to receive a Mobile Transaction Authentication Number via SMS to increase security.
  19. 19. PayPal – Access and Use in App  Accessed through the PayPal Adaptive API  The PayPal API uses both RESTful and SOAP protocol and responses can be formatted as XML, JSON or NVP  Encryption over HTTPS  XML is used as the chosen response format. This text-based information allows for easy storage within the application’s transaction database
  20. 20. Google Maps - Functionality  Google maps can be used on both a personal and a business level.  Personal - Finding directions and locations of key areas.  Business - Businesses can use Google Maps in websites and applications.  The Google Maps API allow for the embedding of Google Maps onto web pages of outside developers, using a simple JavaScript interface or a Flash interface. It is designed to work on both mobile devices as well as traditional desktop browser applications. The API includes language localization for over 50 languages, region localization and geocoding, and has mechanisms for enterprise developers who want to utilize the Google Maps API within an intranet. The API HTTP services can be accessed over a secure (HTTPS) connection by Google Maps API Premier customers.  Within our application, Google Maps integration with transaction history would provide the user with a visual representation of where their money is being spent, and would help them target specific locations or stores in which they need to budget.
  21. 21. Google Maps – Owners and providers  Google Maps is owned and operated by Google.  The intended audience of this service are businesses and developers that want to have an accurate map system in their application. Google Maps - Constraints  Quality of service dependent on internet coverage. Additionally, if no access to internet, PayPal cannot be used.
  22. 22. Google Maps – Pricing Factors  Google maps have no costing policy as they make their money off advertisements and selling data. Google Maps – Legal Factors  It is important to remember that people’s locations are being recorded and to consider extra security so people’s privacy is not at risk.  The data can be sent over the HTTPs encryption, giving the data an added level of security
  23. 23. Google Maps – Access and Use in App  Accessed through Google Maps adaptive API.  The API is accessed by grabbing the functions in a simple JavaScript attached to the application.  APIs can talk over multiple encryptions such as HTTP and HTTPs.
  24. 24. Proximiant - Functionality  Application used to create digital receipts from specific transaction data  While the application also includes a bump-to-pay feature and NFC tagging, only the functions required to produce the digital receipt are needed and the information used will be stored within the database.  Digital receipts are also location-based  Both iPhone and Android application
  25. 25. Proximiant – Owners and providers  Owned and provided by a Silicon Valley-based start-up Proximiant  Intended audience is smartphone users (generally from between the ages 18 and 30 - due to bank implementation) who wish to obtain efficient transaction records to create a smart shopper Proximiant - Constraints  While NFC-payments are constrained by transceiver availability, we are only interested in the functions required to generate the digital receipts and hence this constraint is eliminated.  Quality of service dependent on internet coverage. Additionally, if no access to internet, Proximiant cannot be used.
  26. 26. Proximiant – Pricing Factors  Proximiant is a free service, provides perfect business application Proximiant – Legal Factors  Proximiant develops digital receipts based off information, in this case we would utilise the XML data stored in the database, without having to share personal information such as email address  Additionally, data is stored in secure servers app sent via encrypted HTTPS
  27. 27. Proximiant – Access and Use in App  SOAP, HTTPS, XML FILES -> Converts to digital receipts
  28. 28. Google Charts - Functionality  Used to visualise data into graphs/charts for mainly a Business perspective but can be used for personal use. This may vary from small line charts to a complex hierarchical tree.  Personal: Used for small visualisations of data. for example, a small presentation  Business: Businesses can use Google charts to visualize their data for things such as work presentations, Business meetings or just for general use.  The most common way to use Google Charts is with simple JavaScript that you embed in your web page. these charts are rendered using HTML5/SVG technology so that it can be compatible with all common browsers.  To create these charts, a Datatable is used to sort, modify and filter all data that can be directly imported onto a webpage.
  29. 29. Google Charts – Owners and providers  Google Charts is owned and operated by Google.  The intended audience for this is for businesses to make a clear, visual representation of their data towards other businesses or within their own. Google Charts - Constraints  Operating goggle charts requires internet access to operate. Although saved images of data can be taken for use outside of Google charts.
  30. 30. Google Charts – Pricing Factors  The Google charts website states that Google charts is completely free and guarantees three years compatibility. Google Charts – Legal Factors  Their is a small risk that people can obtain your data through breaching specific networks.  HTTPs can be used to make the use of their business data more secure, with the added level of security over the network.  It states within the privacy region within Google charts that Google does not share or obtain data that you have uploaded with other charts outside of your account.
  31. 31. Google Charts – Access and Use in App  The Google Chart API lets you dynamically generate charts with a URL string and embed these charts on a web page, or download the image for local or offline use. The Google Chart Tools enable adding live charts to any web page. They provide advantages such as a rich gallery of visualizations provided as image charts and interactive charts and they can read live data from a variety of data sources Users embed the data and formatting parameters in an HTTP request, and Google returns a PNG image of the chart. Many types of chart are supported, and by making the request into an image tag the chart can be included in a web page.  The API is accessed by grabbing the functions in a simple JavaScript attached to the application.  APIs can talk over multiple encryptions such as HTTP and HTTPs.  Accessed through the Google Charts API
  32. 32. So what is MoneyMind?
  33. 33. Application Overview  Powerful, easy-to-use money managing application  Purpose is to allow users to use their phone to:  Pay using NFC (Bump-to-pay)  Collate Digital Receipts  Organise receipts into powerful Infographics  Track expenditure  Budget  Become more ‘money aware’
  34. 34. Platform  Application was chosen to run on Android exclusively. This is due to the following reasons:  NFC feature is not available in iPhones – they do not have an embedded NFC chip  Hence they would not be an effective device to use with the application  As the main purpose of the phone is to provide a unified, complete finance management package the necessity of this NFC feature is vital  Android applications are written in Java, which would effectively integrate all the web services easily
  35. 35. How is better value generated?  Currently, methods of payment and transaction tracking are limited, despite this age of technological advancement - for example, the fact that we still use paper receipts  The purpose of MoneyMind is to provide users with a visual representation of where their money is being spent, as well as integrating current payment methods through the use of PayPal, and payment tracking methods through the use of Proximiant digital receipts and Google Maps.  As well as having the ability to use the bump-to-pay feature through PayPal, users have on-hand access to graphical representations of where their money is being spent, for example. in the past month they 70% of their expenditure was for purchasing food.
  36. 36. How is better value generated? (contd.)  By utilising the information through the PayPal transaction data such as: store locations, store type, amount spent, products purchased etc. can then be delivered into services such as:  Google Charts - to create a visual representation of spending habits and allow the user to become money-aware  Google Maps - so that users can see location-based spending habits and determine areas or stores in which they are purchasing too much items  Proximiant - to create a neat digital receipt, and allow the user to search through their purchasing history. Proximiant also provides the user with discounts and coupons based on their purchasing history. GPS-data can be synced with Proximiant to enable this feature.
  37. 37. Strengths and Limitations Strengths Limitations Integrates the four web services to create a powerful financial management tool Internet connection is required to use the payment, Google Maps and Google Charts features Eliminates the need for physical receipts Data and privacy concerns – Data must be kept secure at all stages throughout the app and data messages encrypted Eliminates the need for multiple bank accounts, cards etc. Lack of NFC features within iPhones disallow the use of bump-to-pay. User-centred design that focuses on the app being user-friendly and easy to use Beautiful Infographics that allow effective representation of spending habits Google Maps integration to show location-based spending habits
  38. 38. What would it look like?
  39. 39. Marketing  Social media outlets as platforms to reach our target users  Target users are between 18 and 30 year old (smartphone users)  Users are money-conscious shoppers  Free versions of the app will be sent to reputable app reviewing websites, such as App Advice  Websites and blogs focused on Finance industry, such as DailyFinance.com will be sent a copy to test and publish on their site  Utilise Google Ads to ensure high-priority in searches  Use Google’s alert system
  40. 40. Future Directions  In the future new integrations could be added to this application:  Integrate more banks to this application so any bank accounts can be used and not just PayPal  Integrate voice recognition so that the user can ask the application basic questions about their monetary status.  Expansion of the application so that it can be used on iPhones, which would come with the addition of an NFC chip in the iPhone  Turn this application into a web service by creating APIs for this application so it could be integrated into other web applications  Introduce extra security such as finger printing or voice recognition so that money cannot be stolen
  41. 41. Thank you

×