0% found this document useful (0 votes)
44 views

Software Requirements Specification: Sheeda Talli Cash & Carry

This document provides a software requirements specification for a cash and carry system for a supermarket. The system aims to easily maintain records of products to avoid data loss and facilitate customers and cashiers. It will allow viewing products, inserting new products, updating and deleting records, viewing sales, and generating receipts. The system is intended for use in supermarkets and similar stores. It will have security measures and limit some functions like record modification to managers only.

Uploaded by

mexiwe
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views

Software Requirements Specification: Sheeda Talli Cash & Carry

This document provides a software requirements specification for a cash and carry system for a supermarket. The system aims to easily maintain records of products to avoid data loss and facilitate customers and cashiers. It will allow viewing products, inserting new products, updating and deleting records, viewing sales, and generating receipts. The system is intended for use in supermarkets and similar stores. It will have security measures and limit some functions like record modification to managers only.

Uploaded by

mexiwe
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 9

Software Requirements Specification for Cash and Carry System Page 

Prepared By:
Omer Fayyaz (01­131172­045)

SOFTWARE
M.Behlole Aqil(01­131172­018)
Abu Huraira (01­131172­050)
REQUIREMENTS
SPECIFICATION
Sheeda Talli Cash & Carry
 | P a g e
Software Requirements Specification for Cash and Carry System Page i

Content
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................1
1.4 Product Scope.............................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective....................................................................................................................2
2.2 Product Functions.......................................................................................................................2
2.3 Operating Environment..............................................................................................................2
2.4 Design and Implementation Constraints.....................................................................................2
2.5 Assumptions and Dependencies.................................................................................................2
3. System Features.......................................................................................................................2
3.1 View products............................................................................................................................3
3.1.1 Description and Priority:........................................................................................................3
3.1.2 Stimulus/Response Sequences:..............................................................................................3
3.1.3 Functional Requirements........................................................................................................3
3.2 Insert New Products:..................................................................................................................3
3.2.1 Description and Priority:........................................................................................................3
3.2.2 Stimulus/Response Sequences:..............................................................................................3
3.2.3 Functional Requirements........................................................................................................3
3.3 Update Record:...........................................................................................................................4
3.3.1 Description and Priority:........................................................................................................4
3.3.2 Stimulus/Response Sequences:..............................................................................................4
3.3.3 Functional Requirements........................................................................................................4
3.4 Delete Record:............................................................................................................................4
3.4.1 Description and Priority:........................................................................................................4
3.4.2 Stimulus/Response Sequences:..............................................................................................4
3.4.3 Functional Requirements........................................................................................................4
3.5 View Sales:.................................................................................................................................4
3.5.1 Description and Priority:........................................................................................................4
3.5.2 Stimulus/Response Sequences:..............................................................................................5
3.5.3 Functional Requirements........................................................................................................5
3.6 Generate Slip:.............................................................................................................................5
3.6.1 Description and Priority:........................................................................................................5
3.6.2 Stimulus/Response Sequences:..............................................................................................5
3.6.3 Functional Requirements........................................................................................................5
4. Other Nonfunctional Requirements.......................................................................................5
4.1 Performance Requirements.........................................................................................................5
4.2 Security Requirements................................................................................................................5
4.3 Business Rules............................................................................................................................6

Revision History
Name Date Reason For Changes Version

i | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

1 Introduction

1.1 Purpose 

 To easily maintain the record of products.
 To avoid unnecessary mishaps
 Prevent possible loss of data
 To facilitate customers as well as cashiers.
 To store the record of each product in database.

1.2 Document Conventions

Our documents convention we followed during writing this SRS document are:
 Text style is in Times new Romans
 Headings are bold
 Simple English with some technical terms will be used.

1.3 Intended Audience and Reading Suggestions

Intended audience of this document are:
 Managers of supermarket branches.
 Cashiers
 Developers

The document should be read from top to bottom with a proper sequence but the reader 
should read the glossary of our document first.

1.4 Product Scope

 This project is specified to keep the record of products
 Manager will be able to do all CRUD operations on database
 Cashier and other users will only be allowed to view the product generate a bill.
 It will help any branch to maintain record without any ambiguities and confusions.
 the project can hold the record of almost 1 million products.
 Capacity of storing products can also be increased.
 With some increments and adding some features ,this system can also be used 
internationally.

1 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

2. Overall Description

2.1 Product Perspective

We discovered after several surveys that some supermarkets are facing a lot of problems in handling
with the database of products as well as customers.
Generating receipts for the shopping of customer and holding record of all the products that the 
particular supermarket currently has is the basic perspective of our project

2.2 Product Functions

Following are the functions of our project:
 To create record of any new product
 To update record
 To delete a record of a product
 To hold exact quantity of a product
 To generate a reciept

2.3 Operating Environment

This software will be used in supermarkets, cash & carry shops as shopping malls as well.
With some modifications this product can be used worldwide. 

2.4 Design and Implementation Constraints

Some of the functionality of this product will be limited to some user.
Modification of record can only be done by manager of shop. However, cashier at counter can only 
view record and generate a receipt.
For security purpose, along with the tables of record, there will be the table of system users along 
with usernames and passwords through which only authorized can access the document.

2.5 Assumptions and Dependencies

This product assumes that the user of this product will know the basics of computer operating
system and to deal with its functionality.
This product’ functionality depends and rely on its user i-e cashier, manager etc.

3. System Features
Following are features of our project
 View the products
 Insert new product
 Update the record of existing product
 Delete any product

2 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

 View all sales per month, per week or per year. And display the total revenue generated
 Generate a slip

3.1 View products

3.1.1 Description and Priority:

 This feature will be allowed to both managers and cashiers
 This feature will be given one of the most top priority

3.1.2 Stimulus/Response Sequences:

 When the user will click the VIEW icon another window will be displayed
 Query for viewing data will be generated in SQL
 The system will directly access the database (oracle based).
 Table of products will be returned by database and will be shown to user in an interactive 
manner.
 On this window, other options will be provided to user to perform certain actions like 
SEARCH (by id number, by name) and EXIT icon will also be provided to user.

3.1.3 Functional Requirements

 System shall display the view button on main window.
 The new windows that will be displayed after clicking view button will contain the record of
products in a pagination form and will 
 Allow the user to search the product.

3.2 Insert New Products:

3.2.1 Description and Priority:

 This feature will be allowed to only cashiers

3.2.2 Stimulus/Response Sequences:

 When the user clicks the INSERT icon another window will be displayed
 A dialogue box will be displayed to user.
 The dialogue box will take the name, id number, price and shelf number from the user.
 The entered entities will be stored in the database, from where it can be viewed or updated 
later.

3.2.3 Functional Requirements

 System shall display the INSERT button on main window.
 System will display a form to user to enter details the record of the product.
 The new windows that will be displayed after clicking INSERT button will provide the user
a form in order to get certain entities necessary for the product.

3 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

3.3 Update Record:

3.3.1 Description and Priority:

 This feature will be allowed to only cashiers

3.3.2 Stimulus/Response Sequences:

 When the user clicks the UPDATE icon another window will be displayed.
 New window will show all the products with their information. New window will also have 
a SEARCH box for efficient and fast retrieval of product’s data. 
 The user will select the product to update from the list of products.
 After selection of Product a new window will be displayed that will contain name, price, 
shelf number that user will enter in the provided space.

3.3.3 Functional Requirements

 System shall display the INSERT button on main window.
 The new windows that will be displayed after clicking INSERT button will provide the user
a dialogue box in order to get certain entities necessary for the product.

3.4 Delete Record:

3.4.1 Description and Priority:

 This feature will be allowed to only cashiers

3.4.2 Stimulus/Response Sequences:

 When the user clicks the DELETE icon another window will be displayed
 New window will show all the products with their information. 
 The user will select the product to delete it from the database.

3.4.3 Functional Requirements

 System shall display the INSERT button on main window.
 The new windows that will be displayed after clicking INSERT button will provide the user
a dialogue box in order to get certain entities necessary for the product.

4 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

3.5 View Sales:

3.5.1 Description and Priority:

 This feature will be allowed to only manager.

3.5.2 Stimulus/Response Sequences:

 When the user clicks the SALES icon another window will be displayed
 New window will show all the products that have been sold.
 View revenue annually, monthly and weekly will be provided as icon to user in order to 
have all details about business. 
 The user can also view the total revenue generated annually, monthly, weekly as selected.

3.5.3 Functional Requirements

 System shall display the INSERT button on main window.
 The new windows that will be displayed after clicking INSERT button will provide the user
a dialogue box in order to get certain entities necessary for the product.

3.6 Generate Slip:

3.6.1 Description and Priority:

 This feature will be allowed to only cashiers.

3.6.2 Stimulus/Response Sequences:

 When any Product is about to be sold the system automatically generates the slip (bill). 

3.6.3 Functional Requirements

 System shall display the VIEW button on main window.
 The new windows that will be displayed after clicking VIEW button will provide the user a 
dialogue box in order to get certain entities necessary for the product.

4. Other Nonfunctional Requirements

4.1 Performance Requirements

Our product will be easier to use and efficient as well.
It will take less space on memory and will run smoother and faster

5 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

4.2 Security Requirements

There will be a table of all the users in database along with the data of products in which there will
be usernames and passwords of authorized users and only authorized users can access the
database.

4.3 Business Rules

 Only manager can manipulate the data of products and enter new user.
 There will be time and data on receipt along with name of cashier stamped on slip.

6 | P a g e
SRS DOCUMENT                          CASH AND CARRY SYSTEM                                         Date:04/03/2019
                                               Muhammad Behlole Aqil (01­131172­018)

5. USE­CASE diagram:

7 | P a g e

You might also like