The Bank database is implemented and unit tested. The Bank database has three
major classes: BankDatabaseSchema, BankDatabaseManager and
BankDatabaseSimulation. BankDatabaseSchema is an abstract class and defines the
each tables from the ER relations. BankDatabaseManager creates and maintains the
database, retrieve specific tables and return a SQLiteDatabase object for a more
general-purpose query. BankDatabaseSimulation simulates a database by creating
five tables (user, bankAccount, transactionRecord, userBankAccount, purchase)
with random data for each simulation. We have three users. Each has a checking
or saving account. Each person now has 10 transactions. Since the simulation
needs to be done only once, the data stays in the private storage of the
application until the uninstallation of Plutus. Nonetheless, the option of
simulation for the new data will be provided at the menu of login page for
convenience. Or we can hide it somewhere by creating an administrator account in
Plutus.

The rest is to integrate the current implementation to Plutus, clean up a code a
bit or code walkthru, and test the Bank Database on Plutus.
Merge branch 'kevincheng99'

The Bank Database v0.1 has finished in its own workspace. Tomorrow, I will
integerate the implementation to Plutus and test it on Plutus.