-
Notifications
You must be signed in to change notification settings - Fork 4
Backlog
Jarrod Los edited this page Nov 29, 2019
·
8 revisions
Project Breakdown: The design provided by the customer has been broken down into four epics and there corresponding user stories in the chronological order that they will be followed:
NOTE: ALL USER STORIES HAVE BEEN COMPLETED AS SEEN IN USER STORIES PAGE
User Story #1A
- Design a basic UI that displays the user's input as a list
- Rationale: Fundamental starting block to provide with a basic interface which will be customized as requested.
- Story Point: 3
- Risk: High Risk
User Story #1B
- Add a mood to the user post
- Add a date and time stamp to each post
- Add a location input which is optional
- Display list in reverse chronological order
- Rationale: Start focusing on easy deliverable's to customer to maintain constant feedback.
- Story Point: 1.5
- Risk: Medium Risk
User Story #1C
- Implement FireStore database to the list
- Have sub categories for the properties of Mood and User
- Implement deletion from both list and database
- Rationale: Further customize the list and set the base for expanding to multiple users.
- Story Point: 2
- Risk: High Risk
User Story #2A
- Link project to FireBase
- Create U.I. for login/ User creation
- Rationale: Starting point for data base usage where a user a user will be created and saved on the database.
- Story Point: 1.5
- Risk: Medium Risk
User Story #2B
- Work on user authentication on FireBase side to allow the project to be taken off "public" mode
- Work on user authentication on App side
- Conditionals to creating a new user / incorrect login
- Security rules on Firebse
- Rationale: Starting point for data base usage where a user a user will be created and saved on the database.
- Story Point: 1.5
- Risk: Medium Risk
User Story #3A
- Create interface to display map
- Pass the input location to the map to display coordinate
- Rationale: Start building on location functionality leading up to multiple users
- Story Point: 4
- Risk: High Risk
User Story #3B
- Associate the current user mood to a location and reflect this on the map
- Rationale: Adding the tracking of mood by location as another simple deliverable
- Story Point: 1.5
- Risk: Low Risk
User Story #4A
- Create a custom username which may access there list of moods
- Tie this username to there corresponding data saved in FireStore
- Rationale: Create the notion of a unique "User" with a username tied to the corresponding database from which will be able to later find other users. Critical to the usage of the app on multiple devices.
- Story Point: 2.5
- Risk: High Risk
User Story #4B
- Create a new data set that is stored in the database that has record of all unique users and there corresponding posts.
- Modify the existing interface to allow search for a unique user in this new set.
- Create a fragment to send a "request" to said user (Just the layout, no actual implementation )
- Rationale: Allow search for other users and a fragment that will later allow the "user" to request and receive access
- Story Point: 2
- Risk: Medium Risk
User Story #4C
- Implement a function to send information between users with the ID
- From this, implement the fragment to both "Send a Request" and "Receive a Request"
- From this request, send the information to access their database
- Rationale: Once users may find each other, they may share add each other to eventually see their posts.
- Story Point: 3.5
- Risk: High Risk
User Story #4D
- Update users "Feed" with those the user follows (List in database containing users followed and a link to there own personal posts)
- Rationale: Once a link between users has been established, they may pass posts between each other
- Story Point: 3
- Risk: Medium Risk
Epic #5: A user will be able to sort other users posts as well as see there mood and location via the map
User Story #5A
- Using the interface for the location services, implement "followed" users posts
- Include custom username above each post for the people "followed"
- Rationale: Final steps towards fulfilling the users requests, just implementing the already created infrastructure to take in more data.
- Story Point: 3
- Risk: Medium Risk
User Story #5B
- Dealing with clustering of posts on map
- Any additional features as requested
- Rationale: Anticipating changes or new requests, better designs to the app.
- Story Point: xx
- Risk: Low Risk
Scarntech