Inventory Management System

Documentation

By

P. Praveen Raj (20080275)

P. Praveen kumar (20080277)

G. Raja (20080281)

V. Siva Subrmanian (20080304)

 Software Requirements Specification

Project Inventory system

Date 19/07/2010

Document Type Software Requirements Specification

Version 1.0

Revision History

S Date Authored By Revised By

No

1 19/07/2010 1)G.Raja

2)P.Praveen Raj

3)P.Praveen Kumar

4)V.Siva Subramanian
INTRODUCTION
Inventory System is client based software to monitor and control the
employee and system works in the company and stocks report in the company. The
application contain employee, personal detail, company detail, and so on. It is easy
for an employee to approach for leave from employee.

PROJECT SCOPE
This project aims at reducing the manual errors also it fastens the work and it
maintains the stock entry system, item entry system, maintenance system. It
comprises the maximum amount of official work done on the company.

USERS OF THE SYSTEM

 Customer

People, who buys a product or person involved in the product sharing.

 Trader

The trader, who involves in the exchange of product or source of the

product who trades from another place.

 Staff

The person working in the company or shop who involved in the

every process of the system.

 Manager

The person who takes overall in-charge of the stock and the staff etc.
  Store in-charge

The person who takes care of the store, where stocks are placed.

DEFINITIONS, ACRONYMS AND ABBREVIATIONS

HTML - Hypertext Markup Language is to create static web

pages.

JSP - Java Server pages is used to create dynamic web

content.

J2EE - Java 2 Enterprise Edition is a programming platform and

it is the part of the java platform for developing and

running distributed java applications.

WASCE - Web sphere application server community edition is an

application server that runs and supports the J2EE and

web service applications.

DB2 - Database 2 is the database management system that
provides a flexible and efficient database platform to
erect strong on demand business applications.

JASPER - Reporting tool for generating reports exportable in pdf.

UMBRELLO - Software Modelling Tool for creating a design framework

SSL - Secured Socket Layer to protect Data Integrity and

Confidentiality during data transmission.

REFERENCES

“Software Engineering – A Practitioner's Approach” by Roger S. Pressman.

TECHNOLOGIES TO BE USED

UML, J2EE, XML, AJAX, JSP, SSL.

TOOLS TO BE USED

Umbrello
Eclipse
REQUIREMENTS
 Hardware Requirements

Client side

Processor Ram Disk space

Intel Pentium III 256 MB 512 MB

at 1 GHz

Server side

Server A Intel Pentium 16GB 2TB

Core 2 Duo at 2.2
GHz each

Server B Intel Pentium 32GB 2TB

Core 2 Duo at 2.2
GHz each
 Software Requirements

 Client Side

Internet Explorer 6 (or) Mozilla Firefox 3.5 (or) Google Chrome

 Server Side

JVM, WASCE, DB2 V9.1

 Functional Requirements

 Employee login verification

It verify the password to access employee account.

 Transaction details

To maintain the details about the company transaction.

 Schedule management

An application to maintain the schedule of the employee.

 Salary management

To maintain the salary of the various grade employees.

 Non-Functional Requirements

 Secure access of confidential data (user's details). SSL can be used.

 24 X 7 availability.

 Better component design to get better performance at peak time.

 Flexible service based architecture will be highly desirable for future

extension.
 Use Case Model (One Column Format)

Use Case Name : Item entry report and

Maintenance system

Level : System Goal

Primary Actor : Manager

Stakeholders and Interests

 Customer

People, who buys a product or person involved in the product sharing.

 Trader

The trader, who involves in the exchange of product or source of the

product who trades from another place.

 Staff

The person working in the company or shop who involved in the

every process of the system.

 Store in-charge

The person who takes care of the store, where stocks are placed.
Preconditions
The customer is identified and the stock are available in the store which is
identified at initial state.

Post conditions
The stock details, product details are saved and updated and the details of
the staff came to work or leave or noted and the product sale details are saved.

Main Success Scenario

 The staff or manager creats the item entry and search for item.

 The manager can delete or edit a item.

ITEM REPORT SYSTEM

1. Display inventory support report.

2. Print budget report.

3. Print inventory summary report.

4. Print inventory budget report.

USER ENTRY SYSTEM

1. Delete existing record.

2. Create new user account.

3. Edit user account.

 IN MAINTENANCE SYSTEM

1. Log actually survelliance

2. System secure and stable.

3. Ensure data accurate.

Extensions ( or Alternative Flows )

*a. To buy a product

1. Buy process coupen.

2. Online order.

3. Browse product.

4. sales report.

5. pay tax.

*b. Loan Transfer

1. Transfer to inventories.

2. Transfer to organiser.

3. Transfer to victims.
 *c. Report on Inventories

1. Delete Report.

2. Expired item report.

3. Re credit level.

4. Item forecasting report.

5. Inventory forecasting report.

Special Requirements
 Secure access of confidential data ( user's details ).

 24 x 7 availability.

 Better component design to get better performance at peak time.

 Flexible Service based Architecture for future extension.

Technology and Data Variations List

4a. SSL is used for protecting integrity and confidentiality of form data.

9a. The customer is informed by mail ( using JMS )

Frequency of Occurrence : Could be nearly continuous

Open Issues
- What happen if any item is deleted?

- Is your data is accurate?

 Use Case Model (Two Column Format)

Use Case Name : Item entry report and

Maintenance system

Level : System Goal

Primary Actor : Manager

Stakeholders and Interests

 Customer

People, who buys a product or person involved in the product sharing.

 Trader

The trader, who involves in the exchange of product or source of the

product who trades from another place.

 Staff

The person working in the company or shop who involved in the

every process of the system.

 Store in-charge

The person who takes care of the store, where stocks are placed.

Preconditions
The customer is identified and the stock are available in the store which is
identified at initial state.
Post conditions
The stock details, product details are saved and updated and the details of
the staff came to work or leave or noted and the product sale details are saved.

Main Success Scenario

Actor Action (or intention) System Responsibility

1. Customer request a product.
2. Redirected to inventory manager.
3. Inventory manager confirm the order.
4. Customer fills out the requirement
form.

5. The manager creates a product record

with the Requirement.
6. The staff deals with the required
product.
7. The details of products are discussed
with the customer.
8. Status of product is informed
9. The product is delivered.
Extensions ( or Alternative Flows )

*a. To buy a product

1. Buy process coupen.

2. Online order.

3. Browse product.

4. sales report.

5. pay tax.

*b. Loan Transfer

4. Transfer to inventories.

5. Transfer to organiser.

6. Transfer to victims.

*c. Report on Inventories

6. Delete Report.

7. Expired item report.

8. Re credit level.

9. Item forecasting report.

10. Inventory forecasting report.

Special Requirements

 Secure access of confidential data ( user's details ).

 24 x 7 availability.

 Better component design to get better performance at peak time.

 Flexible Service based Architecture for future extension.

Technology and Data Variations List

4a. SSL is used for protecting integrity and confidentiality of form data.

9a. The customer is informed by mail ( using JMS ).

Frequency of Occurrence : Could be nearly continuous

Open Issues

- What happen if any item is deleted?

- Is your data is accurate?

 ELICITATION PROCESS
FOR DEVELOPING NEXT GENERATION INVENTORY
MANAGEMENT SYSTEM
This study represents an exposition of requirements elicitation/specification
concepts and challenges involved in development of next generation police and
law enforcement system. Groups of Project Managers, Business Analysts and users
of IS/IT systems have been surveyed and interviewed and the data on 19 projects is
analysed to ascertain experiences and problems when eliciting and specifying
requirements. A 17 factor assessment model is suggested and used for evaluation
of the requirements specification documents of the project cases studied.
This approach is called the Technical Facilitator/Integrator (TFI) approach. Most
of the generic process description is taken from this document. Comments related
to the application of the process to this project are also provided.

Framework of key attributes and weightings for requirements specification:

Item Factor Weightin

g

Introduction – Purpose of the requirements document, scope,

1 definitions, acronyms and 25 abbreviations, references, specialized 5
terms defined and overview of the requirements
specification.
Objectives at different levels are outlined. Project without clear goals 4
2 will rarely achieve their targets clearly.
3 Functional requirements 10
4 Non-Functional requirements 3
5 Design and implementation constraints (Server deployment and 8
firewall constraints)
6 Identify Quality and project management requirements (Time, Cost, 3
Resource, Quality).
7 Assumptions and dependencies (client should have a jre installed, 2
firewall should be configured .,)
FURTHER ANALYSIS OF DATA

Percentage fit against the suggested requirements specification framework

Project Score Percentage

Poor if
0% ≤ Sc ≤ 33%
Fair if
33% ≤ Sc ≤ 50%
Good if
50% ≤ Sc ≤ 66%
Very Good if
66% ≤ Sc ≤ 83%
Excellent if
83% ≤ Sc ≤ 100%

Analysis of data from Questionnaires and Interviews

Who is the main user of the system?

 The main user of the system is manager. He handles the inventory database.

What are all the features it should provide?

 It should automatically update all the inventory system immediately after

production and after every successful transaction is done.
How is it different from existing Inventory system modules?

 The existing inventory does not provide or incorporate all the above feature
in one package. The inventory will list over 10,000 product and provide us
with a clear view of available products.

How user friendly is your system?

 The menus and icons are self-explanatory and written in simple English.
Help manuals and documents have also been provided.

Which is the minimum purchase amount to avail offer?

 The minimum purchase amount to avail offer is Rs1000, this amount will be
reduced in future.
 VALIDATION

The implementation framework to be used is a Struts type MVC ( Model –

View – Controller ). J2EE Specs 1.6 based WASCE Server and EJB Container
shall be used. Testing shall be done with suitable tools. The answers for the
following questions shall be compared with the final V&V process to measure the
success of the project. Requests to change the answers during the course of
development shall not be entertained.

1. Are there any more users of the system ?

2. When can the system be shut down for maintenance ?

3. Should maintenance be done automatically or by the administrator ?

4. Should the administrator be able to specify databases location

information for the system to access ?

5. Should the administrator be given facilities for configuring the system

?

6. What is the use of the review system?

7. Where to report broken products?

8. What will happen if system crashes during transaction?