You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

MoneyManager - GR1

>> Back to MoneyManager

Team members: Stephanie Chang, Qian Long, Isabella Lubin

User Analysis

We have two main sources of user populations: college students and their parents.

College Students

Characteristics:
  • 18-23 years old
  • evenly male and female
  • proficient with technology
  • diverse ethnic backgrounds and origins (but basic proficiency with English)
  • wide variation of income level and spending capacities

Luke is a freshman at college.  His parents pay for his tuition and housing and provide him with $300 a month for food and other necessities.  Luke wants to keep track of his spending so he always has enough money for food and textbooks and knows if he has any extra money for recreational activities.

Parents

Characteristics:
  • 40-60 years old
  • evenly male and female
  • very basic experience with smartphones
  • diverse ethnic backgrounds and origins (but basic proficiency with English)
  • wide variation of income level

Vader is Luke's 42 year old father.  He wants to keep track of his son's spending so he knows where his hard-earned money is going, and if his son asks him for more money he wants to make sure that his son has been responsible with what he's already been given.

Task Analysis

1. Register and log in (Luke and Vader)

  • Create username/password (first time app users)
  • Input username/password (repeat users)

This task is the entry point to the app, used to create an account for the user so that he can modify personal data. The user is assumed to have an email address that will be used for the username, and the user will generate his own password for this account.

This task can be performed anywhere as long as the user has a mobile phone that is connected to the Internet. The registration task is only performed once, but once the user has created an account, he can log in anytime afterwards or simply remain logged in, so overall, this task will be performed very infrequently.

This task will be learned by trying it as it will be consistent with other login and registration interfaces. The user might input the wrong username and/or password, but the interface will give immediate feedback so that the user can try again. Only the user is involved in this task.

2. Submit advice or personal stories (Ash)

  • Precondition: logged in with MIT certificates
  • Post story associated with a particular location
  • Select whether or not others can ask questions about this story (If “yes”, then they are allowing others to email them)
  • Preview story 
  • Submit story
  • Delete story

The purpose of this task is for current MIT students to share their experiences with regards to a particular aspect of MIT life.

The preview feature allow the user to proofread what s/he has written before final submission to check for errors. Nonetheless, a user could still submit a story for the wrong dorm or accidentally mark that people may not ask follow-up questions, in which case they are able to delete the story and create a new one.

A potential use case would be students submitting malicious stories about other dorms. We may include an option to report stories for spam or abuse, or simply have an option to notify the webmasters/moderators to remove the story manually.

3. Ask a question (Pichu/Pikachu/Raichu)

  • Input email address and question about a particular student story
  • Preview question
  • CAPTCHA and submit question to the MIT student

Prefrosh and prospective students want to be able to communicate with current MIT students about their actual experiences. They will be able to do so by filling out a form linked to each story.  

The preview feature before final submission will allow the user to proofread for errors. On submission, an email containing the question will be sent to both the questioner and the author of the post.

  • No labels