cmput301w20t03 / ontime Goto Github PK

Rationale: It is important for the rider to check the current request and check the driver details.

Estimated size in story points: 9/10

Risk: High; It is a crucial function of this app.

Rationale: We need to revise our UML as the progress is moving forward.

Estimated size in story points: 4/10

Risk: Low; It is important for an app to have a more complete UML diagram.

Rationale: We need to make the main activity up-to-date in order to implement all the basic functions of the app.

Estimated size in story points: 10/10

Risk: High; It is crucial to have the main activity implement correctly; it requires to access the firebase and associate with other activities, etc.

Rationale: Finished the SignUp Activity and connect it to the database.

Estimated size in story points: 8/10

Risk: High; It is crucial to have SignUp activity for users to register.

Rationale: a function for riders to see the locations of all available drivers nearby.

Estimated size in story points: 9/10

Risk: High; It is important to show the correct drivers near the rider and provides an approximated fees.

Rationale: We need to provide unit tests for all the existing classes to make sure everything works properly.
Estimated size in story points: 8/10

Risk: Medium; It is important for an app to have complete test.

Rationale: Rider can scan the driver's QR code and proceed with the payment.

Estimated size in story points: 9/10

Risk: High; It is a crucial interaction between riders and drivers in this app.

Rationale: Finished the Login Activity and connect it to the database.

Estimated size in story points: 7/10

Risk: High; It is crucial to have login activity for registered users.

Rationale: provide initial object-oriented analysis using a UML class diagram.

Estimated size in story points: 6/10

Risk: Medium; It is important to do the OOA analysis before we design the app; we may improve it throughout the project.

Rationale: We need to make the mockups for the user interface and storyboard sequences

Estimated size in story points: 4/10

Risk: low; It is important but low risk to make the user interface mockups before we design the app.

Rationale: It is important for the rider to cancel a request if he/she changed the mind.

Estimated size in story points: 9/10

Risk: High; It is high risk if the riders can't cancel the request. It will be problematic.

Rationale: a function for drivers to see the locations of all available riders nearby.

Estimated size in story points: 9/10

Risk: High; It is important to show the correct riders near the drivers so that the drivers can pick them up.

Rationale: Rider can see their requests are accepted and see drivers' info like name, rating, etc.

Estimated size in story points: 9/10

Risk: High; It is important for drivers to know the request is accepted and connect to the driver.

Rationale: As a rider, I want to request rides between two locations after I log in.

Estimated size in story points: 8/10

Risk: High. it is one of the basic functions of this app.

Rationale: The app needs an appropriate icon.

Estimated size in story points: 4/10

Risk: Low; It is important but low risk to have an icon.

Rationale: a function for drivers to accept the ideal request and change its status to unavailable.

Estimated size in story points: 9/10

Risk: High; It is important for drivers to accept the request and find the riders.

Rationale: We should implement a request activity that can send and receive requests between rider and user.

Estimated size in story points: 8/10

Risk: Medium; It is important to have the request function in a taxi-hailing app.

Rationale: It is important for users to check their balance and make the transfer.

Estimated size in story points: 9/10

Risk: High; It is an important function of this app.

Rationale: We should determine UI/Layout design according to the interface mockup.

Estimated size in story points: 7/10

Risk: Medium; It is important for the app to have a neat, concise, easy-to-use interface.

Rationale: a function that the driver should be able to see all the nearby requests according to the distance calculated and choose the one they'd like to accept.

Estimated size in story points: 8/10

Risk: Medium; It is important for the drivers to pick their customers; one of the main functions of our app.

Rationale: It is important for the driver to check the available requests sent by the rider.

Estimated size in story points: 9/10

Risk: High; It is a crucial function of this app.

Rationale: we should determine all the user cases with quick links, story level and risk level.

Estimated size in story points: 6/10

Risk: Medium; It is important to know all the requirements and specifications; they may adjust in the future.

Form the initial partial user stories into a backlog of the product's requirements. For each user story, complete its rationale, its estimated size in story points, and risk level (i.e., low, medium, or high).

Rationale: We should implement driver and rider classes so that it can store their info.

Estimated size in story points: 8/10

Risk: Medium; It is important to keep track of the names, emails, and other identification data of the users.

Rationale:

1. We need to define any special terminology in the application domain (i.e., not programming terms).
2. Provide a list of useful informational references or links to related or competitive products.

Estimated size in story points: 4/10

Risk: low; It is important but low risk to provide all the necessary information.

Rationale: It is important for the rider to check the current request and check the driver details.

Estimated size in story points: 7/10

Risk: Medium; It is important to have the offline behaviours but not high risk.

Rationale: a function for users to check & edit their own information.

Estimated size in story points: 8/10

Risk: High; It is important to connect to firebase and do the updates as users want.

Rationale: After scanning the QR code, the money is transferred from rider to driver.

Estimated size in story points: 9/10

Risk: High; It is a crucial interaction between riders and drivers in this app.