project blog responsive ads

Free download management system project documentation with JAVA, PHP AND ASP.NET source code. In all project report you will get introduction and objective of the project, system analysis, feasibility study, project planning, DFD diagram, system design, database design, complete project coding, and ER diagram of the project. These project reports and synopsis are useful for BCA, MCA BSC CS, MSC IT B.TECH, M.TECH and BE computer science last year students IGNOU, SMU university final year projects

Sponsored Links

DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT REPORT

DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT REPORT


PROJECT SOURCE CODE


1. Introduction


Stores are required for the following purposes :-

1.                 Capital works
2.                 Operation and Maintenances Works
3.                 Other Commercial activities like hiring equipment etc..,

The ‘Stores Management System’ is targeted to automate the almost all of the processes mentioned above to reduce the clerical labor of the staff working in Stores both technical and as well as Accounts departments using the software Industry’s latest technologies and cost effective tools there by providing the better control to the management by avoiding manual errors etc..,

In this project modules under study are Material Issues module, Reports module.

Material Issues module deals with the Issues functionality of the application. It mainly contains two operations namely Material issues i.e. Issues issued to works based on field requisitions and Inter stores issues i.e. material issues to other stores based on inter store requisitions. For these two operations, we have to issue the gate passes for both types of operations.

Reports module deals with the Reports provided by the application.  This module contains various reports namely Monthly SRB Report, Monthly SIB Report, Monthly Section Wise Issues Reports, Priced Ledger, Monthly Stores Abstract, Monthly Work Order wise Details and Monthly Stock Report.



1.1. Abstract - DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT



Project Title: Stores Management System

            The system creates a web based manufacturing system that enables a manufacturing industry to schedule its manufacturing operations based on the daily update of sales from its dealers. Once the sales figures of items for the past week are entered by the dealers over the internet along with the orders for the next delivery, the schedule for the next week’s production will be drawn up. A report of the required raw materials or parts will be drawn up with the product requirements over the internet & asked to quote their rates.
Once the rates are quoted, the order will be placed with the required delivery schedules. Once the parts the parts are supplied the stocks will be updated. Then a production plan will be drawn up taking the bill of materials into consideration. Once the production plan is approved, the stock will be updated when the material is issued. Once the finished products are available the delivery schedules will be drawn up based on the orders placed by the Dealers. The stocks with the dealers will also be maintained.
The Benefits of the Stores Management System is
§  It is used as an intranet Application.
§  Providing High-Security.
§  Easy Business Solutions.


1.2. Organization Profile

ABOUT ORGANIZATION
Company Profile:

SYSTEM ANALYSIS

2. System Analysis -DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT


2.1. Software Requirement Specification (SRS)
What is SRS?
Software Requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex, it became evident that the goal of the entire system cannot   be easily comprehended. Hence the need for the requirement phase arose. The software project us initiated by the client needs. The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.)

          The SRS phase consists of two basic activities:
                  
1)    Problem/Requirement Analysis:
The process is order and more nebuious of the two, deals with understand the problem, the goal and constraints.

2) Requirement Specification:
Here, the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.

The requirement phase terminates with the production of the validate SRS
document. Producing the SRS document is the basic goal of this phase.


Role of SRS

The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers. Software Requirement Specification is the medium through which the client and user needs are accurately specified. It forms the basis of software development. A good SRS should satisfy all the parties involved in the system.


Purpose
                  
The purpose of this document is to describe all external requirements for mobile task manager. It also describes the interfaces for the system.

2.2. Existing System - DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT



The existing system for Stores Management System activities uses open source standard & technologies. It had been developed on WINDOWS 2000 PROFESSIONAL platform with ‘POSTGRESQL’ database. All the stores of the power distribution company limited are made through the open source standards & technologies. The user interaction is in GUI (Graphical User Interface) mode.

          Stores are required for the following purposes.

          1. Capital works
          2. Operation and Maintenances Works
          3. Other Commercial activities like hiring equipment etc.

The ‘Stores Management System  package’ is targeted to automate the almost all of the processes mentioned above to reduce the clerical labour of the staff working in Stores both technical and as well as Accounts departments using the software Industry’s latest technologies and cost effective tools there by providing the better control to the management by avoiding manual errors etc..,


2.3. Hardware And Software Requirements
2.3.1. Hardware requirements
SERVER:
Processor                                   :                  Pentium IV
Speed                               :                  1.7 GHz
Memory Capacity            :                  1 GB
Hard Disk Capacity                  :                  80 GB
Monitor Make                           :                  HP
Client:
Processor                                   :                  Pentium IV
Speed                               :                  1.7 GHz
Memory Capacity            :                  256 MB
Hard Disk Capacity                  :                  20 GB
Monitor Make                           :                  HP
2.3.2. Software Requirements
Operating System                     :         Windows 2000 Professional
Web Server                               :         Apache Tomcat Web Server
Database                                             :         Postgresql
Enterprise Application              :         J2EE, JBOSS
Implementation Architecture     :         MVE,
                                                           3 Tier using Servlets, JSP
Scripting Languages                  :         Java Script
Programming Language            :         Java



2.4. Feasibility Study - DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT

The existing system is clearly understood the next step is to conduct the feasibility study, which is a high level capsule version of the entire System Analysis and Design process. The objective is to determine whether the proposed system is feasible. The three tests of feasibility have been carried out:
2.4.1.  Technical Feasibility
2.4.2.  Economical Feasibility
2.4.3.  Operational Feasibility
2.4.1. Technical Feasibility
In technical feasibility study, one has to test whether the proposed system can be developed using existing technology or not. It is planned to implement the proposed system using Windows 2000 Professional, JSP and Apache Tomcat Wed Server. The Organization already possesses Windows 2000 Professional Operating System. It is evident that the necessary hardware and software are available for the development and implementation of the proposed system. Hence the solution is technically feasible.

2.4.2. Economical Feasibility


As part of this, the costs and benefits associated with the proposed system are to be compared and the project is economically feasible only if benefits outweigh costs. The Organization has already its own satellite link, and a host of SUN FIRE 6800 servers. So it need not invest newly for the internet connection and also the organization initiated to use Open Source in project development, hence there is 0 additional cost incurred for the tools that will be used.

2.4.3. Operational Feasibility:

This test of feasibility checks if the system works with least difficulties when it is developed and installed. The technical staff has sufficient knowledge of the tools being used and the users need just to know how to access and run the programs in the Apache Web Sever. Hence it is concluded that the system is operationally feasible.

 SYSTEM SPECIFICATION

3. System Specification - DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT


3.1. System Environment and Tools

JAVA

Java is actually a platform consisting of three components:

1) Java programming language.

2) Java library of classes and interfaces.

3) Java virtual Machine.

The following sections will say more about these components:




Java is Portable:
         
One of the biggest advantages Java offers is that it is portable. An application written in Java will run on all the major platforms. Any computer with a Java based browser can run the applications or applets written in the Java programming language. A Programmer no longer has to write one program to run on a Macintosh, another program to run on a windows machine, still another to run on a UNIX machine, and so on. In other words, with Java, developers write programs only once. Rather than being compiled in to machine language, which is different for each operating systems and computer architecture, Java code is compiled in to byte codes.

With other languages, the program code is compiled in to a language that the computer can understand; the problem is that other computers with different machine instructions set cannot understand that language. Java code, on the other hand is compiled in to byte codes rather than a machine language. These byte codes go to the Java virtual machine, which executes them directly or translates them in to the language that is understood by the machine running it.

In the summary, these means that with the JDBC API extending Java, a programmer writing Java code can access all the major relational databases on any platform that supports the Java virtual machine.



Java Is Object-Oriented:

         
Java programming language is object oriented, which makes program design focus on what you are dealing with rather than on how you are going to do something. This makes it more useful for programming in sophisticated projects because one can break the things down into understandable components. A big benefit is that these components can than be reused.


Object Oriented languages use the paradigm of classes. In simplest terms, a class includes both the data and the functions to operate on the data, all the data members and functionality of its class. Because of this, you can think of a class as being like template, with each object being a specific instance of a particular type of a class.


The class paradigm allows one to encapsulate data so that specific data values are those using the data cannot see function implementation. Encapsulation makes is possible to make the changes in code without breaking other programs that use that code. If for example the implementation of a function is changed, the change is invisible to the programmer who invokes that function, and it does not affect his/her program, except hopefully to improve it.




Java includes inheritance, or the ability to derive new classes from existing classes. The derived class, referred to as the parent class. A subclass can add new data members to those inherited from the parent class. As far as methods are concerned, the subclass can reuse the inherited methods as it is, change them, and/or add its own new methods.


Java Makes It Easy To Write Correct Code:
         
In addition to being portable and object oriented, java facilitates writing correct code. Programmers spend less time writing java code and a lot less time debugging it. In fact, development time reduces by as much as two thirds.


SYSTEM DESIGN

4. System Design: DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT

4.1. Data Flow Diagrams:

The data flow diagrams from the important modeling tools in the structure system analysis methodologies.  The data flow diagrams are on of the most important tools used by system analyst.

Data flow diagram should be the first tool used by the system analyst to model system components.  There are three kinds of system components.

1.     Process
2.     Entity
3.     Data flow

1. Process:

Processes show what system does.  Each process has one more data inputs or more data outputs.  Circles in a DFD represent processes.  Each process has a unique name and number.  This name and number appear inside the circle that represents the process in a


2. External Entities:

External entities are outside the system they either supply input data into the system or use the system output.  They are entities over which the designer has no control.  They may be organizational customers or other bodies with which the system interact.  External entities may be represented by a square or rectangle.  External entities that supply data into a system are sometimes called sources.  External entities that use the system data are sometimes called sources.  External entities that use the system data are sometimes calls sinks.

3. Data flows DIAGRAM: DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT


Data flows model the passage of the system and are represented by lines joining the system components.  An arrow indicates the direction of the flow and the lines is labeled by the name of the data flow.  Flow of data in the system can take place.


5.2. Database Description: DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT



User


Field
Data type
Constraint
Userid
Varchar2 (50)
Primary key
Password
Varchar2 (50)

Fname
Varchar2 (50)

Lname
Varchar2 (50)

Initials
Varchar2 (50)

Designation
Varchar2 (20)

Job
Varchar2 (20)

Store_code
Number (10)
Foreign key
Timestamp
Varchar2 (100)

Macaddress
Varchar2 (100)


Designation


Field
Data type
Constraint
Designation
Number (10)
Primary key
Short_name
Varchar2(20)

Full_name
Varchar2(50)







Organization


Field
Data type
Constraint
Organisationid
Varchar2 (10)
Primary key
Org_short_name
Varchar2 (50)

Org_full_name
Varchar2 (200)

Address
Varchar2 (100)

Street
Varchar2 (100)

City
Varchar2 (100)

Phone
Varchar2 (50)

url 
Varchar2 (50)


 

Log table


Field
Data type
Constraint
Userid
Varchar2(50)
Foreign key
Appname
Varchar2(50)

Operation
Varchar2(100)

Date
Date


Issues

Field
Data type
Constraint
Sib_slno
Varchar2 (20)
Primary key
Sib_number
Varchar2 (20)

Date
Date

Receiving_section
Number (10)

Receivers_name
Varchar2 (150)

Receivers_designation
Varchar2 (50)

Tda
Varchar2 (20)

Work_order_number
 Varchar2(100)

Remarks
Varchar2 (100)

Store_id
Varchar2(20)

Userid
Varchar2(50)
Foreign key
Timestamp
Timestamp

Macadderess
Varchar2(50)

Reqno
Varchar2(100)

Reqdate
Date

Work_order_date
Date

Scheme
Number(10)










Issues-items

Field
Data type
Constraint
Sib_slno
Varchar2 (20)
Primary key
Item_id
Varchar2 (20)

Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (20)
Foreign key
Timestamp
Timestamp

Macadress
Varchar2 (20)

Reqno
Varchar2(20)

Reqdate
Date

Flag
Varchar2(20)



Issues_corr

Field
Data type
Constraint
Sib_slno
Varchar2 (20)
Primary key
Sib_number
Varchar2 (20)

Date
Date

Receiving_section
Number (10)

Recievies_name
Varchar2 (150)

Receivers_designation
Varchar2(50)

Tda
Varchar2 (20)

Work_order_number
Varchar2(100)

Remarks
Varchar2 (1000)

Store_id
Varchar2(20)

Userid
Varchar2 (50)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2 (50)

Reqno
Varchar2(100)

Reqdate
Date

Work_order_date
Date

Scheme
Number (10)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macadress
Varchar2(50)







Issue_item_corr

Field
Data type
Constraint
Sib_slno
Varchar2 (20)
Primary key
Item_id
Varchar2 (20)

Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (50)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2 (50)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macaddress
Varchar2(50)



Issues_item_corr

Field
Data type
Constraint
Sib_slno
Varchar2 (20)
Primary key
Item_id
Varchar2 (20)

Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (50)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2 (50)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macaddress
Varchar2(50)




Getpass

Field
Data type
Constraint
Gpslno
Varchar2 (20)
Primary key
Sib_slno
Varchar2 (20)

Reqno
Varchar2 (100)

Reqdate
Date

Item_id
Varchar2 (50)

Pqty
Double

Vehicle_no
Varchar2 (50)

Remarks
Varchar2(500)

Userid
Varchar2(50)
Foreign key
Timestamp
Varchar2(50)

Macadress
Varhcar2(50)



Getpass_diversion

Field
Data type
Constraint
Gpslno
Varchar2 (20)
Primary key
Sib_slno
Varchar2 (20)

Reqno
Varchar2 (100)

Reqdate
Date

Item_id
Varchar2 (50)

Pqty
Double

Vehicle_no
Varchar2 (50)

Remarks
Varchar2(500)

Userid
Varchar2(50)
Foreign key
Timestamp
Varchar2(50)

Macadress
Varhcar2(50)





Sis-Item

Field
Data type
Constraint
Item_id
Varchar2 (20)
Primary key
Item_name
Varchar2 (200)

Min_stock
Number (10)

Max_stock
Number (10)

Units
Varchar2 (50)

Bin_card
Varchar2 (100)

Qty
Double

Ledger_folio
Varchar2(300)

Major_head
Varchar2(10)

Submajor_head
Varchar2(10)

Minor_head
Varhcar2(10)

Storage
Varchar2 (10)





Sis-item_new

Field
Data type
Constraint
Item_id
Varchar2 (20)
Primary key
Item_name
Varchar2 (200)

Min_stock
Number (10)

Max_stock
Number (10)

Units
Varchar2 (50)

Bin_card
Varchar2 (100)

Qty
Double

Ledger_folio
Varchar2(300)

Major_head
Varchar2(10)

Submajor_head
Varchar2(10)

Minor_head
Varhcar2(10)

Storage
Varchar2 (10)




Sis-item_old

Field
Data type
Constraint
Item_id
Varchar2 (20)
Primary key
Item_name
Varchar2 (200)

Min_stock
Number (10)

Max_stock
Number (10)

Units
Varchar2 (50)

Bin_card
Varchar2 (100)

Qty
Double

Ledger_folio
Varchar2(300)

Major_head
Varchar2(10)

Submajor_head
Varchar2(10)

Minor_head
Varhcar2(10)

Storage
Varchar2 (10)



Sis-item_new1

Field
Data type
Constraint
Item_id_new
Varchar2 (20)
Primary key
Item_id_old
Varchar2 (20)
Foreign key
Ledger folio
Varchar2 (15)

Units
Varchar2 (100)

Name
Varchar2 (20)

Stork
Number (15,5)

Price
Number (20,2)

Value
Number (25,2)

Account
Varchar2(20)

Mhead
Varchar2(5)

smhead
Varhcar2(5)



Sis_diversion_items

Field
Data type
Constraint
Isd_slno
Varchar2 (20)
Primary key
Item_id
Varchar2 (20)
Foreign key
Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (20)

Timestamp
Timestamp

Macaddress
Varchar2(50)

Reqno
Varchar2(50)

Reqdate
Date

Flag
Varchar2(10)



Sis_diversion_modifications

Field
Data type
Constraint
Srb_modno
Varchar2 (20)
Primary key
Isd_slno
Varchar2 (20)
Foreign key
Date
Date

Order_number
Varchar2 (100)

Storied
Varchar2 (20)

Receiving_storeid
Varchar2(20)

Remarks
Varchar2(1000)

Srb_number
Varchar2(20)

Userid
Varchar2(20)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2(50)

Requisition_no
Varchar2(50)

Requisition_date
Date

Diversion_order_date
Date

Flag
Varchar2(10)



Sis_item_types

Field
Data type
Constraint
Type_id
Varchar2 (20)

Type_name
Varchar2 (20)
Foreign key


Sis_diversion_items_corr


Field
Data type
Constraint
Isd_slno
Varchar2 (20)

Item_id
Varchar2 (20)
Foreign key
Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (50)

Timestamp
Timestamp

Macaddress
Varchar2(50)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macaddress
Varchar2(50)

 

Sis_diversion_corr


Field
Data type
Constraint
Isd_slno
Varchar2 (20)

Date
Date

Order_number
Varchar2 (100)

Storied
Varchar2 (20)

Receiving_storied
Varchar2 (20)

Remarks
Varchar2(1000)

Srb_number
Varchar2(20)

Userid
Varchar2(50)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2(50)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macaddress
Varchar2(50)

Requisition_no
Varchar2(50)

Requisition_date
Date

Division_order_date
Date

  
Si_devolution_item2_corr

Field
Data type
Constraint
Dev_slno
Varchar2 (20)
Primary key
Item_id
Varchar2(20)
Foreign key
Quantity
Number (10)

Price
Number (10)

Userid
Varchar2 (50)
Foreign key
Timestamp
Timestamp

Macaddress
Varchar2(50)

E_userid
Varchar2(50)

E_timestamp
Timestamp

E_macaddress
Varchar2(50)



Form 13

Field
Data type
Constraint
Slno
Varchar2 (20)
Primary key
Srb_slno
Varchar2(20)

Status
Varchar 2(1)

Timestamp
Timestamp



Updates

Field
Data type
Constraint
Storied
Varchar2 (20)
Primary key
Client_time
Timestamp

Server_time
Varchar2(20)

Hwaddress
Varchar2(20)

Userid
Varchar2(50)
Foreign key


Tda

Field
Data type
Constraint
Tda_slno
Varchar2 (20)
Primary key
Branched
Varchar2(20)

Branch_name
Varchar2(20)

User_id
Varchar2(50)
Foreign key
Timestamp
Varchar2(50)

Macaddress
Varchar2(50)



Pricing

Field
Data type
Constraint
Ledger_folio
Varchar2 (20)

Stock
Varchar2(20)

value
Number (20,2)


  
Sis_price_list

Field
Data type
Constraint
Pl_slno
Number (10)

Branched
Varchar2(20)
Foreign key
Date
Date

Item_id
Varchar2(20)
Foreign key
Price
Number (20,2)

Stock
Number (20,5)

Table_name
Varchar2(50)

Row_id
Varchar2(20)

                     

SYSTEM TESTING

6. System Testing: DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT


The development of Software system involves a series of production activities.  There is a chance of errors to occur at any stage.  Because of human inability to perform and communicate with perfection, a Quality Assurance Activity accompanies software development.

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation.

The increasing visibility of software as a system element and the costs associated with software failure are motivating forces for well planned, thorough testing.

For testing the system we followed the strategies given below.

Testing Techniques:

Different types of testing are

v Boundary Condition Testing
v Integration Testing
v Black Box Testing
v Validation Testing
v User Acceptance Testing


During the implementation for the system each module of the system is tested separately to uncover errors within its boundaries. User interface is used as a guide in this process. The validations have been done for all the inputs using Java Script.

For example to check whether the work allotted among the database correctly without exceeding the schemes which are not validated thoroughly and the internal database has to check the reflections in the database.

Boundary conditions Test:

Boundary conditions as in case of generating sequences were tested to ensure that the module operates properly at boundaries establish to limit or restrict processing also it is able to handle incorrect out of the boundary values properly.

Integration Test:

The objective of Integration Test is to take the until tested modules and build a program structure that has been defined in the design.  We have done top down integration, which is constructing and testing small segments where errors are easier to isolate, and correct. The integration process was performed in three steps:

Ø   The main control was used as test driver.
Ø   Test was conducted as each module was integrated.
Ø   Regression testing to ensure that new errors have not been introduced due to the corrections.

Block Box Testing:


It focuses on functional requirements of the software.  Block box testing attempts to find errors in the following categories.

Incorrect or missing function
Interface error
Errors in external device access
Performance error
Initialization and termination errors

The above testing was successfully carried out for the developed system.

Validation Testing:


At the culmination of integration testing, software is completely assembled as a package, interfacing errors have been uncovered and corrected, and a final series of software tests namely validation tests are performed.  Validation succeeds when the software functions in the manner that can be easily accepted by the customer.

After validation test has been conducted, one of the possible condition is satisfied. The functions or performance characteristics confirmed to specifications are acceptable. The deviation form specifications are uncovered and a note of what is lacking is made. The developed system has been tested satisfactorily to ensure its  performance is satisfactory and it is working efficiently.




User Acceptance Testing:


User acceptance of a system is a key factor for the success of any system.  The system under consideration was tested for user acceptance constantly, by keeping the users informed of the progress and incorporating changes suggested, at the development time itself.


Test Case Report:


Here we specify all the test cases that are used for system testing.  The different conditions that need to be tested along with the test case used for testing those conditions and the expected outputs are given.  The goal is to test the different functional requirements.  Test cases have been selected for both valid and invalid inputs.


S.No
Test case
Condition
Expected Output
1
Get Systems
Input Domain name
Print list of all system in current domains & response time
2
Get User
Input Domain name
System id, user id, port no, domain name
3
Get Processes details
Select process
Output the details of processes
4
Get modules details
Select process & select thread opt
Details of modules
5
Get thread details
Select process & select thread opt
Details of threads
6
Stop the processes
System id, user id, password
Process close
7
Stop the system
System id
System close


Testing Analysis:


S.No
Testing object
Expected value
Simulated value
Explanation
Remarks
1
User name & Password
AEIND
GUEST
AEIND
GUEST
Equal of expected and simulated values
Pass
2
User name & Password
AEIND
GUEST
AEIND
GUEST
Unequal of expected and simulated value
Fail
3
Change password
GUESS
GUEST
(Old password)
Equal of these two passwords
Pass
4
Start time and end time
11:03:05
11:03:05
Equal of these times
Pass
5
Start date and end date
02/01/2006
02/01/2006
Equal of these dates
Pass


SCOPE OF THE PROJECT


7. Scope Of The Project: DEPARTMENTAL STORE MANAGEMENT SYSTEM PROJECT


Stores Management System :

The proposed system is ‘Stores Management System ’. This system is GUI based system and is user friendly. Stores Management System  is accessible through the internet. Stores are required for the following purposes.

1.     Capital works
2.     Operation and Maintenances Works
3.     Other Commercial activities like hiring equipment etc..,

The ‘Stores Management System  package’ is targeted to automate the almost all of the processes mentioned above to reduce the clerical labour of the staff working in Stores both technical and as well as Accounts departments using the software industry’s latest technologies and cost effective tools there by providing the better control to the management by avoiding manual errors etc..,
    
This application discusses the initial screens like login, logout and main menu of the application. The application can be accessed by typing the URL in the address bar of the web browser like Internet Explorer. The URL is of the format http://localhost:8080/contextname on which it will invoke login screen.

The stores operations as per the stores manual have been described as two different processors owing to the complexity and tediousness of the operations by effective division of labour as physical receipts and issue has been the responsibility of Accounts section.

To solve the problem using computer systems for which the complexity and tediousness is not an issue, the pricing is calculated at the time of receiving the materials itself and stock price will be fixed then and there and fetching that price while issuing the material.

The software package is described in detailed below. The package provides three basic functionalities

1.     Material Receipts Module
2.     Material Issues Module
3.     Different Reports serving the Quantity ledgers, Priced ledgers and material indexing and ledger folio indexing etc.

In this project Issues module and Reports module have been handled.
7.1. Issues Module:

The Issues Module deals with the issues functionality of the application. In this Module, there are different operations performed under issues function.

1.     Material Issues
2.     Inter Stores Issues
3.     Gate Pass Generation

1. Material Issues:

Material Issues to works based on field requisitions.

In this New Material Issues, it has two parts. The top portion is called Header area and bottom portion is called detailed area. Enter the data in all fields including detail area that is item details. After entering the data, press Submit button. If we try to submit with out filling any field, appropriate error message indicating the same will be thrown. Facilities are there to enter multiple items for a requisition by pressing the ‘Add_Item’ button in the detail area. Provision is also there to enter multiple requisitions in an Issue by pressing the ‘Another Requisition’ button in the bottom of the screen. On pressing the Submit button a screen will be displayed which gives a message ‘Is Given Information Correct’. If you press ‘Yes’ button a Print screen is shown & if you press ‘No’ button then again it will enter into material issues form.

After printing this page, these transactions will be received by another user.

2. Inter Stores Issues:

Material is issued to other stores based on Inter store Requisitions.
In this Inter Stores Issues, for processing ‘Inter Stores Issues’ truncation we have to select the ‘Inter Stores Issues’ link of the Issues Menu. The processing will be same as explained in the above with slight modification in header area.


3. Gate Pass Generation:


By selecting the ‘Material Issues Gate Pass’ link in the Issues main menu page you will be taken to selection of gate pass page. To issues a gate pass for the Issue we have to select edit link of that Issue.

By checking the required material you want, send in a particular vehicle by selecting the check boxes against those materials and by providing the vehicle no in the text field provided and submitting the page by pressing the ‘Submit’ button.
                     
If you press the Issue button then gate pass process will be generated & printable gate pass will be displayed. If you press the cancel button the gate pass generation will be canceled.

7.2. Reports module:


In this module, we will discuss about various Reports provided by the Application. There are different reports forms in this module.

There are
1.     Monthly SRB Report
2.     Monthly SIB Report
3.     Single Work Order Wise Report
4.     Section Wise Stores Issues
5.     Monthly Stores Abstract
6.     Stock Report


1. Monthly SRB Report:

This Report will display the Monthly Receipts i.e. all New Material Reports. Devolutions from works and Receipts from other stores will be available. Selection of monthly SRB Report will take you to the following selection screen to enable you to specify the year, starting month and ending month for which the details are required.

2. Monthly SIB report:

This Report displays the details like slno, sibno, requisition no…etc of the material issues i.e. both issues to the field, issues to the other stores.

3. Single Work Order Wise Report:

This report will display the details of the transaction i.e., devolutions and Issues grouped on work orders no and accounts code (TDA code).


4. Section Wise Stores Issues:

This report will display the issues details, for the month /month’s specified initial selection screen of the report, grouped on DA wise i.e. Accounts code wise.


5. Monthly Stores Abstract:

This report will also provide the same details of the items as that of Monthly Pricing Ledger except abstract values of quantities and values of all receipts and all issues for each material with in the specified dates and opening balances and closing balances.

6. Stock Report:

This Report will display the stock balances i.e., closing balances of all materials at the end of the selected month or present day’s closing balance if the selected month is current month.

3 comments:

Unknown said...

I download the project source code but I unable to understand how to use them so please help me

Nitin Shah said...

Great Article . Thanks for sharing. Store Management Course

VJES said...

Thrilled to pursue the PG Diploma in Digital Marketing at Vidya Jyoti Eduversity. Excited for the advanced learning opportunities ahead!

G+

Pages