Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Receipt
  • Account
  • Purchase
  • Traveler
  • Trip
  • Business Administrator
  • Spending Report
  • System Administrator

Entity-Relationship Diagram

Image Added

Diagram Details

From the diagram above, system administrators handle the maintenance and logistics of the interface.  They also create and manage (to some degree) user accounts and delegate permissions to users depending on their job functions.  Travelers can use their account to scan in receipts from the purchases made during a trip.  Once a receipt is scanned in, purchase details, such as date and time, store name, expense categories, and spending total, will be parsed and recorded in the backend system.  Business administrators use their account to watch the spending of the travelers that they manage.  Spending reports are provided to satisfy this function.  Assuming a prototypical sales company, there could be 50 system administrators watching over the system, 2,000 salespeople who are the travelers of the company, and 250 business administrators who manage these salespeople.  Each traveler has a single account.  The same applies for business administrators.  Some other assumptions that are made in the diagram:

  • The numbers are based on an annual average.  Thus, in a given year, a traveler will make 60 trips on average, with 15 purchases per trip on average and exactly 1 receipt per purchase.
  • Business administrators will expect to see a monthly report of spending.  This could vary from quarterly to weekly reports, depending on the granularity that the administrator would like to achieve.
  • Business administrators could also enter their own receipts, but these could call for a separate traveler account for the administrator.