Use Case - J-Jullaphong/b2d-ventures GitHub Wiki

Use Cases for B2D Ventures

Use Case ID: B2D_001

Use Case Name: Browse Businesses

Actor: Investor
Main Scenario:

  1. Investor navigates to the search page.
  2. System displays the search page.
  3. Investor enters search criteria or applies filters.
  4. System processes the search and displays matching businesses.
  5. Investor browses the list of businesses.

Alternative Scenario: No matching businesses found.
Alternative Flow:

  1. Investor navigates to the search page.
  2. System displays the search page.
  3. Investor enters search criteria or applies filters.
  4. System displays a message indicating no matching businesses.

Use Case ID: B2D_002

Use Case Name: View Business Details

Actor: Investor
Main Scenario:

  1. Investor browses the list of businesses.
  2. Investor selects a business of interest.
  3. System retrieves detailed information for the selected business.
  4. System displays the detailed business information.
  5. Investor reviews the business details.

Alternative Scenario: Business details unavailable.
Alternative Flow:

  1. Investor browses the list of businesses.
  2. Investor selects a business of interest.
  3. System fails to retrieve detailed information.
  4. System displays an error message.

Use Case ID: B2D_003

Use Case Name: Invest in Business

Actor: Investor
Preconditions: Investor is authenticated and viewing the business details. Admin is authenticated and has access to the admin dashboard.
Main Scenario:

  1. Investor reviews the business details.
  2. Investor decides to invest.
  3. System displays the investment form and QR code for payment.
  4. Investor enters the desired investment amount.
  5. Investor completes payment via the QR code.
  6. Investor fills in payment confirmation.
  7. System acknowledges the submission.
  8. Admin reviews the payment confirmation.
  9. Admin approves the investment.
  10. System records the investment transaction.

Alternative Scenario: Admin rejects the investment.
Alternative Flow:

  1. Investor reviews the business details.
  2. Investor decides to invest.
  3. System displays the investment form and QR code for payment.
  4. Investor enters the desired investment amount.
  5. Investor completes payment via the QR code.
  6. Investor fills in payment confirmation.
  7. System acknowledges the submission.
  8. Admin reviews the payment confirmation.
  9. Admin rejects the investment request.
  10. System notifies the investor of the rejection.

Postconditions: Investment transaction is recorded. The investment appears in the investor’s portfolio.

Use Case ID: B2D_004

Use Case Name: View Portfolio

Actor: Investor
Main Scenario:

  1. Investor navigates to the portfolio page.
  2. System displays the portfolio with a list of investments and a pie chart representation.
  3. Investor clicks on a specific investment to view detailed information about the business.
  4. System displays the business details page.

Alternative Scenario: No current investments.
Alternative Flow:

  1. Investor navigates to the portfolio page.
  2. System displays a message indicating no current investments.

Use Case ID: B2D_005

Use Case Name: Register as Investor

Actor: Investor
Main Scenario:

  1. Investor navigates to the signup page.
  2. System displays the signup page and form.
  3. Investor completes the form, providing first name, last name, email, phone number, password.
  4. Investor submits the form.
  5. System confirms the successful submission of the signup request.

Alternative Scenario: Investor submits an unsuccessful signup request.
Alternative Flow:

  1. Investor navigates to the signup page.
  2. System displays the signup page and form.
  3. Investor enters incorrect or incomplete information.
  4. System notifies the investor of the errors and prevents form submission.

Use Case ID: B2D_006

Use Case Name: Investor or Business Owner Login

Actor: Investor/Business Owner
Main Scenario:

  1. Investor or Business Owner navigates to the login page.
  2. System displays the login page and form.
  3. Investor or Business Owner enters their email and password.
  4. System validates the credentials.
  5. System redirects the user to the home page upon successful validation.

Alternative Scenario: Failed login.
Alternative Flow:

  1. Investor or Business Owner navigates to the login page.
  2. System displays the login page and form.
  3. Investor or Business Owner enters incorrect credentials.
  4. System validates the credentials.
  5. System notifies the user of the incorrect information.

Use Case ID: B2D_007

Use Case Name: Register as Business

Actor: Business Owner
Main Scenario:

  1. Business Owner navigates to the signup page.
  2. System displays the signup page and form.
  3. Business Owner completes the form, providing required details such as business name, email, phone number, password, business registration certificate, tax identification number, proof of address, financial statements, ownership documents, director identification, licenses, permits, and bank account details.
  4. Business Owner submits the form.
  5. System confirms the successful submission of the signup request.

Alternative Scenario: Business Owner submits an unsuccessful signup request.
Alternative Flow:

  1. Business Owner navigates to the signup page.
  2. System displays the signup page and form.
  3. Business Owner enters incorrect or incomplete information.
  4. Business Owner submits the form.
  5. System notifies the Business Owner of the errors and prevents form submission.

Use Case ID: B2D_008

Use Case Name: Add Business Details

Actor: Business Owner
Main Scenario:

  1. Business Owner navigates to the create business details page.
  2. System displays the form for entering comprehensive business information.
  3. Business Owner completes the form with business name, description, category, images, videos, pitch, and team members.
  4. Business Owner submits the form.
  5. System stores and publishes the business details on the platform.

Use Case ID: B2D_009

Use Case Name: Create Fundraising

Actor: Business Owner
Main Scenario:

  1. Business Owner navigates to the create fundraising page.
  2. System displays a form for specifying the fundraising goal, duration, and investment terms.
  3. Business Owner completes the form.
  4. Business Owner submits the fundraising campaign.
  5. Admin reviews the fundraising campaign.
  6. Admin approves the fundraising campaign.

Alternative Scenario: Business Owner submits an unsuccessful fundraising.
Alternative Flow:

  1. Business Owner navigates to the create fundraising page.
  2. System displays a form for specifying the fundraising goal, duration, and investment terms.
  3. Business Owner enters incorrect or incomplete information.
  4. Business Owner submits the fundraising campaign.
  5. System notifies the Business Owner of the errors and prevents form submission.

Use Case ID: B2D_010

Use Case Name: Track Funding Progress

Actor: Business Owner
Main Scenario:

  1. Business Owner navigates to the funding dashboard.
  2. System displays a summary of funding details, including investor names and amounts.
  3. Business Owner clicks on a specific investment to view detailed information.
  4. System displays detailed investment information.

Use Case ID: B2D_011

Use Case Name: Admin Approval or Rejection of Signup Request

Actor: Admin
Main Scenario:

  1. Admin navigates to the admin dashboard.
  2. Admin selects the investor/business registration fields in the dashboard.
  3. System displays the dashboard with a list of pending signup requests.
  4. Admin reviews pending requests and associated documents.
  5. Admin approves or rejects the signup request.

Use Case ID: B2D_012

Use Case Name: Admin Approval or Rejection of Investment Request

Actor: Admin
Main Scenario:

  1. Admin navigates to the admin dashboard.
  2. Admin selects the investment field in the dashboard.
  3. System displays the dashboard with a list of pending investment requests.
  4. Admin reviews pending requests and associated documents.
  5. Admin approves or rejects the investment request.

Use Case ID: B2D_013

Use Case Name: Admin Approval or Rejection of Fundraising

Actor: Admin
Main Scenario:

  1. Admin navigates to the admin dashboard.
  2. Admin selects the fundraising field in the dashboard.
  3. System displays the dashboard with a list of pending fundraising requests.
  4. Admin reviews pending requests.
  5. Admin approves or rejects the fundraising request.