Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
2 views

Software Requirements Specification

The Software Requirements Specification (SRS) outlines the Supermarket Automation Software (SAS) as a standalone system for managing sales transactions, inventory, and reporting. Key features include sales transaction processing, inventory management, price management, and sales reporting, with distinct user roles for sales clerks, managers, and employees. The system will interface with a backend database and is designed to be user-friendly, compatible with standard hardware and software platforms.

Uploaded by

luciferro9073
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

Software Requirements Specification

The Software Requirements Specification (SRS) outlines the Supermarket Automation Software (SAS) as a standalone system for managing sales transactions, inventory, and reporting. Key features include sales transaction processing, inventory management, price management, and sales reporting, with distinct user roles for sales clerks, managers, and employees. The system will interface with a backend database and is designed to be user-friendly, compatible with standard hardware and software platforms.

Uploaded by

luciferro9073
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Requirements Specification

(SRS) for Supermarket Automation


Software (SAS)

1. Overall Description

1.1 Product Perspective

SAS will be a standalone system deployed either as a desktop or web-based


application. It will interface with a backend database to store inventory data, sales
records, and generate reports. The system will be easy to use, featuring different user
interfaces for sales clerks and managers.

1.2 Product Features

 Sales Transactions & Billing: Sales clerks will input item codes and quantities. SAS will
generate a bill containing transaction details and the total payable amount.
 Inventory Management: Employees can update stock levels, and sales will automatically
adjust inventory after each transaction.
 Price Management: Managers can modify prices, which will immediately affect all future
transactions.
 Sales Reporting: Managers can generate sales statistics for any time period, detailing the
quantity sold, revenue generated, and profit from each item.

1.3 User Classes and Characteristics

Sales Clerks:

o Primary role: Handle customer transactions.


o Required features: Enter item codes and quantities, generate bills, and view basic
inventory data.
o Permissions: Can process sales transactions, but cannot modify item prices or
access sales statistics.

Managers:

o Primary role: Oversee operations, change prices, and generate reports.


o Required features: Modify item prices, view inventory levels, generate sales
statistics.
o Permissions: Full access to all system features, including price management and
reporting.

Employees:

o Primary role: Update inventory when new stock arrives.


o Required features: Add new stock to the inventory.
o Permissions: Can update inventory but cannot process sales or modify prices.

2. Functional Requirements

2.1 Sales Transaction and Billing

 FR1.1: The system shall allow sales clerks to enter item codes and quantities of items
purchased by the customer.
 FR1.2: The system shall retrieve item details (name, unit price) from the database based on
the entered item code.
 FR1.3: The system shall automatically calculate the total price for each item by multiplying
the unit price with the quantity.
 FR1.4: The system shall generate a bill (receipt) that includes:

o Transaction ID
o Item Name
o Item Code
o Quantity
o Unit Price
o Item Price (calculated as Quantity * Unit Price)
o Total Amount Payable (sum of all item prices)

 FR1.5: The system shall update the inventory by decreasing the quantity of the item sold,
ensuring that the available stock reflects the new quantity after each sale.

2.2 Inventory Management

 FR2.1: The system shall display the current inventory levels for each item, including the item
name, ID, unit price, and stock quantity.
 FR2.2: The system shall allow employees to update the inventory by entering the item code
and the quantity of new stock added.
 FR2.3: The system shall automatically adjust inventory quantities when items are sold,
reducing the stock accordingly.
 FR2.4: The system shall notify the manager if an item is low in stock, so they can reorder
inventory.

2.3 Price Management

 FR3.1: The system shall allow the manager to change the sale price of an item at any time.
 FR3.2: The system shall reflect the updated price in all future transactions for that item.
 FR3.3: The system shall log the date, user, and item code for any price changes made,
providing an audit trail.

2.4 Sales Statistics and Reporting

 FR4.1: The system shall allow the manager to generate a sales report for a specific time
period (e.g., daily, weekly, monthly).
 FR4.2: The report shall display the following sales statistics for each item:

o Total quantity sold


o Total revenue generated (calculated as Quantity sold * Unit Price)
o Profit (if cost price is available)

 FR4.3: The system shall allow the manager to generate a report showing total sales for all
items within the specified period.

3. System Interfaces

3.1 Hardware Interfaces

 The system shall be compatible with standard desktop or server hardware, requiring no
special hardware configurations.

3.2 Software Interfaces

 The system shall be compatible with popular web browsers (for web-based systems) or
operating systems (Windows, macOS, Linux for desktop versions).

3.3 Communications Interfaces

 The system shall operate using standard network connections to ensure seamless
communication between the frontend (user interface) and backend (database).

You might also like