Air Force Canteen Management System

AIR FORCE CANTEEN MANAGEMENT SYSTEM
Indira Gandhi National Open University

इइंददिरर गरइंधध ररष्टट्रीय ममक्त वविश्विवविद्यरलय
Maidan Garhi, New Delhi-110068, INDIA
Project Detail:-
CONTROL NO : 178
ENROLMENT NO : 158659654
PROGRAMME : BCA
NAME OF THE LEARNER : AMAN KUMAR
EVALUATOR CODE : R29-E13
DATE OF VIVA-VOCE : 17/05/19
TITLE OF THE PROJECT REPORT :
AIR FORC CANTEEN MANAGEMENT SYSTEM
1
Synopsis
2
2. INTRODUCTION
Canteen Management System (CMS) also Known as Canteen Stores Department
(CSD) has been in the service of the Defence Services for more than five decades.
CMS provides its consumers, all over the country, quality products of daily use at
rates less than those prevailing in the market. These items are meant for sale to
troops, ex-servicemen and their families. So in present context it is necessary for the
management to have a computerized management & control system for manage
the resources as accurately as possible also to increase the facilities to the users. The
Management by itself does not come in direct or daily contact with its customers.
Only Managers/In-Charges (ICs) interact with the CMS Area Depots. It is,
therefore, necessary that these persons must really be aware of what their
customers' need. Needless to say, the Department continues to be scrutinized every
day by the customers for availability, rates and range of the products.
Main Objectives of CMS are:
 Provide consumer goods of high quality to the troops wherever they are at
prices cheaper than the prevailing market rates, as far as possible.
 Ensure that the level of consumer/customer satisfaction is maintained at the
maximum.
 Generate reasonable profitability to sustain the organization, permit growth
and provide additional facilities for troops and their families.
 Formulate and execute development programmes to improve and maintain
organizational effectiveness.
 Periodically analyze and assess the diverse long-term needs and aspirations
of Defence Services and undertake timely measures to meet them.
In this paper, we present the development of an application for CMS to benefit the
Canteen administration and staff for better decision making process, resulting in
providing better facilities and products to customers.
3
3. OBJECTIVES OF THE PROJECT
 The objective of the project is to design a computerized Canteen Management

System, automating the database and functioning of CMS.
 The Software would benefit the CMS by reducing the Workforce & tasks of
maintaining the database & creation and generation of Bills, Report &
Summary & updating the information.
 The project aims to reduce time spent in performing the various jobs in CMS,
as manual work will take a lot of time.
 The onetime cost of the system will be high, but then the running cost of the
system would be much lower than the cost in Current System as it will
reduce manpower & thus reducing salary payments.
 The System has to become Centralized so that Canteen Manager can control
& manage any of the System through its Centralized System. Air Force
Canteens are also Centralized state wise. As in Delhi the main depot of
Canteen is in Delhi Cantt. from where all other branches of Canteen in Delhi
are connected through this Centralized System.
4
4. PROJECT CATEGORY
This project is under the category of “RDBMS”.
This project aims to provide the improved functionality and better User Interactive
Environment. In this software information is handled by using MySQL for storing
records in a database, as backend and Java with NetBeans is used as front end.
Relational Database Management System has permeated every segment of

commercial world. They are required as the backbone of any information system. A
database is a mechanized, shared, formally defined, and centrally controlled
collection of data used in an organization. A database management system (DBMS)
is the software that controls access to the information stored in the database.
Although there are various approaches to the logical and physical organization of
data, today’s database environment is dominated by relational database
management systems (RDBMS).
Facilities offered by RDBMS:
 Creation of files, Addition of data, Deletion of data, Modification of data.

 The data stored can be sorted or indexed at user’s discretion or direction.
 Various reports can be produced from the system. These may either be
standardized reports or that may be specifically generated according to
specific user definition.
5
5. TOOLS/PLATFORM, HARDWARE & SOFTWARE

REQUIREMENTS SPECIFICATIONS
Software and hardware specification as the name suggests, tells us about the
various characteristics of the software and the hardware environment used i.e. the
development environment used. Here we specify various software languages,
supporting tools that have been used for the development of the system. These
tools and the languages have been used because of their relative ease of understand
and personal interest of the team developing the project.
TOOLS :
 Front End Tool : Java with Net Beans.
 Back End Tool : MySQL.
PLATFORM :
 WINDOWS 98 / WINDOWS XP
MINIMUM HARDWARE REQUIREMENT :
 PROCESSOR : PENTIUM IV PROCESSOR
 RAM : 512 MB
 STORAGE CAPACITY : 20 GB
 DRIVES : 52X CD
SOFTWARE REQUIREMENT :
OPERATING SYSTEM : WINDOW 98,XP
RDBMS : MySQL
LANGUAGES USED : JAVA WITH NETBEANS
6
SOFTWARE USED IN THE SYSTEM

The software selection was done after considering a few alternatives and
constraints imposed by the company. The following Software’s are used for
designing and implementing the system.
1. JAVA NETBEANS
NetBeans is an open-source project dedicated to providing rock solid software

development products (the NetBeans IDE and the NetBeans Platform) that address
the needs of developers, users and the businesses who rely on NetBeans as a basis
for their products. The two base products, the NetBeans IDE and NetBeans
Platform, are free for commercial and non-commercial use. The source code to both
is available to anyone to reuse as they see fit, within the terms of use. The NetBeans
project is also a vibrant community where people from across the globe can ask
questions, give advice, make various contributions, and ultimately share in the
success of our products.
Here, I build Canteen Management System (CMS) using Java NetBeans because
Java is Platform Independent and a Open Product which is freely available to all.
NetBeans consist of RAD tools which enable the programmer to create applications
in shorter time as compared to conventional Language.
With NetBeans IDE, we can develop applications by just creating frames, dragging
and dropping controls on to frames, setting properties for various things, adding
some application-specific code to handle events. Java offers more security to make
its programs safe and secure.
2. MySQL
MySQL is the world's most popular open source database software, with over 100
million copies of its software downloaded or distributed throughout it's history.
With its superior speed, reliability, and ease of use, MySQL has become the
preferred choice for Web, Web 2.0, SaaS, ISV, Telecom companies and forward-
thinking corporate IT Managers because it eliminates the major problems
7
associated with downtime, maintenance and administration for modern, online

applications.
Many of the world's largest and fastest-growing organizations use MySQL to save
time and money powering their high-volume Web sites, critical business systems,
and packaged software — including industry leaders such as Yahoo!, Google,
Nokia, YouTube, Wikipedia, and Booking.com.
In Canteen Management System (CMS) MySQL is used to store and manage large
amount of Data in a multi-user environment so that many users can concurrently
access the same data. A database server must also prevent unauthorized access and
provide efficient solution for failure recovery.
MySQL database system refer to the combination of a MySQL server instance and a
MySQL database. MySQL operates using client/server architecture in which the
server runs on the machine containing the database and clients connect to the
server over a network.
6. PROBLEM DEFINITION
 The System is manual. Hence a lot of manpower is required.
 The system is error prone due to high portability of mistakes in manual work.
 Information maintenance as paper work is complex task.
 As the data is very large, no Backup can be maintained.
 Modify the details of the Customer, Items etc. is a large procedure & may
lead to chaos.
 Analysis on data & access to databases is tedious task & large work force is
required.
 The process is prone to delays & cost ineffectiveness.
8
7. REQUIREMENT SPECIFICATIONS
7.1 FACILITATED APPLICATION SPECIFICATION

TECHNIQUES (FAST)
It is a work product of Team of End Users and Software Engineers that help in
understanding the Software demands completely. This approach encourages the
creation of a joint team or customers and developers to work together to identify
the problem, purpose elements of the solution, negotiate different approaches and
specify a preliminary set of solution requirements.
A meeting is conducted at a neutral site and attended by both Software Engineers

and Customers.
Before the FAST meeting, each FAST attendee is asked to make a List of Objects,
List of services, List of Constraints, Performance Criteria.
Based on our project I make all these Lists.
7.1.1 Requirements taken from Team of End Users
 List of Services
 Interact with Customer.
 Issue Canteen Card to Customer.
 Check the availability of items in the Database.
 Sale the Items to different Customers and Update Database
Information.
 Generate Bill for the Customer.
 Generate Canteen Summary and Report for the Organization.
9
 List of Constraints
 System must be User Friendly.

 The System must have a manufacturing cost less than or equal to
the calculated cost.
 List of Validations
 The Customer Details in the form for issuing Canteen Card should be
valid.
 The Customer Card number entered should be valid.
 For Defence Civilians card is valid up to the Date of Retirement.
 For Ex-Serviceman Card is valid for 1 year.
 For Dependents card is valid for 1 year along with parent card.
 Performance Criteria
 As the request for purchasing the items is made by the Customer the
items are selected and sold to the Customer through his/her account
and Bill is generated and the amount of Cash is deducted from the
Customer account automatically.
 System should update the database information frequently.
7.2 QUALITY FUNCTION DEPLOYMENT (QFD)

QFD is a Quality Management Technique that translates the needs of the Customer
into technical requirements for Software.
QFD identifies three types of requirements:-
10
Normal Requirements:- The objectives and goals that are stated for product or
system during meetings with the customer. If these requirements are presents, the
customer is satisfied.
Expected Requirements:- These requirements are implicit to the product or

system and may be so fundamental that the customer does not explicitly state
them.
Exciting Requirements:- These features go beyond the customer’s expectations

and prove to be very satisfying when present.
7.2.1 Normal Requirements for CMS :-

 Interact with Customer.
 Issue Canteen Card to Customer.
 Check the availability of items in the Database.
 Sale the Items to different Customers and Update Database Information.
 Generate Bill for the Customer.
 Generate Canteen Summary and Report for the Organization.
7.2.2 Expected Requirements for CMS :-

 Provide Gift Items for some Items selected by Customer if gifts are available
with those items.
 Amount of VAT provided should be lowest. VAT amount is calculated by

providing VAT% on the Items.
 If the Customer purchase any AFD Item then amount from his/her account
will not be deducted and if Customer purchase Non-AFD item then the
amount will be deducted from his/her account.
7.2.3 Exciting Requirements for CMS :-

11
 Interface i.e. form can be made attractive by using graphics.

 Answers to User inquiry can be in dialog boxes.
 Interface can be Menu Driven.
8. PROJECT PLANNING
The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, is necessary to coordinate activities and manage project risks
effectively. Project plans refine the information gathered during the initiation phase
by further identifying the specific activities and resources required to complete a
project. A critical part of a project manager’s job is to coordinate discussions
between user, audit, security, design, development, and network personnel to
identify and document as many functional, security, and network requirements as
possible.
During this phase, a plan is developed that documents the approach to be used and
includes a discussion of methods, tools, tasks, resources, project schedules, and
user input. Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning,
concept of operations, system security, verification and validation, and systems
engineering management planning.
8.1 FEASIBILITY OF PRODUCT

The feasibility of the product is a question that confirms reality to the ideas.
Feasibility test is critical. The dimensions that define feasibility of project are:
8.1.1 ECONOMICAL FEASIBILITY

Previously when Canteen Management Systems were handled manually then a lot
of manpower is used. Customer Canteen Card was not used at that time. All work
12
i.e. Billing, maintain Data was done manually. Three copies of each Bill (Customer
Copy, Office Copy and Depot Copy) was maintained by the Organization. Cost
involved was very high because at that time more Stationary & manpower was
used. So, the total cost involves is very high. Now the cost of computerized
Canteen Management System includes cost of a few components plus the cost of
developing the software. So, it is high but not as much high as in the past. Since the
manpower is reduced & cost of stationary is less. So we can say that Economically
the feasibility of the Software is High.
8.1.2 TECHNICAL FEASIBILITY

The Technical Feasibility is high as the software can be deployed on any machine
using some languages like JAVA,VB,C++,HTML etc.
8.1.3 ENVIRONMENTAL FEASIBILITY

The Software is simple; the User will find it very easy to perform all the required
jobs. It would also be very convenient for the members of Canteen Management
System as the Software is User Friendly & easy to use.
8.2 SOFTWARE MODEL USED

Now the major question is which process model is to be chosen for the
development of software and Why???
For this I can use THE INCREMENTAL MODEL.
I use this model, because it is a combination of Linear Sequential Model &

prototyping Model. In this Model, basic requirements of the Customer and Items
are addressed in the first increment, and many additional features are addressed in
the other increments as per the needs of the customer. So this model is appropriate
for this project.
13
9. DATA FLOW DIAGRAMS(DFD)
DFD serves two purposes:-
 To provide an indication of how data are transformed as they move through

the system, and
 To depict the functions ( and sub functions ) that transforms the data flow.
The DFD provides additional information that is used during the analysis of the
information domain and serves as a basis for the modeling of function.
10. ENTITY-RELATIONSHIP DIAGRAM (ERD)
Entity-relationship model is database analysis and design tool. It lists real-life

application entities, attributes of entities and relationships amongst entities. The
type of each relationship is also indicated. Entity-relationship model is represented
in graphical form.
14
DFD LEVEL 0
DEMAND
SYSTEM
CARD CUSTOMER
CANTEEN
CARD
CUSTOMER
CANTEEN SALESMAN
MANAGER COUNTER
ITEMS GROCERY
BILL
CUSTOMER
CANTEEN REPORT
CANTEEN
CARD MANAGEMEN
T SYSTEM
CANTEEN
SUMMARY
SALESMAN Information is stored

CUSTOMER
& update in the
ACCOUNT
Database.
SHOP
SYSTEM
ADMINISTRATOR
CANTEEN
MANAGEMENT
SYSTEM DATABASE
15
DFD LEVEL 1
CUSTOMER
SYSTEM Taking Card
CANTEEN
CARD information for login
CARD
the S/W
Login CMS
Software Issuing Customer
Daily Canteen Card
CUSTOMER
1.
Taking Customer
Details CUSTOMER
System Start ACCOUNT
Creating
Customer A/c
Stock
CANTEEN Will DEMAND
Enquire & Checking, Creating
MANAGER
perform Take info. , Demands & send
these task Issue Card, to depot
SYSTEM Create A/C 2.
Give permission
ADMINISTRATOR
SALESMAN
Give permission Generate,
COUNTER
Control Generate Counters
Counters,
SALESMAN Taking Salesman
permit
details
Salesman 3. GROCERY
BILL
ITEMS Generating the Bill
Get Items Details
Enter Pin
SHOP REPORT
Get Shop Details No., Sale Generate
Items , report
Get Customer Details Generate Bill

CUSTOMER
4. Generate
CANTEEN CARD
report CANTEEN
SUMMARY
Update DB
Generate
Items and
Canteen
Customer
Summary
Update DB A/c 5.
DAMAGE ITEMS Database
Generate
DATABASE Update DB updated
Update DB Canteen
Update DB
Summary &
GIFT ITEMS CUSTOMER A/C
DATABASE BULK DATABASE Report 6.
DATABASE
16
DFD LEVEL 2
Generate
System Administrator various counters Control all
3 Counters for
sale
3.1
Canteen Manager Stock Checking,
Get Customer
Information etc. Issue a Card
Customer 2 for Customer Customer Canteen Card
2.1
Customer A/C
Create
Customer A/C
Permit the salesman
For purchasing
for
2.2
sale
Demand
3.2
Check
availability of
stock 2.3
Salesman Counter
Salesman
Enter pin no. of Customer &
open
Customer A/C
Customer Canteen Card 4
Grocery Bill
Generate Bill
& Report
Items 4.2
Select Shop Type,
Items for Sale
Shop
4.1
Customer A/C
Database
Update
Customer A/C
5
Bulk
Generate
Database Generate
Update Canteen Canteen Summary
Canteen
Databases Summary
Summary
5.1 6.1
& report
6
Gift
Database Damage Generate Report
Database Report
6.2
ERD Rank
Demand_desc Demand_id
Demand_date
17 Demand
Create
Manager_id CName Gender Address
Scard_No Canteen_code
Put in
Canteen Manager System Card
Issue/Rene Card_SNo Pin_no Card_Type Name

Take & w DOR
fill Customer_Canteen_Card Rank
Personal_No
Rank Address
Gender Card_SNo
Has
Customer Salesman_id Put in
SName
Address
DOB Communicate
Name
Father_ PAN_no
Name Salesman
Gender
Address Counter_id
DOR Counter_id Counter_nam
e
Shop_Name
Has Counter_nam
Shop_id
e
Sale
Goto Salesman_Counter
Index_No Pluno_no
Price
Group
Purchase Items
Shop_Type
Item_desc
Cust_Acc_no Personal_No
Name Under Max_Qty
Balance
Has Shop_Name
Customer Account
Shop Select
Shop_Type
Bill_No
Bill_wise Item_wise Shop_Code
Generates Generates
Report
Bills
S_No
Card_Serial_No Vat_perc
TBCS BCFY MBCR Index
TBCR
SName
BAFY Grocery Bill Rank
TBAS Canteen_Summary
Dat Rate
TBAR BATD
Counter_Name Item_desc
MBCS BCTD
MBAR
MBAS Shop_Name
Name
Bill_No Qty
18
11. DATA STRUCTURE (DATABASE)
1.Login_details (Table)
// This Table shows login details of the CMS
Field name data type Size Key Constraints Description

SystemCardNo Int 10 Primary key Not Null Canteen System
card no. for
starting main
server.
Canteen_code Int 04 Not Null
2.Customer_details (Table)
// This Table shows Customer details
Field name data size key Constraints Description

type
Personal_No Int 04 Primary Key Not Null Customer
Identification
No.
Name Varchar 30 Not Null
Father_Name Varchar 30 Not Null
Gender Char 07 Not Null
Marital_Status Char 10
DOB Date Not Null Customer Date
of Birth
DOR Date Not Null Customer Date
of Retirement
19
Rank Varchar 20 Not Null Identify

Customer
Rank, Eg:
Officer,Civilian
Primary_Relation Varchar 15 Customer’s
relatives
primary
relation with
the Customer
No_of_dependent Int 02 No. of
dependents of
the Customer.
PAN_no Int 11 Not Null PAN no. of
Customer
Card_SNO Int 10 Foreign key of Not Null Card Serial No.
Customer_card_details
Table
Address Varchar 40 Not Null
3.Canteen_Manager_details (Table)
// This Table shows Manager details
Field name data type size key Constraints Description

Manager_id Int 04 Primary Key Not Null
CName Varchar 30 Not Null Canteen
Manager’s Name
4.Salesman_details (Table)
// This Table shows Salesman details
20

type
Salesman_id Int 04 Primary Key Not Null
SName Varchar 30 Not Null Salesman Name
Counter_id Int 04 Foreign Key of Not Null
Salesman_Counter_
details Table
5.Customer_Account_details (Table)
// This Table shows Customer Account details

type
Cust_Acc_no Int 04 Primary Key Not Null Customer Account
Number
Personal_No Int 04 Foreign Key of Customer
Customer_ Identification No.
details Table
CardSNo Int 10 Foreign Key of Not Null Card Serial No.
Customer_card_
details Table
Balance Int 05
6. Customer_card_details (Table)
// This Table shows Customer Card details
Field name data size Key Constraints Description
21
type
Card_SNo Int 10 Primary Key Not Null Card Serial No.
PIN_No Int 04 Unique Key Not Null Personal
Identification No.
of Customer
Card_Type Varchar 20 Not Null Type of Card
Card_Category Char 04 Not Null
Customer_ details Identification No.
Table
FromDate Date Validity of Card
From Date
To Date Date Validity of Card
To Date
CustAcNo Int 04 Foreign Key of Customer Account
Customer_Account Number
_ details Table
7.Shop_Master_details (Table)
// This Table shows details of each Shop

type
S_No Int 04 Unique Key Not Null
Shop_Code Int 04 Primary Key Not Null Identification code
of each shop
Shop_Name Varchar 30 Not Null
Shop_Type Varchar 30 Not Null
8.Salesman_Counter_details (Table)
// This Table shows details of each Counter of a Salesman
22

type
Counter_id Int 04 Primary Key Not Null
Shop_id Int 04 Foreign Key of Not Null Identification code
Shop_Master_ of each shop
details Table
Counter_Name Varchar 30 Not Null
Chk_smartcard Varchar 10 Not Null Checking the
Customer Smart
Card
9.Bill_details (Table)
// This Table shows Bill details

type
Bill_No Int 10 Primary Key Not Null
Dat Date Not Null Billing Date
Timing Time Not Null
Card_Serial_No Int 10 Foreign key of Not Null
Table
Shop_Code Int 04 Foreign Key of Not Null Identification
Shop_Master_details code of each
Table shop
Salesman_id Int 04 Foreign Key of Not Null
Salesman_details
Table
Salesman_Counter_
details Table
23
Cust_id Int 04 Foreign Key of Not Null Customer

Customer_ details Identification
Table no.
IndexNo Varchar 08 Foreign Key of Item_ Not Null Identification
details Table no. of each Item
Qty Int 03 Not Null Quantity of
Each Item
PayType Varchar 30 Not Null Type of
Payment done
by the
Customer
10.Gift_details (Table)
// This Table shows Gift details

type
GIndex_No Varchar 08 Primary Key Not Null Gift Item
Identification No.
GItem Varchar 50 Not Null Gift Item
Gat_Indexno Varchar 08 Foreign Key of Not Null Item Identification
Item_ details No. which has
Table some gift
11. Item_details (Table)
// This Table shows details of each Item in Stock

type
Index_No Varchar 08 Primary Key Not Null Item
Identification
24
No.
Pluno_no Varchar 08 Unique Key Not Null Pluno no is
similar to Item
Index no.
Item_desc Varchar 50 Not Null Description of
Item
Group_Name Char 04 Not Null Item belong to
which
group,Eg: I,I
upto VII
Generic_Head Varchar 40 Not Null Generic Head
of Each Item,Eg:
priyagold is
come under
generic head
Biscuit.
Amt_Unit Int 10 Amount of Unit
of each Item
Max_Qty Int 10 Not Null Maximum
Quantity of
each Item
MPP Decimal (6,2) Maximum
Profit percent
Item_cat Char 08 Not Null Category of
Each Item
Case_pack Int 05 Case pack
shows No. of
Items in a
box(peti).
Tax_perc Decimal (4,2) Percentage of
Tax
Tax_amt Decimal (5,2) Amount of Tax
25
Medium Char 06 Not Null Medium of each

Item which
depends on
Sale
Shop_Master_ code of each
details Table shop
GiftScheme Char 05 Not Null If gift if
Available with
item then it
shows yes else
no.
Price Decimal (8,2)
Vat_perc Decimal (4,2) VAT percentage
Vat_amt Decimal (4,2) Amount of VAT
TotPrice_Tax Decimal (8,2) Total Price
including Tax
TotPrice_VAT Decimal (8,2) Total Price
including VAT
12. Barcode_details (Table)
// This Table shows Barcode details of each Item

type
S_No Int 05 Primary Key Not Null
Index_No Varchar 08 Foreign Key of Not Null Item Identification
Item_ details No.
Table
Barcode_no Int 10 Not Null Barcode No. for
each Item
26
13.Canteen_summary_details (Table)
// This Table shows Summary of Canteen

type
TBCS Int 10 Not Null Today’s Bill
Count (Sale)
TBCR Int 10 Not Null Today’s Bill
Count
(Refund)
TBAS Int 11 Not Null Today’s Bill
Amount (Sale)
TBAR Int 11 Not Null Today’s Bill
Amount
(Refund)
MBCS Int 10 Not Null Monthly Bill
Count (Sale)
MBCR Int 10 Not Null Monthly Bill
Count
(Refund)
MBAS Int 11 Not Null Monthly Bill
Amount (Sale)
MBAR Int 11 Not Null Monthly Bill
Amount
(Refund)
BCTD Int 10 Not Null Bill Count Till
Date
BATD Int 11 Not Null Bill Amount
Till Date
BCFY Int 10 Not Null Bill Count
Financial Year
27
BAFY Int 11 Not Null Bill Amount

Financial Year
14. Salesman_summary_details (Table)

// This Table shows Summary of each Salesman

type
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Date
28

Till Date
15.Demand_details (Table)
// This Table shows details of those items which are Demanded

type
Demand_id Int 10 Primary Key Not Null Identification No.
of each Demand
Demand_date Date Date of creating
Demand
Item_ details No.
Table
Demand_desc Varchar 30 Not Null Description of
Demand
16.Voucher_details (Table)
// This Table shows details of each Item which is transfered to MiniBulk

type
Voucher_id Int 10 Primary Key Not Null Voucher
Identification no.
Voucher_desc Varchar 50 Not Null Description of
Voucher
Index_No Varchar 08 Foreign Key of Not Null Identification no. of
Item_ details each Item
Table
29
Voucher_date Date Date of Voucher

Qty_casepack Int 08 Case pack shows No.
of Items in a
box(peti).
Qty_loose Int 08 No. of Items
demanded loosly i.e.
items not contained
in Box.
ShopCode Int 04 Foreign Key of Not Null Identification code of
Shop_Master_ each shop
details Table
17.DamageItem_details (Table)
// This Table shows details of each Damage Item
Field name data Size Key Constraints Description

type
Index_No Varchar 08 Primary Key, Foreign Not Null Identification
Key of Item_ details no. of each
Table Item
18.GroceryInCharge_details (Table)
// This Table shows Grocery Incharge details

type
GrInC_id Int 04 Primary Key Not Null Grocery Incharge
Identification No.
30
Name Varchar 30 Not Null Grocery Incharge

Name
19.GiftInCharge_details (Table)
// This Table shows Gift Incharge details

type
GiftInC_id Int 04 Primary Key Not Null Gift Incharge
Identification No.
Name Varchar 30 Not Null Gift Incharge Name
20.Report_details (Table)
// This Table shows Report details generated by CMS

type
Report_Name Varchar 30 Name of
Report which
describe its
type
21.Bill_Wise_Report (Table)
// This Table shows details of Bill Wise Report

31
type
Bill_No Int 10 Primary Key, Foreign Not Null Bill Number
Key of Bill_ details
Table
Table
Page_No Int 04 Not Null
Round_Off Decimal (4,2) Rounding off
the Price of
Total Items
Amtpaid Decimal (6,2) Not Null Amount paid
by the
Customer
Net_Profit Decimal (6,2) Not Null Net Profit
Earned
Shop_Master_ details code of each
Table Shop
Salesman_Counter_
details Table
22.Item_Wise_Report (Table)
// This Table shows details of Item Wise Report

type
Index_No Varchar 08 Primary Key ,Foreign Not Null Item
key of Item_details Identification
32
Table No.
Bill_No Int 10 Foreign Key of Bill_ Not Null Bill Number
details Table
Table
R_Amt Decimal (6,2) Not Null Retail Amount
of Item
Vat_amt Decimal (4,2) Amount of
VAT
the Price of
Total Items
by the
Customer
W_Amt Decimal (6,2) Not Null Whole Sale
Amount of the
Item
Earned
Table Shop
Salesman_Counter_
details Table
23.OCDayDetails (Table)
// This Table showing Canteen Opening/Closing Day Details
33

type
Day Varchar 12 Primary Key Not Null Day at which
the Canteen is
Open or Close
Status Varchar 06 Not Null This shows
either Canteen
is Open or
Close
OpenTime Not Null Opening time
of Canteen
CloseTime Not Null Closing time of
Canteen
24.OCMonthDetails (Table)
// This Table showing Canteen Opening/Closing Month Details

type
Dat Date Primary Key Not Null Date at which
the Canteen is
Open or Close
either Canteen
is Open or
Close
25.MiniBulkDetails (Table)
// This Table showing Items in Mini Bulk
34
type
Index_No Varchar 08 Primary Key, Foreign Not Null Item
Key of Item_details Identification
Table No.
Table Shop
No_of_Qty Int 10 No. of
Quantity of
Item
Voucher_id Int 10 Foreign Key of Voucher Not Null Voucher
_details Table Identification
no.
35
12. NUMBER OF MODULES & ITS DESCRIPTION
CMS MAIN MENU
System Administrator Details
Canteen Grocery Master Card Management

Master Details Details
Shop Master Item Details Renew Card

Details Details
Add Items
Update Card
Add Shop
Details
Delete Items
Delete Shop
Update Items Unblock Canteen Card
Pin Details
Update shop
Counter Barcode
Display Card
Add Barcode Details
Add Counter
Delete Barcode
Delete Counter
Update Barcode
Update
Cost Details
Salesman Details
Add Salesman
Delete Salesman
Update Salesman
36
Canteen Manager Details
Canteen Canteen Enquiry Bill Approval Card Issue Details View Manager
Opening/Closing Opening/Closing Details Details Details
Details for Day Details for Month
Refund Bill Add Customer
approval Details
Update Update
Details Details
Duplicate
Update Customer
Bill approval
Details
Create Customer
Account
B C
Grocery Salesman Detail Card Issuance Detail
Grocery Grocery Duplicate Bill Salesman View

Register new Card Renew Card
Sale Refund Printing Detail Summary Salesman
Detail Detail Detail Details
Net Sale Sale Refund

Detail Detail
C D
37
Grocery Bulk Details
Display Issue to Display STB Transfer

Stock in Mini Bulk Demand Details Details
Bulk Details
Reduced Item Damage Transfer Items to

Details Item Details Damage Bulk
Display Details Display Details
D E
Grocery Shop I/C Details
Grocery Demand Issue Voucher STB View I/C

Details Details Details Details Details
Add New Add New Add New Reduced Bulk Details

Items Items Items
Add New Items

Delete Delete Delete
Items Items Items
Delete Items
Update Update Update

Update Items
Items Items Items
Damage Bulk Details
Update Items
38
E F
Reports Details Grocery Damage Details
Bill Wise Item Wise Display Damage Update Items

Report Report Bulk
Add New Add New F G

Items Items
Delete Delete Customer Details

Items Items
Update Update
Items Items
Add New Delete Update Display
Customer Customer Customer Customer
Display Display details Details Details
Items Items
G H
Gift I/C Details Canteen Summary Details
Add Delete Update Display View Gift Day Wise Month Annual
Items to Items Items Items I/C Details Wise Details
Gift Bulk Details Details
Display Display Display

Details Details Details
13. PROCESS LOGIC

39
As all the programming is divided into different modules and they will interact
with each other to maintain the Data and Information. Modular structure is
designed with the consideration of case to maintain the Logic for modification and
maintenance. Since program has to interact with the database, it is basically based
on the User interface as Front-End Tool and Database as Back-End Tool. Each
module is interacting with Database gives the desired Output.
This project has the following modules:
 System Administrator Details
 Canteen Manager Details
 Grocery Salesman Detail
 Card Issuance Detail
 Grocery Bulk Details
 Grocery Shop I/C Details
 Customer Details
 Reports Details
 Grocery Damage Details
 Gift I/C Details
 Canteen Summary Details
 System Administrator Details
40
The System Administrator Detail is the important module for this project. In this
module we are showing how many types of shops, counters and salesmans are
there in the Organization and how many items are there in the Bulk with their
Barcodes. We can add, delete & Update the Shop Details, Counter Details,
Salesman Details and Item Details etc in the Database. This module also performs
the Card Management process.
 Canteen Manager Details

In this Module A Canteen Manager has the major responsibility of handling the
various tasks perform in the Organization. A Manager decides when to open the
Canteen and when to close it. In this module Manager will issue the Card to the
Customer create Customer account. Manager will also enquire that the Stock of
items is available or not and also approve the Refund and Duplicate Bills.
 Grocery Salesman Detail

In this module we can view the Salesman Details. How much sale is achieved by a
Salesman and how much refunded, and printing of Duplicate Bills is the various
task performed in this module. Here we are also showing the Salesman Summary.
 Card Issuance Detail

This is the very important module of this project as this module issues the Canteen
Card the Customer and also renew that Card. Without this Card Customer cannot
purchase any items. So this module is very important.
 Grocery Bulk Details

41
This module shows how much stock of items is there in the Bulk, Mini Bulk. What
are the Demands generated by the Manager if the items are not there in the Bulk
and Damage and Reduced Item Bulks are also shown in this module. Details of
how many items are transferred from Grocery Bulk to Damage Bulk is also shown
in this module.
 Grocery Shop I/C Details

In this module we can view the details of grocery I/C, add, delete and update the
Grocery details, Demand details, Voucher details etc.
 Customer Details
In this module we are getting the Customer details for issuing Card to him/her
and store all the details in the database.
 Reports Details
In this module we are generating the Bill wise and Item wise reports for the
Customer and the Organization.
 Grocery Damage Details

In this module we are displaying the items in the Damage Bulk and update them
whenever necessary.
42
 Gift I/C Details

In this module we can view the details of Gift I/C, and add, delete, update and
display the Gift items in the Database.
 Canteen Summary Details

In this module we are displaying the whole Canteen Summary i.e. Day wise Sale,
Monthly Sale and yearly Sale of Items in the Canteen. This is very important
module as this module shows how much Profit is earned by the Organization and
how much it grow.
14. SCOPE OF THE PROJECT
Canteen Management Software is a software that is the computerized version of

the manual work so as to ease the functioning of Canteen Management System.
It has been designed to fulfill basic requirements of Canteen Management and can
be modified as per the future requirements; it is really flexible for further projection
as here it designed to reduce the work load of maintaining the files of information
about Customers,Items etc. manually.
Reducing the man power it helps the management system to employee the human
resources to some other requirements. Anybody dealing in this field can opt for
this, being flexible designing will require only slight changes.
This project can be used in Air Force Canteen after adding some more useful
modules in the project.
43
15. BIBLIOGRAPHY
 SOFTWARE ENGINEERING: A PRACTITIONER’S APPROACH BY ROGER

S. PRESSMAN
 SOFTWARE ENGINEERING BY PANKAJ JALOTE
 SOFTWARE ENGINEERING BY K. K. AGGARWAL & YOGESH SINGH
 FUNDAMENTALS OF DATABASE SYSTEMS BY RAMEZ ELMASRI &

SHAMKANT B. NAVATHE.
INFORMATICS PRACTICES BY SUMITA ARORA.
44
Indira Gandhi National Open University

इइंददिरर गरइंधध ररष्टट्रीय ममक्त वविश्विवविद्यरलय
Maidan Garhi, New Delhi-110068, INDIA
SCHOOL OF COMPUTER AND INFORMATION SCIENCES

BACHELOR OF COMPUTER APPLICATION
PROJECT REPORT
ON
Air Force Canteen

Management System
GUIDE NAME :
SUBMITED BY :-
ENROLLMENT NO :-
STUDY CENTER CODE :-
45
Table of Contents
Synopsis.................................................................................................................................................................................
Project Report……………………………………………………………………………………………………………………………………………………………………
Title of the Project.................................................................................................................................................................
Chapter 1 - Introductio
1.1 Introduction of the Present System……………………………………………………………………………………………………………………
1.2 Objectives of the Project...........................................................................................................................................
1.3 Proposed System.......................................................................................................................................................
Chapter 2 – System Analysis..................................................................................................................................................
2.1 Identification of the Need.........................................................................................................................................
2.2 Preliminary Investigation..........................................................................................................................................
2.3 Inputs of the Project.................................................................................................................................................
2.4 Outputs of the Project..............................................................................................................................................
2.5 Feasibility Study........................................................................................................................................................
2.6 Project Planning........................................................................................................................................................
2.7 Project Scheduling....................................................................................................................................................
2.7.1 PERT Chart ....................................................................................................................................................
2.7.2 Gantt Chart ...................................................................................................................................................
2.8 Software Requirement Specifications(SRS) ..............................................................................................................
46
2.8.1 Facilitated Application Specification Techniques(FAST) ...............................................................................
2.8.2 Quality Function Deployment(QFD) .............................................................................................................
2.9 Software & Hardware Requirement Specifications...................................................................................................
2.10 Software Engineering Paradigm Applied................................................................................................................
2.11 Data Flow Diagrams(DFD).......................................................................................................................................
2.12 Entity Relationship Diagram (ERD)..........................................................................................................................
Chapter 3 - System Design.....................................................................................................................................................
3.1 Modularisation Details..............................................................................................................................................
3.2 Process Logic.............................................................................................................................................................
3.3 Database Designing...................................................................................................................................................

3.3.1 Creating Database & Tables..........................................................................................................................
3.3.2 Structure of Tables........................................................................................................................................
3.3.3 Inserting Values in Tables..............................................................................................................................
3.3.4 Showing Data in Tables.................................................................................................................................
3.4 User Interface Design................................................................................................................................................
Chapter 4 - Coding.................................................................................................................................................................
4.1 Complete Project Coding..........................................................................................................................................
4.2 Code Efficiency..........................................................................................................................................................
4.3 Optimisation of Code................................................................................................................................................
4.4 Validation Checks......................................................................................................................................................
Chapter 5 - Testing.................................................................................................................................................................
5.1 Testing Techniques & testing Strategies....................................................................................................................
5.2 Implementation........................................................................................................................................................
5.3 Evaluation.................................................................................................................................................................
5.4 Maintenance.............................................................................................................................................................
Chapter 6 – Security Measures & Cost Estimation ................................................................................................................
6.1 System Security Measures........................................................................................................................................
6.2 Cost Estimation of the Project..................................................................................................................................
Chapter 7 – Reports (Output Forms) .....................................................................................................................................
Chapter 8 – Scope & Conclusion ...........................................................................................................................................
8.1 Future Scope of the Project......................................................................................................................................
47
8.2 Conclusion.................................................................................................................................................................
8.3 Limitations of the System .........................................................................................................................................
Bibliography...........................................................................................................................................................................
Glossary.................................................................................................................................................................................
2. INTRODUCTION
Canteen Management System (CMS) also Known as Canteen Stores Department

(CSD) has been in the service of the Defence Services for more than five decades.
CMS provides its consumers, all over the country, quality products of daily use at
rates less than those prevailing in the market. These items are meant for sale to
troops, ex-servicemen and their families. So in present context it is necessary for the
management to have a computerized management & control system for manage
the resources as accurately as possible also to increase the facilities to the users. The
Management by itself does not come in direct or daily contact with its customers.
Only Managers/In-Charges (ICs) interact with the CMS Area Depots. It is,
therefore, necessary that these persons must really be aware of what their
customers' need. Needless to say, the Department continues to be scrutinized every
day by the customers for availability, rates and range of the products.
Main Objectives of CMS are:
 Provide consumer goods of high quality to the troops wherever they are at
prices cheaper than the prevailing market rates, as far as possible.
 Ensure that the level of consumer/customer satisfaction is maintained at the
maximum.
 Generate reasonable profitability to sustain the organization, permit growth
and provide additional facilities for troops and their families.
 Formulate and execute development programmes to improve and maintain
organizational effectiveness.
48
 Periodically analyze and assess the diverse long-term needs and aspirations
of Defence Services and undertake timely measures to meet them.
In this paper, we present the development of an application for CMS to benefit the
Canteen administration and staff for better decision making process, resulting in
providing better facilities and products to customers.
49
4. OBJECTIVES OF THE PROJECT
 The objective of the project is to design a computerized Canteen Management

System, automating the database and functioning of CMS.
 The Software would benefit the CMS by reducing the Workforce & tasks of
maintaining the database & creation and generation of Bills, Report &
Summary & updating the information.
 The project aims to reduce time spent in performing the various jobs in CMS,
as manual work will take a lot of time.
 The onetime cost of the system will be high, but then the running cost of the
system would be much lower than the cost in Current System as it will
reduce manpower & thus reducing salary payments.
 The System has to become Centralized so that Canteen Manager can control
& manage any of the System through its Centralized System. Air Force
Canteens are also Centralized state wise. As in Delhi the main depot of
Canteen is in Delhi Cantt. from where all other branches of Canteen in Delhi
are connected through this Centralized System.
50
8. PROJECT CATEGORY
This project is under the category of “RDBMS”.
This project aims to provide the improved functionality and better User Interactive
Environment. In this software information is handled by using MySQL for storing
records in a database, as backend and Java with NetBeans is used as front end.
Relational Database Management System has permeated every segment of

commercial world. They are required as the backbone of any information system. A
database is a mechanized, shared, formally defined, and centrally controlled
collection of data used in an organization. A database management system (DBMS)
is the software that controls access to the information stored in the database.
Although there are various approaches to the logical and physical organization of
data, today’s database environment is dominated by relational database
management systems (RDBMS).
Facilities offered by RDBMS:
 Creation of files, Addition of data, Deletion of data, Modification of data.

 The data stored can be sorted or indexed at user’s discretion or direction.
 Various reports can be produced from the system. These may either be
standardized reports or that may be specifically generated according to
specific user definition.
51
9. TOOLS/PLATFORM, HARDWARE & SOFTWARE

REQUIREMENTS SPECIFICATIONS
Software and hardware specification as the name suggests, tells us about the
various characteristics of the software and the hardware environment used i.e. the
development environment used. Here we specify various software languages,
supporting tools that have been used for the development of the system. These
tools and the languages have been used because of their relative ease of understand
and personal interest of the team developing the project.
TOOLS :
 Front End Tool : Java with Net Beans.
 Back End Tool : MySQL.
PLATFORM :
 WINDOWS 98 / WINDOWS XP
MINIMUM HARDWARE REQUIREMENT :
 PROCESSOR : PENTIUM IV PROCESSOR
 RAM : 512 MB
 STORAGE CAPACITY : 20 GB
 DRIVES : 52X CD
SOFTWARE REQUIREMENT :
OPERATING SYSTEM : WINDOW 98,XP
RDBMS : MySQL
LANGUAGES USED : JAVA WITH NETBEANS
52
SOFTWARE USED IN THE SYSTEM

The software selection was done after considering a few alternatives and
constraints imposed by the company. The following Software’s are used for
designing and implementing the system.
3. JAVA NETBEANS
NetBeans is an open-source project dedicated to providing rock solid software

development products (the NetBeans IDE and the NetBeans Platform) that address
the needs of developers, users and the businesses who rely on NetBeans as a basis
for their products. The two base products, the NetBeans IDE and NetBeans
Platform, are free for commercial and non-commercial use. The source code to both
is available to anyone to reuse as they see fit, within the terms of use. The NetBeans
project is also a vibrant community where people from across the globe can ask
questions, give advice, make various contributions, and ultimately share in the
success of our products.
Here, I build Canteen Management System (CMS) using Java NetBeans because
Java is Platform Independent and a Open Product which is freely available to all.
NetBeans consist of RAD tools which enable the programmer to create applications
in shorter time as compared to conventional Language.
With NetBeans IDE, we can develop applications by just creating frames, dragging
and dropping controls on to frames, setting properties for various things, adding
some application-specific code to handle events. Java offers more security to make
its programs safe and secure.
4. MySQL
MySQL is the world's most popular open source database software, with over 100
million copies of its software downloaded or distributed throughout it's history.
With its superior speed, reliability, and ease of use, MySQL has become the
preferred choice for Web, Web 2.0, SaaS, ISV, Telecom companies and forward-
thinking corporate IT Managers because it eliminates the major problems
53
associated with downtime, maintenance and administration for modern, online

applications.
Many of the world's largest and fastest-growing organizations use MySQL to save
time and money powering their high-volume Web sites, critical business systems,
and packaged software — including industry leaders such as Yahoo!, Google,
Nokia, YouTube, Wikipedia, and Booking.com.
In Canteen Management System (CMS) MySQL is used to store and manage large
amount of Data in a multi-user environment so that many users can concurrently
access the same data. A database server must also prevent unauthorized access and
provide efficient solution for failure recovery.
MySQL database system refer to the combination of a MySQL server instance and a
MySQL database. MySQL operates using client/server architecture in which the
server runs on the machine containing the database and clients connect to the
server over a network.
10. PROBLEM DEFINITION
 The System is manual. Hence a lot of manpower is required.
 The system is error prone due to high portability of mistakes in manual work.
 Information maintenance as paper work is complex task.
 As the data is very large, no Backup can be maintained.
 Modify the details of the Customer, Items etc. is a large procedure & may
lead to chaos.
 Analysis on data & access to databases is tedious task & large work force is
required.
 The process is prone to delays & cost ineffectiveness.
54
11. REQUIREMENT SPECIFICATIONS
7.1 FACILITATED APPLICATION SPECIFICATION

TECHNIQUES (FAST)
It is a work product of Team of End Users and Software Engineers that help in
understanding the Software demands completely. This approach encourages the
creation of a joint team or customers and developers to work together to identify
the problem, purpose elements of the solution, negotiate different approaches and
specify a preliminary set of solution requirements.
A meeting is conducted at a neutral site and attended by both Software Engineers

and Customers.
Before the FAST meeting, each FAST attendee is asked to make a List of Objects,
List of services, List of Constraints, Performance Criteria.
Based on our project I make all these Lists.
7.1.1 Requirements taken from Team of End Users
 List of Services
 Interact with Customer.
 Issue Canteen Card to Customer.
 Check the availability of items in the Database.
 Sale the Items to different Customers and Update Database
Information.
 Generate Bill for the Customer.
 Generate Canteen Summary and Report for the Organization.
55
 List of Constraints
 System must be User Friendly.

 The System must have a manufacturing cost less than or equal to
the calculated cost.
 List of Validations
 The Customer Details in the form for issuing Canteen Card should be
valid.
 The Customer Card number entered should be valid.
 For Defence Civilians card is valid up to the Date of Retirement.
 For Ex-Serviceman Card is valid for 1 year.
 For Dependents card is valid for 1 year along with parent card.
 Performance Criteria
 As the request for purchasing the items is made by the Customer the
items are selected and sold to the Customer through his/her account
and Bill is generated and the amount of Cash is deducted from the
Customer account automatically.
 System should update the database information frequently.
7.2 QUALITY FUNCTION DEPLOYMENT (QFD)

QFD is a Quality Management Technique that translates the needs of the Customer
into technical requirements for Software.
QFD identifies three types of requirements:-
56
Normal Requirements:- The objectives and goals that are stated for product or
system during meetings with the customer. If these requirements are presents, the
customer is satisfied.
Expected Requirements:- These requirements are implicit to the product or

system and may be so fundamental that the customer does not explicitly state
them.
Exciting Requirements:- These features go beyond the customer’s expectations

and prove to be very satisfying when present.
7.2.1 Normal Requirements for CMS :-

 Interact with Customer.
 Issue Canteen Card to Customer.
 Check the availability of items in the Database.
 Sale the Items to different Customers and Update Database Information.
 Generate Bill for the Customer.
 Generate Canteen Summary and Report for the Organization.
7.2.3 Expected Requirements for CMS :-

 Provide Gift Items for some Items selected by Customer if gifts are available
with those items.
 Amount of VAT provided should be lowest. VAT amount is calculated by

providing VAT% on the Items.
 If the Customer purchase any AFD Item then amount from his/her account
will not be deducted and if Customer purchase Non-AFD item then the
amount will be deducted from his/her account.
7.2.3 Exciting Requirements for CMS :-

57
 Interface i.e. form can be made attractive by using graphics.

 Answers to User inquiry can be in dialog boxes.
 Interface can be Menu Driven.
8. PROJECT PLANNING
The planning phase is the most critical step in completing development,

acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, is necessary to coordinate activities and manage project risks
effectively. Project plans refine the information gathered during the initiation phase
by further identifying the specific activities and resources required to complete a
project. A critical part of a project manager’s job is to coordinate discussions
between user, audit, security, design, development, and network personnel to
identify and document as many functional, security, and network requirements as
possible.
During this phase, a plan is developed that documents the approach to be used and
includes a discussion of methods, tools, tasks, resources, project schedules, and
user input. Personnel assignments, costs, project schedule, and target dates are
established.
A Project Management Plan is created with components related to acquisition
planning, configuration management planning, quality assurance planning,
concept of operations, system security, verification and validation, and systems
engineering management planning.
8.1 FEASIBILITY OF PRODUCT

The feasibility of the product is a question that confirms reality to the ideas.
Feasibility test is critical. The dimensions that define feasibility of project are:
8.1.1 ECONOMICAL FEASIBILITY

Previously when Canteen Management Systems were handled manually then a lot
of manpower is used. Customer Canteen Card was not used at that time. All work
58
i.e. Billing, maintain Data was done manually. Three copies of each Bill (Customer
Copy, Office Copy and Depot Copy) was maintained by the Organization. Cost
involved was very high because at that time more Stationary & manpower was
used. So, the total cost involves is very high. Now the cost of computerized
Canteen Management System includes cost of a few components plus the cost of
developing the software. So, it is high but not as much high as in the past. Since the
manpower is reduced & cost of stationary is less. So we can say that Economically
the feasibility of the Software is High.
8.1.2 TECHNICAL FEASIBILITY

The Technical Feasibility is high as the software can be deployed on any machine
using some languages like JAVA,VB,C++,HTML etc.
8.1.3 ENVIRONMENTAL FEASIBILITY

The Software is simple; the User will find it very easy to perform all the required
jobs. It would also be very convenient for the members of Canteen Management
System as the Software is User Friendly & easy to use.
8.2 SOFTWARE MODEL USED

Now the major question is which process model is to be chosen for the
development of software and Why???
For this I can use THE INCREMENTAL MODEL.
I use this model, because it is a combination of Linear Sequential Model &

prototyping Model. In this Model, basic requirements of the Customer and Items
are addressed in the first increment, and many additional features are addressed in
the other increments as per the needs of the customer. So this model is appropriate
for this project.
59
10. DATA FLOW DIAGRAMS(DFD)
DFD serves two purposes:-
 To provide an indication of how data are transformed as they move through

the system, and
 To depict the functions ( and sub functions ) that transforms the data flow.
The DFD provides additional information that is used during the analysis of the
information domain and serves as a basis for the modeling of function.
10. ENTITY-RELATIONSHIP DIAGRAM (ERD)
Entity-relationship model is database analysis and design tool. It lists real-life

application entities, attributes of entities and relationships amongst entities. The
type of each relationship is also indicated. Entity-relationship model is represented
in graphical form.
60
DFD LEVEL 0
DEMAND
SYSTEM
CARD CUSTOMER
CANTEEN
CARD
CUSTOMER
CANTEEN SALESMAN
MANAGER COUNTER
ITEMS GROCERY
BILL
CUSTOMER
CANTEEN REPORT
CANTEEN
CARD MANAGEMEN
T SYSTEM
CANTEEN
SUMMARY
SALESMAN Information is stored

CUSTOMER
& update in the
ACCOUNT
Database.
SHOP
SYSTEM
ADMINISTRATOR
CANTEEN
MANAGEMENT
SYSTEM DATABASE
61
DFD LEVEL 1
CUSTOMER
SYSTEM Taking Card
CANTEEN
CARD information for login
CARD
the S/W
Login CMS
Software Issuing Customer
Daily Canteen Card
CUSTOMER
1.
Taking Customer
Details CUSTOMER
System Start ACCOUNT
Creating
Customer A/c
Stock
CANTEEN Will DEMAND
Enquire & Checking, Creating
MANAGER
perform Take info. , Demands & send
these task Issue Card, to depot
SYSTEM Create A/C 2.
Give permission
ADMINISTRATOR
SALESMAN
Give permission Generate,
COUNTER
Control Generate Counters
Counters,
SALESMAN Taking Salesman
permit
details
Salesman 3. GROCERY
BILL
ITEMS Generating the Bill
Get Items Details
Enter Pin
SHOP REPORT
Get Shop Details No., Sale Generate
Items , report
Get Customer Details Generate Bill

CUSTOMER
4. Generate
CANTEEN CARD
report CANTEEN
SUMMARY
Update DB
Generate
Items and
Canteen
Customer
Summary
Update DB A/c 5.
DAMAGE ITEMS Database
Generate
DATABASE Update DB updated
Update DB Canteen
Update DB
Summary &
GIFT ITEMS CUSTOMER A/C
DATABASE BULK DATABASE Report 6.
DATABASE
62
DFD LEVEL 2
Generate
System Administrator various counters Control all
3 Counters for
sale
3.1
Canteen Manager Stock Checking,
Get Customer
Information etc. Issue a Card
Customer 2 for Customer Customer Canteen Card
2.1
Customer A/C
Create
Customer A/C
Permit the salesman
For purchasing
for
2.2
sale
Demand
3.2
Check
availability of
stock 2.3
Salesman Counter
Salesman
Enter pin no. of Customer &
open
Customer A/C
Customer Canteen Card 4
Grocery Bill
Generate Bill
& Report
Items 4.2
Select Shop Type,
Items for Sale
Shop
4.1
Customer A/C
Database
Update
Customer A/C
5
Bulk
Generate
Database Generate
Update Canteen Canteen Summary
Canteen
Databases Summary
Summary
5.1 6.1
& report
6
Gift
Database Damage Generate Report
Database Report
6.2
ERD Rank
Demand_desc Demand_id
Demand_date
63 Demand
Create
Manager_id CName Gender Address
Scard_No Canteen_code
Put in
Canteen Manager System Card
Issue/Rene Card_SNo Pin_no Card_Type Name

Take & w DOR
fill Customer_Canteen_Card Rank
Personal_No
Rank Address
Gender Card_SNo
Has
Customer Salesman_id Put in
SName
Address
DOB Communicate
Name
Father_ PAN_no
Name Salesman
Gender
Address Counter_id
DOR Counter_id Counter_nam
e
Shop_Name
Has Counter_nam
Shop_id
e
Sale
Goto Salesman_Counter
Index_No Pluno_no
Price
Group
Purchase Items
Shop_Type
Item_desc
Cust_Acc_no Personal_No
Name Under Max_Qty
Balance
Has Shop_Name
Customer Account
Shop Select
Shop_Type
Bill_No
Bill_wise Item_wise Shop_Code
Generates Generates
Report
Bills
S_No
Card_Serial_No Vat_perc
TBCS BCFY MBCR Index
TBCR
SName
BAFY Grocery Bill Rank
TBAS Canteen_Summary
Dat Rate
TBAR BATD
Counter_Name Item_desc
MBCS BCTD
MBAR
MBAS Shop_Name
Name
Bill_No Qty
64
11. DATA STRUCTURE (DATABASE)
1.Login_details (Table)
// This Table shows login details of the CMS
Field name data type Size Key Constraints Description

SystemCardNo Int 10 Primary key Not Null Canteen System
card no. for
starting main
server.
Canteen_code Int 04 Not Null
2.Customer_details (Table)
// This Table shows Customer details

type
Personal_No Int 04 Primary Key Not Null Customer
Identification
No.
Name Varchar 30 Not Null
Father_Name Varchar 30 Not Null
Marital_Status Char 10
DOB Date Not Null Customer Date
of Birth
DOR Date Not Null Customer Date
of Retirement
65
Rank Varchar 20 Not Null Identify

Customer
Rank, Eg:
Officer,Civilian
Primary_Relation Varchar 15 Customer’s
relatives
primary
relation with
the Customer
No_of_dependent Int 02 No. of
dependents of
the Customer.
PAN_no Int 11 Not Null PAN no. of
Customer
Card_SNO Int 10 Foreign key of Not Null Card Serial No.
Table
3.Canteen_Manager_details (Table)
// This Table shows Manager details
Field name data type size key Constraints Description

Manager_id Int 04 Primary Key Not Null
CName Varchar 30 Not Null Canteen
Manager’s Name
4.Salesman_details (Table)
// This Table shows Salesman details
66

type
SName Varchar 30 Not Null Salesman Name
Salesman_Counter_
details Table
5.Customer_Account_details (Table)
// This Table shows Customer Account details

type
Cust_Acc_no Int 04 Primary Key Not Null Customer Account
Number
Customer_ Identification No.
details Table
CardSNo Int 10 Foreign Key of Not Null Card Serial No.
Customer_card_
details Table
Balance Int 05
6. Customer_card_details (Table)
// This Table shows Customer Card details
67
type
Card_SNo Int 10 Primary Key Not Null Card Serial No.
PIN_No Int 04 Unique Key Not Null Personal
Identification No.
of Customer
Card_Type Varchar 20 Not Null Type of Card
Card_Category Char 04 Not Null
Customer_ details Identification No.
Table
FromDate Date Validity of Card
From Date
To Date Date Validity of Card
To Date
CustAcNo Int 04 Foreign Key of Customer Account
Customer_Account Number
_ details Table
7.Shop_Master_details (Table)
// This Table shows details of each Shop

type
Shop_Code Int 04 Primary Key Not Null Identification code
of each shop
Shop_Name Varchar 30 Not Null
Shop_Type Varchar 30 Not Null
8.Salesman_Counter_details (Table)
// This Table shows details of each Counter of a Salesman
68

type
Counter_id Int 04 Primary Key Not Null
Shop_id Int 04 Foreign Key of Not Null Identification code
Shop_Master_ of each shop
details Table
Counter_Name Varchar 30 Not Null
Chk_smartcard Varchar 10 Not Null Checking the
Customer Smart
Card
9.Bill_details (Table)
// This Table shows Bill details

type
Bill_No Int 10 Primary Key Not Null
Dat Date Not Null Billing Date
Timing Time Not Null
Table
Table shop
Salesman_id Int 04 Foreign Key of Not Null
Salesman_details
Table
Salesman_Counter_
details Table
69
Cust_id Int 04 Foreign Key of Not Null Customer

Customer_ details Identification
Table no.
IndexNo Varchar 08 Foreign Key of Item_ Not Null Identification
details Table no. of each Item
Qty Int 03 Not Null Quantity of
Each Item
PayType Varchar 30 Not Null Type of
Payment done
by the
Customer
10.Gift_details (Table)
// This Table shows Gift details

type
GIndex_No Varchar 08 Primary Key Not Null Gift Item
Identification No.
GItem Varchar 50 Not Null Gift Item
Gat_Indexno Varchar 08 Foreign Key of Not Null Item Identification
Item_ details No. which has
Table some gift
11. Item_details (Table)
// This Table shows details of each Item in Stock

type
Index_No Varchar 08 Primary Key Not Null Item
Identification
70
No.
Pluno_no Varchar 08 Unique Key Not Null Pluno no is
similar to Item
Index no.
Item_desc Varchar 50 Not Null Description of
Item
Group_Name Char 04 Not Null Item belong to
which
group,Eg: I,I
upto VII
Generic_Head Varchar 40 Not Null Generic Head
of Each Item,Eg:
priyagold is
come under
generic head
Biscuit.
Amt_Unit Int 10 Amount of Unit
of each Item
Max_Qty Int 10 Not Null Maximum
Quantity of
each Item
MPP Decimal (6,2) Maximum
Profit percent
Item_cat Char 08 Not Null Category of
Each Item
Case_pack Int 05 Case pack
shows No. of
Items in a
box(peti).
Tax_perc Decimal (4,2) Percentage of
Tax
Tax_amt Decimal (5,2) Amount of Tax
71
Medium Char 06 Not Null Medium of each

Item which
depends on
Sale
Shop_Master_ code of each
details Table shop
GiftScheme Char 05 Not Null If gift if
Available with
item then it
shows yes else
no.
Price Decimal (8,2)
Vat_perc Decimal (4,2) VAT percentage
Vat_amt Decimal (4,2) Amount of VAT
TotPrice_Tax Decimal (8,2) Total Price
including Tax
TotPrice_VAT Decimal (8,2) Total Price
including VAT
12. Barcode_details (Table)
// This Table shows Barcode details of each Item

type
Item_ details No.
Table
Barcode_no Int 10 Not Null Barcode No. for
each Item
72
13.Canteen_summary_details (Table)
// This Table shows Summary of Canteen

type
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Date
Till Date
BCFY Int 10 Not Null Bill Count
Financial Year
73
BAFY Int 11 Not Null Bill Amount

Financial Year
14. Salesman_summary_details (Table)

// This Table shows Summary of each Salesman

type
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Count (Sale)
Count
(Refund)
Amount (Sale)
Amount
(Refund)
Date
74

Till Date
15.Demand_details (Table)
// This Table shows details of those items which are Demanded

type
Demand_id Int 10 Primary Key Not Null Identification No.
of each Demand
Demand_date Date Date of creating
Demand
Item_ details No.
Table
Demand_desc Varchar 30 Not Null Description of
Demand
16.Voucher_details (Table)
// This Table shows details of each Item which is transfered to MiniBulk

type
Voucher_id Int 10 Primary Key Not Null Voucher
Identification no.
Voucher_desc Varchar 50 Not Null Description of
Voucher
Index_No Varchar 08 Foreign Key of Not Null Identification no. of
Item_ details each Item
Table
75
Voucher_date Date Date of Voucher

Qty_casepack Int 08 Case pack shows No.
of Items in a
box(peti).
Qty_loose Int 08 No. of Items
demanded loosly i.e.
items not contained
in Box.
ShopCode Int 04 Foreign Key of Not Null Identification code of
Shop_Master_ each shop
details Table
17.DamageItem_details (Table)
// This Table shows details of each Damage Item
Field name data Size Key Constraints Description

type
Index_No Varchar 08 Primary Key, Foreign Not Null Identification
Key of Item_ details no. of each
Table Item
18.GroceryInCharge_details (Table)
// This Table shows Grocery Incharge details

type
GrInC_id Int 04 Primary Key Not Null Grocery Incharge
Identification No.
76
Name Varchar 30 Not Null Grocery Incharge

Name
19.GiftInCharge_details (Table)
// This Table shows Gift Incharge details

type
GiftInC_id Int 04 Primary Key Not Null Gift Incharge
Identification No.
Name Varchar 30 Not Null Gift Incharge Name
20.Report_details (Table)
// This Table shows Report details generated by CMS

type
Report_Name Varchar 30 Name of
Report which
describe its
type
21.Bill_Wise_Report (Table)
// This Table shows details of Bill Wise Report

77
type
Bill_No Int 10 Primary Key, Foreign Not Null Bill Number
Key of Bill_ details
Table
Table
the Price of
Total Items
by the
Customer
Earned
Shop_Master_ details code of each
Table Shop
Salesman_Counter_
details Table
22.Item_Wise_Report (Table)
// This Table shows details of Item Wise Report

type
Index_No Varchar 08 Primary Key ,Foreign Not Null Item
key of Item_details Identification
78
Table No.
Bill_No Int 10 Foreign Key of Bill_ Not Null Bill Number
details Table
Table
R_Amt Decimal (6,2) Not Null Retail Amount
of Item
Vat_amt Decimal (4,2) Amount of
VAT
the Price of
Total Items
by the
Customer
W_Amt Decimal (6,2) Not Null Whole Sale
Amount of the
Item
Earned
Table Shop
Salesman_Counter_
details Table
23.OCDayDetails (Table)
// This Table showing Canteen Opening/Closing Day Details
79

type
Day Varchar 12 Primary Key Not Null Day at which
the Canteen is
Open or Close
either Canteen
is Open or
Close
OpenTime Not Null Opening time
of Canteen
CloseTime Not Null Closing time of
Canteen
24.OCMonthDetails (Table)
// This Table showing Canteen Opening/Closing Month Details

type
Dat Date Primary Key Not Null Date at which
the Canteen is
Open or Close
either Canteen
is Open or
Close
25.MiniBulkDetails (Table)
// This Table showing Items in Mini Bulk
80
type
Index_No Varchar 08 Primary Key, Foreign Not Null Item
Key of Item_details Identification
Table No.
Table Shop
No_of_Qty Int 10 No. of
Quantity of
Item
Voucher_id Int 10 Foreign Key of Voucher Not Null Voucher
_details Table Identification
no.
81
12. NUMBER OF MODULES & ITS DESCRIPTION
CMS MAIN MENU
System Administrator Details
Canteen Grocery Master Card Management

Shop Master Item Details Renew Card

Details Details
Add Items
Update Card
Add Shop
Details
Delete Items
Delete Shop
Update Items Unblock Canteen Card
Pin Details
Update shop
Counter Barcode
Display Card
Add Barcode Details
Add Counter
Delete Barcode
Delete Counter
Update Barcode
Update
Cost Details
Salesman Details
Add Salesman
Delete Salesman
Update Salesman
82
Canteen Manager Details
Canteen Canteen Enquiry Bill Approval Card Issue Details View Manager
Opening/Closing Opening/Closing Details Details Details
Details for Day Details for Month
Refund Bill Add Customer
approval Details
Update Update
Details Details
Duplicate
Update Customer
Bill approval
Details
Create Customer
Account
B C
Grocery Salesman Detail Card Issuance Detail
Grocery Grocery Duplicate Bill Salesman View

Register new Card Renew Card
Sale Refund Printing Detail Summary Salesman
Detail Detail Detail Details
Net Sale Sale Refund

Detail Detail
C D
83
Grocery Bulk Details
Display Issue to Display STB Transfer

Stock in Mini Bulk Demand Details Details
Bulk Details
Reduced Item Damage Transfer Items to

Details Item Details Damage Bulk
Display Details Display Details
D E
Grocery Shop I/C Details
Grocery Demand Issue Voucher STB View I/C

Details Details Details Details Details
Add New Add New Add New Reduced Bulk Details

Items Items Items
Add New Items

Delete Delete Delete
Items Items Items
Delete Items
Update Update Update

Update Items
Items Items Items
Damage Bulk Details
Update Items
84
E F
Reports Details Grocery Damage Details
Bill Wise Item Wise Display Damage Update Items

Report Report Bulk
Add New Add New F G

Items Items
Delete Delete Customer Details

Items Items
Update Update
Items Items
Add New Delete Update Display
Customer Customer Customer Customer
Display Display details Details Details
Items Items
G H
Gift I/C Details Canteen Summary Details
Add Delete Update Display View Gift Day Wise Month Annual
Items to Items Items Items I/C Details Wise Details
Gift Bulk Details Details
Display Display Display

Details Details Details
13. PROCESS LOGIC

85
As all the programming is divided into different modules and they will interact
with each other to maintain the Data and Information. Modular structure is
designed with the consideration of case to maintain the Logic for modification and
maintenance. Since program has to interact with the database, it is basically based
on the User interface as Front-End Tool and Database as Back-End Tool. Each
module is interacting with Database gives the desired Output.
This project has the following modules:
 System Administrator Details
 Canteen Manager Details
 Grocery Salesman Detail
 Card Issuance Detail
 Grocery Bulk Details
 Grocery Shop I/C Details
 Customer Details
 Reports Details
 Grocery Damage Details
 Gift I/C Details
 Canteen Summary Details
86
The System Administrator Detail is the important module for this project. In this
module we are showing how many types of shops, counters and salesmans are
there in the Organization and how many items are there in the Bulk with their
Barcodes. We can add, delete & Update the Shop Details, Counter Details,
Salesman Details and Item Details etc in the Database. This module also performs
the Card Management process.

In this Module A Canteen Manager has the major responsibility of handling the
various tasks perform in the Organization. A Manager decides when to open the
Canteen and when to close it. In this module Manager will issue the Card to the
Customer create Customer account. Manager will also enquire that the Stock of
items is available or not and also approve the Refund and Duplicate Bills.
 Grocery Salesman Detail

In this module we can view the Salesman Details. How much sale is achieved by a
Salesman and how much refunded, and printing of Duplicate Bills is the various
task performed in this module. Here we are also showing the Salesman Summary.
 Card Issuance Detail

This is the very important module of this project as this module issues the Canteen
Card the Customer and also renew that Card. Without this Card Customer cannot
purchase any items. So this module is very important.

87
This module shows how much stock of items is there in the Bulk, Mini Bulk. What
are the Demands generated by the Manager if the items are not there in the Bulk
and Damage and Reduced Item Bulks are also shown in this module. Details of
how many items are transferred from Grocery Bulk to Damage Bulk is also shown
in this module.
 Grocery Shop I/C Details

In this module we can view the details of grocery I/C, add, delete and update the
Grocery details, Demand details, Voucher details etc.
In this module we are getting the Customer details for issuing Card to him/her
and store all the details in the database.
 Reports Details
In this module we are generating the Bill wise and Item wise reports for the
Customer and the Organization.
 Grocery Damage Details

In this module we are displaying the items in the Damage Bulk and update them
whenever necessary.
88
 Gift I/C Details

In this module we can view the details of Gift I/C, and add, delete, update and
display the Gift items in the Database.

In this module we are displaying the whole Canteen Summary i.e. Day wise Sale,
Monthly Sale and yearly Sale of Items in the Canteen. This is very important
module as this module shows how much Profit is earned by the Organization and
how much it grow.
14. SCOPE OF THE PROJECT

89
15. BIBLIOGRAPHY

S. PRESSMAN

 INFORMATICS PRACTICES BY SUMITA ARORA.
90
Inputs of the Project

 Canteen Master Details
 Grocery Master Details
 Card Management
 Shop Master Details
 Counter Master Details
 Salesman Details
 Item Details
 Barcode Details
 Cost Details
 Card Renew Details
 Operate PIN Details
 Customer Card Details
 View PIN Details
 Canteen Manager Work Details
 Canteen Opening/Closing Day Details
 Canteen Opening/Closing Month Details
 Enquiry Details
 Bill Approval Details
 Card Issue Details
 Customer Account Details
 Grocery Salesman Details
 Grocery Sales Details
 Grocery Refund Details
 Duplicate Bill Printing Details
 Salesman Summary Details
91
 New Card Registration Details

 Bulk Details
 Demand Details
 STB Details
 Reduced Bulk Details
 Damage Item Details
 Grocery InCharge Details
 Grocery Shop InCharge Details
 Voucher Details
 Mini Bulk Details
 Gift InCharge Work Details
 Gift Details
 Gift InCharge Details
 PIN Information Details
 Generate Bill Details
 Grocery Bill Details
 Refund Bill Approval Details
 Report Details
 Bill Wise Report Details
 Item Wise Report Details
 Canteen Summary Day Wise
 Canteen Summary Month Wise
 Canteen Summary Yearly
92
outputs of the Project

 Canteen Master Details
 Grocery Master Details
 Card Management
 Shop Master Details
 Counter Master Details
 Salesman Details
 Item Details
 Barcode Details
 Cost Details
 Card Renew Details
 Operate PIN Details
 Customer Card Details
 View PIN Details
 Canteen Manager Work Details
 Canteen Opening/Closing Day Details
 Canteen Opening/Closing Month Details
 Enquiry Details
 Bill Approval Details
 Card Issue Details
 Customer Account Details
 Grocery Salesman Details
 Grocery Sales Details
 Grocery Refund Details
 Duplicate Bill Printing Details
 Salesman Summary Details
93
 New Card Registration Details
 Bulk Details
 Demand Details
 STB Details
 Reduced Bulk Details
 Damage Item Details
 Grocery InCharge Details
 Grocery Shop InCharge Details
 Voucher Details
 Mini Bulk Details
 Gift InCharge Work Details
 Gift Details
 Gift InCharge Details
 PIN Information Details
 Generate Bill Details
 Grocery Bill Details
 Refund Bill Approval Details
 Report Details
 Bill Wise Report Details
 Item Wise Report Details
 Canteen Summary Day Wise
 Canteen Summary Month Wise
 Canteen Summary Yearly
94
3.4. user interface design
Startpage Form
95
Login Details Form
96
Welcome Form
97
Main Menu Form
98
System Administrator Form
99
Canteen Master Details Form
100
Shop Master Details Form
101
Salesman Counter Details Form
102
103
Salesman Details Form
104
Grocery Master Details Form
105
Item Details Form
106
Barcode Details Form
107
Cost Details Form
108
Card Management Form
109
Card Renew Form
110
Operate PIN Details Form

111
Customer Card Details Form
112
113
View PIN Details Form
114
Canteen Manager Work Form
115
Canteen Opening/Closing Day Details Form
116
Canteen Opening/Closing Month Details Form
117
Enquiry Details Form
118
Bill Approval Details Form
119
Card Issuance Details Form
120
Customer Account Details Form
121
122
Canteen Manager Details Form
123
Grgocery Salesman Details Form
Chapter 4
coding
124
4.1 complete project coding
1.code for start page form
package CMS;
public class Startpage extends javax.swing.JFrame {
/** Creates new form Startpage */

public Startpage() {
initComponents();
}
private void LoginBtnActionPerformed(java.awt.event.ActionEvent evt) {
this.setVisible(false);
new LoginDetails().setVisible(true);
}
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
125
public void run() {

new Startpage().setVisible(true);
}
});
}
// Variables declaration - do not modify

private javax.swing.JButton LoginBtn;
private javax.swing.JLabel jLabel2;
private javax.swing.JPanel jPanel1;
// End of variables declaration
2.code for login details form
package CMS;
import java.sql.*;
import javax.swing.JOptionPane;
public class LoginDetails extends javax.swing.JFrame {
/** Creates new form LoginDetails */

public LoginDetails() {
initComponents();
}
private void SubmitbtnActionPerformed(java.awt.event.ActionEvent evt) {
int scn=Integer.parseInt(SCNtf.getText());
int cc=Integer.parseInt(CCtf.getText());
if(cc==73)
126
{
new Welcome().setVisible(true);
}
else
{
JOptionPane.showMessageDialog(null,"Canteen code is Incorrect, Please
Check It");
}
}
public void run() {
new LoginDetails().setVisible(true);
}
});
}

private javax.swing.JTextField CCtf;
private javax.swing.JTextField SCNtf;
private javax.swing.JButton Submitbtn;
private javax.swing.JLabel cmdetails;
127
3.code for welcome form
package CMS;
public class Welcome extends javax.swing.JFrame {
/** Creates new form Welcome */

public Welcome() {
initComponents();
}
private void clickBtnActionPerformed(java.awt.event.ActionEvent evt) {
new MainMenu().setVisible(true);
}
public void run() {
new Welcome().setVisible(true);
}
});
}

private javax.swing.JButton clickBtn;
128
4.code for main menu form
package CMS;
public class MainMenu extends javax.swing.JFrame {
/** Creates new form MainMenu */

public MainMenu() {
initComponents();
}
private void cardIsuDActionPerformed(java.awt.event.ActionEvent evt) {
new CardIssueDetails().setVisible(true);
}
private void VSDActionPerformed(java.awt.event.ActionEvent evt) {

new SalesmanDetails().setVisible(true);
}
private void SABtnActionPerformed(java.awt.event.ActionEvent evt) {

new SystemAdmin().setVisible(true);
}
private void CMBtnActionPerformed(java.awt.event.ActionEvent evt) {

new ManagerWork().setVisible(true);
}
private void CantSBtnActionPerformed(java.awt.event.ActionEvent evt) {

new Canteen_Summary().setVisible(true);
}
private void GSBtnActionPerformed(java.awt.event.ActionEvent evt) {

new GrocerySalesman().setVisible(true);
129
private void CIBtnActionPerformed(java.awt.event.ActionEvent evt) {

new CardIssueDetails().setVisible(true);
}
private void CustIBtnActionPerformed(java.awt.event.ActionEvent evt) {

new CustomerDetails().setVisible(true);
}
private void ReportBtnActionPerformed(java.awt.event.ActionEvent evt) {

new ReportDetails().setVisible(true);
}
private void GiftICBtnActionPerformed(java.awt.event.ActionEvent evt) {

new GiftIncWork().setVisible(true);
}
private void SMDActionPerformed(java.awt.event.ActionEvent evt) {

new ShopMasterDetails().setVisible(true);
}
private void CntMDActionPerformed(java.awt.event.ActionEvent evt) {

new SalesmanCounterDetails().setVisible(true);
}
private void SalesManDActionPerformed(java.awt.event.ActionEvent evt) {

}
private void ItemdActionPerformed(java.awt.event.ActionEvent evt) {
130
new ItemDetails().setVisible(true);
}
private void bardActionPerformed(java.awt.event.ActionEvent evt) {

new BarcodeDetails().setVisible(true);
}
private void costdActionPerformed(java.awt.event.ActionEvent evt) {

new CostDetails().setVisible(true);
}
private void COCDDActionPerformed(java.awt.event.ActionEvent evt) {

new CanteenOCDayDetails().setVisible(true);
}
private void COCDMActionPerformed(java.awt.event.ActionEvent evt) {

new CanteenOCMonthDetails().setVisible(true);
}
private void EnquiryActionPerformed(java.awt.event.ActionEvent evt) {

new EnquiryDetails().setVisible(true);
}
private void RBAActionPerformed(java.awt.event.ActionEvent evt) {

new RefundBillApproval().setVisible(true);
}
private void DBAActionPerformed(java.awt.event.ActionEvent evt) {

new DuplicateBillPrinting().setVisible(true);
}
131
private void CCAActionPerformed(java.awt.event.ActionEvent evt) {

new CustomerAccountDetails().setVisible(true);
}
private void VMDActionPerformed(java.awt.event.ActionEvent evt) {

new CanteenManagerDetails().setVisible(true);
}
private void GSaleDActionPerformed(java.awt.event.ActionEvent evt) {

new GrocSaleDetails().setVisible(true);
}
private void GRefundDActionPerformed(java.awt.event.ActionEvent evt) {

new GrocRefundDetails().setVisible(true);
}
private void DBPDActionPerformed(java.awt.event.ActionEvent evt) {

new DuplicateBillPrinting().setVisible(true);
}
private void SalesmanSActionPerformed(java.awt.event.ActionEvent evt) {

new SalesmanSummary().setVisible(true);
}
private void RegisNCActionPerformed(java.awt.event.ActionEvent evt) {

new RegisterCard().setVisible(true);
}
private void RenewCActionPerformed(java.awt.event.ActionEvent evt) {

132
new CardRenew().setVisible(true);
}
private void DSINBActionPerformed(java.awt.event.ActionEvent evt) {

new BulkDetails().setVisible(true);
}
private void IssueMBActionPerformed(java.awt.event.ActionEvent evt) {

}
private void DisDDActionPerformed(java.awt.event.ActionEvent evt) {

new DemandDetails().setVisible(true);
}
private void DamageDActionPerformed(java.awt.event.ActionEvent evt) {

new DamageItemDetails().setVisible(true);
}
private void RIDActionPerformed(java.awt.event.ActionEvent evt) {

}
private void TItoDBActionPerformed(java.awt.event.ActionEvent evt) {

}
private void GroceryDActionPerformed(java.awt.event.ActionEvent evt) {

}
133
private void DemandDActionPerformed(java.awt.event.ActionEvent evt) {

new DemandDetails().setVisible(true);
}
private void VoucherDActionPerformed(java.awt.event.ActionEvent evt) {

new VoucherDetails().setVisible(true);
}
private void ReduceBulkDActionPerformed(java.awt.event.ActionEvent evt) {

}
private void DamageBulkdActionPerformed(java.awt.event.ActionEvent evt) {

}
private void BWReportActionPerformed(java.awt.event.ActionEvent evt) {

new BillWiseReport().setVisible(true);
}
private void IWReportActionPerformed(java.awt.event.ActionEvent evt) {

new ItemWiseReport().setVisible(true);
}
private void DisplayDBActionPerformed(java.awt.event.ActionEvent evt) {

}
private void UpdateItemsActionPerformed(java.awt.event.ActionEvent evt) {

134
private void AddCustActionPerformed(java.awt.event.ActionEvent evt) {

}
private void DelCustActionPerformed(java.awt.event.ActionEvent evt) {

}
private void UpdatCustActionPerformed(java.awt.event.ActionEvent evt) {

}
private void DispCustActionPerformed(java.awt.event.ActionEvent evt) {

}
private void AddItemsActionPerformed(java.awt.event.ActionEvent evt) {

new GiftDetails().setVisible(true);
}
private void DelItemsActionPerformed(java.awt.event.ActionEvent evt) {

}
private void UpdatItemsActionPerformed(java.awt.event.ActionEvent evt) {

}
private void DispItemsActionPerformed(java.awt.event.ActionEvent evt) {
135
}
private void ViewDetailsActionPerformed(java.awt.event.ActionEvent evt) {

new GiftIncharge().setVisible(true);
}
private void DWDActionPerformed(java.awt.event.ActionEvent evt) {

new CanteenSummary().setVisible(true);
}
private void MWDActionPerformed(java.awt.event.ActionEvent evt) {

new CSMonthWise().setVisible(true);
}
private void AnnualDActionPerformed(java.awt.event.ActionEvent evt) {

new CSAnnual().setVisible(true);
}
private void InchargeDActionPerformed(java.awt.event.ActionEvent evt) {

new GroceryIncDetails().setVisible(true);
}
private void GDBtnActionPerformed(java.awt.event.ActionEvent evt) {

}
private void GSICBtnActionPerformed(java.awt.event.ActionEvent evt) {

new GrShopICDetails().setVisible(true);
}
136
private void ExitBtnActionPerformed(java.awt.event.ActionEvent evt) {

// System.exit(0);
this.dispose();
}
private void GBBtnActionPerformed(java.awt.event.ActionEvent evt) {

new GroceryBulkDetails().setVisible(true);
}
private void renewdActionPerformed(java.awt.event.ActionEvent evt) {

new CardRenew().setVisible(true);
}
private void unblockCActionPerformed(java.awt.event.ActionEvent evt) {

new OperatePIN().setVisible(true);
}
private void DisplayCActionPerformed(java.awt.event.ActionEvent evt) {

}
private void SGBbtnActionPerformed(java.awt.event.ActionEvent evt) {

new PIN_Info().setVisible(true);
}
public void run() {
}
});
}
137

private javax.swing.JMenuItem AddCust;
private javax.swing.JMenuItem AddItems;
private javax.swing.JMenuItem AnnualD;
private javax.swing.JMenu BAD;
private javax.swing.JMenuItem BWReport;
private javax.swing.JMenuItem CCA;
private javax.swing.JButton CIBtn;
private javax.swing.JButton CMBtn;
private javax.swing.JMenu CManagerD;
private javax.swing.JMenu CMdetails;
private javax.swing.JMenuItem COCDD;
private javax.swing.JMenuItem COCDM;
private javax.swing.JButton CantSBtn;
private javax.swing.JMenu CanteenS;
private javax.swing.JMenu CardIssueD;
private javax.swing.JMenu CardMg;
private javax.swing.JMenuItem CntMD;
private javax.swing.JMenu CustDetails;
private javax.swing.JButton CustIBtn;
private javax.swing.JMenuItem DBA;
private javax.swing.JMenuItem DBPD;
private javax.swing.JMenuItem DSINB;
private javax.swing.JMenuItem DWD;
private javax.swing.JMenuItem DamageBulkd;
private javax.swing.JMenuItem DamageD;
private javax.swing.JMenuItem DelCust;
private javax.swing.JMenuItem DelItems;
private javax.swing.JMenuItem DemandD;
private javax.swing.JMenuItem DisDD;
private javax.swing.JMenuItem DispCust;
private javax.swing.JMenuItem DispItems;
private javax.swing.JMenuItem DisplayC;
private javax.swing.JMenuItem DisplayDB;
private javax.swing.JMenuItem Enquiry;
private javax.swing.JButton ExitBtn;
private javax.swing.JButton GBBtn;
private javax.swing.JMenu GBD;
138
private javax.swing.JButton GDBtn;

private javax.swing.JMenu GDamage;
private javax.swing.JMenu GMdetails;
private javax.swing.JMenuItem GRefundD;
private javax.swing.JButton GSBtn;
private javax.swing.JMenu GSD;
private javax.swing.JButton GSICBtn;
private javax.swing.JMenuItem GSaleD;
private javax.swing.JMenu GShopInc;
private javax.swing.JButton GiftICBtn;
private javax.swing.JMenu GiftInC;
private javax.swing.JMenuItem GroceryD;
private javax.swing.JMenuItem IWReport;
private javax.swing.JMenuItem InchargeD;
private javax.swing.JMenuItem IssueMB;
private javax.swing.JMenuItem Itemd;
private javax.swing.JMenuItem MWD;
private javax.swing.JMenuItem RBA;
private javax.swing.JMenuItem RID;
private javax.swing.JMenuItem ReduceBulkD;
private javax.swing.JMenuItem RegisNC;
private javax.swing.JMenuItem RenewC;
private javax.swing.JButton ReportBtn;
private javax.swing.JButton SABtn;
private javax.swing.JButton SGBbtn;
private javax.swing.JMenuItem SMD;
private javax.swing.JMenu STBD;
private javax.swing.JMenu STBDetails;
private javax.swing.JMenuItem SalesManD;
private javax.swing.JMenuItem SalesmanS;
private javax.swing.JMenuItem TItoDB;
private javax.swing.JMenuItem UpdatCust;
private javax.swing.JMenuItem UpdatItems;
private javax.swing.JMenuItem UpdateItems;
private javax.swing.JMenuItem VMD;
private javax.swing.JMenuItem VSD;
private javax.swing.JMenuItem ViewDetails;
private javax.swing.JMenuItem VoucherD;
139
private javax.swing.JMenuItem bard;

private javax.swing.JMenuItem cardIsuD;
private javax.swing.JMenuItem costd;
private javax.swing.JMenuBar jMenuBar1;
private javax.swing.JMenuItem renewd;
private javax.swing.JMenu reportD;
private javax.swing.JLabel secondLbl;
private javax.swing.JMenu sys_admenu;
private javax.swing.JMenu transD;
private javax.swing.JMenuItem unblockC;
5.code for system administrator details form
package CMS;
public class SystemAdmin extends javax.swing.JFrame {
/** Creates new form SystemAdmin */

public SystemAdmin() {
initComponents();
}
private void GroceryBtnActionPerformed(java.awt.event.ActionEvent evt) {

new GroceryMasterDetails().setVisible(true);
}
private void CanteenBtnActionPerformed(java.awt.event.ActionEvent evt) {

new CanteenMasterDetails().setVisible(true);
}
private void BackBtnActionPerformed(java.awt.event.ActionEvent evt) {

140
}
private void CardBtnActionPerformed(java.awt.event.ActionEvent evt) {

new CardManagement().setVisible(true);
}
public void run() {
}
});
}

private javax.swing.JButton BackBtn;
private javax.swing.JButton CanteenBtn;
private javax.swing.JButton CardBtn;
private javax.swing.JButton GroceryBtn;
6.code for Canteen master details form
package CMS;
public class CanteenMasterDetails extends javax.swing.JFrame {
/** Creates new form CanteenMasterDetails */

public CanteenMasterDetails() {
initComponents();
}
private void CounterBtnActionPerformed(java.awt.event.ActionEvent evt) {
141
}
private void ShopBtnActionPerformed(java.awt.event.ActionEvent evt) {

}
private void SalesmanBtnActionPerformed(java.awt.event.ActionEvent evt) {
}
}

public void run() {
}
});
}

private javax.swing.JButton CounterBtn;
private javax.swing.JButton SalesmanBtn;
private javax.swing.JButton ShopBtn;
7.code for shop master details form
142
package CMS;
import java.sql.*;
public class ShopMasterDetails extends javax.swing.JFrame {
/** Creates new form ShopMasterDetails */

public ShopMasterDetails() {
initComponents();
}

}
private void ViewBtnActionPerformed(java.awt.event.ActionEvent evt) {
int sc=Integer.parseInt(sctf.getText());
try {
Class.forName("java.sql.Driver");
String database="jdbc:mysql://localhost/cms";
Connection conn=DriverManager.getConnection(database,"root","tiger");
Statement stmt = conn.createStatement();
String sql="SELECT * FROM Shop_Master_details WHERE Shop_Code = " +
sc;
ResultSet rs = stmt.executeQuery(sql);
rs.next();
String str1=rs.getString("S_No");
sntf.setText(str1);
String str2=rs.getString("Shop_Name");
snamtf.setText(str2);
String str3=rs.getString("Shop_Type");
sttf.setText(str3);
rs.close();
stmt.close();
conn.close();
143
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Enter Correct Shop Code, Error
Occur...");
}
}
private void AddBtnActionPerformed(java.awt.event.ActionEvent evt) {

int sn=Integer.parseInt(sntf.getText());
String Shnam=snamtf.getText();
String Shtyp=sttf.getText();
try {
String sql="Insert into Shop_Master_details VALUES ( " + sn +","+ sc +",'"+
Shnam+"','"+ Shtyp + "')";
stmt.executeUpdate(sql);
sntf.setText(" ");
sctf.setText(" ");
snamtf.setText(" ");
sttf.setText(" ");
JOptionPane.showMessageDialog(null,"Shop detail is added, Now You can
View it by Clicking on View Button or Add more...");
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"There is an Error, Please Check It");
}
144
private void DeleteBtnActionPerformed(java.awt.event.ActionEvent evt) {

try {
String sql="DELETE FROM Shop_Master_details WHERE Shop_Code = " +
sc ;
sntf.setText(" ");
sctf.setText(" ");
sttf.setText(" ");
stmt.close();
conn.close();
}
catch(Exception e)
{
Occur...");
}
}
private void UpdateBtnActionPerformed(java.awt.event.ActionEvent evt) {
try {
Statement stmt1 = conn.createStatement();
String sql1="UPDATE Shop_Master_details SET Shop_Name =
'"+snamtf.getText()+ "' WHERE Shop_Code = " + sc ;
String sql2="UPDATE Shop_Master_details SET Shop_Type = '"+sttf.getText()
+ "' WHERE Shop_Code = " + sc ;
stmt1.executeUpdate(sql1);
145
stmt1.close();
stmt2.close();
conn.close();
JOptionPane.showMessageDialog(null,"Information Updated Sucessfully");
}
catch(Exception e)
{
Occur...");
}
}

public void run() {
}
});
}

private javax.swing.JButton AddBtn;
private javax.swing.JButton DeleteBtn;
private javax.swing.JButton UpdateBtn;
private javax.swing.JButton ViewBtn;
private javax.swing.JTextField sctf;
private javax.swing.JTextField snamtf;
private javax.swing.JTextField sntf;
private javax.swing.JTextField sttf;
146
8.code for salesman counter details form
package CMS;
import java.sql.*;
public class SalesmanCounterDetails extends javax.swing.JFrame {
/** Creates new form SalesmanCounterDetails */

public SalesmanCounterDetails() {
initComponents();
}

}
private void ADDBtnActionPerformed(java.awt.event.ActionEvent evt) {

int cid=Integer.parseInt(cidtf.getText());
int sid=Integer.parseInt(sidtf.getText());
String cn=cntf.getText();
String chksc=chktf.getText();
try {
String sql="Insert into Salesman_Counter_details VALUES ( " + cid +","+ sid
+",'"+ cn +"','"+ chksc +"')";
cidtf.setText(" ");
cntf.setText(" ");
sidtf.setText(" ");
147
chktf.setText(" ");
JOptionPane.showMessageDialog(null,"Counter detail is added, Now You can
stmt.close();
conn.close();
}
catch(Exception e)
{
}

try {
String sql="SELECT * FROM Salesman_Counter_details
SC,Shop_Master_details SM WHERE Counter_id = " + cid +" AND SC.Shop_id =
SM.Shop_Code";
rs.next();
String str1=rs.getString("Counter_Name");
cntf.setText(str1);
String str2=rs.getString("Shop_id");
sidtf.setText(str2);
String str3=rs.getString("Shop_Name");
snamtf.setText(str3);
String str4=rs.getString("Chk_smartcard");
chktf.setText(str4);
rs.close();
stmt.close();
conn.close();
}
catch(Exception e)
148
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Counter ID
...");
}
}

try {
String sql1="UPDATE Salesman_Counter_details SET Counter_Name =
'"+cntf.getText()+ "' WHERE Counter_id = " + cid ;
String sql2="UPDATE Salesman_Counter_details SET Shop_id =
"+sidtf.getText()+ " WHERE Counter_id = " + cid ;
stmt1.close();
stmt2.close();
conn.close();
}
catch(Exception e)
{
...");
}
}

try {
149

String sql="DELETE FROM Salesman_Counter_details WHERE Counter_id = "
+ cid ;
cidtf.setText(" ");
cntf.setText(" ");
sidtf.setText(" ");
chktf.setText(" ");
stmt.close();
conn.close();
}
catch(Exception e)
{
...");
}
}

public void run() {
}
});
}

private javax.swing.JButton ADDBtn;
private javax.swing.JTextField chktf;
private javax.swing.JTextField cidtf;
private javax.swing.JTextField cntf;
150

private javax.swing.JTextField sidtf;
private javax.swing.JTextField snamtf;
9.code for salesman details form
package CMS;
import java.sql.*;
public class SalesmanDetails extends javax.swing.JFrame {
/** Creates new form SalesmanDetails */

public SalesmanDetails() {
initComponents();
}
private void BackbtnActionPerformed(java.awt.event.ActionEvent evt) {

}

int si=Integer.parseInt(sitf.getText());
String sn=sntf.getText();
String adr=adrta.getText();
String cn=cntf.getText();
String gn=gntf.getText();
try {
151
String sql="Insert into Salesman_details VALUES ( " + si +",'"+ sn +"','"+
gntf.getText()+"','"+ adr +"',"+ cid +")";
sitf.setText(" ");
sntf.setText(" ");
adrta.append(" ");
cidtf.setText(" ");
cntf.setText(" ");
JOptionPane.showMessageDialog(null,"Salesman detail is added, Now You

can View it by Clicking on View Button or Add more...");
stmt.close();
conn.close();
}
catch(Exception e)
{
}
}

try {
String sql="SELECT * FROM Salesman_details SD,Salesman_Counter_details
SC WHERE Salesman_id = " + si +" AND SD.Counter_id = SC.Counter_id";
rs.next();
String str1=rs.getString("SName");
sntf.setText(str1);
String str2=rs.getString("Gender");
152
gntf.setText(str2);
String str3=rs.getString("Address");
adrta.append(str3);
String str4=rs.getString("Counter_id");
cidtf.setText(str4);
String str5=rs.getString("Counter_Name");
cntf.setText(str5);
rs.close();
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Salaesman
ID ...");
}
}
private void gntfActionPerformed(java.awt.event.ActionEvent evt) {

try {
String sql1="UPDATE Salesman_details SET SName = '"+sntf.getText()+ "'
WHERE Salesman_id = " + si ;
String sql2="UPDATE Salesman_details SET Gender = '"+gntf.getText()+ "'
String sql3="UPDATE Salesman_details SET Address = '"+adrta.getText()+ "'
153
String sql4="UPDATE Salesman_details SET Counter_id = '"+cidtf.getText()+ "'

stmt1.close();
stmt2.close();
stmt3.close();
stmt4.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Salesman
ID ...");
}
}

try {
String sql="DELETE FROM Salesman_details WHERE Salesman_id = " + si ;
sitf.setText(" ");
sntf.setText(" ");
gntf.setText(" ");
adrta.append(" ");
cidtf.setText(" ");
cntf.setText(" ");
stmt.close();
conn.close();
}
154
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Salesman
ID ...");
}
}

public void run() {
}
});
}

private javax.swing.JButton Backbtn;
private javax.swing.JTextArea adrta;
private javax.swing.JTextField cidtf;
private javax.swing.JTextField cntf;
private javax.swing.JTextField gntf;
private javax.swing.JScrollPane jScrollPane1;
private javax.swing.JTextField sitf;
155
10.code for grocery master details form
package CMS;
public class GroceryMasterDetails extends javax.swing.JFrame {
/** Creates new form GroceryMasterDetails */

public GroceryMasterDetails() {
initComponents();
}
private void ItemBtnActionPerformed(java.awt.event.ActionEvent evt) {

}
private void BarcodeBtnActionPerformed(java.awt.event.ActionEvent evt) {

}
private void CostBtnActionPerformed(java.awt.event.ActionEvent evt) {

new CostDetails().setVisible(true);
}

}

public void run() {
156
}
});
}

private javax.swing.JButton BarcodeBtn;
private javax.swing.JButton CostBtn;
private javax.swing.JButton ItemBtn;
11.code for item details form
package CMS;
import java.sql.*;
import javax.swing.table.*;
public class ItemDetails extends javax.swing.JFrame {
/** Creates new form ItemDetails */

public ItemDetails() {
initComponents();
}

String in=intf.getText();
String pn=pntf.getText();
String id=idtf.getText();
String gr=grtf.getText();
String gh=ghtf.getText();
int au=Integer.parseInt(autf.getText());
int mq=Integer.parseInt(mqtf.getText());
157
double mpp=Double.parseDouble(mpptf.getText());
String ic=ictf.getText();
int cp=Integer.parseInt(cptf.getText());
double tp=Double.parseDouble(tptf.getText());
double ta=Double.parseDouble(tatf.getText());
String md=mdtf.getText();
double pr=Double.parseDouble(prtf.getText());
double vp=Double.parseDouble(vptf.getText());
double va=Double.parseDouble(vatf.getText());
String gs=gstf.getText();
double tpt=pr+ta;
double tpv=pr+va;
tpttf.setText(" "+tpt);
tpvtf.setText(" "+tpv);
DefaultTableModel dm = (DefaultTableModel)ItemTbl.getModel();
try {
String sql="Insert into Item_details VALUES ( '" + in +"','"+ pn +"','"+ id +"','"+
gr +"','"+ gh +"',"+ au +","+ mq +","+ mpp +",'"+ ic +"',"+ cp +","+ tp +","+ ta +",'"+
md +"',"+ sc +",'"+ gs +"',"+ pr +","+ vp +","+ va +","+ tpt +","+ tpv +")";
Object[] newRow= {
intf.getText(),pntf.getText(),idtf.getText(),grtf.getText(),ghtf.getText(),autf.getText(),
mqtf.getText(),mpptf.getText(),ictf.getText(),cptf.getText(),tptf.getText(),tatf.getText
(),mdtf.getText(),sctf.getText(),gstf.getText(),prtf.getText(),vptf.getText(),vatf.getTex
t(),tpttf.getText(),tpvtf.getText() };
dm.addRow(newRow);
intf.setText(" ");
pntf.setText(" ");
idtf.setText(" ");
grtf.setText(" ");
ghtf.setText(" ");
autf.setText(" ");
mqtf.setText(" ");
158
mpptf.setText(" ");
ictf.setText(" ");
cptf.setText(" ");
tptf.setText(" ");
tatf.setText(" ");
mdtf.setText(" ");
sctf.setText(" ");
gstf.setText(" ");
prtf.setText(" ");
vptf.setText(" ");
vatf.setText(" ");
tpttf.setText(" ");
tpvtf.setText(" ");
JOptionPane.showMessageDialog(null,"Item detail is added, Now You can
stmt.close();
conn.close();
}
catch(Exception e)
{
}
}

DefaultTableModel dm = (DefaultTableModel)ItemTbl.getModel();
try {
String sql="SELECT * FROM Item_details ID, Shop_Master_details SD
WHERE Index_No =’ " + in +"' AND ID.Shop_Code=SD.Shop_Code";
rs.next();
String str1=rs.getString("Pluno_No");
pntf.setText(str1);
159
String str2=rs.getString("Item_desc");
idtf.setText(str2);
String str3=rs.getString("Group_Name");
grtf.setText(str3);
String str4=rs.getString("Generic_Head");
ghtf.setText(str4);
String str5=rs.getString("Amt_Unit");
autf.setText(str5);
String str6=rs.getString("Max_Qty");
mqtf.setText(str6);
String str7=rs.getString("MPP");
mpptf.setText(str7);
String str8=rs.getString("Item_cat");
ictf.setText(str8);
String str9=rs.getString("Case_pack");
cptf.setText(str9);
String str10=rs.getString("Tax_perc");
tptf.setText(str10);
String str11=rs.getString("Tax_amt");
tatf.setText(str11);
String str12=rs.getString("Medium");
mdtf.setText(str12);
String str13=rs.getString("Shop_Code");
sctf.setText(str13);
String str14=rs.getString("Shop_Type");
sttf.setText(str14);
String str15=rs.getString("Price");
prtf.setText(str15);
String str16=rs.getString("Vat_perc");
vptf.setText(str16);
String str17=rs.getString("Vat_amt");
vatf.setText(str17);
String str18=rs.getString("GiftScheme");
gstf.setText(str18);
String str19=rs.getString("TotPrice_Tax");
tpttf.setText(str19);
String str20=rs.getString("TotPrice_VAT");
tpvtf.setText(str20);
160
Object[] newRow= {
intf.getText(),pntf.getText(),idtf.getText(),grtf.getText(),ghtf.getText(),autf.getText(),
mqtf.getText(),mpptf.getText(),ictf.getText(),cptf.getText(),tptf.getText(),tatf.getText
(),mdtf.getText(),sctf.getText(),sttf.getText(),prtf.getText(),vptf.getText(),vatf.getTex
t(),gstf.getText(),tpttf.getText(),tpvtf.getText()
};
dm.addRow(newRow);
rs.close();
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Index
No ...");
}
}

try {
161

String sql1="UPDATE Item_details SET Pluno_No = '"+pntf.getText()+ "'
WHERE Index_No = ‘" + in + "'" ;
String sql2="UPDATE Item_details SET Item_desc = '"+idtf.getText()+ "'
WHERE Index_No =’ " + in + "'" ;
String sql3="UPDATE Item_details SET Group_Name = '"+grtf.getText()+ "'
String sql4="UPDATE Item_details SET Generic_Head = '"+ghtf.getText()+ "'
String sql5="UPDATE Item_details SET Amt_Unit = "+autf.getText()+ "
String sql6="UPDATE Item_details SET Max_Qty = "+mqtf.getText()+ "
String sql7="UPDATE Item_details SET MPP = "+mpptf.getText()+ " WHERE
Index_No = ‘" + in + "'" ;
String sql8="UPDATE Item_details SET Item_cat = '"+ictf.getText()+ "' WHERE
Index_No = ‘" + in + "'" ;
String sql9="UPDATE Item_details SET Case_pack = "+cptf.getText()+ "
String sql10="UPDATE Item_details SET Tax_perc = "+tptf.getText()+ "
String sql11="UPDATE Item_details SET Tax_amt = "+tatf.getText()+ "
String sql12="UPDATE Item_details SET Medium = '"+mdtf.getText()+ "'
String sql13="UPDATE Item_details SET Shop_Code = "+sctf.getText()+ "
String sql14="UPDATE Item_details SET Shop_Type = '"+sttf.getText()+ "'
String sql15="UPDATE Item_details SET Price = "+prtf.getText()+ " WHERE
Index_No = ‘" + in + "'" ;
String sql16="UPDATE Item_details SET Vat_perc = "+vptf.getText()+ "
162
String sql17="UPDATE Item_details SET Vat_amt = "+vatf.getText()+ "

String sql18="UPDATE Item_details SET GiftScheme = '"+gstf.getText()+ "'
stmt1.close();
stmt2.close();
stmt3.close();
stmt4.close();
stmt5.close();
stmt6.close();
stmt7.close();
stmt8.close();
stmt9.close();
stmt10.close();
stmt11.close();
stmt12.close();
stmt13.close();
stmt14.close();
stmt15.close();
stmt16.close();
163
stmt17.close();
stmt18.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur in Updating
Information..");
}
}

try {
String sql="DELETE FROM Item_details WHERE Index_No = ‘" + in +”’” ;
intf.setText(" ");
pntf.setText(" ");
idtf.setText(" ");
grtf.setText(" ");
ghtf.setText(" ");
autf.setText(" ");
mqtf.setText(" ");
mpptf.setText(" ");
ictf.setText(" ");
cptf.setText(" ");
tptf.setText(" ");
tatf.setText(" ");
mdtf.setText(" ");
sctf.setText(" ");
sttf.setText(" ");
gstf.setText(" ");
prtf.setText(" ");
164
vptf.setText(" ");
vatf.setText(" ");
tpttf.setText(" ");
tpvtf.setText(" ");
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur in Deleting
Information..");
}
}

}

public void run() {
}
});
}

private javax.swing.JTable ItemTbl;
private javax.swing.JTextField autf;
private javax.swing.JTextField cptf;
private javax.swing.JTextField ghtf;
165
private javax.swing.JTextField grtf;

private javax.swing.JTextField gstf;
private javax.swing.JTextField ictf;
private javax.swing.JTextField idtf;
private javax.swing.JTextField intf;
private javax.swing.JTextField mdtf;
private javax.swing.JTextField mpptf;
private javax.swing.JTextField mqtf;
private javax.swing.JTextField pntf;
private javax.swing.JTextField prtf;
private javax.swing.JTextField sctf;
private javax.swing.JTextField sttf;
private javax.swing.JTextField tatf;
private javax.swing.JTextField tptf;
166
private javax.swing.JTextField tpttf;

private javax.swing.JTextField tpvtf;
private javax.swing.JTextField vatf;
private javax.swing.JTextField vptf;
12.code for barcode details form
package CMS;
import java.sql.*;
import javax.swing.table.*;
public class BarcodeDetails extends javax.swing.JFrame {
/** Creates new form BarcodeDetails */

public BarcodeDetails() {
initComponents();
}

int bn=Integer.parseInt(bntf.getText());
DefaultTableModel dm = (DefaultTableModel)barcodeTbl.getModel();
try {
String sql="Insert into Barcode_details VALUES ( " + sn +",'"+ in +"',"+ bn +")";
Object[] newRow= {
sntf.getText(),intf.getText(),bntf.getText()
};
dm.addRow(newRow);
167
sntf.setText(" ");
intf.setText(" ");
pntf.setText(" ");
itemtf.setText(" ");
bntf.setText(" ");
JOptionPane.showMessageDialog(null,"Barcode detail is added, Now You can
stmt.close();
conn.close();
}
catch(Exception e)
{
}
}

DefaultTableModel dm = (DefaultTableModel)barcodeTbl.getModel();
try {
String sql="SELECT * FROM Barcode_details BD,Item_details ID WHERE
S_No = " + sn +" AND BD.Index_No = ID.Index_No";
rs.next();
String str1=rs.getString("Index_No");
intf.setText(str1);
String str2=rs.getString("Pluno_no");
pntf.setText(str2);
String str3=rs.getString("Item_desc");
itemtf.setText(str3);
String str4=rs.getString("Barcode_no");
bntf.setText(str4);
Object[] newRow= {
sntf.getText(),intf.getText(),pntf.getText(),itemtf.getText(),bntf.getText()
168
};
dm.addRow(newRow);
rs.close();
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur..,Enter Correct Serial
No ...");
}
}

}

try {
String sql1="UPDATE Barcode_details SET Index_No = '"+intf.getText()+ "'
WHERE S_No = " + sn ;
String sql2="UPDATE Barcode_details SET Barcode_no = "+bntf.getText()+ "
WHERE S_No = " + sn ;
stmt1.close();
stmt2.close();
conn.close();
}
catch(Exception e)
169
{
JOptionPane.showMessageDialog(null,"Error Occur in Updating
Information..");
}
}

try {
String sql="DELETE FROM Barcode_details WHERE S_No = " + sn ;
sntf.setText(" ");
intf.setText(" ");
pntf.setText(" ");
itemtf.setText(" ");
bntf.setText(" ");
stmt.close();
conn.close();
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"Error Occur in Deleting
Information..");
}
}

public void run() {
}
});
}
170

private javax.swing.JTable barcodeTbl;
private javax.swing.JTextField bntf;
private javax.swing.JTextField intf;
private javax.swing.JTextField itemtf;
private javax.swing.JTextField pntf;
4.2 code efficiency

In an effort to maintain computational efficiency and to allow the eventual
adaptation of the algorithm to face tracking applications, intense optimization of
the code has been performed. Although further development is in progress, the
algorithm is currently fast and compact enough to run interactively on most
generic platforms. Note, first, the sequential hierarchical search which proceeds
171
from large scales to small scales. This allows a rapid convergence if the face is
dominant in the image. Furthermore, the algorithm does not always flow through
the complete loop. It stops as soon as one of the modules reports a failure and
loops back to an earlier stage. For example, we do not sale items to the Customer
until the correct PIN No is entered. In this case, no time is wasted, if PIN No
entered is not correct then Error Message will appear .
Additionally, in this Project I have utilized special programming techniques to

reduce the run-time. The 3rd-normalization algorithm is also extremely efficient
and uses look-up tables and minimal calculations for increased speed.
4.3 optimisation of code

Optimization refers to increase in the throughput of the system with minimal use
of effort and system resources. It also includes faster response through better
system design practices including optimal utilization of code, normalized database
structures and their use in the code.The very first instance that stands for
172
optimization of this application is that it would prove to be most favorable and best
possible for the progress in the working of the company.
This system is optimized because all the modules are more cohesive that the
connectivity among the modules is less. So that it will take less time to complete
any process. As the modules are less dependent on each other so in future if we
want to make any changes in our system then it will be very easy to change system
and we have to make changes only on those modules that we have to change. If our
system will not be cohesive then in this case it will take more time to complete any
process and the efficiency of the system to do work will be poor.
The other criteria that ensure the optimization of this software application are
enlisted as under:-
 Use of modular design structure of application development.
 Use of Normalized Database Structures-Database Optimization.
 Use of code modules extensively-Code Optimization.
 Use of minimum number of code lines for maximum processing of input
data.
 Re-use of similar code wherever necessary to reduce the overall size of the
application.
We find optimal solution of a project that is cost effective as well as time effective.
Both are equally important for a project we divide the project into modules so that
we can easily understand the project. And also it will take less time to solve the
problems. Modularity is the single attribute of software that allows a program to be
intellectually manageable.
4.4 validation checks

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 test - Validation Testing - may begin. Validation can be defined in many
ways, but a simple is that validation succeeds when software functions in a manner
that can be reasonably expected by the customer.
173
Validation is an important characteristic of a good project because many times it

has been seen that running project may come to a halt stage or just because of
ignorance of validation invalid or insufficient data may get enter in the database.
In this project I adopted many level of validations like in any entry form user is not
supposed to leave any field blank.
As there is a form CUSTOMER DETAILS, in which there are some fields which are
mandatory like Name, Gender, Address, DOB, etc and also some fields are optional
because it might be possible that it does not have any unessential field which is not
required in data storage.
Then in the second level of validation I have checked individual fields like the
Name can not be numeric, Personal No. should not contain any alphabet, if by
mistake any alphabets are entered then the message appears that Personal No.
should be in Digits.
The Canteen Code, it is checked that the Canteen Code shall not be less than two
digits. Similarly the Balance field in Customer Account Details, it has been checked
that it should not contain any negative values. Other fields have also been
validated which can be found out in the coding.
174
Chapter 5
Testing
5.1 Testing techniques &

testing strategies
Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing
are used later on during maintenance also.
Psychology of Testing:
175
The aim of testing is often to demonstrate that a program works by showing that it
has no errors. The basic purpose of testing phase is to detect the errors that may be
present in the program. Hence one should not start testing with the intent of
showing that a program works, but the intent should be to show that a program
doesn’t work.
Testing is the process of executing a program with the intent of finding errors.
Testing Objectives:
The main objective of testing is to uncover a host of errors, systematically and with
minimum effort and time. Stating formally, we can say,
 Testing is a process of executing a program with the intent of finding an
error.
 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
 The tests are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.
Levels of Testing :
In order to uncover the errors present in different phases we have the concept of
levels of testing. The basic levels of testing are
Client Needs
Acceptance Testing
Requirements System Testing
Design Integration Testing
176
Code Unit Testing
Unit testing:
Unit testing focuses verification effort on the smallest unit of software i.e. the
module. Using the detailed design and the process specifications testing is done to
uncover errors within the boundary of the module. All modules must be
successful in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. There are so many
modules like Login, Register New Card, Card Issuance, Search Items, View
Customer details, Generate Bill etc.. Each module has been tested by giving
different sets of inputs. When developing the module as well as finishing the
development so that each module works without any error. The inputs are
validated when accepting from the user.
Integration Testing:
After the unit testing we have to perform integration testing. The goal here is to see
if modules can be integrated properly. The emphasis being on testing interfaces
between modules. This testing activity can be considered as testing the design and
hence the emphasis on testing module interactions.
In this project the main system is formed by integrating all the modules. When
integrating all the modules I have checked whether the integration effects working
of any of the services by giving different combinations of inputs with which the
two services run perfectly before Integration.
System Testing:
Here the entire software system is tested. The reference document for this process
is the requirements document, and the goal as to see if software meets its
requirements.
Here entire ‘CANTEEN MANAGEMENT SYSTEM’ has been tested against
requirements of project and it is checked whether all requirements of project have
been satisfied or not.
177
Acceptance Testing:
Acceptance Test is performed with realistic data of the client to demonstrate that
the software is working satisfactorily. Testing here is focused on external behavior
of the system. The internal logic of program is not emphasized.
Test cases should be selected so that the largest number of attributes of an
equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations
and also a complete verification to determine whether the objectives are met and
the user requirements are satisfied.
White Box Testing:

This is a unit testing method where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.
I tested step wise every piece of code, taking care that every statement in the code
is executed at least once. The white box testing is also called Glass Box Testing.
I have generated a list of test cases, sample data. Which is used to check all possible
combinations of execution paths through the code at every module level.
Black Box Testing:

This testing method considers a module as a single unit and checks the unit at
interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block box that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.
Tests Conducted on the System
Testing Phase Objectives

Unit The various functions within each program and the
program blocks are tested for proper working.
Testing
178
A module is composed of various programs related to

Module that module. Module testing is done to check the
Testing module functionality and interaction between units

within a module
Integration Integration testing is done to test the functionality and
Testing interfacing between the modules.
Acceptance testing is done after implementation to
Acceptance
check if the system runs successfully in the customer
Testing
environment/site.
5.2 implementation
One of the crucial phases in the Software Development Life Cycle is the successful
implementation of the software. Implementation includes all those activities that
take place to convert from the old system to the new one.
The new system may be completely new, replacing an existing manual or
automated system or it may be major modification to an existing system. In either
case, proper implementation becomes necessary so that a reliable system based on
the requirements of the organization can be provided.
Successful implementation may not guarantee improvement in the organization
using the new system, but improper installation will prevent it. It has been
observed that even the best system cannot show good result if the analysts
managing the implementation do not attend to every important detail. This is an
area where the systems analysts need to work with utmost care.
In this Project the implementation discusses the three aspects of implementation
179
 Training personnel
 Conversion procedures
 Post- implementation review
5.3 evaluation
In this Project much of the management is decision making, according to one of
many approaches to management. While there are several views of what
constitutes management, according to the decision oriented view, management
mainly comprises the following in view of this project:
 Planning
 Organizing
 Directing and
 Control
Each one of these functions may be at the strategic, tactical or operational level. To
illustrate this point we will use a series of examples of strategic, tactical and
operational decisions and the information needs, in each of these functional areas.
5.4 Maintenance
The last part of the system development life cycle is system Maintenance which is
actually the implementation of the post – implementation review plan. When
180
systems are installed they are generally used for long periods. The average life of a
system is 4 to 6 years with oldest application often in use for over 10 years.
However, this period of use brings with it the need to continually maintain the
system.
Programmers/analyst sends sufficient time for maintaining programs. The study
on the maintenance requirement for the information system of this Project AIR
FORCE CANTEEN MANAGEMENT SYSTEM revealed that:
(a) Sixty to Ninety percent of the overall cost of the software during life of a
system is spent on maintenance.
(b) In documented cases, cost of maintenance, when measured on the basis of
writing each instruction in coding form, is more than the 50 times the cost of
developing a system.
(c) The software demand is increasing at a faster rate than supply many
programmers are devoting more time on system maintenance than on a new
software development. There is backlog of new development work.
So in this Project the maintenance can be classified as:

 Corrective
 Adaptation or perfective.
Corrective maintenance means repairing, processing or performance failures or

making alterations because of previously ill-defined problems.
Adaptation maintenance means changing the program functions. Enhancing the

performance or modifying the programs according to user additional or changing
needs are included in perfective maintenance the greatest amount of maintenance
work is for user enhancement and improve documentation of the system for better
efficiency. More time and money are spent on perfective than on corrective and
adaptive maintenance together.
Maintenance covers a wide range of activities including correcting coding and

design errors, updating documentation and test data and upgrading user support.
Many activities classified to its original position. Unlike hardware, software does
181
not wear out ; it is corrected. In contrast enhancement means adding, modifying or

redeveloping the code to support changes in the specifications.
The keys to reduce the need for maintenance while making it possible to carry on
with essential tasks more efficiently as follows.
 More accurately defining the user’s requirement during system development.

 Preparation of system documentation in a better way.
 Using more effective ways for designing processing logic and communicating
it to project team members.
 Making better use of existing tools and techniques.
 Managing the systems engineering process effectively.
An addition factor in the success of the maintenance programmer is the work

environment. Maintenance programmers have generally been paid less amounts
and receive less recognition than other programmers.
Little attention has been paid to their training and career plans with the MIS
functions. Maintenance demands more orientation and training then any other
programming activities, especially for entry-level programmers. The environment
must recognize the needs of the maintenance programmer for tools, methods and
training.
182
Chapter 6
Security
measures
&
183
cost
estimation
6.1 system Security measures
The Security Measures is the most important task, which should be done with
much care no need to say why this is so crucial. The security measures starts right
from the selection of operating system in that case for server MySQL is best choice
because it provides best security in its peer OS as we know this project is very
versatile and there are variety of users who uses systems according to their needs
so authentication is an major task which has to perform by the system
administrator as I have already mentioned that there are different type of access
permission like viewing the records modifying etc.
Here, I am using Java NetBeans IDE, which offers more security to make its
programs safe and secure.
Another security measure I took in this project is System Card No. and Canteen
Code, provide to selected staff so that no unidentified person can not access the
system.Then I switch the concept of file sharing which is an essential service in
these types of companies. Particular type of file can be shared by the person
holding the same position.
184
185
6.2 cost estimation of the project
The software project management process begins with a set of activities that are
collectively called project planning. The first of these activities is ESTIMATION.
Whenever estimates are made. We look into the future and accept some degree of
uncertainty as a matter of course. Estimation of resources, cost and schedule for a
software development effort requires experiences, access to good historical
information and the courage to commit to quantitative measures when qualitative
data are all the exist. Estimation carries inherent risk that leads to uncertainly.
Project size is another important factor can affect the accuracy of estimates. As size
increases, the interdependency among various elements of the software grows
rapidly time also affect cost of the project. If time increases then cost is also
increased, this project takes six months for completion.
Risk is measured by the degree if uncertainty in the quantitative estimates

established for resources, cost and schedule. If project scope is poorly understand
or project requirements are subject to change, uncertainty and risk factors become
dangerously high. The software planner should demand completeness of function
performance and interface definitions. The planner and the customer should
recognize that variability in software requirement means instability in cost and
schedule, a project manager should not become obsessive about the estimation, and
modern software engineering approaches take an iterative view of development. In
such approaches, it is possible to revisit the estimate and revise it when customer
makes changes to the requirements.
186
Cost estimation for canteen MANAGEMENT SYSTEM
No. of s/w Developer 1

S/W Development charges Rs. 300 per day
Project development duration 90 days
Cost of developer Rs 27,000/-
Cost of Development : cost of man work + misc. cost
: 27000 + 3000
: 30000 INR
So the estimated cost of this Project is around 30,000 Indian Rupees.
187
Chapter 7
Reports
8.1 Future Scope of the project

188
8.2 CONCLUSION
Now we conclude that:
189
 Using the Computerized software for Canteen Management System, the sale
of Items is done very easily & very fastly.
 Workload is reduced as whatever is done manually at past, now it is done

through the computerized software.
 This computerized System will save time as it Sale the Items & generate the
Bill for different people very quickly & maximize the profit for the
Organisation.
 This being a big step in terms of improvement in the Canteen Management

System it is widely accepted across the Country.
8.3 LIMITATIONS OF THE SYSTEM
 The knowledge possessed by me as an post graduate student is incomplete to

give sufficient information of organization.
 This software has to go for numerous changes if implemented anywhere, as it

has not been developed with larger perspective.
bibliography

S. PRESSMAN
190

 INFORMATICS PRACTICES BY SUMITA ARORA.
191

Air Force Canteen Management System

Uploaded by

Copyright:

Available Formats

Air Force Canteen Management System

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Air Force Canteen Management System

Uploaded by

Copyright:

Available Formats

AIR FORCE CANTEEN MANAGEMENT SYSTEM

Indira Gandhi National Open University

Main Objectives of CMS are:

3. OBJECTIVES OF THE PROJECT

 The objective of the project is to design a computerized Canteen Management

This project is under the category of “RDBMS”.

Relational Database Management System has permeated every segment of

Facilities offered by RDBMS:

 Creation of files, Addition of data, Deletion of data, Modification of data.

5. TOOLS/PLATFORM, HARDWARE & SOFTWARE

 Front End Tool : Java with Net Beans.

 Back End Tool : MySQL.

MINIMUM HARDWARE REQUIREMENT :

 PROCESSOR : PENTIUM IV PROCESSOR

OPERATING SYSTEM : WINDOW 98,XP

LANGUAGES USED : JAVA WITH NETBEANS

SOFTWARE USED IN THE SYSTEM

NetBeans is an open-source project dedicated to providing rock solid software

associated with downtime, maintenance and administration for modern, online

 The System is manual. Hence a lot of manpower is required.

 Information maintenance as paper work is complex task.

 As the data is very large, no Backup can be maintained.

 The process is prone to delays & cost ineffectiveness.

7.1 FACILITATED APPLICATION SPECIFICATION

A meeting is conducted at a neutral site and attended by both Software Engineers

Based on our project I make all these Lists.

7.1.1 Requirements taken from Team of End Users

 System must be User Friendly.

7.2 QUALITY FUNCTION DEPLOYMENT (QFD)

QFD identifies three types of requirements:-

Expected Requirements:- These requirements are implicit to the product or

Exciting Requirements:- These features go beyond the customer’s expectations

7.2.1 Normal Requirements for CMS :-

7.2.2 Expected Requirements for CMS :-

 Amount of VAT provided should be lowest. VAT amount is calculated by

7.2.3 Exciting Requirements for CMS :-

 Interface i.e. form can be made attractive by using graphics.

The planning phase is the most critical step in completing development,

8.1 FEASIBILITY OF PRODUCT

8.1.1 ECONOMICAL FEASIBILITY

8.1.2 TECHNICAL FEASIBILITY

8.1.3 ENVIRONMENTAL FEASIBILITY

8.2 SOFTWARE MODEL USED

For this I can use THE INCREMENTAL MODEL.

I use this model, because it is a combination of Linear Sequential Model &

9. DATA FLOW DIAGRAMS(DFD)

DFD serves two purposes:-

 To provide an indication of how data are transformed as they move through

10. ENTITY-RELATIONSHIP DIAGRAM (ERD)

Entity-relationship model is database analysis and design tool. It lists real-life

SALESMAN Information is stored

Get Items Details

Get Customer Details Generate Bill

Issue/Rene Card_SNo Pin_no Card_Type Name

Bill_wise Item_wise Shop_Code

11. DATA STRUCTURE (DATABASE)

// This Table shows login details of the CMS

Field name data type Size Key Constraints Description

// This Table shows Customer details