...
Characteristics
Parent characteristics:*
- Ages: any parent age
- Education: Literate
- Language: English
- Technological experience: Low to Medium - owns a computer and/or smartphone and can use websites on either
- Motivation: wants to be informed about children’s safety and/or activities
- Attitude: High - safety of children is something that is a #1 priority
Child characteristics:*
- Ages: 11 (whenever they are old enough for a smartphone) through 22 (college-aged), with application focus on high schoolers
- Education: Literate
- Language: English
- Technological experience: High - owns and can easily use a smartphone
- Motivation: Have parents be satisfied with information about their activities
- Attitude: Varies, probably Medium - may not consider parents’ motivation important or have high desire to use application in depth
...
Set Check-in Time and Create New Form:
Set up a future or instantaneous check-in with possible reminders and custom questions.
User class: parent
Precondition:*
- Has a profile set up
- Is a parent user and is linked to a child user
Subtasks:*
- Set a check-in time
- Choose which questions they want the child to answer:** can use or edit previous form created
- can choose questions from a sample list
- can create their own questions
Frequency of use:*
- Once for every time that they want the child to check in (efficiency is important)
Check in and complete form:
Respond to a check-in request from a parent.
User class: child
Precondition:*
- Parent has created a form and set a check in time
- The check in time is now (Optional: Child received a warning that the check in time is now)
Subtasks:*
- Open app
- See option to just send location at top of page.
- Below it see form with answers filled in from last time, if within 12 hours of last check-in (otherwise blank)
- Change appropriate answers
- Submit the form (will send answers as well as location to parent)
Frequency of use:*
- Once for every time the parent set a check-in
Send help message to parent:
A child might feel uncomfortable in their situation and want the parent to take some action to help them (e.g. to call them for an excuse to leave a party, to pick them up).
User class: child
Precondition:*
- None - any time child is in the app
Subtasks:*
- Press button to send help message
- Choose type of help
- Enter optional extra information (child is alone, with x number of friends, buzzed, etc.)
Frequency of use:*
- Probably minimal - only used in uncomfortable situations (otherwise, child might as well call parent directly)
View check-in:
User class: parent
Precondition:*
- Child has checked in at a specific time
Subtasks:*
- Choose check-in from list (see task “View check-in history”) or see most recent one
Frequency of use:*
- In theory once per check-in
View check-in history:
User class: parent
Precondition:*
- Child has checked in at least once previously
Subtasks:*
- View one page at a time of prior check-ins
Frequency of use:*
- Probably minimal - more likely to view most recent check-in