Scribd
Upload
5 views6 pages

Oose2 Me

The document outlines the Software Requirements Specification (SRS) for a Supermarket Billing System aimed at automating billing and inventory management. It details the system's purpose, scope, intended audience, and specific functional and non-functional requirements, including user roles, product management, and security measures. Additionally, it describes the overall product perspective, operating environment, and external interface requirements.

Uploaded by

mohit.121322
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views6 pages

Oose2 Me

The document outlines the Software Requirements Specification (SRS) for a Supermarket Billing System aimed at automating billing and inventory management. It details the system's purpose, scope, intended audience, and specific functional and non-functional requirements, including user roles, product management, and security measures. Additionally, it describes the overall product perspective, operating environment, and external interface requirements.

Uploaded by

mohit.121322
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Experiment – 5

Aim: To write the SRS document for Supermarket Billing System


Introduction
1.1 Purpose

The purpose of this document is to outline the software requirements for the development
of a Supermarket Billing System. This system will automate the process of billing and
inventory management in a supermarket. It will help cashiers, managers, and customers by
simplifying the billing process and maintaining accurate records of transactions.

1.2 Scope

The Supermarket Billing System will be a desktop/web application used in supermarkets to:

• Generate bills for purchased items.

• Maintain inventory records.

• Track sales and generate reports.

• Manage user roles (Admin, Cashier).

• Print invoices and store them for records.

1.3 Intended Audience

• Developers: For implementation.

• Testers: To create test plans.

• Clients: To understand system functionalities.

• Instructors/Evaluators: To evaluate the project.

1.4 Definitions, Acronyms, and Abbreviations

• GUI: Graphical User Interface

• DBMS: Database Management System

• Admin: System manager with full access

• POS: Point of Sale

2. Overall Description
2.1 Product Perspective
The Supermarket Billing System is a standalone product that automates the billing process
and integrates with a local or cloud-based database for storing product and transaction
details.

2.2 Product Functions

• Product search by barcode/name.

• Automatic calculation of bill with discounts and taxes.

• Real-time inventory updates.

• User login system (Admin/Cashier).

• Report generation (daily, monthly).

• Backup and restore options.

2.3 User Classes and Characteristics

• Admin: Full control over the system, can add/edit/remove products, view reports,
and manage users.

• Cashier: Can process sales, generate bills, and print receipts.

• Customer: Interacts indirectly; receives invoices and service.

2.4 Operating Environment

• Platform: Windows/Linux/Mac (desktop) or Web browser

• Database: MySQL / PostgreSQL

• Language: Java / C# / Python / PHP / React (as per implementation choice)

2.5 Design and Implementation Constraints

• Must support at least 1000 products in the database.

• Should function offline for at least basic billing.

• Backup and restore must not require admin privileges outside the app.

2.6 Assumptions and Dependencies

• Internet may not be available all the time (for cloud backup).

• Barcode scanner may or may not be integrated.


3. Specific Requirements
3.1 Functional Requirements

3.1.1 User Login

• Admin and Cashier must log in to access the system.

• Password should be encrypted in the database.

3.1.2 Product Management (Admin)

• Add/Edit/Delete products.

• View inventory levels.

• Set discounts and tax rates.

3.1.3 Billing (Cashier)

• Scan product barcode or search manually.

• Auto-calculate total amount.

• Print receipt with product details, taxes, and final amount.

• Update inventory after billing.

3.1.4 Reports (Admin)

• View sales reports daily, weekly, and monthly.

• Export reports as PDF or CSV.

3.1.5 Backup and Restore

• Admin can back up the database and restore it when needed.

3.2 Non-Functional Requirements

3.2.1 Performance Requirements

• Should handle at least 20 concurrent billing sessions (web version).

• Generate bills within 1 second.

3.2.2 Security Requirements

• Password encryption.

• Role-based access control.


• Secure database access.

3.2.3 Usability

• Simple and intuitive GUI.

• Easy product search and billing.

3.2.4 Reliability

• System should be 99% available during working hours.

3.2.5 Maintainability

• Code must follow naming conventions and be modular.

4. External Interface Requirements


4.1 User Interfaces

• Login page.

• Dashboard (Admin/Cashier).

• Product management screen.

• Billing screen with cart view.

• Report viewer.

• Receipt print preview.

4.2 Hardware Interfaces

• Barcode scanner (if integrated).

• Printer for receipts.

4.3 Software Interfaces

• Database (MySQL/PostgreSQL).

• Printer drivers.

• Operating system APIs.


Experiment – 7
Aim: To design the class diagram for supermarket billing system.
Experiment – 6
Aim: To design the sequence diagram for supermarket billing system.

You might also like