... | ... | @@ -3,6 +3,7 @@ title: Body |
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
# Final Deliverable III
|
|
|
|
|
|
## Required Links
|
... | ... | @@ -269,4 +270,178 @@ Users can view profiles of participating farmers, including their farming practi |
|
|
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. |
|
|
\ No newline at end of file |
|
|
5. System updates the farmer’s profile with the new 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.
|
|
|
|
|
|
|
|
|
|
|
|
### 2. *Product Catalog and Search*
|
|
|
|
|
|
- *Justification:* Ensures that users can easily find and access the products they need, promoting efficient shopping and reducing frustration.
|
|
|
|
|
|
|
|
|
|
|
|
### 3. *Order Management*
|
|
|
|
|
|
- *Justification:* Streamlines the purchasing process, making it user-friendly and encouraging repeat purchases.
|
|
|
|
|
|
|
|
|
|
|
|
### 4. *Payment Processing*
|
|
|
|
|
|
- *Justification:* Provides a secure and convenient way for users to complete their transactions, which is critical for building trust in the platform.
|
|
|
|
|
|
|
|
|
|
|
|
### 5. *Farmer Profiles and Reviews*
|
|
|
|
|
|
- *Justification:* Creates transparency, allowing consumers to make informed decisions and fostering a connection between farmers and customers.
|
|
|
|
|
|
---
|
|
|
|
|
|
# UML DIAGRAM
|
|
|
|
|
|
## Use Case Model
|
|
|
|
|
|
### 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.
|
|
|
|
|
|
### 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.
|
|
|
|
|
|
### 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.
|
|
|
|
|
|
---
|
|
|
|
|
|
## Functional Properties (FPs)
|
|
|
|
|
|
### 1. *User Registration and Profiles*
|
|
|
- *Description:* Users can create accounts and set up profiles to save their preferences, order history, and payment methods. This feature allows for a personalized shopping experience.
|
|
|
|
|
|
### 2. *Product Catalog and Search*
|
|
|
- *Description:* The application will provide a comprehensive catalog of available products, sortable by categories such as fruits, vegetables, dairy, and meats. Users can also search for specific items, filtering by location, availability, and price.
|
|
|
|
|
|
### 3. *Order Management*
|
|
|
- *Description:* Users can add products to their cart, review their selections, and place orders. This includes functionalities for tracking order status and managing past orders.
|
|
|
|
|
|
### 4. *Payment Processing*
|
|
|
- *Description:* The platform will securely handle various payment methods, enabling users to pay for their purchases directly through the application.
|
|
|
|
|
|
### 5. *Farmer Profiles and Reviews*
|
|
|
- *Description:* Users can view profiles of participating farmers, including their farming practices and product offerings. They can also leave reviews and ratings based on their experiences.
|
|
|
|
|
|
---
|
|
|
|
|
|
## Detailed Use Case Scenarios
|
|
|
|
|
|
### 1. *User Registration and Login*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* Register and log in to access profile and order history.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Validate Credentials, Send Confirmation Email
|
|
|
- *Exclude:* Access Restricted Features
|
|
|
|
|
|
### 2. *View Product Catalog*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* View a catalog of available products.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Search Product, Filter by Category, Sort by Price
|
|
|
|
|
|
### 3. *Search and Filter Products*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* Search and filter products based on specific criteria.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Sort by Price, Filter by Availability
|
|
|
|
|
|
### 4. *Order Management*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* Manage the shopping cart and place orders.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Add to Cart, Calculate Total, Apply Discounts, Generate Order Confirmation
|
|
|
- *Exclude:* Edit Order
|
|
|
|
|
|
### 5. *Process Payment*
|
|
|
- *Primary Actor:* Payment Gateway
|
|
|
- *Goal:* Handle payment processing for user orders.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Validate Payment Details, Send Payment Confirmation
|
|
|
- *Exclude:* Retry Payment
|
|
|
|
|
|
### 6. *View Farmer Profiles and Reviews*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* View details about farmers and their reviews.
|
|
|
- *Relationships:*
|
|
|
- *Include:* View Farming Practices, View Product Offerings
|
|
|
|
|
|
### 7. *Leave Review*
|
|
|
- *Primary Actor:* User
|
|
|
- *Goal:* Leave reviews and ratings for farmers after purchasing products.
|
|
|
- *Relationships:*
|
|
|
- *Include:* Submit Rating, Submit Comment
|
|
|
- *Exclude:* Edit Review
|
|
|
|
|
|
---
|
|
|
|
|
|
## Detailed Use Case Relationships
|
|
|
|
|
|
### Include Relationships (<<include>>)
|
|
|
- User Registration and Login includes Validate Credentials and Send Confirmation Email.
|
|
|
- View Product Catalog includes Search Product, Filter by Category, and Sort by Price.
|
|
|
- Order Management includes Add to Cart, Calculate Total, Apply Discounts, and Generate Order Confirmation.
|
|
|
- Process Payment includes Validate Payment Details and Send Payment Confirmation.
|
|
|
- View Farmer Profiles and Reviews includes View Farming Practices and View Product Offerings.
|
|
|
- Leave Review includes Submit Rating and Submit Comment.
|
|
|
|
|
|
### Exclude Relationships (<<exclude>>)
|
|
|
- User Registration and Login excludes Access Restricted Features.
|
|
|
- Order Management excludes Edit Order.
|
|
|
- Process Payment excludes Retry Payment.
|
|
|
- Leave Review excludes Edit Review.
|
|
|
|
|
|
---
|
|
|
|
|
|
![image](uploads/80b9c18564456584d1914128364bf96f/image.png)
|
|
|
|
|
|
## Quality Attributes
|
|
|
|
|
|
### 1. *Usability*
|
|
|
- *Description:* Usability is crucial for our web application as it directly affects user satisfaction and engagement. The platform should have an intuitive interface that allows users of all ages and technological backgrounds to navigate easily. Features like clear labeling, straightforward navigation, and accessible search options will enhance the overall user experience.
|
|
|
|
|
|
### 2. *Performance*
|
|
|
- *Description:* Performance is another key quality attribute that our system must support. The application should load quickly, with minimal latency during browsing, searching, and checkout processes. We will optimize the application’s backend and frontend, ensuring efficient database queries and responsive design.
|
|
|
|
|
|
### 3. *Security*
|
|
|
- *Description:* Security is a non-negotiable quality attribute for our web application, especially given that it involves handling sensitive user data, including personal information and payment details. The system must incorporate robust security measures, such as data encryption, secure payment gateways, and regular security audits, to protect against data breaches and cyberattacks. |
|
|
\ No newline at end of file |