Skip to content

Architectures

Thinh Nguyen edited this page Jan 26, 2020 · 1 revision

Login/Sign Up

  • By Phone Number
    1. Direct to the login page when app load
      • Will implement session to keep client login.
    2. Client need to insert their phone number to the field
      • An verification code will be sent to the client's email they used to register.
    3. Direct to authentication code page to verify the verification code in the step above.
      • Successful allow grant access to the homepage(dashboard)
      • Else will keep asking for another verification code
    4. In case if client's number does not exist in the system
      • Direct client to Signup page
  • Case Scenario
    1. If the user already has an account -> Will ask for verification.
    2. If the user does not has an account yet -> Will redirect to sign up page. More info below

Signup/registered

  1. Will direct to sign up page
    • Input fields include: [Email, Fullname, Date of birth, Major??]
  2. A verification code will send to the client email address they used in step 1
  3. Redirect the client to authentication code to verify and give the client access to the homepage(dashboard)
    • Invalid code will not able to get in

Client Type

  • When client register an account -> (userID, and hostID) will be generated for his or her
    • userID: Unique ID for client
    • hostID: ID for client to host events. * Only the person has hostID same as eventID will able to adjust the event
  • Client allows to attend or join any groups or events. But not able to edit the content.

Event/Session

  • All clients have the ability to create events or groups.
  • Only the host (client who created the event or group) able to change the content of the event.
    • Second host: This person will has the ability to adjust the contents of the event, but not able to delete the event or delete attendee out of the event
Clone this wiki locally