R. M. K.
ENGINEERING COLLEGE
RSM Nagar, Kavaraipettai-601206
Software Development Practices (24CS102)
Mini Project
Unit 1. AGILE SOFTWARE DEVELOPMENT , GIT
AND GITHUB
Team Name Syntax Squad
Register Number Student
111725104080 JEYANTH. S
Submitted By 111725104076 JEEVAN. R
111725104094 KATHIRAVAN
THIRUMALAI
111725104092 KARTHIGEYAN. R
Problem
Statement AGRI SHOP : FARMERS SELLING ONLINE
1. INTRODUCTION
The purpose of this document is to specify the complete functional
and non-functional requirements for the Online Organic Food
Selling Platform. This system will provide a secure, efficient, and
user-friendly e-commerce solution for vendors to sell certified organic
food products directly to consumers.
1.1 SCOPE
The system will be a multi-vendor e-commerce platform that
facilitates the following:
Vendor Management: Allowing certified organic food
producers/sellers to register, list products, and manage
inventory.
Customer Experience: Providing customers with browsing,
searching, purchasing, and order tracking capabilities.
Admin Control: Centralized management for platform
operations, user accounts, security, and payment processing.
Logistics Integration: Basic tools for managing order
fulfillment and integrating with third-party delivery services.
2. USERS AND STAKEHOLDERS
This section identifies all users who will interact with the system and
their primary roles.
User Role Description Primary Goal
General public user To easily and securely
Customer who browses, searches, purchase certified
and purchases products. organic food.
User Role Description Primary Goal
Business (farm/store)
To list, manage
registered to sell
Vendor inventory, and sell
organic products on the
products efficiently.
platform.
Personnel responsible To ensure smooth
System
for overall platform operation, security,
Administrator
maintenance and and policy
(Admin)
moderation. enforcement.
External service
To receive order
Delivery/Logistics integrated for picking
details and update
Partner up and delivering
delivery status.
orders.
3. BACKGROUND
The platform will feature several mandatory, core components for
foundational operation:
1. Secure Authentication and Authorization: Robust registration,
login, and profile management for all user types, with role-based
access control .
2. Product Catalog Engine: A dynamic database and retrieval
system capable of handling complex filtering (e.g., by organic
certification, dietary needs, vendor location, season).
3. Integrated Payment Gateway: Essential functionality to process
transactions securely, supporting multiple payment methods (e.g.,
credit/debit card, net banking, mobile wallets).
4. Order Management System (OMS): A centralized module to
track the lifecycle of every order: Placed → Confirmed → Shipped
→ Delivered → Completed/Cancelled.
5. Reporting and Analytics: Basic, automated functions to generate
reports for the Admin (e.g., sales volume, top-selling products) and
for Vendors (e.g., commission statements, inventory alerts).
4. FEATURES
These are the high-level features that the platform must provide across
its three main interfaces.
Feature Name Description User Role
Search by name, category, vendor,
Multi-Criteria
location, price range, and organic Customer
Product Search
certification status.
Multi-step checkout process with
Secure Checkout integrated, encrypted payment and Customer
saved addresses.
Vendor A process for new vendors to apply
Vendor,
Registration & and submit their organic
Admin
Verification certification for Admin review.
Tools for vendors to update stock
Inventory and
levels, SKUs, product pricing, and Vendor
Stock Management
track low stock alerts.
Automated calculation and
Commission-Based Admin,
generation of commission invoices
Billing Vendor
for vendors based on sales.
Product Review Ability for customers to rate and Customer,
and Rating System review purchased products, visible Admin
Feature Name Description User Role
to other users.
Admin and Vendors can create
Promotions and Admin,
time-bound promotions (e.g.,
Discount Engine Vendor
percentage-off, buy-one-get-one).
5. FUNCTIONALITIES
This section details the necessary functional requirements (F) broken
down by user role.
5.1 Customer Functionalities
The system shall allow a customer to register using email/social
media and maintain a profile.
The system shall allow customers to add products to a shopping
cart, which persists across sessions.
The system shall calculate shipping costs based on the
cumulative weight/volume of the order and the delivery address.
The system shall provide real-time status updates and estimated
delivery dates for placed orders.
The system shall allow customers to request a return or refund
based on the stated return policy.
5.2 Vendor Functionalities
The system shall provide a secure dashboard for vendors to
manage their store profile and bank details.
The system shall allow vendors to upload new product listings,
including images, detailed descriptions, organic certification
proof, and pricing.
The system shall generate and display sales reports, showing
total revenue, commissions, and net payout.
The system shall notify the vendor instantly upon a new order
being placed and confirmed.
The system shall allow the vendor to print shipping labels
containing all necessary customer and product information.
5.3 Administrator Functionalities
The system shall allow the Admin to approve or reject new
vendor applications after verifying certification documents.
The system shall allow the Admin to manage and set the
platform-wide commission rates.
The system shall provide a centralized view to monitor all user
accounts (Customer, Vendor) and suspend/deactivate them for
policy violations.
The system shall allow the Admin to manage content (e.g., FAQ,
Privacy Policy, banner images) without developer intervention.
The system shall monitor system performance and alert the
Admin of security breaches or server errors.
6. HARDWARE AND SOFTWARE SPECIFICATIONS
This section defines the minimum hardware and software
requirements for both the development environment and the deployed
production environment.
6.1 Production Environment (Deployment)
Component Minimum Specification Justification
Virtual Private Server Scalability to handle peak
Server (VPS) or Cloud-based loads and geographic
server (e.g., AWS, Azure, distribution.
GCP)
To handle simultaneous
user requests, database
CPU 8 Cores (Scalable)
queries, and background
jobs.
For effective caching and
RAM 32 GB DDR4 (Scalable) concurrent user session
management.
High-speed data access for
Storage 500 GB SSD (Scalable) product images and
transactional data.
Operating Linux (Ubuntu 22.04 LTS Stability, security, and cost-
System or equivalent) effectiveness.
Robust, transactional, and
Database PostgreSQL or MySQL scalable database
management.
6.2 Client-Side and Development Specifications
Component Specification Type
Chrome (latest 3 versions),
Supported
Firefox (latest 3 versions), Software (Client)
Browsers
Edge, Safari
Frontend Software
React or [Link]
Framework (Development)
Backend Django (Python) or Laravel Software
Framework (PHP) or [Link]/Express (Development)
Minimum Screen
1024 x 768 pixels Hardware (Client)
Resolution
Responsive design or dedicated
Mobile Access Software (Client)
mobile application (Phase 2)
Export to Sheets
7. RISK ANALYSIS
This section identifies potential risks to the project, their severity, and
proposed mitigation strategies.
Risk Description Probability Impact Mitigation Strategy
Implement SSL, regular
Data Security
High Catastrophic security audits
Breach
(penetration testing),
encrypt sensitive PII and
payment tokens. Use a
highly secure, PCI-
Risk Description Probability Impact Mitigation Strategy
compliant payment
gateway.
Implement load testing
before launch. Use
Content Delivery
Performance Networks (CDN) for
Medium Critical
Degradation static assets. Optimize
database queries and scale
server resources
dynamically.
Mandate annual re-
verification of organic
certification. Implement a
Vendor/Product
Medium Major three-strike policy for
Fraud
vendors selling non-
organic or counterfeit
products.
Enforce strict change
control processes. All new
feature requests must be
Scope Creep High Medium
reviewed, prioritized, and
approved against the
initial SRS.
