...

1. This user needs a way to look up the facilities present in their dorm, and their availability for usage.
   1. Packaging System (are desk workers present?)
   2. Laundry (are dryers/washers taken or usable?)
   3. Exercise equipment (do we have a treadmill and is someone currently using it?) 
2. This user wants to be able to access information on the progression of processes initiated by dorm facilities.
   1. Mail System (has my mail been shipped/arrived, where in the world is it?)
   2. Laundry (how much time until my clothing has dried?)
   3. Personal cooking (will my brownies ever finish baking?)
3. This user wants to be able to check the occupancy of dorm rooms.
   1. Room's semester occupancy (is this someone's address?).
   2. Room's current occupancy (is the person living here available?). 
4. The user wants to be able to conveniently request maintenance of facilities.
5. The user wants to be able to access centralized information about dorm events and maintenance. 

Task Analysis

The following are the basic functions that the application will perform.

Track - Photo taking

The user will want to easily store digital copies of their physical receipts in order to free them from physically managing them.

The user will want to still keep this method as a reliable source of proof of payment (hard-to-forge, no transcription errors, no omitted info). This feature should, for the user, give all the benefits of keeping physical receipts except without the physical hassle.

Organize - Categorization

The user will most likely have expenditures from various venues/domains. Therefore, they might want to be able to have some way of organizing the different expenditures based on the different places/locations/venues where the expenses where made. In some sense the user wants something that allows them to remember where they spent that money and organize these expenses.

The user will want to categorize and organize their expenditure as-it-happens, rather than having to do after-the-fact categorization of large batches of receipts. This is beneficial as it is much easier to categorize on the spot, as opposed to 3 weeks later where the memory of the expenditure (not to mention the receipt itself!) would have faded.

This feature needs to be powerful enough that the user will not need to post-process their expenses later to add in data that could not be added on-the-go, and yet fast enough that categorizing your expenses does not get in the way in the moments immediately after a user has made an expenditure.

Analysis - Statistics

Should the app perform basic analysis on the spending history data set, the user will want to see his/her spending patterns in terms of time, location or the various categories (tags).

It seems likely that many users will not need anything more than the most basic analytics: spending breakdowns by category or by times. By saving the data, by-default, as an Excel file, this allows more advanced users to use the spreadsheet capabilities of Excel in order to perform other analysis not pre-packaged with the app.

The most advanced users, who use high-powered financial applications, will be able to simply import the provided Excel file into their preferred financial software to manipulate and analyse. Hence users of all levels will be able to utilize our software.

Possible Features

• Tasklist: For paying off bills or keeping track of future payments. ** Allows users to keep track of future bills or payments they have to pay.
  • As the user pays it off, the amount is added to their statement.
• Debt tracking: Take a photo of a group receipt, along with the quantity you owe as an individual and the person it is owed too
  • I owe you
  • Who owes me

• User expenditure analysis: A detailed analysis of the user’s spending habits during a specific period of time
  • GPS tracking of expenditures by geographic location** Displaying on Google Maps how much the user has spent
  • Time** Graph of how much on average the user spends during the day

Change of Scope

...