moziliar/cs2102_2021_s1_team49

cs2102_2021_s1_team49's Issues

Create API

After settling UI Mockup, let's first settle on our API with either Swagger, gRPC or GraphQL for FE/BE communication. Then, the FE and BE team can do API-centric development.

Create Dashboard for PCS admin

The following functionalities are required:

• Set a base daily price for each category of pet
• Update available pet categories
• Approve/Reject application for Care Taker
• See ongoing transaction and manage the transfer of pet from pet owner to care taker

Create Home Page

Create home page which includes

• static information about the service
• Sign up/Sign in as modal or link to seperate page)

Create Care Taker Page

Profile page:

• See/edit user information(name, picture, rating, number of pet days, category of pets that can be taken care of, etc.)
• Link to past transactions
• Ongoing transactions
• Apply for leave and add availability for a part-timer
• Set(part-timer only) and View the current daily rate for different category of pets

Basic Backend Server

Once the API issue #2 is done, we shall start implementing the backend server.

We shall divide the work on the backend server. The first blocker will be the router setup, which might require a solo work here with help from reviews.

The target to hit within MVP is a fully functional MVC backend server running on Heroku

The following can be largely done in parallel

• Router (in gRPC, it'd be adding services interfaces to the server)
• User (might block the following two, set up a basic interface first)
• Transaction/Bidding
• Pet

We will be using gRPC. So after router setup, we should just implement the interfaces generated by the proto files, and use the objects as is. A translation to persistent object is needed too.

Create Pet Owner Pages

• Search Page(with filter) to find available Care Taker
• Profile page to see user information, saved pets, etc.(include functionality to add pets as modal/seperate link)
• History Page to review past transactions and give rating

UI Mockup

Let's decide on the frontend UI before all. To be done concurrently with API design.

• Basic UI layout
• Theme
• Link components to API and update API if necessary

Create DB layer

Create DB layer logic and a query store

• Setup in code
• Discuss queries needed

Translate User Stories to Requirements

Please do translate all the user stories we have so far or upcoming ones into the Kanban board, so that we could assign issues to facilitate the overall development.

Link

Why is the the link not working? Is "http://backend-2012.herokuapp.com/" correct (this page is according to video)?