Release Planning - CMPUT301F16T01/Carrier GitHub Wiki

Project Timeline Part 4

Plan: Address a certain number of use cases every week.

Contingency: We have reading week and a week before project part five as a buffer if we are behind in completing use cases.

OCT 09 to OCT 15 week 1

Meeting: Oct 12
Deadlines: PROJECT PART 2 (OCT 14, Fri)

OCT 16 to OCT 22 week 2

Meeting: Oct 19, develop UML diagram
Complete 3 use cases (for Project Part 4)
Finish XML based on storyboard and mock-ups
Create a working login activity
Address User Profile use cases

OCT 23 to OCT 29 week 3

Meeting: Oct 26
Deadlines: PROJECT PART 3 (OCT 24, Mon)
User Profile (Kieter + Mike)
Search Activity (Sarah)
- By Geolocation (bring up map dialogue?)
- By Keyword (enter in search box) *View request as Driver (Mandy)
We all have a large number of midterms this week, so we've all agreed to work through the weekend.

OCT 30 to NOV 05 week 4

Meeting: Nov 02
Complete 5 use cases (for Project Part 4)

NOV 06 to NOV 12 week 5

READING WEEK
Meeting: Nov 09
Complete 5 use cases (for Project Part 4)
Contingency: This is a "catch up and get ahead" week, where we will address missed use cases and try to do future ones if we have run out of time

Project Timeline Part 5

UPDATED AS OF NOVEMBER 13TH 2016

NOV 13 to NOV 19 week 6

Meeting: Nov 16
Deadlines: PROJECT PART 4 (NOV 14, Mon)
Make sure the updating of the screen shows up (listeners and what not)
Make sure tests are up to date
Complete 15 use cases, bolded ones have been completed.
- Requests
  - US 01.05.01 - As a rider, I want to be able to phone or email the driver who accepted a request.
  - US 01.07.01 - As a rider, I want to confirm the completion of a request and enable payment.
  - US 01.08.01 - As a rider, I want to confirm a driver's acceptance. This allows us to choose from a list of acceptances if more than 1 driver accepts simultaneously.
- Searching
  - US 04.01.01 - As a driver, I want to browse and search for open requests by geo-location.
- Offline behavior
  - US 08.01.01 - As an driver, I want to see requests that I already accepted while offline.
  - US 08.02.01 - As a rider, I want to see requests that I have made while offline.
  - US 08.03.01 - As a rider, I want to make requests that will be sent once I get connectivity again.
  - US 08.04.01 - As a driver, I want to accept requests that will be sent once I get connectivity again.
- Accepting (Needs more testing)
  - US 05.01.01 - As a driver, I want to accept a request I agree with and accept that offered payment upon completion.
  - US 05.03.01 - As a driver, I want to see if my acceptance was confirmed.
  - US 05.04.01 - As a driver, I want to be notified if my ride offer was accepted
- Surprise (Requirements cluster 2)
  - US 1.09.01 - As a rider, I should see a description of the driver's vehicle.
  - US 03.04.01 - As a driver, in my profile I can provide details about the vehicle I drive.
  - US 04.03.01 - As a driver, I should be able filter request searches by price per KM and price.
  - US 04.04.01 - As a driver, I should be able to see the addresses of the requests.
  - US 04.05.01 - As a driver, I should be able to search by address or nearby an address.

NOV 20 to NOV 26 week 7

Meeting: Nov 23
All use cases should be complete or caught up on immediately.
This week is for refactoring and polishing our code.
Java doc and GH pages
Make sure all tests pass
get friends to try it out and attempt to break it
We will also be preparing the demo for our app.

NOV 27 to DEC 03 week 8

Meeting: no meeting
Deadlines: PROJECT PART 5 (NOV 28, Mon)

Project Timeline Part 6

DEC 04 to DEC 10 Week 9

Meeting: Dec 07
Complete the extra user stories that were added but not required.
Work to be done:
- US 1.10.01 As a rider, I want to see some summary rating of the drivers who accepted my offers.
- US 1.11.01 As a rider, I want to rate a driver for his/her service (1-5).
- Address Estimate fare arrow transparencies when it is not possible to click
- Address Sort requests by status
- Address Update the price when you change the location
- Attempt to refactor Requests to implement the proxy pattern.

DEC 11 to DEC 17 Week 10

Meeting: Dec 14
Update UML to reflect changes to the code.
Start addresses enhancements and bugs we have labelled won't fix.
Aim to get one enhancement done each a week.
To be done this week:
- Address Create StatusIconView class
- Address Refactor User Profile Activity
- Address Code duplication in array adapter and view request for status image
- Address Make notifications link to the request it is about
- Address Linking data instead of nesting it in Elastic Search

DEC 18 to DEC 24 Week 11

Meeting: Dec 21
Update UML to reflect the modified and added code.
Continue completing enhancements.
To be done this week:
- Address Status for make request
- Address Adding button feedback for call
- Address Make username bigger to click
- Address Allow user to specify geo-radius for searching

DEC 25 to DEC 31 Week 12

Meeting: Dec 28
Update UML
To be done:
- Make sure the app looks nice when the phone is rotated.
- Address Flush cached files when user logs out online
- Add other payment methods (PayPal, Credit card, etc.)
- User can change start and end points

Additional Information

Midterm Schedules for Team Members

Week	Mandy	Bennett	Kieter	Mike	Sarah
1	0	1	1	0	0
2	2	0	0	2	0
3	1	2	2	2	4
4	1	0	1	0	1
5	0	0	0	0	0
6	0	0	0	0	0
7	0	0	0	0	0
8	0	0	0	0	0