21.03.

2016

Session: 2014 - 2016 | <THE ISLAMIA UNIVRSTY OF BAHAWALPUR DCS & IT>

Factory Management system

Revision History
Date

Description

Author

Comments

<date>

<Version 1>

<Your Name>

<First Revision>

Document Approval
The following Software Requirements Specification has been accepted and approved by the
following:
Signature

Printed Name

Title

Date

Mam Asfah Imtiaz

Supervisor, CSIT 21306

<date>

Factory Management system

Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope 1
1.3 Definitions, Acronyms, and Abbreviations. 1
1.4 References

1.5 Overview

2. The Overall Description

2.1 Product Perspective

2.1.1 Operations 2
2.1.2 Site Adaptation Requirements 3
2.2 Product Functions 3
2.3 User Characteristics

2.4 General Constraints

2.5 Assumptions and Dependencies

3. Specific Requirements

3.1 External Interface Requirements

3.1.1 System Interfaces 5

3.1.2 Interfaces

3.1.3 Hardware Interfaces

3.1.4 Software Interfaces

3.1.5 Communications Interfaces

3.2 Functional Requirements 6

3.2.1 <Functional Requirement or Feature #1> 6
3.2.2 <Functional Requirement or Feature #2> 7
3.3 Use Cases

3.3.1 Use Case #1

Factory Management system

3.3.2 Use Case #2

3.4 Classes / Objects

3.4.1 <Class / Object #1>

3.4.2 <Class / Object #2>

3.5 Non-Functional Requirements

3.5.1 Performance
3.5.2 Reliability

3.5.3 Availability 8
3.5.4 Security

3.5.5 Maintainability
3.5.6 Portability

1. Introduction
Purpose
This SRS define the all requirements and Specifications of Bahawal shoes
Factory. It describe the Functional purpose. By making this software we can
easily expand our business. It also helpful for time saving , money saving,
customer satisfaction , and keep record of all Employee and transaction.
We build Such software which keep all aspects like timely delivery, Price
availability, Advancement , Customer Records and theft.
1.2 Scope
We are creating this software for our shoes factory. It should keep track of all
the transaction of customer, supplier and availability of product. Record of all
workers, Manger and other persons which works in shoes factory. It also
make a slip of each transaction.
It is helpful for better working of factory. The manger have record of
everything. It also save our time , effort and all our data and record are
secured. Hence the main benefit of shoes factory management system is
provide the all record are saved and factory owner see easily our all
expense, records, products selling details. Through this system the owner of
factory every time connected to our business.
The only General manager can used this database software.
Stock automatically manage.

Factory Management system

General manager mange all the expenses of three shoes plants.

check the daily sale or purcshase records or enter.
General Manger store all the employee record who work our factory.
General Manager control all the transaction of our factory.

1.3 Definitions, Acronyms, and Abbreviations.

This SRS describe the software for the management of our shoes factory. It
consist of three plants that make different types of products. That are :(a) BASP
Bahawal Air Soft Plant
(b) BRSP
Bahawal Rubber Soft Plant
(c) HSP
Hawaii Soft Plant
All plants have same working that is, it work under an assistant manager
who keep record of all products made in this plant and Raw material
required for product. It keep also record of all the workers that work in this
plant. This assistant manager submit reports to manger daily.
1.4 References
Books:system Analysis and Design methods six edition by Jeffery L.whitten
professsor, Lonnie D.Bentley professor, Kevin C.Dittman Assistant Professor
All at purdue University West Lafayette
Concerned to:Falak shair Butt owner of bahawal shoes factory
Ammar Butt Assistant manager of bahawal shoes factory of
Umar butt assistant manager of bahawal shoes factory of
Nadeem assistant manager of bahawal shoe factory of

1.5 Overview

Factory Management system

This software is used for the management of our shoes factory. In this
software we save all the records of our factory. Further this documents have
two parts. In the First part we describe what should product do. And in
second part we tell about the requirements of the software.

2. The Overall Description

2.1 Product Perspective
In this factory our aim to develop a new variety of Leather shoes , Rubber
shoes. In this SRS we describe a way to sale purchase related products of
factory. In this we have a convenient way. In which we can save the all
records of purchasing orders and selling products
Further more we may save all the employers data and their performances
for example salary, status, attendance writing performance etc. All the
expense of this factory is majorly under the supervision owner and General
manger and assistant manger. Who are responsible for all their dealings.
All the records relating expense like selling, purchase, order, Raw material
etc will be saved on the shape of softcopy and we will also give a prove in
the shape of hardcopy. In general we may said slip.
2.2 Product Functions
General Manger should Login to use application.
If customer want anything he should visit are factory to choose the products.
If customer want to place any order then he will interact with general
manager about products and provide his required information.
General manger should fill all data in the application and that should save in
database on clicking on submit button and it also generate a slip for
customer.

Factory Management system

2.3 User Characteristics

Only general manger can use the application and no other user have access
to it.
2.4 General Constraints

Factory Management system

Software language should be in English.

General Manager should authenticate before using software.
Software must have logout option.
General Manager have unique name and password for authentication.
General Manager can update stocks and customer information.
General must have employees and their salary information.
2.5 Assumptions and Dependencies
Its a desktop application.
For using this software we just needed a simple laptop or computer having
jdk installed and a simple printer.
This software based on wempServer or vertrigo.
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 System Interfaces
On starting of software it shows a login window where general manager
login. After login General manager enter into the software in which he can
check stocks. It should have a option to add a new order booking form,
employee records form and customer records. It shows expense of all three
plants separately in a form. It must have menu bar that have all these menus
any of them can be open by clicking on them.
3.1.2 Interfaces
When general manger write the user name, password and click on login
button he come to the main page.

Factory Management system

After Login when general manager click on stocks button the all stocks of
plants from database will be shown.
By clicking on new order button a form will show to record a new order.
By clicking on employee or customer button its shows their records from
database in a form.

Factory Management system

By clicking on expense button its shows the expense of each plants

separately.
By clinking logout button General manager direct to login page.
3.1.3 Hardware Interfaces
The software require a laptop and printer. The laptop must be at least 2nd
Generation , RAM 4GB, ROM 500GB and core i5 pro.
3.1.4 Software Interfaces
Mysql database and OS(window 8 or higher)
Eclipse or visual studio(window)
3.1.4.1 MYSQL Server
It contain the database of our software. The general manager can have
access to it for updating and modification.

3.1.5 Communications Interfaces

Factory Management system

Software communicates with MYSQL server

3.2 Functional Requirements

Store all expense record of all plants.
Store all the customer record.
Store all the transactions.
Store daily sale shoes record.
General Manager must login before using the software.
System must secure all Employee or unknown persons.
General Manager must see the all previous customer record, employee
record, order booking record, expense Record by using database.

Factory Management system

Function 1

Add Employee Record

Input

CNIC, Employee Name, Employee Address, Salary,

Name Salary Per Month, Overtime wages, Vacations,
Gross Salary.

Output

Database Record, Database successfully updated

message

Processing

Validate the given details and record the information in

to the database.

Function 2

Search Employee Record

Input

By CNIC

Output

CNIC, Employee Name, Employee Address, Salary,

Name Salary Per Month, Overtime wages, Vacations,
Gross Salary.

Processing

Validate the given details and check Employee in a

given time period and return its availability.

Factory Management system

Function 3

Stationary Sales

Input

Order Name,shoes types ,shoes

Quantity,Price,Total,Discount,Grand Total

Output

Database Record, Database successfully updated

message

Processing

Validate the given details and record the

information in to the database.

Function 4

Set Rates

Input

Price, Extension price

Output

Database Record, Database successfully updated

message

Processing

Validate the given details and record the

information in to the database.

Factory Management system

Function 5

Order booking

Input

Order Name,Quantity,Price,Total,Discount,Grand
Total

Output

Printed version of the bill

Processing

Validate the given details and total cost is

calculated according to the
Services gain by the customer.

Factory Management system

3.3 Use Cases

Factory Management system

Manager login
Modify customer record

with username and password

Manager can modify customer
record and also can delete it

Modify inventory record

Check daily sale

Manager can update stock

As customer info is stored with
date we can also check sale

Buy product
Generate bill

Customer can buy

Manager will put all customer data
in form and system will generate
bill
Every customer detail will store in
database table

Customer detail

3.4 Classes / Objects

This section contains major classes of the factory management system
system.

Factory Management system

3.4.1 <Admin>
3.4.1.1 Username, password
3.4.1.2 for admin login for interaction with system
3.4.2 <Buyer>
3.4.2.1 Name, cnic, address, city, cell number
3.4.2.2 for storing information of buyer

3.5 Non-Functional Requirements

3.5.1 Performance: performance will very fast.
3.5.2 Reliability: system will easy to use and understand.
3.5.3 Availability: interface well designed and easy to handle.
3.5.4 Security: system will secure from unauthorized access.
3.5.5 Maintainability: system will support modification.
3.5.6 Portability: system will also run from one P.C to another

Appendix B Data Dictionary