Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P PureRoots_UFV
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Akshit.Marwaha
  • PureRoots_UFV
  • Wiki
  • Main_Description

Main_Description · Changes

Page history
Update Main_Description authored Dec 09, 2024 by Akshit.Marwaha's avatar Akshit.Marwaha
Show whitespace changes
Inline Side-by-side
Main_Description.md
View page @ 66effd4f
......@@ -256,49 +256,110 @@ Users can view profiles of participating farmers, including their farming practi
# UML Diagram
## Use Case Model
![image](uploads/f61b42e467b716f3f4d12a5f27681843/image.png)
# Actors
- User
- Farmer
- System
- Payment Gateway
# Use Cases
- Register/Login
- Browse Products
- Place Order
- View Farmer Profile
- Leave Review
- View Order History
# Use Case: Place Order
## Actors
- Consumer
- System
- Payment Gateway
## Preconditions
- User must be logged in.
- Cart must contain products.
## Steps
1. User selects "Proceed to Checkout."
2. System calculates total cost.
3. User enters payment details.
4. Payment Gateway validates payment.
5. System confirms the order and provides a summary.
## Postconditions
- Order is recorded.
- User receives confirmation.
### 1. *User Registration*
- *Actors:* Consumer
- *Preconditions:* User has internet access.
- *Postconditions:* User has an account and can log in.
- *Main Flow:*
1. User navigates to the sign-in/sign-up page.
2. User fills out the registration form (name, email, password).
3. User submits the form.
4. System confirms registration and directs the user to their profile.
---
![image](uploads/9953592c914dc43dc28ab034c15830e8/image.png)
# Use Case: Register/Login
## Actors
- User
## Preconditions
- The user must have access to the internet.
## Postconditions
- A user account is created, or the user is logged in to access their profile and features.
## Main Flow
1. User navigates to the registration or login page.
2. User enters required information:
- For login: email and password.
- For registration: email, password, and additional details like name.
3. The system validates the input.
4. For registration:
- The system stores user information.
- The system sends a confirmation email.
5. The user is redirected to their profile/dashboard.
---
![image](uploads/5e89c8c2b1cfd5633ffc97d174593c45/image.png)
# Use Case: Browse Products
### 2. *Product Search and Order Placement*
- *Actors:* Consumer
- *Preconditions:* User is logged in.
- *Postconditions:* User has successfully placed an order.
- *Main Flow:*
1. User navigates to the product catalog.
2. User searches for a specific product or browses categories.
3. User adds desired items to the cart.
4. User reviews the cart and proceeds to checkout.
5. User enters payment information and confirms the order.
## Actors
- User
## Preconditions
- The user is logged in to the system.
## Postconditions
- The user views available products, filtered and sorted as needed.
## Main Flow
1. User navigates to the product catalog.
2. User browses the catalog or enters keywords in the search bar.
3. User applies filters (e.g., product category, price range) and sorts products (e.g., by price or availability).
4. System displays the filtered/sorted results.
5. User selects a product for more details.
---
![image](uploads/b58b42a3512303dd31300879806c34d3/image.png)
# Use Case: Leave Review
### 3. *Farmer Profile and Review*
- *Actors:* Consumer
- *Preconditions:* User is logged in and has purchased from a farmer.
- *Postconditions:* User has submitted a review.
- *Main Flow:*
1. User navigates to the farmer’s profile page.
2. User reads information about the farmer and their practices.
3. User clicks on the review section.
4. User submits a rating and a written review.
5. System updates the farmer’s profile with the new review.
## Actors
- User
## Preconditions
- The user has completed a purchase from a farmer.
## Postconditions
- The system records the user’s review and updates the farmer’s profile.
## Main Flow
1. User navigates to the farmer's profile or order history.
2. User selects "Leave a Review."
3. User enters a star rating and optional written feedback.
4. System validates the review and adds it to the farmer’s profile.
5. Other users can view the submitted review.
---
# Justifications
### 1. *User Registration and Profiles*
- *Justification:* Enhances user engagement by personalizing the shopping experience, making it easier for users to return and reorder.
......
Clone repository
  • Home
  • Main_Description
  • Project Description
  • Sprint Meetings