Category: .Net Projects

The project titled “Inventory Control System” is to control the general stores department. Hindustan Shipyard Limited is an automation of issuing an item to different departments inside the organization, returning back the item to the stores if the department doesn’t have any need with the item or if the stock is full, issuing the receipt to the department to whom the item is being issued, checking the balance of the stock of each item, making a new purchase of an item if the store doesn’t contains the stock of that particular item.

The purchase of an item is indifferent modes i.e., local abroad and indigenous. If the item is purchased locally then it is said to be local. If the item is imported from other countries then it is said to be imported. If the item is purchased from any department inside the organization then it is said to be indigenous.

The project contains five modules:

Issue Module, Returns Module, Receipts Module, Balance Module and Purchase Module.

The Issue Module contains the information about the item are issued by the department to various other department in the organization. This module contains the following fields as card code, item code, department code, work order number, document number, transaction date, rate of the item, quantity of the item to be issued, its value.

The Returns Module contains the information about the item are issued by the department to various other department in the organization. This module contains the same fields as in the issue module they are as follow fields card code, item code, department code, work order number, document number, rate of the item, transaction date, quantity of the item to be issued, its value.

The Receipts module contains the information about the item that are issued and address of the department to which the item was sold are the supplier details. The details contains the following fields as card code, item code, department Code, order number, document number, transaction date, rate of the item, quantity of the item to be issued, its supplier details.

The Balance module contains the information about the balance that is/was present before/after the issue of each item and about the new stock. This module contains the following fields as card code, item code, department code, rate of the item transaction code, transaction date, quantity of the item to be issued, its value.

The Purchase module contains the information about the purchase that made by the department. Whenever the department needs any new item, the value of the purchased item is calculated according to the mode of purchase i.e. local, abroad, indigenous. We can make addition of a new item, deletion, modification, etc for this file. It contains the fields such as item code, item desc, units, quality grade, item value.

Inventory control system is a client/server application.
Software requirements Visual Basic.Net front end, MS SQL Server back end.

SYSTEM REQUIREMENT SPECIFICATION

The data processing department is accepting many requests, which comes from different department. Currently the request like updates, stop details, issues, returns are done manually. So they would like to automate it.
We have to first understand this problem and produce a requirement documents based on understanding the problem.

End User: Office Staff

While studying the current system, after speaking with the director, front office staff we found the system as follows.

Whenever a new work comes, the work is divided into different parts and each part is submitted to the respective department. The respective department checks their work and the material needed for their work. If the material is sufficient for them for doing their work to carry out with it otherwise they send a request for Data Processing Department for the issue for the material. The data Processing Department then sends a request to stores department whether the mat is available or not. If the material is available they will issue it otherwise they will place as an order.
If the allocated material is more than sufficient, the respective departments will handover that extra material to Data Processing Department by a note. Then the Data Processing Department will update their respective stores. In automating the whole process we find that the inventory system consists of three main parts.

1. ISSUES:
This process is used to store the issue details of the item which is requested by the respective department.

2. RETURNS:
This process is used to store the return details of the item, which IS the respective department.

3. RECEIPTS:
This process is used to store the receipt details of the item, which is attested by the respective department.
After discussion with the staff the following decisions were taken regarding what the automated systems should do and what new environment will be.

1.    The format for each entry should be similar over currently being used.
2.    Entries might have errors, so system should be able to check for errors.
3.    Information about the items, departments, and work orders should be kept in permanent database.

Requirement Specification Document:

Introduction:

Purpose:

The purpose of this document is to describe the external requirement for the atomization of stock details. The atomization will provide management to accept item details and quality. It also describes the interface for the system.

Scope:

The document is the only one that describes the requirements of the system. It is meant for the use by and will also be the basis for validating the full system. Any change made to the requirements in future will have to go through a formal change approval process. The developer is responsible for asking for classification whenever necessary and will give any alteration without the permission of the client.

Conversion Methods:

Conversion methods are of four types these are parallel systems, direct cut over method, pilot method and phase in method. Each method has some advantages it offers and some problems that it may cause. However some situations force one method to be used over others, even though other methods may be more beneficial. In general, system conversion should be accomplished as quickly as possible. The present module contains the same fields as in the issue module they are as follows card code, item code, department code, work order number, document number, transaction date, rate of the item, quantity of the item to be issued., its value etc.,

Receipts Module:

This module contains the information about the items that are issued and their the details of the department to which the item was sold and the supplier details. This module contains the following fields as card code, item code, department code, order number, document number, transaction date, rate of the item, quantity of the item to be issued, its value, supplier details etc.

Balance Module:

This module contains the information about the balance that is/was present before/after the issue of each item and about the new stock. This module contains the following fields as card code, item code, department code, transaction date, rate of the item, quantity of the item to be issued, its value.

Purchase Order Master:

This module contains the information about the purchases that are made by the department. Whenever the department needs any new item, system is developed using ORACLE 7.3 as backend and VISUAL BASIC 6.0 as front end that helps us to create easier and flexible data entry.

The system automation that has been developed will be installed in the organization in a phased manner. This helps the end user who will be using the system in future to get a feel of the system. This also helps the end user to clarify their doubts and get rid any reservations or inhabitations that they have. The phased manner approach that the organization is implementing makes it possible systematic automated system.

CONCLUSION

After completing the proposed system successfully it is worth to talk about the limitations and advantages of the system.

LIMITATIONS:

This system is capable of fulfilling the current requirements, but it is required to make modification to meet the future requirements. Disk space to increased when information increases.

ADVANTAGES:

As all the screens are self explanatory it is easy to work with the system with a little training for new operator. The system eliminated the problem of the existing system and enhances its capability.

Inventory Management System is a system which is used to keep track of sales and purchase of electronic goods. Its main objective is to keep track of stocks, sales and purchase of goods, maintain staff and customer information and generate reports.

The main functionalities of this system are as follows:

• To maintain information about current availability of stock based on which it decides whether there is a need to purchase goods, if they are out of stock.
• To display the information about dealer and also add information about new dealer.
• To maintain the information about staff, their personal details such as contact number, name, address, qualification, birth date, etc.
• To maintain the information about customer who visit the store for shopping.
• It also provides discounts to customers who frequently visit the shop and purchase goods.
• To provide information regarding sales and purchase of goods.
• To provide information about sales summary.
• The system can be accessed by administrator and accounts department.
• It provides the functionality to create new user who can access the system.
• It also provides the records of the defective products which the customers return back to the shop for replacement.
• It also generates the purchase bill.

Project Scope

This document covers the requirements for the Inventory Management System. This Software will provide a graphical environment in which the users of the system will be able to perform various operations that are associated with storing, marinating, updating   and retrieving Stock information. The purpose of this is to guide developers in selecting a design that will be able to accommodate the full-scale application.

Product Perspective

The product Inventory Management system, is an independent product and does not depend on any other product or system. The product will automate various tasks associated with handling stock details and better organizing the Megastore information and  optimum performance, thus helping  the manager to ensure smooth working of these processes.

Product Features

The product, IMS will automate various tasks associated with handling stock details. The software will be used by the Megastores to Megastore the details of new and existing product. Periodically it will be used by the Megastores to input the total sales and sales rate information after the month/years. His software inherently makes automatic calculations on sales rate. And all this information is accessible to administrators and manager to keep track of their selling progress of the product. Also the software has a provision that will allow administrators to print the required reports of various products .

User Classes and Characteristics

This software gives access to 2 kinds of users.

Administrator: The manager and Megastore administrator will have administrator access to add, delete and modify information Megastore in the database.

Authorized User: computer operator staff will have access to only view the data Megastored in the database in the form of formatted reports.

System Features

Login

Description and Priority

The login form is used all the users. This module has the highest priority when compared to all the other modules. This model allows the the user to enter his username and password in order to make use of the software.

Stimulus/Response Sequences

This module has text boxes where the user can enter the his username name and password. If the necessary information is not provided or if invalid inputs are given by the user then the system will pop a message box.

Functional Requirements

Only authorized users are allowed to login.. If invalid user Name or password is given by the end-users then system should inform the user. If Unauthorized   users try to access then it should not allow the user to work on the System.

Data Entry module

Description and Priority

This module is used by data entry operator who is responsible for entering the details of products. The module requests that the Data entry Operator specify the function he/she would like to perform (either Add a product, update a product, or delete a product details).

In “Update a product” Once the Data entry Operator updates the necessary information ,the system updates the product record with the updated information.

In “Delete a product” Once the Data entry operator deletes the record, the system prompt s the user to confirm the deletion of the product.

Stock Entry Module

Description and Priority

This module allows the stock entry operator to add, delete or modify the product information from the system.

Stimulus/Response Sequences

The system requests the stock entry staff to specify the function she/he would like to perform(either Add stock, Update stock, Delete stock and Generate Report)

Functional Requirements

In “Add stock” Once the stock entry clerk provide the requested information, the system saves the stock and an appropriate message is displayed.

In “Update stock” the stock entry operator makes the desired changes to the stock details and at the same time the database will save the changes that are made by the stock entry operator.

In “Delete stock” if the clerk wishes to proceed with the deletion of the record on click of this the record is deleted from the system.

In “Report generation” the computed result of a particular product is displayed.

This project implements a network print spooler, which can accept multiple simultaneous print requests and handle them gracefully. The Client and Server architecture is built to receive the print requests from various users and aggregate all request in the server and manage them effectively according to the prioirity / rights / privileges of each and every user in the network.

The administrator of the network who is nothing but spooler manager can reorder jobs and remove any jobs from the queue and he as the final discretion as far as the processing of print requests are concerned .This project ensures the Network Sprint Spooler supports multiple requests from different users at the same time. In the Server, the queue status is displayed and the spooler manager re-orders the jobs and remove any jobs from the queue at his discretion.

The first is a client program that interacts with the user for accepting print requests of their documents files. The Client Program sends the request to the server program that runs in the network server to which the all the systems and printer are connected. The server program of this project  accepts requests from clients over the network, and serves them according the rights / permission / privileges.

The connection between the Client program and server program is established by using TCP/IP protocols using the .NET components. The management hierarchy of the company is studied and the access rights, permission and privileges of each every user of the network printer is given and configured in the Server program of the project.

The administrator ie. Spool Manager is the authorized person to login with the administrator username and password and login and configured the rights and permission accordingly to the respective users.

MODULES:

1. Client –server architecture establishment module.
2. Client side request processing module.
3. Server side request processing module.
4. Rights and permission checking and process module.
5. Reporting and administration module.
6. Client side request processing module:

In this model the client login into their resource by using login and his password. The client in the particular network will send a request to the server in the network. The request is about to take print in the network and ask whether the Printer are connected with the network and the request may be delete any. The response may be printer is connected in network, client can give request to see their file in server buffer to take print out, it can also delete any document file has been in server buffer by given request to server by him.

3) Server side request processing module:

In this module all the request from the client are process according to their priority. And all the request is process according to client request the response will be send the clients. The response may be yes printer is connected u can send the file or print is not connected so wait for some time.

4) Rights and permission checking and process module:

In this module the client will send set of files to the server to take print out. And that set of files will be store in the queue. The entire request from the server will process and find out he is authorized client if he is authorized client his request will    be store in queue and priority will be allocated according to the request time from the client and output will be given to the user. Using this module support display of the queue status, and allow users to remove their own jobs from the queue are delete according to the client request.

5) Reporting and administration module:

The administrator can login their area by admin user name and password. Admin is the one he has authority to control all the client system in the network. he has authorized   person to process all the request and send response to all the client in the network.