The Distribution System for Food Security Project itself is a web Based module. So this software module is having better scope of implementation in all the ways.
The clients need not bother to send the monthly, quarterly, half yearly and yearly returns in time. As soon as the person enters the data all the returns will be prepared by the system automatically. This Software is totally public oriented i.e., it gives the information about how much of food grains should the Govt. have in order to supply food grains to the people.
Dependencies in my project are elaborated below.
First we have to take the initial table which has following fields
Dist_name, Div_name, Mandal_name, Village_name, FPS_add, Deler_name, Licence_no, Date_Of_Issue, Ren_date, CSG_id, Rationcard_no, cardholder_name, card_type.
In the above table we have redundant data because if we take the FPS’s in one district say East-Godavari then we should again and again type that district name, resulting redundancy.
Same situation occurs in the case of Div_name, Mandal_name, Village_name then we have to enter FPS details for each and every card holder.
If we are not apply the first normal form then we have anomalies (update, insert, delete)
Update anomaly: if we make any update by using filed like dist_name, Div_name etc. then all the fields which have the same dist_name, Div_name etc. can also updated.
Delete anomaly: if we delete any row by using repetition data field then we can loss the necessary data.
Insertion anomaly: with out FPS details we cannot insert card holder details.
Applying second normal:
Div_name is dependent on dist_id and div_id because according to second normal form, a relation scheme R is in 2Nf if every non attribute A in R is fully functionally depended in the primary key of R i.e., divi_name is partially depended on div_id and fully depended on dist_id and div_id.
Applying third normal form:
A functional dependency X->Y in a relation scheme R is a transitive dependency if there is set of attributes Z i.e., neither a candidate Key nor a subset of any key of R and both X->Z and Z->Y hold.
Here cardholder is dependent on FPS and FPS dependent on Dist_id, Div_id etc… i.e., ration card_no is dependent on FPS Licence_no and FPS licence_no is dependent on dist_id, Div_id etc… so here transitive dependency holds. So rationalcard is dependent on Dist_id, div_id etc.
Lifting and Distribution:
The PDS Kerosene is released by the Government of India through Public Sector Undertaking Oil Companies i.e., IOC, HPC, BPC and IBP. Each company has appointed the required number of wholesale dealers for each district. The wholesalers lift Kerosene oil from the Oil Depots tagged on to the wholesale point. Basing on the allocation of the District Collector to Mandals and re-allocation by the concerned M.R.O. to the Fair Price Shop Dealers, the whole sale dealers are delivering the kerosene to the Fair Price Shop Dealer / Nominated Retail Dealers. Similarly, rice, wheat etc commodities are lifting from go downs.
As the software is a web Based Software, the application can be used from any where by registered user just like any mail application. System has been designed as per the requirement fro the client. The bottle necks such as physical boundaries are also kept in mind while designing the system.
The system has been developed to provide better utilities than manual system to the users. The system is providing data security, data warehousing and even the data mining utilities for features analysis for data.
Download Distribution System for Food Security Project source code in java with project report.