# Software Requirements Specification (SRS)

---

**Document Version:** 1.0  
**Project:** Student Bazaar  
**Document Type:** Software Requirements Specification (SRS)  
**Status:** Approved  
**Last Updated:** 28 June 2026  
**Author:** Nemmi Tangha

---

# Table of Contents

1. Introduction
2. Purpose
3. Intended Audience
4. Definitions and Acronyms
5. Product Overview
6. Product Perspective
7. Product Objectives
8. User Classes
9. Functional Requirements
10. Non-Functional Requirements
11. Business Rules
12. System Constraints
13. Assumptions
14. Future Enhancements

---

# 1. Introduction

This Software Requirements Specification (SRS) defines the functional and non-functional requirements for Student Bazaar. It serves as the primary reference for the design, development, testing, deployment, and maintenance of the application.

The purpose of this document is to ensure that all stakeholders have a common understanding of the system requirements before implementation begins.

---

# 2. Purpose

Student Bazaar is a web-based marketplace designed for students to buy and sell second-hand products.

The platform enables students to:

- Create product listings.
- Browse available products.
- Negotiate prices using a structured offer system.
- Communicate through an integrated messaging system.
- Arrange meet-ups after agreeing on a price.
- Manage listings through a seller dashboard.

The platform does not process payments and does not participate in financial transactions between users.

---

# 3. Intended Audience

This document is intended for:

- Software Developers
- Project Supervisors
- Testers
- Super Admin
- Future Developers
- Project Reviewers

---

# 4. Definitions and Acronyms

| Term | Description |
|------|-------------|
| Student | A registered user who can both buy and sell products. |
| Listing | A product posted for sale. |
| Offer | A proposed purchase price submitted by a buyer. |
| Counter Offer | A revised offer submitted by either party. |
| Premium User | A student with an active premium subscription. |
| Meet-up | A scheduled meeting between buyer and seller. |
| Super Admin | Administrator responsible for managing the platform. |

---

# 5. Product Overview

Student Bazaar is an online marketplace focused exclusively on helping students exchange second-hand products.

Unlike traditional e-commerce platforms, Student Bazaar facilitates communication between buyers and sellers but does not process payments or deliveries.

The platform combines marketplace functionality with structured bargaining, conversation management, advertisement integration, premium subscriptions, seller analytics, and administrative moderation.

---

# 6. Product Perspective

Student Bazaar is a standalone web application developed using the Python Flask framework following a modular architecture. The frontend is implemented using HTML5, CSS3, Bootstrap 5, and JavaScript, while MySQL is used as the relational database management system.

The system consists of multiple interconnected modules including:

- Authentication
- Marketplace
- Bargaining
- Chat
- Notifications
- Seller Dashboard
- Advertisement Management
- Premium Membership
- Reporting
- Administrative Dashboard

Each module operates independently while sharing a centralized relational database.

---

# 7. Product Objectives

The objectives of Student Bazaar are:

- Provide a student-focused marketplace.
- Encourage reuse of second-hand products.
- Simplify product discovery.
- Improve negotiation through structured offers.
- Facilitate communication between students.
- Generate revenue through advertisements and premium subscriptions.
- Provide Super Admin with effective moderation tools.

---

# 8. User Classes

## Student

A Student can:

- Register
- Login
- Create Listings
- Buy Products
- Sell Products
- Negotiate Prices
- Chat
- Schedule Meet-ups
- Save Favorites
- Report Listings
- Purchase Premium

---

## Super Admin

A Super Admin can:

- Manage Students
- Moderate Listings
- Review Reports
- Manage Advertisements
- Manage Premium Memberships
- View Analytics
- Manage Notifications
- Moderate Chats

---
### Personal Contact Information Policy

To maintain user safety and encourage communication within the platform, students are not permitted to share personal contact information (such as phone numbers, WhatsApp numbers, email addresses, Telegram usernames, or similar contact details) through the chat before an offer has been accepted.

Once an offer is accepted and a meet-up has been scheduled, students may exchange contact details if necessary.

This policy supports platform safety, moderation, and the Premium messaging model.
---

# 9. Functional Requirements

*This section will be completed in the next phase of the SRS and will contain detailed requirements for every module.*

---

# 10. Non-Functional Requirements

*This section will define system quality attributes including security, performance, usability, scalability, and maintainability.*

---

# 11. Business Rules

*This section will define the operational rules governing the platform.*

---

# 12. System Constraints

*This section will define technical and business constraints.*

---

# 13. Assumptions

*This section will document assumptions made during system design.*

---

# 14. Future Enhancements

*This section will reference features planned beyond Version 1.*