Heavy Lender/User Persona

John Doe is a regular MIT student who is pretty nitpicky about his money and likes bills to be split equally. He really doesn’t mind paying for others, but gets annoyed when multiple people borrow money and then forget to pay it back. He finds that he can manually keep track of how much people owe him and how much he owes others, but finds that it’s simply too cumbersome and slow to be effective when there’s more than four people. Since John would use this app extensively as he likes to keep a detailed record about his money, he would like a simple user-interface that allows him to input records super efficiently. 

Lessons learned from Heavy User Persona

Current Solution for Debt Tracking

• Pencil/Paper - really low-level way of keep tracking, works for only a few people
• iPhone - uses a money managing app meant for one person and attempts to use it for multiple people 

Requirements of Desired Solution

• Super simple user-interface - Should not take more than a few seconds to input a debt or payment of debt
• Approvals - When another person places a debt on Shawn, he wants to be able to approve it so that people do not make up claims for money.

Task Analysis
The PennyPincher application will attempt to perform three main tasks

• Adding people (people who owe you money or you owe money to)
• Add transaction (Users are allowed to say that another person owes them X amount of dollars)
• View all transactions (like a credit-card bill)

Adding People

Goal: Allow users to register a two-way connection with people that owe them money. 

Subtasks: 

• Searching for user by username
• Adding user by username
• Removing user

Preconditions:

• User must have an account with PennyPincher

Postconditions:

• User establishes a connection with another user and can now add transactions
  How often used?  

• Depending on the user, but should be used fairly infrequently as users usually only incur debt with friends

Adding/Approve a transaction

Goal: Allow users to input an amount that a particular person owes them 

Subtasks: 

• Set the amount that another user owes them
• Input the name of the transaction (what it was for) 
• Send the transaction
• Approve transaction 
  Preconditions:
• The two exchanging parties must have an established connection.

Postconditions: 

• A transaction will be sent from one party to another.
• Approval message will be displayed to the person who owes money
• Upon approval, net balance between the two parties will be updated
  How often used? 
• This task will be performed very frequently as its the core of PennyPincher