#'Iolani Economics of Personal Finance ###Travis CI Build Status on master branch

on dev branch

##About this project This project started as part of an effort to rework the existing Economics of Personal Finance curriculum at 'Iolani School. Currently, the app functions as a virtual checkbook and achievement system for students to easily make virtual payments while remaining easy for teacher(s) to manage balances, experience points, and other relevant student information.

This app's primary function is to create the framework necessary to support "gamified learning", and we are hoping to expand this app to be compatible with a variety of teaching, learning, and classroom styles. In the future, we plan to eventually create a framework that can track fewer or more student variables. These are currently XP and money, but could potentially include stocks from a stock market simulation,

##Getting Started ###Introduction The Finance app is written in Objective-C, and was built using Apple's Xcode IDE. Originally built for iOS 6 on Xcode 4, the app has been transitioned over to provide iOS 7 and Xcode 5 compatibility. For centralized database management, we use Parse, since it provides pseudorelational database capabilities and push notifications through their API. ###Dependencies and Frameworks To interface with Parse, we use the Parse SDK.

For beta testing, distribution, and remote error logging, we use TestFlight and the TestFlight SDK. The TestFlight platform also allows us to distribute apps to both testers and EPF students quickly with minimal effort, and it provides an easy system for testers and users to submit feedback quickly.

For processing login data and integration with Google+, the Google and Google+ SDKs allow us to create sign-in buttons on the app welcome screen. This scheme allows us to take advantage of the fact that all 'Iolani students will have a Google account, reducing the need to deal with separate accounts, password management, etc. associated with a separate database structure. NOTE: The Google SDKs have several dependencies on built-in iOS frameworks. As the Google SDKs are updated, the list is subject to change at any time. The updated list of frameworks to include can be found on Google's Developer site. ###Setting up a development machine

1. If you're reading this on GitHub, it's a safe bet that you have a GitHub account. If not, register for one here.
2. Register for an Apple Developer account through the Apple Developer Portal. This isn't 100% necessary, but it will be if you want to run your app on an iOS device.
3. On the Mac you plan to use for development, download and install Xcode from the Mac App Store.
4. Once finished, open Xcode and sign in using the Apple ID that you created a developer account with.
5. Clone the repository into the location of your choosing on your hard drive. (Run git clone https://github.com/IolaniEPF/Finance from the command line in your desired folder to clone the repository over HTTPS).
6. You're finished! You should now have the tools necessary to develop, build, and run the Finance app. Read on if you need help opening the project and running it.
7. Once you've cloned the repository, navigate to its folder on your hard drive and double-click the Finance.xcodeproj container. This will launch Xcode and open the project.

###Contributing to the project If you are not a member of the IolaniEPF organization, please fork the project, make any changes you feel are necessary, and open a pull request that best describes the changes you are making and why you feel they are necessary. #Project overview ##General data structure ###User data-holding objects The Finance app uses several types of non-primitive objects in conjunction to store data about each student. These include PFUsers, Avatars,Transactions, XPTransactions, Badges, and Balances.

Each PFUser object represents a student and has its own Avatar and Balance objects to store profile and account balance information. An Avatar contains references to a student's profile and background images, while Balance objects store a student's available cash balance and experience points.

A Transaction represents a payment to or from a student and will either credit or debit their account balance accordingly. Each XPTransaction holds points received from a teacher to a student for completing a "quest" or other class assignment, with the cumulative XP total being stored as part of a student's balance.

Balances contain data fields for storing a students cash balance (determined by Transactions) and XP total (determined by XPTransactions). A Transaction contains pointers about the sender and recipient of the data, representing a debit from the sender's account and a credit to the recipient's account. Transactions also contain data about the transaction's creator, in the event that the transaction is challenged by the student, or to note who initiated a payment/deposit.

NOTE: Transactions and XPTransactions should never be modified once created. If the Parse database receives an updated transaction from the Finance app client, it will process it like a new transaction and re-add it to a student's balance. Instead, if transactions need to be modified or otherwise corrected, the object should be destroyed and an identical object with corrected values should be sent to Parse instead. This preserves the integrity of a student's balance. Work is underway to create a Cloud Code function to automatically recalculate balances if data integrity is disrupted.

Badges are used by the teacher to reward one or more students for special occasions, achievements, or innovative thinking. To introduce students to badges, each student receives a badge at the start of the course for successfully installing and setting up the app. #Cloud Code Parse provides a server-side data processing feature called Cloud Code, which allows developers to intercept object saves, verify data, and manipulate data within that Parse instance. We've elected to use Parse with Cloud Code as a database editing tool for several key reasons.

1. Parse comes with Cloud Code support built in. This means that there are no hoops or hurdles to pass in order to get it working.
2. Server-side data processing allows us to verify data before it is allowed to be saved in our database. This maintains consistency across the data and allows us to modify objects to conform to our format. manipulating requests and forces all balance calculation to be performed by Parse.
3. Cloud Code enables us to intercept objects before they are saved and run verification checks against them before completing the save. This prevents savvy app users from modifying objects by forcing Parse to process all transactions.
4. It saves bandwidth and reduces latency. With Cloud Code, the app only needs to push the transaction it wants to save up to Parse. Otherwise it would need to download the PFUser object, extract the balance, and add the appropriate value, package it back up, then push it back up to Parse. Using Cloud Code, however, the app only needs to send up the new transaction. Parse will then calculate the new balance, add it to the database, and trigger a balance refresh on the client, which can then pull down updated values.
5. It is incredibly easy to alter the data structure. Cloud Code can be redeployed in a matter of seconds, without needing to redistribute the app. This is helpful for performing maintenance, as we could deploy a Cloud Code model that rejects any saves within a certain time period, or modify it to penalize late transactions or give bonuses to early work submittal.

#Contributing We'd love for you to contribute to our project. For contributing guidelines, please read the CONTRIBUTING.md file to get started. Feel free to fork our project and send us a pull request once you've read the contributing documentation and made a change!

For information about GitHub pull requests, please read the documentation available on GitHub.