Inventory Management System

Documentation

By P. Praveen Raj (20080275) P. Praveen kumar (20080277) G. Raja (20080281) V. Siva Subrmanian (20080304)

Software Requirements Specification

Project Date Document Type Version

Inventory system 19/07/2010 Software Requirements Specification 1.0

Revision History

S No 1

Date

Authored By

Revised By

19/07/2010

1)G.Raja 2)P.Praveen Raj 3)P.Praveen Kumar 4)V.Siva Subramanian

 Staff The person working in the company or shop who involved in the every process of the system. who buys a product or person involved in the product sharing. item entry system. USERS OF THE SYSTEM  Customer People.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. . PROJECT SCOPE This project aims at reducing the manual errors also it fastens the work and it maintains the stock entry system. The application contain employee. It is easy for an employee to approach for leave from employee. who involves in the exchange of product or source of the product who trades from another place. maintenance system. personal detail.  Manager The person who takes overall in-charge of the stock and the staff etc. company detail.  Trader The trader. It comprises the maximum amount of official work done on the company. and so on.

. DEFINITIONS. WASCE - Web sphere application server community edition is an application server that runs and supports the J2EE and web service applications. ACRONYMS AND ABBREVIATIONS HTML - Hypertext Markup Language is to create static web pages. Store in-charge The person who takes care of the store. where stocks are placed. 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.

XML. AJAX. Pressman. TECHNOLOGIES TO BE USED UML. 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. J2EE. SSL. TOOLS TO BE USED Umbrello Eclipse . JSP.DB2 - Database 2 is the database management system that provides a flexible and efficient database platform to erect strong on demand business applications.

2 GHz each Intel Pentium Core 2 Duo at 2.REQUIREMENTS  Hardware Requirements Client side Processor Intel Pentium III at 1 GHz Ram 256 MB Disk space 512 MB Server side Server A Intel Pentium Core 2 Duo at 2.2 GHz each 16GB 2TB Server B 32GB 2TB .

 Software Requirements  Client Side Internet Explorer 6 (or) Mozilla Firefox 3.  Schedule management An application to maintain the schedule of the employee. DB2 V9. WASCE. .1  Functional Requirements  Employee login verification It verify the password to access employee account.  Transaction details To maintain the details about the company transaction.5 (or) Google Chrome  Server Side JVM.  Salary management To maintain the salary of the various grade employees.

 Flexible service based architecture will be highly desirable for future extension. Non-Functional Requirements  Secure access of confidential data (user's details). SSL can be used. .  Better component design to get better performance at peak time.  24 X 7 availability.

 Store in-charge The person who takes care of the store. 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. . who buys a product or person involved in the product sharing. where stocks are placed.  Trader The trader.Use Case Model (One Column Format) Use Case Name : Item entry report and Maintenance system Level : System Goal Primary Actor Stakeholders and Interests  Customer : Manager People.

 The manager can delete or edit a item. Delete existing record. . ITEM REPORT SYSTEM 1. Print budget report. 3. Edit user account. 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. USER ENTRY SYSTEM 1. Print inventory summary report. Create new user account. Print inventory budget report. 4. Main Success Scenario  The staff or manager creats the item entry and search for item. 3.Preconditions The customer is identified and the stock are available in the store which is identified at initial state. 2. Post conditions The stock details. 2. Display inventory support report.

2. Loan Transfer 1. Buy process coupen. Log actually survelliance 2. 3. Online order. To buy a product 1. Browse product. System secure and stable. . 3. 2. Transfer to organiser.IN MAINTENANCE SYSTEM 1. Transfer to victims. Transfer to inventories. 3. sales report. pay tax. Extensions ( or Alternative Flows ) *a. *b. 4. 5. Ensure data accurate.

Better component design to get better performance at peak time. 9a. Technology and Data Variations List 4a. Expired item report. 4. Re credit level. Item forecasting report. The customer is informed by mail ( using JMS ) Frequency of Occurrence : Could be nearly continuous .*c. Special Requirements     Secure access of confidential data ( user's details ). Delete Report. 5. 3. SSL is used for protecting integrity and confidentiality of form data. Inventory forecasting report. 2. Flexible Service based Architecture for future extension. Report on Inventories 1. 24 x 7 availability.

What happen if any item is deleted? .Is your data is accurate? .Open Issues .

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.  Staff The person working in the company or shop who involved in the every process of the system.  Trader The trader. . who involves in the exchange of product or source of the product who trades from another place. where stocks are placed.  Store in-charge The person who takes care of the store. Preconditions The customer is identified and the stock are available in the store which is identified at initial state.

Post conditions The stock details. 4. Main Success Scenario Actor Action (or intention) 1. Customer request a product. The manager creates a product record with the Requirement. 8. 6. The staff deals with the required product. 3. Redirected to inventory manager. 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. Inventory manager confirm the order. The details of products are discussed with the customer. Status of product is informed 9. The product is delivered. 7. System Responsibility 2. . 5. Customer fills out the requirement form.

Buy process coupen. 8. 7. Loan Transfer 4. 10.Extensions ( or Alternative Flows ) *a. sales report. 3. pay tax. To buy a product 1. Expired item report. 5. Inventory forecasting report. Transfer to victims. Online order. 2. Re credit level. Item forecasting report. *b. Report on Inventories 6. Transfer to organiser. 4. 6. *c. Transfer to inventories. 5. Browse product. Delete Report. . 9.

Frequency of Occurrence : Could be nearly continuous Open Issues - What happen if any item is deleted? Is your data is accurate? . SSL is used for protecting integrity and confidentiality of form data. Flexible Service based Architecture for future extension. Technology and Data Variations List 4a. 9a.Special Requirements     Secure access of confidential data ( user's details ). 24 x 7 availability. The customer is informed by mail ( using JMS ). Better component design to get better performance at peak time.

Groups of Project Managers. definitions. specialized 5 terms defined and overview of the requirements specification. Project without clear goals 4 will rarely achieve their targets clearly. This approach is called the Technical Facilitator/Integrator (TFI) approach. Cost. Framework of key attributes and weightings for requirements specification: Item Factor Weightin g 1 Introduction – Purpose of the requirements document. 3 Resource.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. scope. 2 firewall should be configured . Quality). Assumptions and dependencies (client should have a jre installed. A 17 factor assessment model is suggested and used for evaluation of the requirements specification documents of the project cases studied. Comments related to the application of the process to this project are also provided. Most of the generic process description is taken from this document. Objectives at different levels are outlined.. 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.) . acronyms and 25 abbreviations. references. Functional requirements Non-Functional requirements 10 3 2 3 4 5 6 7 Design and implementation constraints (Server deployment and 8 firewall constraints) Identify Quality and project management requirements (Time.

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.FURTHER ANALYSIS OF DATA Percentage fit against the suggested requirements specification framework Project 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% Score Percentage 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. .

. The inventory will list over 10. How user friendly is your system?  The menus and icons are self-explanatory and written in simple English. this amount will be reduced in future. Which is the minimum purchase amount to avail offer?  The minimum purchase amount to avail offer is Rs1000.000 product and provide us with a clear view of available products.How is it different from existing Inventory system modules?  The existing inventory does not provide or incorporate all the above feature in one package. Help manuals and documents have also been provided.

J2EE Specs 1.VALIDATION The implementation framework to be used is a Struts type MVC ( Model – View – Controller ).6 based WASCE Server and EJB Container shall be used. 1. Should the administrator be able to specify databases location information for the system to access ? 5. Requests to change the answers during the course of development shall not be entertained. Should the administrator be given facilities for configuring the system ? 6. Should maintenance be done automatically or by the administrator ? 4. What will happen if system crashes during transaction? . What is the use of the review system? 7. Where to report broken products? 8. Are there any more users of the system ? 2. 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. When can the system be shut down for maintenance ? 3.