Escolar Documentos
Profissional Documentos
Cultura Documentos
Submitted By:
INDEX
S.NO CONTENT PAGE NO.
1. INTRODUCTION 4
Acknowledgement 5
Objective 6
Study of System 8
Hardwares Used 16
Softwares Used 17
Limitations 18
Hardwares Used 18
Softwares Used 19
Methodology 20
PERT Chart 22
Implementation Phase 26
Code Snippets 27
6. FLOW DIAGRAM 35
7. DATABASE 36
ER-Diagram 36
Tables 38
8. OUTPUT SNAPSHOTS 43
9. TESTING 53
10. MAINTENANCE 54
11. CONCLUSION 55
12. LIMITATIONS 56
14. BIBLOGRAPHY 58
DATE OF SUBMISSION:
SUBMITTED TO:
CFEES, DRDO,
Ministry of Defense,
Timarpur, Delhi
ACKNOWLEDGEMENT
I express my sincere gratitude and thanks to Mrs.Alka Diwan, Scientist-F, for providing me the
excellent opportunity to do a project on CSD Online Shopping & Inventory Management
System and providing me with all the essential elements required for the completion and
enhancement of this project.
I am also grateful to Mr. S D Gupta, Technical Officer-C, for his expert guidance and
cooperation in making my project a learning and worthwhile experience.
I would like to thanks those respondents who have taken pain in successful completion of my
project work.
OBJECTIVE
One will definitely prefer to lap up a system, which is cost effective yet highly efficient,
easy to install and operate. It is here that Canteen Inventory Management System (CIMS)
is fast gaining its foothold in companies as an easy cost saving tool for CSD Canteen
Management. The objective of the system is to reduce the work load of the operator right
from stocks to selling goods. The system should maintain a detailed account of all
provisions bought and goods sold at the canteen. In addition to this, it should also
maintain the daily report of canteen sales & shopping quota of registered members. The
system should provide an interface to payroll for deductions. Several inquiry facilities
should also be provided to view the expenses incurred/ planned menus/cash payment etc.
In short following are the list of facilities that should be provided with the system: list of
items available with rates, stock left, transactions’ summary, damages and demands,
The objective of the project is to develop a CSD Online Shopping and Inventory
Management System meeting the needs of employees and reducing the rush at CSD
Canteen.
The computer application development life cycle can be thought of six main steps, which are:
2. Study Phase
3. Feasibility phase
4. Definition phase
5. Design phase
6. Implementation phase
7. Maintenance phase
i. System Administrator:
A. Master Maintenance:
Masters essential for running CIMS application are maintained. Masters like
Shops, Counters, Users, Inventory, Profit Percentage, and Sales Tax are stored in
the database.
B. Rate Revision:
Apart from invoice, Rate revision can take place through Circulars. Whole Sale /
Retail Rate can be revised. Whenever Rate Revision is done, system logs the
impact on Stock Value for Bulk and all Minibulks.
C. User Maintenance:
a. The CIMS Users are defined. Each User has a default LOGIN ID, Shop and
Counter. A Secondary Shop can also be defined. It is relevant only when
Grocery and Liquor Bills can be cut from the same counter.
b. CIMS users are of two types – Supervisor and Operator. Supervisor can
perform all roles. But Operator cannot perform roles of Canteen Manager,
administrator, Card Issuer, OIC Liquor and Data Transferer.
c. The Roles can be assigned and unassigned.
B. Close Canteen:
a. At the end of the day, canteen is closed so that NO un-authorized user can access the
system.
b. STB cannot be done if Canteen is not close.
c. Month Closing can be done only if Canteen is Close.
d. All the Draft Vouchers exceeding the grace period are deleted.
e. All Non-Finalized Sale / Refund Bills are deleted and its history maintained.
C. Finalize Invoices:
a. Material Inward, Receipts from Depot, is finalized by the Manager.
b. Price Variation can occur upon finalization.
c. Case Pack of an item can get changed.
d. Items not demanded can be received.
D. Month Closing:
a. When New Month starts, System forces for Month Closing.
b. It can be done only if Canteen is Close.
c. It cannot be proceeded, if any Non-Finalized STB exists.
d. The Ledger Balance becomes the New Month’s Opening.
e. If besides Month Closing, a New Year also is starting then the Voucher Numbers are
initialized.
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
11
Project Report CSD Online Shopping and Inventory Management System
E. Approve Refunds:
a. A Bill can be refunded from the respective shop by any salesman only if it has been
approved for Refund.
b. Bill can be refunded partly or wholly. That is, only one item or more than one item
can be refunded. The Original Quantity of item can be refunded fully or partly as
maybe the case.
c. Once a Bill has been refunded, its status is updated to ‘Close’. Salesman does not see
that Bill for refund. But, Manager can view the status of all the Bills approved for
Refunds.
c. Civilians:
Entitled only for Single Grocery Card
B. Liquor Billing:
a. There is Daily, Fortnightly and Monthly Quota. A member can buy liquor as per
the balance quota.
b. If a person has not availed fortnightly quota before 15th of the month then
remaining balance can be bought after 15th.
c. Monthly, Fortnightly, Daily consumption gets initialized every month
C. Grocery Billing:
a. Monthly NON AFD consumption gets initialized every month
b. Yearly AFD consumption gets initialized every year
D. Refund:
a. A refund can be made only if Manager approves the Bill for Refund
b. Refund of a Bill can be whole or in parts
F. Summaries:
Three summaries can be generated:
a. General Sales
b. Refund Sales
c. Net Sale (General Sales – Refunds)
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
13
Project Report CSD Online Shopping and Inventory Management System
v. Shop/Bay Incharge:
A. Material Return from Minibulk to Bulk
C. STB:
a. STB can be done any day during the Month
b. The canteen has to be close
c. The Material transferred to Damage Stores is reflected in ‘Condemn’ column of STB.
d. On Finalization, the Ground Balance declared in STB becomes the Ledger Balance of
Minibulk Inventory Master
D. Raise Demand:
a. Demands are raised when Bulk needs to be replenished with Stock.
b. Bulk Incharge has to enter Index Number and Quantity demanded.
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
14
Project Report CSD Online Shopping and Inventory Management System
F. STB:
a. STB can be done any day during the Month
b. The canteen has to be close
c. The Material transferred to Damage Stores is reflected in ‘Condemn’
column of STB.
d. On Finalization, the Ground Balance declared in STB becomes the Ledger
Balance of Bulk Inventory Master.
B. Return Vouchers:
a. It is the Material returned by Supplier against Replacement Voucher
b. In Lieu of Item sent for Replacement - Equivalent Amount can be received,
another item can be received, and same item with same quantity of different
quantity can be received.
B. Issuance:
a. Search is made in the Database and corresponding records meeting the criteria are
retrieved
b. Depending on the default values pertaining to respective category, the Entitlements
are displayed
c. In case of dependent card, all dependents of the Primary Card Holder, have same
NON AFD grocery entitlement
d. Flexibility is given where the customer can define the Grocery Entitlement on Primary
and Dependent Cards. But the sum total can never exceed the monthly entitlement
e. On successful issuance, Two reports are generated-
1. Acknowledgment Receipt
2. Letter to Customer
f. If card is not issued then Rejection Note is printed
Card Issue Failure Note
C. Issue Vouchers:
The gifts are issued to Customers through Issue Voucher
D. STB:
Gift STB is done to know the Gift Stock Position.
x. Data Transferer:
A. Data Transfer from Main Canteen to Extension Counter and vice versa
v HARDWARES USED
• RAM: 1 GB
• Std. Smart Card reader (for customer’s account login) Std. Smart card reader (for
master key by cashier) Printer (for paper bill)
• A monitor
• A CPU
v SOFTWARES USED
• Front End Language: Visual Basic
• If system fails all canteen work may halt. Canteen would remain close until
system starts working normally.
• In case of disk failure, all data may lose and might not be recoverable.
• Inconvenience to customer:
Usually, long queues for billing as registered employees/members shall
be shopping in their free time which is common in an organization (here,
Ministry of defense). Members have to visit canteen for shopping.
• New Business logic for user login through LAN using unique user-ID &
password.
v HARDWARES USED
• RAM: 1 GB
• Printer
• A CRT monitor
• A CPU
v SOFTWARES USED
• Front End Languages: JAVA server pages, HTML, JAVA script
• Database Used: ORACLE Architecture Employed: 2 tier Arch. OS: WIN Server
2003 (64 bit)
v METHODOLOGY
The project proceeded according to the steps of SDLC (Software Development Life
Cycle) that is in seven phases which include the following:-
1) Requirement Analysis: All the requirements are analyzed using verbal or written
questionnaires with CSD canteen shopkeeper & employees.
2) High-Level Design: The purpose of this phase is to design the overall functioning of the
proposed system and finalize the input and output format.
5) Testing: In this phase module level testing is performed with mock values.
6) Acceptance: At this time the software is actually provided to the company and checking
it according to need.
• Front-end
• Back-end
• Connectivity
When we use JAVA as software development tool, connectivity code is written as a part of
front-end code itself.
FRONT-END
It has been coded so as to provide maximum user friendliness and ease. Stress is laid on the
point that the user should type as minimum as possible. Most of the work is done in few
clicks. From each page, jumps to the other pages are provided.
These event-linked functions contain connection string (which connects front-end with
applications) and queries, which are executed when the corresponding event occurs.
BACK-END
Database is designed using Oracle. Our main databases required for this application are: stock
item details, customer details, & username and password details of customers.
All tables are normalized and do not have redundant or unwanted records.
CONNECTIVITY
A connection string is used to connect the queries written in front-end codes with the
database.
Provider used—sun.jdbc.odbc.JdbcOdbcDriver ()
PERT CHART
Activity Time
Coding 14 days
Maintenance none
ANALYSIS
Analysis can be referred to as study of a problem and its division into smaller modules so as
to solve particular problem. A complete understanding of software requirements is necessary to
help the new software being developed succeed. No matter how well designed or well coded, a
poorly analyzed and specified program will disappoint the user and will also be a burden to
the developer. At this stage comes Requirement analysis that is a process of discovery,
refinement, modeling and specification. Models of the required data, information and control
flow are created. It bridges together the gap between system-level software allocation and
software design.
The first step of the development of system is the need of a new system. This might be a user
request to change, improve or enhance an existing system. This step Determine whether the
request is valid and feasible or not before improving or modifying the current system or build a
new one.
At this stage, the user’s requirements are determined with the help of prototyping, asking
question and obtaining information from the existing system.
Once the problem is clearly determined, the problem is defined in terms as to what is required,
how etc.
4. Background Analysis:
Once the project is initiated, the analyst begins to learn about the setting, the existing system
and the physical processes related to the revised system. All the background information is
collected and thoroughly studied. After obtaining background knowledge, the analyst begins
to collect data on the existing system, output, input and costs with the help of written
documents, on site observations, interviews and questionnaires.
5. Fact Analysis:
After gathering data, they must be organized and evaluated and conclusions drawn for preparing
a report to the users for final review and approval. At this stage, some tools are used i.e. data
flow diagrams, decision tables, structure charts etc.
1. Initial Investigation:
We saw that there were very few sites that could give complete information about air
management system to the users. Also there was a need to automate the entire system
We contacted a number of people about this Project who agreed with the idea that this system
will help a lot many people rather that entire nation.
Problem definition is an initial investigation, which defines the problem that led to the user
request. It states the objectives the user is trying to achieve and the user wants to see. It gives
more stress on logical requirements than the physical requirements.
4. Fact Analysis:
All the data and information collected was organized to show how information flows and at
what stage, exactly what happens? For this we tried to explain this with the help of Data Flow
diagrams.
IMPLEMENTATION PHASE
The implementation phase is less creative than system design. It is primarily concerned with
user training, site preparation, and file conversion. When the candidate system is linked to
terminals or remote sites, telecommunication network and test of the network along with the
During the final testing, user acceptance is tested, followed by user training. Depending on the
nature of the system, extensive user training may be required. Conversion usually takes place
In the extreme, the programmer is viewed as someone who ought to be isolated from other
aspects of the system development. Programming is itself design work, however. The initial
Programming provides a ‘reality test’ for the assumptions made by the analyst. Therefore, it is a
CODE SNIPPETS: A few important highlights of the code are unveiled below.
<td>
<%=rs.getString("cardHolderName")%>
</td>
<td>
<%=rs.getString("rank")%>
</td>
<td>
<%=rs.getString("contactNo")%>
</td>
<td>
<%=rs.getString("smart_cardNo")%>
</td>
<td>
<%=rs.getString("department")%>
</td>
<td>
<%=rs.getString("maritalStatus")%>
</td>
<td>
<%=rs.getString("cardIssueDate")%>
</td>
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
30
Project Report CSD Online Shopping and Inventory Management System
<td>
<%=rs.getString("cardValidityDate")%>
</td>
<%
}
} catch (Exception ex) {
out.println("\nERROR: DATABASE NOT FOUND! \n
PLEASE Look into CustomerLoggedIn.jsp\n" + ex);
}
%>
<script language="JavaScript">
function cart() {
if (window.XMLHttpRequest) {
// // code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
} else {
// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
xmlhttp.onreadystatechange=function() {
if (xmlhttp.readyState==4 && xmlhttp.status==200) {
document.getElementById("daba_cart").innerHTML="";
document.getElementById("daba_cart").innerHTML =
xmlhttp.responseText;
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
31
Project Report CSD Online Shopping and Inventory Management System
}
}
function chintu() {
if (window.XMLHttpRequest) {
// // code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
} else {
// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
xmlhttp.onreadystatechange=function() {
if (xmlhttp.readyState==4 && xmlhttp.status==200) {
document.getElementById("daba2").innerHTML="";
document.getElementById("daba").innerHTML=xmlhttp.responseText;
}
}
xmlhttp.open("GET","Search.jsp?index=" + index.value + "&item=" +
item.value + "&category=" + category.value, true);
xmlhttp.send();
}
</script>
<%
try {
pst = con.prepareStatement("Select * from Item ");
rs = pst.executeQuery();
while (rs.next()) {
%>
<hr>
<tr>
<td>
<%=rs.getString("SNo")%>
</td>
<td>
<a href="BillGeneration.jsp?index=<% out.print(temp); %>">
<%=rs.getString("indexNo")%>
</a>
</td>
<td>
<%=rs.getString("itemName")%>
</td>
<td>
<%=rs.getString("ratePerUnit")%>
</td>
<td>
<%=rs.getString("quantity")%>
</td>
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
33
Project Report CSD Online Shopping and Inventory Management System
<td>
<%=rs.getString("salesTax")%>
</td>
<td>
<%=rs.getString("category")%>
</td>
</tr>
<%
}
} catch (Exception ex) {
out.println("\nERROR: PLEASE Look into Search.jsp \n " + ex);
}
%>
FLOW DIAGRAM
DATABASE
ER-DIAGRAM: The entity relationship diagram is shown on the next page.
Some of the attributes’ names are explained below.
• quantity: it represents the number of units available in the stock of each item i.e.,
ledger balance.
• shopLimit: it stores the upper limit (in INR) of amount up to which an employee
could shop each month. Upper limit is set as per organization’s policy.
Meaning of rest of the attributes, entity sets and relationship sets are understood as per their
names.
TABLES:
v Table “SalesSummary”: This table maintains the log of all the successfully
completed transactions.
v Table “LogIn”:
v Table “CustomerLoggedIn”:
v Table “Item”:
v Table “SalesSummary”:
v Table: “Temporary”:
OUTPUT SNAPSHOTS
LogInPage
LogInPage=>Administrator=>AdministratorLoggedIn
CUSTOMER LOG-IN:
LogInPage=>Customer
TESTING PHASE
Testing is the process of making sure that the programs perform the intended tasks. Once the
system is designed it should be tested for validity. During system testing, the system is used
experimentally to insure that the software does not fail, that means it will run according to
its specification and in the way users expect it to. The system is tested with special test data and
the results are examined for their validity. Some of the users may be permitted to operate on
the system so that the analyst can ascertain that the system can work in the specified
environment.
Test Details:
MAINTENANCE PHASE
After the installation phase is completed and the user staff is adjusted to the changes created by
the candidate system, evaluation and maintenance begin. Like any system, there is an aging
process that requires periodic maintenance of hardware and software. If new information is
inconsistent with the design specification, then changes have to be made. Hardware also
required periodic maintenance to keep in tune with design specification. The importance of
User priorities, changes in organization requirements, or environmental factors also call for the
CONCLUSION
The efficiently performing running application for electronic information retrieval and
ü User can search & select the item(s) from the available lost of stock items.
ü Present mode of payment is via cash or cheque due unavailability of extensive special
devices required for other modes of payment.
ü Manager is provided with rights to search, add, delete and modify stock items’ list.
ü Manager is provided with rights to add, search & delete user details and login
details.
ü User can print report from any form (provided printer should be available)
LIMITATIONS
As such every project has some limitations so this project does. Limitations are mentioned
below.
Ø For successful implementation of the project, we should have a proper network system
where every transaction made should be updated in the server database. Inaccessibility
of internet/intranet.
Ø As this project deals with personal and important data thus requires every security.
Ø More features could be incorporated to facilitate employees additional services and easy
modes of payments.
Ø More features and rights could be incorporated in administrator module for implementing
new services for employees.
FUTURE ENHANCEMENTS
The following additions can be made in future to improve or upgrade the performance of the
application.
BIBLIOGRAPHY
Web sites:
1. www.w3schools.com
2. www.centerkey.com
3. www.java.sun.com
4. www.javaranch.com
Other:
Analysis of on the job Inventory Management System at CSD shop along with
operating staff.
_____________________________________ J _____________________________________
CFEES, DRDO, Ministry of Defense, Timarpur, Delhi
58