Assignment – 4

NAME:SANSKAR AWASTHI
ENROLLMENT NO.S24BCAU0138

Questions:

1. Consider the scenario of a supermarket like Reliance Fresh, etc. that sells groceries (like flour, pulses, rice,
etc), milk and milk products, apparels, etc. all under one roof.

The supermarket (owner) wants a software that can render different functionalities like:

a. Record keeping for the items through its serial number, unit price, quantity, etc.

b. From the software it should be possible to do the following types of analysis, based on which the
supermarket should give some promotional offers from time to time:

1) Which product is the highest selling?

2) Which customer is the most frequent visitor?

3) Which customer buys which item the most? etc.

c. A customer mobile app where he/ she can view promotional offers, order online (if needed), etc. d.

Any other functionality that you can think of.

Design an SRS for the software of the supermarket. For the purpose of reference (just a
recommendation), you can use the following template: https://shorturl.at/bmHU4 2. Now consider the above
for your respective projects. Design an SRS for the same.
 Q1. SRS for Supermarket Software System

1. Introduction
1.1 Purpose:

This document specifies the Software Requirement Specification (SRS) for the Supermarket Management
System (SMS) for a retail chain like Reliance Fresh. The system will offer functionalities such as
inventory management, customer analytics, promotional features, and a mobile app for customers.

1.2 Scope:

• Maintain item records with serial number, quantity, unit price, etc.
• Provide analytical tools to determine product trends and customer behavior.
• Mobile app support for viewing offers and online ordering.
• Administrative control panel.

1.3 Intended Audience:

• Developers
• Stakeholders
• Store Managers
• System Analysts

1.4 Definitions:

• SMS: Supermarket Management System

• CRUD: Create, Read, Update, Delete

2. Overall Description
2.1 Product Perspective:

The product is an independent software system deployable in supermarkets. It integrates with POS
systems and supports both web and mobile environments.

2.2 Product Functions:

• Inventory operations (CRUD)

• Customer data tracking
• Analytics for promotions
• Customer mobile interface
• Staff/Admin login

2.3 User Classes and Characteristics:

User Class Description

Admin Full control over inventory and reports

Staff Update stock and manage sales

Customer View and purchase items via app

 User Class Description

Analyst Monitor product and customer trends

2.4 Operating Environment:

• Backend: Cloud/Local Server

• Frontend: Web and Mobile (iOS & Android)
• Database: SQL or NoSQL

3. Functional Requirements

1. Inventory Management
2. Customer Purchase Tracking
3. Analytics Dashboard
4. Promotional Offer System
5. Online Ordering via Mobile App

4. Non-Functional Requirements

• Performance: Response time < 2 seconds

• Security: Role-based access, secure payments
• Availability: 99.9% uptime
• Usability: Easy-to-use UI for staff and customers

5. Use Case Diagram

+------------------+
| Admin |
+------------------+
/ \
[Manage Inventory] [Generate Reports]

+------------------+
| Staff |
+------------------+
|
[Update Product Info]

+------------------+
| Customer |
+------------------+
/ | \
[View Offers] [Place Order] [Track Purchases]

6. Class Diagram
+----------------+ +----------------+
| Product |<----| Inventory |
+----------------+ +----------------+
| ID | | stockCount |
| Name | | price |
| Category | +----------------+
| Unit Price |
+----------------+

+----------------+
| Customer |
+----------------+
| ID |
| Name |
| Email |
+----------------+

+----------------+
| Order |
+----------------+
| Order ID |
| Customer ID |
| Product ID |
| Quantity |
| Date |
+----------------+

7. Data Flow Diagram (Level 0)

+----------+ +------------------+ +---------------+
| Customer | --------> | Supermarket App | --------> | Database |
+----------+ Search | (Web/Mobile) | Orders +---------------+
^ ^ |
| | |
View Offers Admin/Staff Analytics
Manage Inventory Dashboard

8. Additional Features

• Loyalty Points for frequent customers

• Feedback and Rating System
• Notifications for discounts

Q2. SRS for Project: Link Redirection System with Geo-Tracking

1. Introduction
1.1 Purpose:

This SRS outlines the requirements for a "Link Redirection System with Geo-Tracking" that allows users
to shorten marketing URLs, analyze click behavior, and gather geolocation data for business insights.

1.2 Scope:

• URL shortening feature with custom alias option.

• Track subscriber clicks with geolocation and timestamp.
• Generate reports based on click activity and location.
• Admin panel for analytics and link management.

1.3 Intended Audience:

• Admin Users
• Marketing Teams
• Developers

1.4 Definitions:

• Short URL: Compressed version of a long URL.

• Geo-Tracking: Capturing the user’s geographical location during URL clicks.
 2. Overall Description
2.1 Product Perspective:

The system is web-based and independent, accessible via modern browsers with integrated analytics
tools.

2.2 Product Functions:

• Create, manage, and delete shortened links

• Display analytics dashboard
• View subscriber behavior and geo-location

2.3 User Classes:

User Type Description

Admin Create/view analytics and reports

User Generate short links, view their link performance

2.4 Operating Environment:

• Web application (React/Next.js frontend, Python/Node backend)

• Database (MongoDB/PostgreSQL)

3. Functional Requirements

1. URL Shortening
2. Link Click Tracking with IP and Location
3. User Login and Management
4. Dashboard with Analytics
5. Report Export (CSV, PDF)

4. Non-Functional Requirements

• Performance: Must handle 10,000+ clicks per day

• Security: Token-based auth, HTTPS, encrypted user data
• Scalability: Cloud-deployable
• Availability: 24/7 uptime

5. Use Case Diagram

+----------------+
| Admin |
+----------------+
/ \
[Manage Users] [View Reports]

+----------------+
| User |
+----------------+
/ \
[Shorten URL] [View Analytics]
 6. Class Diagram
+----------------+
| Link |
+----------------+
| ID |
| Original URL |
| Short URL |
| Created By |
| Click Count |
+----------------+

+----------------+
| Click |
+----------------+
| ID |
| Link ID |
| IP Address |
| Location |
| Timestamp |
+----------------+

+----------------+
| User |
+----------------+
| ID |
| Username |
| Password |
+----------------+

7. Data Flow Diagram (Level 0)

+--------+ +-------------------+ +----------------+
| User | -------> | Web Application | -------> | Database |
+--------+ Create | | Track +----------------+
| ^ | | Clicks
| View Stats | | |
+-------------+ +-------------------+

8. Additional Features

• QR Code generator for each link

• Expiry setting for short URLs
• Email notifications on high traffic