SOFTWARE REQUIREMENT
SPECIFICATION
FOR
KINGS CHILLER
PREPARED BY:
GHAZNAFAR ABBAS BSIT (M)-17-29
MUHAMMAD SHAHBAZ BSIT (M)-17-09
MUHAMMAD DILAWAR BSIT (M)-17-42
MUBASHIR ALI
NADIR ABBAS
DATE:
01-OCT-2019
Software Requirements Specification for KINGS CHILLER Page 2 of 6
Table of Contents
Table of Contents...........................................................................................................................2
1. Introduction..............................................................................................................................3
1.1 Purpose............................................................................................................................................. 3
1.2 Document Conventions.................................................................................................................... 3
1.3 Intended Audience and Reading Suggestions.................................................................................. 3
1.4 Product Scope .................................................................................................................................. 3
1.5 References........................................................................................................................................ 3
2. Overall Description..................................................................................................................4
2.1 Product Functions ............................................................................................................................ 4
2.2 User Classess and Characteristics.................................................................................................... 4
2.3 System Stakeholders........................................................................................................................ 4
2.4 Operating Environment.................................................................................................................... 4
3. Specific Requirements .............................................................................................................5
3.1 User Interface................................................................................................................................... 5
3.2 Functional Requiements................................................................................................................... 5
3.3 Non-Functional Requirements......................................................................................................... 6
3.4 Other Requirements ......................................................................................................................... 6
Software Requirements Specification for KINGS CHILLER Page 3 of 6
1.INTORDUCTION
1.1 Purpose
Software of Kings Chiller is a computer system used to manage the
customer records and products records. It includes hardware
components such as computer, printer and software to manage the
process of Kings Chiller.
1.2 DOCUMENT CONVENTIONS
In this document, fonts used as follows:
For Heading: 16pts, bold, Calibri
For paragraphs: 14pts, normal, Calibri
1.3 INTENDED AUDIENCE AND READING SUGGESTIONS
Manager: System manager who is given specific permission for
managing and controlling the system.
Owner: Someone who deals with the product stock, price,
quality and employees of the shop.
Sale’s person: The person who deals with customer for billing.
1.4 PRODUCT SCOPE
This software helps the owner to save the sale of his shop, product
details and the customer details. He can also fetch record on daily,
weekly, monthly and yearly basis.
1.5 REFERENCES
SRS template by Karl E. Wiegers 1999
Software Requirements Specification for KINGS CHILLER Page 4 of 6
2.OVERALL DESCRIPTIONS
2.1 Product functions
i. Manage Sale
ii. Reporting
iii. Manage customer record
iv. Manage product record
v. Manage users
2.2 User classes and characteristics
Manager: The manager is one of that person that interact with the
system. He can manages the products records, sale records,
customer records, add new products, delete products and edit
products.
Owner: The Owner is one of that person who can fetch the sales
records on daily, weekly, monthly and yearly basis. He can add
employees, can add new products, and many more etc.
Salesperson: The salesperson is the man who creates bills and
add customer’s records, manages cash services.
2.3 System Stake Holders
The Stakeholder in this system:-
i. Manager
ii. Owner
iii. Salesperson
2.4 Operating Environment
The environment of this software:
Operating system: windows (10, 8.1, 8, 7)
Version 4.5.0
Software Requirements Specification for KINGS CHILLER Page 5 of 6
3.SPECIFIC REQUIREMENTS
3.1 User interface
3.2 Functional requirement
The functional requirements of the software are following:
i. User login
ii. Add sales
iii. Add customer record
iv. Billing
v. View customer record
vi. View sales
vii. Manage products
viii. Manage users
Software Requirements Specification for KINGS CHILLER Page 6 of 6
3.3 Non-Functional requirement
The non-functional requirements of the software are following:
i. User authentication
ii. Required Products should be available
iii. Payment paid before getting products
iv. Customer id should be unique
3.4 Non-Functional requirement
Database:
Database is used for saving users, products and customers
records.

Software Requirement Specification

  • 1.
    SOFTWARE REQUIREMENT SPECIFICATION FOR KINGS CHILLER PREPAREDBY: GHAZNAFAR ABBAS BSIT (M)-17-29 MUHAMMAD SHAHBAZ BSIT (M)-17-09 MUHAMMAD DILAWAR BSIT (M)-17-42 MUBASHIR ALI NADIR ABBAS DATE: 01-OCT-2019
  • 2.
    Software Requirements Specificationfor KINGS CHILLER Page 2 of 6 Table of Contents Table of Contents...........................................................................................................................2 1. Introduction..............................................................................................................................3 1.1 Purpose............................................................................................................................................. 3 1.2 Document Conventions.................................................................................................................... 3 1.3 Intended Audience and Reading Suggestions.................................................................................. 3 1.4 Product Scope .................................................................................................................................. 3 1.5 References........................................................................................................................................ 3 2. Overall Description..................................................................................................................4 2.1 Product Functions ............................................................................................................................ 4 2.2 User Classess and Characteristics.................................................................................................... 4 2.3 System Stakeholders........................................................................................................................ 4 2.4 Operating Environment.................................................................................................................... 4 3. Specific Requirements .............................................................................................................5 3.1 User Interface................................................................................................................................... 5 3.2 Functional Requiements................................................................................................................... 5 3.3 Non-Functional Requirements......................................................................................................... 6 3.4 Other Requirements ......................................................................................................................... 6
  • 3.
    Software Requirements Specificationfor KINGS CHILLER Page 3 of 6 1.INTORDUCTION 1.1 Purpose Software of Kings Chiller is a computer system used to manage the customer records and products records. It includes hardware components such as computer, printer and software to manage the process of Kings Chiller. 1.2 DOCUMENT CONVENTIONS In this document, fonts used as follows: For Heading: 16pts, bold, Calibri For paragraphs: 14pts, normal, Calibri 1.3 INTENDED AUDIENCE AND READING SUGGESTIONS Manager: System manager who is given specific permission for managing and controlling the system. Owner: Someone who deals with the product stock, price, quality and employees of the shop. Sale’s person: The person who deals with customer for billing. 1.4 PRODUCT SCOPE This software helps the owner to save the sale of his shop, product details and the customer details. He can also fetch record on daily, weekly, monthly and yearly basis. 1.5 REFERENCES SRS template by Karl E. Wiegers 1999
  • 4.
    Software Requirements Specificationfor KINGS CHILLER Page 4 of 6 2.OVERALL DESCRIPTIONS 2.1 Product functions i. Manage Sale ii. Reporting iii. Manage customer record iv. Manage product record v. Manage users 2.2 User classes and characteristics Manager: The manager is one of that person that interact with the system. He can manages the products records, sale records, customer records, add new products, delete products and edit products. Owner: The Owner is one of that person who can fetch the sales records on daily, weekly, monthly and yearly basis. He can add employees, can add new products, and many more etc. Salesperson: The salesperson is the man who creates bills and add customer’s records, manages cash services. 2.3 System Stake Holders The Stakeholder in this system:- i. Manager ii. Owner iii. Salesperson 2.4 Operating Environment The environment of this software: Operating system: windows (10, 8.1, 8, 7) Version 4.5.0
  • 5.
    Software Requirements Specificationfor KINGS CHILLER Page 5 of 6 3.SPECIFIC REQUIREMENTS 3.1 User interface 3.2 Functional requirement The functional requirements of the software are following: i. User login ii. Add sales iii. Add customer record iv. Billing v. View customer record vi. View sales vii. Manage products viii. Manage users
  • 6.
    Software Requirements Specificationfor KINGS CHILLER Page 6 of 6 3.3 Non-Functional requirement The non-functional requirements of the software are following: i. User authentication ii. Required Products should be available iii. Payment paid before getting products iv. Customer id should be unique 3.4 Non-Functional requirement Database: Database is used for saving users, products and customers records.