-
Notifications
You must be signed in to change notification settings - Fork 1
Friends
USE CASE username US02.01
Main actors: Owner
Goal: As an owner, I want to track people I know. Adding a textual username should be enough.
Trigger: create an account
Precondition: network connection
Postcondition: successfully attach a username to an account
Basic Flow:
-
User click "sign up" in login page
-
System jump to sign up activity
-
User Enters usernamen and other info and click "okay"
-
System creates a PERSON with a username
-
return to login page
Exception
1 user don't click sign up
1.1 system stays in login page and waiting
3 user abort creating account
3.1 system jumps back to login page
USE CASE add Friend US02.02
Main actors: Owner
Goal: Add PERSON as friends and form a list
Trigger: click on "add a friend" button
Precondition: Person is in the database
Postcondition: Target person is successfully added and displayed in friend list
Basic Flow:
-
User click "view/search person" button main page
-
System jumps to search activity and returns a Prompt, asking for Name, or ID.
-
User Enters Information, and click confirm
-
system display all members are founded
-
user click person entry
-
system ask if user want to add him/her as a friends
-
user confirms
-
person is added to friendslist
Exception
2 user don't enter any of the name or ID
2.1 system keep the prompt
2.2 user click back button to return the previous activity
5 user cannot find the target person in the list
5.1 system keep the list displayed
5.2 user click back button to return the previous activity
USE CASE remove Friend US02.03
Main actors: Owner
Goal: remove a PERSON from list
Trigger: click on "delete" button
Precondition: PERSON is in your friend list
Postcondition: Target person is successfully removed from friend list
Basic Flow:
-
user click a person entry in friendlist activity
-
system pops up a option bar
-
user click "delete" button
-
System Returns a Prompt, asking to confirm
-
User confirms
-
System remove friends from friendlist and refresh screen
Exception:
3 user decides not to delete this person
3.1 system keep everything steady
3.2 user click back button to dismiss the option bar
5 user click cancel instead of confirm
5.1 deleting process abort
USE CASE view my profile US02.04
Main actors: Owner
Goal: As an owner or borrower, I will have a profile where by my contact information and city are recorded.
Trigger: click on "view my profile" button
Precondition: login-ed with an valid account
Postcondition: my contact information and city displayed
Basic Flow:
-
user click My avatar
-
system pops up option bar
-
user clicks "view my profile"
-
System pops up a new activity
-
System display my contact information and city in new activity
Exception:
5 user don't add contact information and city
5.1 display nothing
USE CASE view friends profile US02.05
Main actors: Owner
Goal: As an owner or borrower, I will be able to view the profile of anyone I know of including friends.
Trigger: click on "viewprofile" button
Precondition: PERSON is in your friend list
Postcondition: Target person's profile is successfully displayed
Basic Flow:
-
user click a person entry in friendlist activity
-
system pops up option bar
-
user click "viewprofile"
-
System pops up a new activity
-
System display my contact information and city in new activity
Exception:
5 target person don't add contact information and city
5.1 display nothing
USE CASE top traders US12.01
Main actors: Owner
Goal: View top traders of the app
Trigger: Click on "top traders" option from view
Precondition: User is in view/search person page
Postcondition: Top traders are displayed in listview
Basic Flow:
-
User click "view/search person" button main page
-
System jumps to search activity
-
User selects "top traders" under view
-
System displays top traders sorted based on number of successful (current, in-progress, and complete) trades
Exception
1 Multiple users have the same amount of trades
1.1 Randomly order users who have the same amount of trades