Software Requirements Specification

For
Factory Management System

Version: 1.0
Prepared by:

Date

Factory Management
System
With the increase in the number of production, better management of
factory management system is required. The Factory management
system focuses on improving the management of factory. “What If you
can check whether a row product is available in the factory through
your phone?” or “what if instead of having many factory worker y o u
have all at one place
?” or “you can check a stock or issue a stock from your phone sitting
at your home!”. The Integrated Factory Management system
provides you the ease of issuing, reviewing, or reserving a stock
from a factory within your town through your phone. The Integrated
Factory Management system is developed on the android platform
which basically focuses on controlling, reviewing and reserving a
stock for product.
 PURPOSE
The purpose of the project is to maintain the details of stock and
factory workers of factory. The main purpose of this project is to
maintain an easy circulation system between clients and the
factory, to issue product using single factory card, also to search
and reserve any product from different available factory and to
maintain details about the user (total no of order, address, and
phone number). Moreover, the user can check all these features
from their home.

SCOPE
• Manually updating the factory system into an android based
application so that the user can know the details of the stock
available and maximum limit on production from their machine
and also through their phones.
• The IFM System provides information's like details of the
product, insertion of new product or machine, deletion of stock,
limitation of production, eye keeping on ongoing production.
• Also, client can provide feedback for adding some new product
to the factory.
OVERVIEW
The implementation of Factory Management starts with entering
and updating stocks records like stock details, factory information.
Any further transaction like product displacement, product delivery
will automatically update the current stock.

OVERALL DESCRIPTION

Product Perspective:
The proposed Factory Management System will take care of the
current stock detail at any point of time. The stock issue, product
delivery will update the current stock details automatically so that
user will get the update current stock details.

Product function:
 • The main purpose of this project is to reduce the manual work.
• This software is capable of managing stock
Issues, product delivery , and
Calculating/Managing payment. Generating
various Reports for Record-Keeping according to
end user requirements

User characteristics:

We have 3 levels of users:

User module: In the user module, user will check the availability of the stock.

• Issue stock
• Reserve stock
• Return stock
• Fund detail

Factory module
• Add new product
• Remove old product
• Update details of stock.

Administration module: The following are the sub module in the administration module.

• Register worker
• Entry stock details
• Delivery of product

General Constraints:
Any update regarding the stock from the factories to be recorded to
have update & correct values.
Assumption and dependencies:
All the data entered will be correct and up to date. This software
package is developed using java as front end which is supported by
sun micro system. Microsoft SQL server 2005 as the back end which
is supported by Window 7.

SPECIFIC REQUIREMENTS

External Interface Requirement:

The user should be simple and easy to understand and use. Also be
an interactive interface. The system should prompt for the user and
administrator to login to the application and for proper input criteria

User Interface:
• The software provides good graphical interface for the user
any administrator can operate on the system, performing the
required task such as create, update, viewing the details of the
stock and product.
• Allows user to view quick reports like stock Issues/Returned
etc. in between particular time.
• Stock verification and search facility based on different
criteria.
Hardware interface:
• Operating system : window
• Hard disk :40 GB
• RAM : 256 MB
• Processor : Pentium(R)Dual-core CPU

Software interface:
• Java language
• Net beans IDE 7.0.1
• MS SQL server 2005.

UML
 DIAGRAMS

Data Dictionary:
Use Case Diagram:
Data flow diagram:
State Diagram:
Sequence Diagram:
Activity Diagram:
Class Diagram:
• Diagram:

• Diagram
Non Functional Requirements
Usability Requirement

The system shall allow the users to access the system from the phone
using android application. The system uses an android application as
an interface. Since all users are familiar with the general usage of
mobile app, no special training is required. The system is user friendly
which makes the system easy.

Availability Requirement

The system is available 100% for the user and is used 24 hrs a day
and 365 days a year. The system shall be operational 24 hours a day
and 7 days a week.
Efficiency Requirement

Mean Time to Repair (MTTR) - Even if the system fails, the system
will be recovered back up within an hour or less.

Accuracy

The system should accurately provide real time information taking into
consideration various concurrency issues. The system shall provide 100%
access reliability.

Performance Requirement

The information is refreshed depending upon whether some

updates have occurred or not in the application. The system shall
respond to the member in not less than two seconds from the time
of the request submittal. The system shall be allowed to take more
time when doing large processing jobs. Responses to view
information shall take no longer than 5 seconds to appear on the
screen.

Reliability Requirement

The system has to be 100% reliable due to the importance of data

and the damages that can be caused by incorrect or incomplete
data. The system will run 7 days a week, 24 hours a day.

System attributes:
• Maintainability: There will be no maintained requirement for
the software. The database is provided by the end user and
therefore is maintained by this user.
• Portability: The system is developed for secured purpose,
so it is can’t be portable.
• Availability: This system will available only until the system
on which it is install, is running.
• Scalability: Applicable.
.