SRS Food Department 19-1-05

Table of Contents (SRS)
1. INTRODUCTION SRS-1
2. INTRODUCTION TO FOOD DEPARTMENT SRS-2
3. ORGANIZATIONAL STRUCTURE SRS-2
4. VISION STATEMENT SRS-4
5. PROJECT SCOPE SRS-5
6. EXISTING SYSTEM SRS-5
7. OVERALL DESCRIPTION OF THE PROPOSED SYSTEM SRS-17
8. HIGH LEVEL SYSTEM ARCHITECTURE SRS-19
9. ASSUMPTIONS AND DEPENDENCIES SRS-20
10. DESIGN AND IMPLEMENTATION CONSTRAINTS SRS-22
11. PROPOSED SYSTEM WORKFLOW SRS-23
12. SYSTEM FEATURES SRS-25
13. NON FUNCTIONAL REQUIREMENTS SRS-37
14. NON-TECHNICAL ISSUES SRS-38
15. USE CASE MODEL SRS-39
16. USER INTERFACE SRS-111
17. REPORTS SRS-140
18. APPENDIX A SRS-155
19. APPENDIX B SRS-156

Food Department Information System
1. Introduction
This section explains the Software Requirement Specifications (SRS) for the
‘Computerization of Food Department’ Project. The document consists of a listing
of the required functionality, system and technical requirements as well as specific
constraints related to the project. Preliminary level GUIs of the required application
are also presented. The specifications provided in this section are based on a
preliminary system analysis and are not final. The SRS is subject to be updated after
the Contractor carries out a detailed system analysis. Similarly Use Case Models and
Graphical User Interfaces are of a preliminary nature and are provided only to
facilitate the Contractor in preparing the Functional Specifications Document.
1.1 Intended Audience and Reading Suggestions

Food Department
Information Technology Department
Bidding Contractor
1.2 References
Bidding Document for Procurement of Computer Hardware & Networking
Equipment for Computerization of Food Department
Manual for “Software Development Standardization” proposed by PITB in
collaboration with MoST (available at PITB’s Website, http://www.pitb.gov.pk)
Khushaal Kissan Khushaal Pakistan Manual
Food Department website (www.punjab.gov..pk/food)
Punjab Sugar Factories Control Rules 1950
Punjab Sugar Factories Control Rules 1950
Punjab Finance Act 1964
Punjab Sugarcane (Dev) Cess Rules 1964
SRS-1
2. Introduction to Food Department
Food Department is responsible for regulating business of food grains including

purchases, storage, sales, transfer, milling, etc. under the Foodstuff (Control) Act,
1958.
Food Department deals with procurement, storage and transportation of wheat. It

ensures payment of support price to the farmers fixed by the Federal Government. It
issues wheat to the mills at subsidized rates to ensure adequate supplies and stable
price of flour throughout the year.
It also supplies wheat to other provinces and agencies.
Food Department is also responsible for monitoring and co-ordination of sugarcane

sector with reference to payment of dues of sugarcane growers and sugarcane cess
fund. A Cane Commissioner heads the Provincial Committee whose functions
include the appointment of cess fund among districts and releases as well as
selection of development schemes and their execution.
3. Organizational Structure
Food Department is headed by Secretary Food. The Directorate Food has 8 divisions
i.e., Gujranwala, Rawalpindi, Lahore, Faisalabad, Sargodha, Bahawalpur, D.G Khan
and Multan working under him. Each division is headed by Deputy Director. Each
district has DFCs (District Food Controllers). Each DFC has a Storage Office
working under him.
There are four Deputy Directors in the Food Directorate with each being incharge of
one section there. These four sections are as follows:
• Purchase deals with wheat procurement and its release. The wheat procurement
and its release are discussed in detail later in the document.
• General deals with the supplies for procurement of wheat, weighing scale, PP
bags, jute bags, pesticides, Polythene Sheets etc
• Administration deals with human resource management of the Food

Department staff. It keeps a complete record of postings, transfers, promotions,
ACRs, departmental proceedings, criminal actions and inquiries against
employees of the Food Department staff of the entire province.
SRS-2
• Budget & Accounts maintains the budgets & accounts of the Food Department.
It works in collaboration with the A.G Office to release the funds allocated by
the Government.
Food Department Information

System (FDIS)
Organizational Chart
Secretary
Food
Director
Cane Commissioner Deputy Secretary-3
Food
Deputy Director Deputy Director

Addl. Director
(Directorate-4) (Field-8)
Asstt. Director Asstt. Director ACI

(Directorate-4) (Field-8) (10)
DFC
(Field-31)
FDIS : Food Department Information System AFC
Food grains
Insp.
SRS-3
The Cane Commissionerate
The Provincial Committee for the monitoring of sugar cane sector includes the
following members:
• Cane Commissioner (Chairman)

• DCO-District concerned (Member)
• Chairman PSMA/nominee (Member)
• Member (Tech) P&D (Member)
• Rep of FD (Member)
• Rep of C&W (Member)
• Rep of growers (Member)
• Any other person co-opted by Chairman (Member)
The composition of the District Committee for the monitoring of sugar cane sector is
as follows:
• DCO (Chairman)
• EDO (Works & Services) (Member / Secy)
• EDO (Agriculture) (Member)
• EDO (F&P) (Member)
• Deputy Director Food (Member)
• DFC (Member)
• 2 Reps of sugar mills (Member)
• 2 Reps of growers in area of each sugar mills (Member)
• Rep of Zila Nazim (Member)
• Rep of P&D (Member)
• Any other person co-opted by Chairman (Member)
The District Committees formulate and initiate development schemes and submit its
recommendations to Provincial Committee for final approval.
4. Vision Statement
The basic vision behind the ‘Computerization of Food Department’ Project is to

develop an IT enabled environment at the Food Department to ease out the
procurement and release operations of wheat and to facilitate the Cane
Commissionerate in acquiring the sugarcane reports directly from the sugarcane mill
owners. This includes developing an inventory management information system for
tracking of all operational activities of the department from procurement to release
of wheat to prevent fraud and forgery as well as developing Financial Management
System for release of payments to the sellers/farmers. This will also enable the food
department to do statistical analysis for increasing the annual wheat production.
SRS-4
5. Project Scope
The scope of the project is to develop an automated information system at the Food
Department. The central database developed containing the particulars of storage
units, their capacity, resources, vehicles; routes etc will be able to retrieve any
information for decision support system. The central database will be updated with
each truck routing especially for import of wheat transaction, hence the Food
Department to track down the exact position of the trucks and its delivery time. The
project also includes developing an online facility for the sugarcane mill owners to
submit their reports to the Cane Commissionrate. The IT Infrastructure will be built
in all the offices at 34 Districts and 8 Regions.
6. Existing System
The existing processes at the Food Department are completely manual. The paper
forms being currently used for wheat procurement, releases etc are in Urdu
language. They have about eight computers in the Directorate whose usage is
basically restricted for data typing, compilation of data, accounts and stock article.
At present, there is no Local Area Network (LAN) in the Food Department.
Currently, there is no online inter-division communication and the officials have to

rely on faxes for this purpose. e.g. if the wheat is being dispatched from Karachi,
they will first inform the Directorate office in Lahore which in turn is responsible for
informing the corresponding district office. Figures regarding the sale of wheat are
also given to the regions by the districts and the regions forwards them to the
Directorate via telephone or fax.
The main functions of the Food Department comprises of:
• Setting the targets for wheat procurement

• Procurement of wheat
• Dispatch of wheat from Purchase point or PR
• Storage of wheat from Other Divisions
• Issuance/Sale of Wheat to the authorized Flour Mills
The Food Directorate sets two types of targets. One is procurement of the wheat for
the province. The other for the mill as to how much quantity will be issued. They are
both briefly discussed below:
The directorate sets a target based on historical data as to how much wheat will be
required in the province for the next year. This target is also in consideration of the
fact that the free market starts to run dry after a few months and then the government
needs to supply the Wheat to the mills at a lower rate in order to curtail the rise in
SRS-5
wheat prices. In order to set the targets the directorate in consultation with the
Agriculture Department estimates as to how much wheat can be acquired from each
district. Once a district wise target has been set it is forwarded to the related DFC.
The related DFC then sets up the targets for each center that he will establish. He
also identifies the bank that will support the center in making payments. He is at
liberty to choose the bank based on the past history and willingness of the bank in
general. The DFC then forwards this information to the Directorate who then
arranges funds to be transferred to the respective bank branches.
The mills set targets based on their milling capacity. Some mills will have more
target than the other simply because it can mill more wheat than the others. This
target can be increased or decreased according to the season or other factors. This
target is set on milling capacity per day. This means that if a mill does not consume
its target for a day it is not entitled to receive that day’s wheat next day. However, if
the mill has deposited the money on a day and cannot move the wheat due to
logistical problems then it may move it to the next day.
After setting the targets for wheat procurement, the Food Department sets up
approximately 400-450 centers all across the province. Depending upon the
requirement, the Food Department may need to set up some temporary centers
known as Flag Centers. The Purchase centers are made and their targets are set fixed
by the Food Department. Sometimes, Government of the Punjab is unable to meet
the target that it has set. In that case, it may need to import wheat. The wheat
procurement season is from April to June and wheat is released to Flour Mills from
October onwards.
Food Department takes loan from the State Bank which makes district wise and
center wise banking arrangements and nominates banks near the centers who makes
the actual payment to wheat seller/farmer. The Stock register is maintained by the
staff at the center and prints consolidated statement (Form 3) and sends it to banks.
The bank basically matches the statements to check the payments that it has made to
the sellers.
The Flour Mills deposits the required amount along with the authorized letter to the
bank. The Challan Form for buying the wheat from the Food Department also
As the wheat is sold to the flourmills on the subsidized rates, the difference of cost
of wheat and sale price is picked by the Punjab Food Department in the shape of
subsidy from the Punjab Finance Department.
In case of a district facing any shortage of the wheat, the wheat stocks in the surplus
districts are shifted/transported to the deficit districts by the following means:
• Pakistan Railways
• Through NLC Vehicles
• Private Transport Contractor (through tenders)
SRS-6
In addition to the expenditure incurred on purchase of wheat, the following extra

expenditure is incurred on the day-to-day requirements in the wheat operation.
i. Purchase of gunny bags
ii. Bank Commission
iii. Delivery charges
iv. Taxes & Duties
v. Transportation Charges
vi. Handling Charges
vii. Godown Expenses
viii. Establishment Charges
ix. Mark Up
Food Department Directorate Wise Segregation
Food Directorate
All the 8 Divisions reports

to the Directorate
Division
Storage Center 1 Storage Center 5 1 to 4 Storage Center 1 Storage Center 5

Districts
Flag Center 1 Flag Center 10 Flag Center 1 Flag Center 10
District 1 District 4
1 to 8 Divisions
Division
Storage Center 1 Storage Center 5

1 to 4 Storage Center 1 Storage Center 5
District
Flag Center 1 Flag Center 10 Flag Center 1 Flag Center 10
District 1 District 4
The Cane Commissioner administers two acts:
1. Sugar Factories Control Act 1950 and its rules (1950)

2. Finance Act 1964 and the Sugar Cane Development Rules 1964
SRS-7
The Salient Features of the Punjab Sugar Factories Control Rules 1950 are as
follows:
1. Examination of weighbridges and purchasing centers

2. Intimation regarding starting and termination of crushing
3. Elimination of middleman
4. Prohibition of price below minimum price
5. Payments to growers within 15 days & imposition of interest @ 11%
6. Cane Commissioner sole interpreter of these rules.
The Salient Features of the Punjab Finance Act 1964 are as follows:
1. Levy of Sugarcane (Dev) Cess

2. Equal sharing by mill and grower
3. Collection and payment by the mills
4. Purpose/utilization of cess
5. Exemption of cess
6. Time and manner of payment
7. Determination of correct deposit of cess by Cane Commissioner
8. Penalty by Cane Commissioner not exceeding the amount due
9. Inspection / audit of accounts
10. Constitution of sugarcane (dev) fund
11. Fund to be operated by the DCOs
12. Appointment of funds (district/mill wise) after deducting 2% collection
charges
13. Constitution of Provincial Committee
14. Constitution of District Committee
Each Sugar Mill operating within Punjab is required to submit two sugar cane
reports (SCR I & SCR II). These reports are to be submitted fortnightly as well as on
a daily basis. The reports/statements at present are being submitted directly to the
office of the Cane Commissioner through fax. The cess collected by the sugar mills
(50% of cess comes from the grower and the other 50% from the mill owner). The
amount deposited in the treasury is verified by the District Food Controller and
District Account Officer. In case of non-reconciliation 95 % of the cess collected
goes back to the district concerned whereas 3% is with held till the verification of
the sum deposited in the treasury. The remaining 2 % are the collection charges. In
case of non compliance, the Cane Commissioner can hold the sugar cane mills liable
to pay a penalty.
There are about 39 sugar mills operating within Punjab covering 19 districts. A
sugar cane mill owner can purchase sugar cane from any district. However this was
not the case in the past when a sugar cane mill owner could only purchase sugar
cane from within his own zone.
SRS-8
6.1 Wheat Procurement

Procurement of wheat is made according to the targets fixed by the Federal
Government/Punjab Government for which necessary arrangements are made by the
Punjab Food Department.
After setting the wheat procurement targets, the targets are handed over to the DFCs.
Each DFC’s further sets the target for each purchase centre.
The above operation of procurement is made through State Trading in wheat which
is financed by short term loan advances obtained from the Commercial Banks on the
cash credit commodity. The borrowed amounts are re-paid to the banks along with
mark-up. Cash Credit Limit on commodity is sanctioned by the Federal Government
on the basis of value of stocks expected to be held in the Provincial Reserve to
facilitate the accounting system.
For Procurement of wheat, temporary flag stations as per requirement required are
set up in addition to the permanent centers.
1. Wheat Seller (Farmer) brings the wheat that he wants to sell to the centre
incharge and tells him about the quantity of wheat that he has to sell.
2. Centre Incharge determines the number of bardana that needs to be issued to the
farmer.
3. Farmer fills his wheat in these bags and takes them to the purchase point i.e.,
Flag Center or the Provincial Reserve (PR). The seller himself is responsible for
unloading and stacking of the wheat.
4. The Incharge officer takes a sample of the wheat to check out its quality of
wheat and prepares GP 16. A copy of GP 16 is sent to the laboratory for analysis
along with the sample and one copy is sent to the DFC.
5. The Office Incharge at the center accepts the wheat if he thinks it is according to
the standards prescribed by law. Unsatisfactory wheat is rejected and bardana is
also taken back.
6. If the wheat needs cleaning, the seller may be asked to clean the wheat and
present it again.
7. If the wheat is received at the flag center and a transport contractor is not
available then the seller can be asked to deliver to the appointed Provincial
Reserve (PR). For this he is then paid the amount that the transport contractor
would have received.
SRS-9
8. If the wheat is received at the flag center, then it needs to be transported to the
PR. The Incharge center fills out GP-13 and sends it along with the wheat to the
PR.
9. If the seller transports the wheat to the PR, then the receiving PR will issue his
bill after an acknowledgement of GP-13. The transporting party brings this
confirmation.
10. If the wheat is accepted, then incharge issues a bill on Form-2, which is issued
for each lot purchased.
11. Each Bill Form -2 is entered in Form-3 and copy of each bill is attached, Form-3
contains all the bills filled during the day that is sent to the bank at the end of
each day that is checked at the bank.
12. The farmer submits his bill at the prescribed bank for collection. Form-2 acts like
a payee’s account cheque. If the payment of wheat is of less than 50 bags then
the bank may pay in cash. If the seller does not draw amount from the bank
within a week then he has to draw permission for extension of payment date.
Incase of delay of month, permission of the DFC is required.
13. The bank counter checks from Form 3 which has received from the Food
Department and copies of Form 2 before making payments to the farmers.
14. The Incharge Officer at the end of the day prepares Form 4 which contains all
the Bill details which are cleared along with un-disbursed bills during the day
which is forwarded to the District Office.
15. At the centre GP-5 also known as the Stock Report is also prepared which
contains the sale and purchase details
16. The Incharge Officer also prepares GP 6, copies of which are forwarded to the
District Office and to the PR to which wheat is dispatched (incase the wheat is
storedat a remote PR). A separate GP 6 is prepared for each different destination
PR.
17. The district office then prepares Form 9 based on all the GP 4’s received from
the centers.
18. Copies of the GP-4 are then sent to the divisional office from where the
information is forwarded to the directorate for further compilation.
SRS-10
Wheat Procurement Process Flow
Seller/Grower
1. Issue bardana
2. The wheat has to be
returned by the seller/ grower Requests for bardana against
with in 7 days of issuance of 2 1 CDR or personal surety
bardana
Flag Center
Checking for weight and
Provincial Reserve 3 quality of food, and after
(PR) (Storage checking the wheat is stored
Center) in a PR or a Flag center
Bill for payment is forwarded

4 to bank where grower/seller
receives payment
Bank
6.2 Receipt at PR
The PR can receive wheat from the flag centers, others PR’s as well as imported
wheat. Regardless of where the wheat is coming from, following is the procedure
that is followed by the PR In charge.
1. The Incoming wheat is accompanied by a GP-13. All the trucks coming in

carries GP-13 where as the last truck will carry GP-6. GP-13 contains the
information regarding the incoming goods. The receiving PR In charge enters the
information about the incoming wheat in the incoming register.
2. The PR Incharge fills in the GP-7, which is a center wise consolidated report,
related to wheat. This is also consolidated from GP 13. A copy of this is sent
with the stock report. GP-6 and GP-7 are compared to check what was
dispatched and what was received. Every center fills in its own GP-7.
SRS-11
3. The incoming GP-13 is counter filled as acknowledgement for the sending party.
This filled GP-13 is handed over to the transporter for him to return at the
starting point.
4. Any transit loss will be recovered from the transport. Recovered transit loss is
when the number of bags received is less than the ones sent.
5. If there is difference in the weight of the wheat received as opposed to the

dispatched weight then the sending DFC is responsible to either deposit the value
of the deficiency or send the difference to the receiving PR.
6. The wheat is then unloaded and stacked in the godown. A GP-8, which is a
goodown wise report, is prepared separately for each godown.
7. At the end of the day, PR Incharge prepares a GP-5, which describes the stock
status of the day and hands it over to the Regional Accounts Office. GP-8 and
GP-5 are also compared with each other, as their totals should tally. The other
copy of GP-5 is given to the respective DFC.
A process flow / workflow which clearly shows the whole process is as below. This
will facilitate the contractor to easily understand the current system and will also
help in understanding the requirements. The whole process ‘Receipt at PR’ is
graphically represented below:
SRS-12
Receipt At Provincial Reserve Process Flow
Flag Center
Provincial Reserve
(PR) (Storage
Center)
Wheat received for storage from other PR
or flag center to another PR center
1 3
Provincial Reserve
Daily consolidated reports of (Storage Center)
Daily consolidated reports of
flag center and storage center
Divisional offices are sent to
are dispatched to the District
2 the Directorate
offices
Daily consolidated reports of

District offices are sent to the
Divisional office
6.3 Dispatch of wheat from PR & Flag Center

If some region is facing a deficit in wheat, it requests the Food Directorate for
additional supplies. The Directorate may ask other PR where wheat is in surplus to
send it to other PR in order to meet the shortfall.
1. The Food Directorate allocates and award contract to the firm which transports
wheat.
2. The DFC on receiving the work order from the Directorate, informs the
transporter about the quantity of wheat that need to be transported and schedule.
3. The PR prepares GP-13 , which is sent with the wheat. All the trucks carry GP-
13.
4. The PR also prepares GP-6 which is sent with the last truck and copies of which
are also forwarded to the District Office and to the PR to which wheat is
dispatched.
SRS-13
5. At the end of the day, PR Incharge prepares GP-5 (Stock Report).
6. Godown card i.e., GP-9 is also prepared which is replica of GP-8.
7. If the godown is being cleared/ emptied, SF-26 is prepared. The form is then
forwarded to the district office.
Wheat Dispatch Process Flow
1 2
DFC Food Directorate Contractor

Proposes Surplus stock to be Allocates and awards
transported contract
3
DFC specify quantity of
Approaches DFC for
wheat to dispatch
4 Contract signing
5
Loading of stocks
Storage Center
(PR or Flag Center)
6
7
Sends acknowledgement to the Provincial
Reserve center or the Flag Center through Destination
contractor
SRS-14
6.4 Sale of Wheat

The wheat is sold to the flourmills according to their allocated quota. The mill can
also purchase wheat from other sources i.e., open market. It cannot however sell
flour at rates other than the government prescribed rates.
1. The flourmills request the Food Department for issuance of wheat as per
allocated quota.
2. The mill deposits the required funds in the government treasury.
3. The mill then presents the bank challan to the DFC who verifies the authenticity
of the challan through bank scroll and issues an authority letter for the PR
Incharge to issue wheat.
4. The PR Incharge updates the Gate Register.
5. The PR prepares SF-21 everyday. This is forwarded to the DFC who then
prepares SF-24 and forwards it to the division office.
6. At the end of the day, the PR Incharge prepares a GP-5, which describes the
stock status of the day and hands it over to the Regional Accounts office.
7. After the issuance of the authority letter, DFC
8. The Authority letter along with the bank challan copy is sent to the PR/Flag
Center to for issuance of wheat.
A process flow / workflow which clearly shows the whole process is as below. This
will facilitate the contractor to easily understand the current system and will also
help in understanding the requirements. The whole process ‘Wheat Sale’ is
graphically represented below:
SRS-15
Wheat Sale to Flour Mills Process Flow
Request for the issuance of Verifies amount deposited

the wheat as per the allotted through bank scroll
5
quota
1 Allows release of wheat as
2
per Gov. policy
4
Submits challan copy to DFC DFC
Flour Mill
3
Bank challan copy is send to
Deposits payments at banks 6 PR or Flag center to issue
the
as per the rates specified wheat
Storage Center
(PR or Flag Center)
7
Issue wheat to flour Mills
SRS-16
7. Overall Description of the Proposed System
This section presents high-level overview of the software being specified (FDIS) and
the environment in which it will be used, the anticipated users of the software and
the known constraints, assumptions and dependencies.
7.1 User Characteristics and Roles

Group Description Access Rights
Administrator Administrat ¾ The administrator has full control over the system. He
ors of the is responsible for creating groups / users, giving them
software access rights, modifying groups / users, creating,
(level-4) editing, and deleting workflows and archival to CD or
magnetic tapes.
¾ Full control (Read, delete, view and write privileges)
of each interface.
¾ Report generation
¾ Database backup
¾ Change tracking
¾ User Management
¾ ACRs/Inquiry Reports should be in encrypted format
Senior Officials Higher ¾ Read privilege for user management interfaces

officials of ¾ Report generation
Food
Department
(level-3)
Officials Officials of ¾ Read privileges for authorized interfaces.
restricted lower grades ¾ Report generating facilities
of Food ¾ Write privileges to a few restricted interfaces for
Department quality assurance
(level-2)
Operators Data entry ¾ Read privileges for User Management interfaces.

for ¾ Read/write (as per the group/security policy) for all
documents interfaces.
(level-1)
7.2 Operating Environment
Microsoft Windows XP Professional will be the standard operating system for the
staff whereas server operating system would be recommended by the software house
according to the given solution. Application should be compatible with Internet
Explorer version 6 or higher.
SRS-17
7.3 Hardware
Some of the hardware for the project has been purchased. The Intel based Pentium
IV workstations; UPS, printers have been bought. The hardware yet to be purchased
includes the Application and Data base server. The details of the hardware are
available in Bid Document for Procurement of Computer Equipment & Goods
(Volume-I) for Computerization of Food Department Information System (FDIS).
7.4 Input to ICDS

As part of the Punjab Portal Project, an Integrated Central Depository System
(ICDS) is to be setup for inter-department information sharing. ICDS will require
input from FDIS.
7.5 Data Flow Diagram
Data Flow Diagram
All Divisions
General Public
Retrieve
Store
Re
tri
ev
e
Retrieve Retrieve
Food Department
All PR Centers Information System Higher Staff
(FDIS)
Store Store
Higher Staff includes the
Secretary, Director, Deputy
Director, etc
Retrieve
Store
Cane
Commissioner
SRS-18
8. High Level System Architecture
High Level Network Architecture Diagram
Food Directorate
Router
ISDN/DSL
Information Technology
Department (ITD) Cane Commissionrate
ISDN/DSL
Up
al
Di
Service
Storage Center
ISDN/D
ia
Provider Dial Up
l Up
Application Server
Rawalpindi Division
Up
/Dial
ISDN
1 to
8D
ivis
ion
s
Application Server
Sarghoda Division
SRS-19
9. Assumptions and Dependencies

9.1 Integration with ICDS
The Contractor is required to lay out a plan and strategy for interfacing the software
with ICDS so that extractions cleaning and transformation operations could be
performed by the contractor engaged for setting up the ICDS. The Contractor would
also be required to distinguish and identify the public and confidential data.
9.2 System Analysis

It is assumed that the Contractor would have carried out a detailed system analysis
before the submission of the Functional Specifications Document. It is also assumed
that the Bidder would have thoroughly read the “Law of Fire Arms and Explosives”
before submitting the proposal.
9.3 Data Collection from Existing Website

The contractor will collect the data for the development of FDIS from the existing
website, www.punjab.gov.pk/food. This information would be of primary
importance and the contractor will analyze this site contents and existing
computerized data after careful study and planning. All the information would be
extracted from the static site and the existing application will become part of the
FDIS.
9.4 Food Department Website

The contractor will re-design a new website incorporating all the features defined for
the website.
9.5 Network and Data Communication

The Punjab Intranet Project which is currently undergoing will establish a link
between the Food Department and other departments of Punjab Government e.g
Agriculture Department. When Punjab Intranet has been successfully deployed all of
the Dial Ups will be terminated and this cost will be diverted towards establishing a
connection between local storage center and the local terminal point of Punjab
Intranet.
For certain tasks, such as estimation of production of annual wheat production,

figures have to be transferred from the Agriculture Department to the Food
Department. It is assumed that the data transfer process can be automated once the
communication link is established. FDIS should be flexible enough to allow the
transfer of data from one office to the other. FDIS should also allow data to be
exported from one office to the other manually (e.g. on a compact disc etc.) as well
as through dialup modem connections with the storage houses. ISDN connections
will be setup between the Directorate and the Regions which will facilitate fast
communications.
SRS-20
9.6 Integration of HRM with Office Automation

A Human Resource Module is being developed for FDIS. The Information
Technology Department is also implementing an “Office Automation” Project. It is
envisioned that this project will form the basis for fully automated Government
offices and will lead to paperless environment. The current HRMS will be later
integrated with the Office Automation project.
9.7 Integration with Lahore WAN

This project is closely linked with Lahore WAN as the data collected from different
storage units will be made available to other departments through it.
9.8 Deployment & Installation

The installation and deployment of the system in various offices of the Food
Department cannot start before the implementation of internal Local Area Network
within those offices.
9.9 Human Resource Potential

Currently, the Food Department has shortage of technical staff. In order to run the
FDIS, it is dependent on the new manpower hired that will need training.
9.10 Wireless Connectivity in Future

The Contractor should also keep into consideration the fact that in near future the
wireless connectivity will be available everywhere in Punjab. This will be really
beneficial for performing data entry at the Flag Centers, which are set on temporal
basis. The contractor should keep a provision for this in the system.
9.11 Cane Commissionerate Module

The Role of Cane Commissionerate role is not yet clearly defined for the past few
years. We may assume that it may be declared as an autonomous body at some later
stage. In any case, the Cane Commissionerate module should be made in such a
manner that it can be independently deployed anywhere.
9.12 Seller/Grower Payments in Future

The system must provide the facility to have an interface with the allocated banks so
that as soon as the payments are made to the seller/grower, it should also be updated
in the FDIS.
SRS-21
10. Design and Implementation Constraints

1. It is assumed that all the employees of the Food Department will have access to
the system. Therefore, the system performance should not be degraded with
increase in number of users.
2. The system should be accessible anytime, anywhere via the desktop or laptop.
3. The system should be able to retrieve data quickly and efficiently.
4. The system should facilitate the users to search data with minimal response time.
5. It should be a collaborated system highly available and reliable for continuous

Government operation offering Real-Time availability when necessary.
6. Data and systems would be at risk; vulnerable to ever-present security breaches

such as virus attacks and information theft, so firm security against such threats
are solicited. Unbreakable Security is required. System should be secured by
default.
7. ACRs etc related to any employee should only be accessible to the high level
users i.e., senior officials and even not to the Administrator. Likewise data should
be updated and deleted by the Administrator. Similarly all the other users of the
system should only be able use the system as per their access levels.
8. Automatic error reporting is required. Errors occurring due to any reasons

including network connectivity, database availability, application crash and
servers availability should be reported using a log, alert notifications to
administrators and system pop ups.
9. The project should be written in an Object-Oriented language that allows for easy
extension and maintenance of code. Languages like Java or Microsoft dot net
platform may be used for high maintainability.
10. The application should be highly reliable and robust providing restrictions at all
the access level, security, virus protection, proper network support, quick
response time and should be highly available to achieve the required reliability.
11. The contractor must keep the following provision in its design for future:
• Efficient access to central database through WAP.
• Wireless networking between districts & divisions as well as Food
Directorate
• Forecasting system to support Government pf Punjab’s planning activities.
SRS-22
11. Proposed System Workflow
Di
al
up
up
al
Di
LA
N
SRS-23
11.1 Proposed System for Cane Commissionerate
4. Exchange latest
Reports
Cane Commissionrate
3. In case of non
Food compliance issue
1. Send sugar cane
Department warnings to Sugar Mills.
Reports to Cane
Commissionrate (Daily
Basis Reports and
Fortnightly Reports)
2. Acknowledgement of
sugar cane report is
displayed.
Sugar Mills (39)
SRS-24
12. System Features
12.1 Application Features
1. Ability to create, edit and view different user groups. A user group is assigned
privileges of reading, writing application resources, e.g. user management screen,
property information entry screen etc.
2. Ability to create a new system user in an already created group and then to edit
and view the user information.
3. Ability to provide login and logout facility to multiple concurrent users (this will
be a multi user application).
4. Ability to authenticate and provide confined view to the user as per permitted
privileges.
5. Software should support both old and new NIC number formats
6. Software should have support to accept historical data.
7. The proposed system shall include full TCP/IP support and capability, including
Telnet, FTP, and SMTP.
8. The software developer will use the process-oriented approach as the basis for
project planning. This approach lays out the importance of particular activities to
be carried out to ensure the quality of the automated system. This also provides
the rudimentary schedule of activities with minimal set of deliverables.
9. Web site must be built on a multi-tiered, distributed architecture. Must

incorporate the latest in technological advances including object-oriented design,
event-driven programming design, and transaction-based processing.
10. The system should be easy to use for first-time, novice, or infrequent users.
11. The system shall be available via local area networks as well as from the Internet.
12. The system should provide prompts to available commands or actions on every
screen.
13. Instructions for receiving help and for quitting from the system should appear on
every screen.
14. The application to be developed must be compatible with the operating hardware
and software purchased for this purpose.
SRS-25
15. The system should have the ability of intelli-sense in which e.g., if an id of an
employee is used in a form then all the related fields on the form, which already
persist in the database, should populate automatically.
16. The system must have the facility to distinguish between the 20th and 21st
century.
11.1.1 Dynamic Report Engine
The engine should facilitate the user in modifying the layout of already created
reports according to requirements.
11.1.2 Performance Criteria
1. Background processes, reporting, data loading, data integrity checking, data

backup operations etc should not take a toll on the performance of the system.
2. System should perform optimally during normal and peak workloads.
3. The system must be designed for less than 1% downtime at normal load.
11.1.3 Operations, Backup and Recovery
1. Mechanisms and techniques must be devised to guard against unintentional loss

of data.
2. When necessary, full data recovery must be made possible
3. The system should have an emergency / contingency module that captures any
data input during a period of possible LAN failure and which permits the upload
of such data to the central database once the LAN becomes operational.
11.1.4 System Monitoring and Logging
1. For the purpose of trouble shooting and performance analysis, authorized

members activity log mechanism must be incorporated in the system.
2. The system must be able to identify and reveal which individual has modified,
added or deleted any data within any part of the system. This feature generates a
comprehensive log of all actions undertaken by various users. This trail ensures
all information in the system is secure and can be used for accountability and
proper monitoring of the system.
SRS-26
11.1.5 User Rights and Security Management
1. The module will control all the authorized users with their assigned rights and
only authorized users can login to the software and can perform the tasks that
the administrator of the software has allowed from menu-level up to the button-
level (add, edit, delete, print, post and view etc.)
2. Authentication of a user to a secure Web site via the Secure Sockets Layer
(SSL) protocol with 128 bits encryption technique.
3. Access level of each user can be defined at the time of creating the user.
4. Access level of each module / interface can be defined at the time of creation of
the user.
5. Food Department Information System (FDIS) should have multiple level

security controls. Few of them are:
User level security Interface level security Group level security

• User name • Read • Read
• Encrypted Permission Permission
Password • Write • Write
• Read Permission Permission
Permission • Print • Print
• Write Permission Permission
Permission • Delete
• Distribute Permission
Permission • View
• Delete Permission
Permission
• Print
Permission
• Supervise
Permission
11.1.6 Confidentiality
Secret data should not be able to view / access the information of any other user
until and unless that information is made public.
11.1.7 Online Accessibility
Internal work of FDIS will be performed offline on the LAN. FDIS also requires
some reports and other related information online. The functionality that will be
offered to users depends on their access privileges that are given to them by the
system administrators or power users.
SRS-27
11.1.8 Component Based Deployment
Software should be installed through setup program providing at least following

three installation options.
• Typical: Install only the single system for any storage house, district.
• Complete: Install all modules, which are required in Food Department
Information System.
• Custom: Choice base installation by manually selecting each module
separately.
12.2 Generic Features
1. The system must have the ability to generate a tracking number/consignment

number from the central database with each consignment being transported.
2. This system must have the ability to determine the exact position of the
consignment being delivered.
3. The system must have the ability to generate separate web pages for Cane
Commisionerate, Food department and Sugar Mill owners. The type of web
pages displayed will depend upon the access rights given to them. e.g., a food
department employee will automatically be directed to the web pages for Food
Department.
4. The system must have the ability to perform statistical analysis of wheat procured
and released by the Food Department in previous years and based on this analysis
should be able to make predictions for the current year.
5. The system must have the ability to automate information regarding inbound and
outbound trucks and the quantities that they are carrying.
6. The system must have the ability to do wheat order management i.e., the wheat
required for one storage center to another storage center or so.
7. The system must have the ability to perform wheat inventory management.
8. The system must have the ability to order/request wheat from other regions.
9. The system must have the ability to see which districts are in shortage of wheat
and where wheat is in surplus.
10. The system must have the ability to update stocks on daily basis.
SRS-28
11. The system must have the ability to maintain record of capacity of each storage
house.
12. The system must have the ability to track down the trucks carrying wheat.
13. The contractor will suggest a tool for making annual wheat estimates.
14. The system must facilitate the applicant by providing a provisional number for a
defined period of time during delay in registration process.
15. The system will facilitate the administrator to use pre-defied access levels to
assign format of reports at storage, district and divisional levels.
16. The system must have the ability to interface and provide information to the Food
Department, I.T Department& Agriculture Department.
17. The system must have the ability to create different user groups.
18. The system must have the ability to track and maintain information about annual
fees related to various transactional activities.
19. The system must have ability to generate reminders and warnings against late
payments.
20. The system must have the ability to maintain audit trail and keep track of each
other’s activities and actions being performed within the system.
21. The system must have the ability to integrate the Financial Account System,
Inventory & Procurement Management System and Gate Management System
(GMS)
22. The system must be able to provide search the database according to the search as
per the criteria specified by the user.
23. The system must have the ability to generate weekly, monthly revenue
statements.
24. The system must have the ability to generate progressive reports.
25. The system must have the ability to generate district wise reports of the wheat
transfer from one PR center to another, procurement of wheat etc.
26. The system must have the ability to generate Sale and Transfer reports.
27. The system must have the ability to generate wheat procurement reports i.e., the
wheat procured for the current fiscal year for any storage center etc.
SRS-29
28. The system must have the ability to generate transactional account details reports.
29. The system must have the ability to generate the transactional data and storage
unit reports.
30. The system must have the ability to generate storage unit capacity
and load reports.
31. The system must have the ability to generate the revenue tracking and
notifications reports.
32. The system must have the ability to send print out report in pre-defined format.
12.3 Financial Accounting System Features

1. The system must have the ability to allow only authorized users to perform their
related task.
2. The system must have the ability to enter, update and delete the different levels of
account heads and their descriptions.
3. The system should have the ability to keep the codes of each account head.
4. The system should provide the facility to authorized staff members of Food
Department to view the summary of different account heads through
LAN/internet.
5. The system must have the ability to enter, update and delete the opening budget
balance of each head.
6. The system must have the ability to prepare the vouchers against the purchase of
different items. Information includes, name, voucher number, account heads
code, item code, quantity, amount etc.
7. The system must have the ability to prepare the bill of different vouchers.
8. The system mush have the ability to keep the information of acknowledgement
slip (token No.) and can print the weekly / monthly / yearly statement of
payment status against each token.
9. The system must have the ability to enter, update and delete the information of
parties / suppliers/vendor.
SRS-30
10. The system must have the ability to transfer remaining amount from any head to
another head for re-appropriation at the end of year according to the government
rules.
11. The system must have the ability to generate complete information regarding
payable accounts in its database.
12. The system must have the ability to generate complete information regarding
receivable accounts in its database
13. The system must have the ability to do budget control estimates during one
financial year.
14. The system must have the ability to keep record of all the vouchers generated by
the system.
15. The system must have the ability to do account management with respect to all
the storage centers, district, and division wise in the province.
16. The system must have the ability to do account management with respect to
various schemes floated from time to time by Government of the Punjab.
17. The system must have the ability to maintain the Invoices of various heads in the
system.
18. The system must have the ability to check out the opening balances.
19. The system must have the ability to generate the following reports
i. Regarding the Account Status
ii. Regarding the Cash Position
iii. Regarding the Cash Flow Reports.
iv. Regarding the General Ledger
v. Regarding the Trial Balance
vi. Regarding the Monthly Comparison ( actual)
vii. Regarding the Monthly Comparison ( budgeted v actual)
viii. Regarding the Transactions Registers
ix. Regarding the Invoices Registers
SRS-31
x. Regarding the Profit & Loss Statements
xi. Regarding the Balance Sheet
xii. Regarding the Financial Statement
12.4 Procurement (PMS) & Inventory Management System (IMS)

Features
1. The system must have the ability to directly enter the transactions from the
storage houses.
2. The system must have the ability to maintain record of sale/transfer of wheat to
other provinces.
3. The system must have the ability to maintain information of available stocks.
4. The system must have the ability to maintain the record of available PP bags, jute
bags, weighing bridges, pesticides, polythene sheets etc and must inform the user
incase of low supplies.
5. The system must have the ability to monitor the wheat stocks.
6. The system must have the ability to maintain a quality report of the bardana for
example indigenous wheat etc with respect to procured wheat.
7. The system must have the ability to maintain information regarding the rejected
wheat.
8. The system must have the ability to maintain the record of quantity of wheat
issued and sold to the Flour Mills.
9. The system must have the ability to maintain the record of wheat transferred
between storage houses of districts, region or province.
10. The system must have the ability to maintain record of imported wheat.
11. The system must have the ability to maintain information of the wheat
seller/grower.
12. The system must have the ability to do maintain the information regarding the
bags issued to the farmers and update it on daily basis.
SRS-32
13. The system must have the ability to ability to enter the information on Form -2 in
the system., the details of the seller/ grower and the purchaser details are added
into the system.
14. The system must have the ability to generate the wheat purchased receipt.
15. The system must have the ability to maintain the history of wheat rates
announced annually by Government of Punjab.
16. The system must have the ability to have complete record of its inventory
17. The system must be able to generate at least the following reports.
i. Regarding the Store/Item Ledger
ii. Regarding the wheat consumption report
iii. Regarding the wheat dead stocks
iv. Regarding the wheat purchased but not issued/consumed.
v. Regarding the wheat party ledger.
vi. Regarding the wheat re-order level report.
vii. Regarding the minimum & maximum stock level report.
viii. Regarding the available wheat stock in each district & region.
ix. Regarding the project order/work order wise wheat movement report.
x. Regarding the Received vs Rejected Wheat report and analysis report.
xi. Regarding the wheat purchased history report
xii. Regarding the rate analysis report.
xiii. Regarding the purchase order status report.
xiv. Regarding the competitive statements.
xv. Customized reports as per the user defined format.
xvi. Generate voucher reports.
SRS-33
12.5 Gate Management System Features
1. Ability of the System to issue an Outward Gate Pass (OGP), based on a tracking
ID to the vehicle / truck carrying the load from any PR center.
2. Ability of the System to enter information like truck number, quantity of wheat
loaded, the route, destination, date of departure, expected date of arrival, driver
name etc.
3. Ability of the System to issue project order / work order Outward Gate Pass.
4. Ability of the System to issue an Inward Gate Pass (IGP) when a vehicle
carrying the load reaches the destination i.e., PR center.
5. Ability of the System to perform comparison between the Outward and Inward
Gate Pass to check whether the vehicle has arrived on due time or not etc.
6. The system must have the ability to enter all the information regarding the gate
passes issued to the trucks.
7. Ability of the System to integrate this Gate Management System with IMS,
PMS and all other modules of the System.
8. The system should be able to perform comparison of wheat stocks at each PR

with the OGPs and IGPs related to that PR.
9. Ability of the System to generate at least the following reports
i. Regarding the Returnable Wheat
ii. Regarding the Wheat Movement History
iii. Regarding the Purchase Order Status Report
iv. Regarding the Periodic information of IGP
v. Regarding the Periodic information of OGP.
SRS-34
12.6 Cane Commissionerate Features
1. The system must have the ability for sugar mills to login to the Food
Department website and enter the data of SCR-I and SCR-II on daily and
fortnightly basis.
2. The system must have the ability to generate a unique receipt number
automatically for sugar mills as soon as the sugar mills submits the SCR-I and
SCR-II on the website.
3. The system must have the ability for both the Cane Commissionerate as well as
the sugar mills employees to view SCR-1 and SCR-II reports using the receipt
no.
4. The system must have the ability for commisionarate to login to the system.
5. The system must have the ability to display to the cane commisionarate list of
all those sugar mills, which has sent their SCR-I and SCR-II, and also of those
mills that have yet to sent their forms.
6. The system must have the ability to send reminders/warnings to all those mills
that have not yet submitted their SCR-I and SCR-II forms.
7. The system must have the ability to allow the cane commisionarate officials to
send warning via through email and viva regular mail to all those sugar mills
that are not complying with Laws/Rules Governing sugar cane industry.
8. The system must aloe the cane commisionarate officials to enter the reports of
SCR-1 and SCR-II for those sugar mills that may not have online facility and
have sent their forms via fax or regular mail.
9. The system must have the ability to allow the DFC to submit online application
report.
10. The system must have the ability for cane commisionarate officials to generate
pre defined online reports (requirement analysis of these reports is o be carried
out by the contractor).
12.7 Human Resource Management System Features
1. The system must have the ability to enter basic data of the employee. Basic data
includes personnel’s posts/designations, religions, occupational groups,
qualifications, departments, provinces, districts, domicile, divisions, languages,
general integrities, general negative characteristics, entitled leaves, payroll etc.
SRS-35
2. The system must have the ability to have administrative privileges like: define
multi-level hierarchy, chain of command; leave approval authority within an
office of the Food Department. The system must allow the Administrator to
update or delete the information related to the employees.
3. The system must have the ability to provide an interface for creating an
employees profile including employee’s name, father’s name, seniority level,
occupational group service, birth date, domicile, post, BPS, joining date,
retirement date, religion, marital status, present address, permanent address,
telephone numbers, email addresses, emergency contacts, employment type,
office location, scanned photograph, place of birth, NIC number etc.
4. The system must have the ability to enter trainings attended by an employee,
inside or outside the country including training title, training particulars,
institution, date and duration (number of days) etc.
5. The system must have the ability to enter complete transfer & posting record of
an employee, including designation held, department served, BPS, joining date,
transfer date, etc.
6. The system must have the ability to store employee resumes in a predefined
format and layout and link up with their individual records. The system should
also save a scanned copy of all the required documents of any particular
employee.
7. The system must have the ability to enter any inquiries or any disciplinary actions
conducted on employee during his tenure, if any, including the date, inquiry type,
inquiry detail, inquiry officer, inquiry results, punishments if any etc.
8. The system must have the ability to enter and save the Annual Confidential
Report (ACR) of the employee. This will be critical in deciding about his future
promotions and appointments. It should be kept in mind that ACR are very
confidential and should only be accessed to some privileged users only and
should in encrypted form to others including the System Administrator. The
contractor must suggest a method to implement this feature.
9. The system must have the ability to search an employee record based on his/her
designation, domicile, background, grade level and training needs and to browse
his details including resume etc.
10. The system must have the ability to view a consolidated list of all employees of
any selected district/division/Grade/Post etc of the Food Department.
11. The system must have the ability to provide enter the leave record of employees.
The database must have complete record of amount of leaves availed from the
leave quota and leaves still available.
SRS-36
12. The system must have the ability to generate at least the following reports:
• Report containing a list with employee name, number, designation etc is

made with this report. It can allow an officer to view at a glance the
important particulars of everyone working in a particular office.
• Report containing a leave balance and record of an employee containing the

list of updated leave balance record at any time.
• Report containing a Leave Record taken by an employee over a given

period of time with the start date, end date, reason of leave, approving
authority etc as well as listing the leaves taken against the quota.
• Report containing the professional record of an employee containing his

name, age, department served and tenure and any complaints against him
etc.
• Report containing the names of all employees against whom any criminal
has been taken.
13. Non Functional Requirements
13.1 Software Quality Attributes
13.1.1 Development Methodology
Standard development methodologies as proposed by PITB in the “Manual for the

Software Development Standardization” should be followed. The manual provides
guidelines for designing, testing, coding and documentation
13.1.2 Software Acceptance Criterion
Bug Levels for FDIS should be classified according to the four level of severity
scale developed by IBM. These levels are:
• Level 0: Critical Problem – software does not work at all.

• Level 1: Significant Problem – major feature disabled or incorrect.
• Level 2: Minor Problem – some inconvenience for users.
• Level 3: Cosmetic Problem – spelling errors etc., no effect on operations.
FDIS should be free of Level 0 and Level 1 bugs. This is an initial guideline, which
is to be followed.
SRS-37
14. Non-Technical Issues

14.1 Scalability
The system should be easily scalable and there should be no additional software or
hardware cost associated to make it scalable.
14.2 Performance
The system should be proposed considering the performance requirements. The
system should behave within norms reckoning the provided statistics.
14.3 Availability
The system should be available and it should meet the availability requirements
mentioned in SRS. To start with, the system might not be 24/7 but it should easily be
convertible to it.
14.4 Reliability
The proposed solution should ensure the integrity and consistency of the application
and all its transactions as the load increases.
14.5 Security
The proposed solution should ensure that the system is secure and it cannot be
compromised.
14.6 Manageability
The proposed system should be capable of managing the system to ensure the
continued health with respect to scalability, reliability, availability, performance and
security.
14.7 Disaster from Recovery

The Contractor would be required to provide detailed disaster recovery procedures.
Considering the scope and importance of the system it is important that the disaster
recovery procedures should be performed using an automated approach. The Bidder
is also required to specify in detail the Disaster Recovery Procedures in his proposed
solution.
14.8 System Transition

The Contractor would be required to provide a detailed system transition plan prior to
the approval of the FS. It is important that the transition from the old system to the
new system happens in an organized and planned manner without disrupting the day
to day operations.
SRS-38
15. Use Case Model
15.1 Hierarchy Management Use Cases
15.1.1 User Login
Logi n Logout
User
Use Case UL-A: User Login

Basic Information
Actor: Data Entry Operator
Purpose: To Login to the system
Cross Reference: UI-A
Pre Condition:
Typical Course Of Events:
1) User will run the program.
2) User will enter the user name and password.
3) The user will click the sign in button.
4) System will verify the username and password and check the privilege level of the
user and enable menus accordingly.
Alternate:
Post Condition:
15.2 Group Management Use Case
Assign User Group Update User Group

Administrator
SRS-39
15.3 User Group Management Use Case
Add Group
Update Group Delete Group

Administrator
View Group
15.3.1 View Group Privileges Use Case
Use Case UG-D: View Group Privileges

Basic Information
Actor: Administrator
Purpose: To view the user group privileges
Cross Reference: UI-B
Pre Condition:
Use Case UI--A: User Login
Primary Course of Events:
1) The user will access the relevant interface.
2) The user will fill in the group name or group type.
3) The user will press view button and information will be shown to the user.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that the
no information found.
Post Condition:
SRS-40
15.3.2 Add Group Privileges Use Case
Use Case UG-E: Add Group Privileges

Basic Information
Purpose: To Add the new user and to assign the privileges to the group.
Pre Condition:
Use Case UI-A: User Login
2) The user will press the add button
3) The user will fill in the group name, group type and will assign the privileges to the
user.
4) The user will press save button and the information will be added into database when
the user presses the ok button of the confirmation box.
Alternate 1 Step 3:
1a) If the information entered already exists the system will give the alert message that
the following information is already in the database.
Post Condition:
15.3.3 Update Group Privileges Use Case
Use Case UG-F: Update Group Privileges

Basic Information
Purpose: To update the user privileges
Pre Condition:
Use Case UI-D: View Group Privileges
1) The user will access relevant interface.
2) The user will retrieve the record that is to be updated.
3) The user will press the update button and the fields will change into edit mode.
4) The user will make the required changes.
5) The user will press the save button and the information will be saved into the
database after user presses the ok button of the confirmation box.
Alternate 1 Step 2:
1a) If record not found then system will show the message that no record found.
Alternate 2 Step 5:
2a) If the user will press the cancel button the information will be discarded and will not
be saved into the data base
Post Condition:
SRS-41
15.3.4 Delete Group Privileges Use Case
Use Case UG-G: Delete Group Privileges

Basic Information
Purpose: To delete the user privileges
Pre Condition:
Use Case UI-D: View Group Privileges
Primary Course Of Events:
2) The user will retrieve the record that he wants to delete.
3) The user will select the relevant record and will press the delete button record will be
deleted (not physically/permanently) from the database after user presses the ok
button of the confirmation box.
Alternate 1 Step 3:
1a) If the user will press the cancel button of the confirmation box the record will not be
deleted from the database.
Post Condition:
15.4 Purchase Weight and Quality Certificate Use Cases
Add Purchase Weight and Quality

Certificate Details
Update Purchase Weight and Quality Delete Purchase Weight and Quality
Data Entry
Certificate Details Certificate Details
Operator (DEO)
View Purchase Weight and Quality

Certificate Details
SRS-42
15.4.1 View Purchase Weight and Quality Certificate Details
Use Case FDIS–001: View Purchase Weight and Quality Certificate Details
Basic Information
Purpose: To view purchase weight and quality certificate details
Cross Reference: UI-FDIS-003
Pre Condition:
1. The user will access the relevant interface.
2. The user will fill in the district, seller/grower name, center and other relevant details.
3. The user will press view button.
4. The similar records as per the step 2 criteria will be shown in a new popup window to
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the weight and quality certificate will be displayed on the
screen.
Alternate 1 Step 3:
Post Condition:
15.4.2 Add Purchase Weight and Quality Certificate Details
Use Case FDIS-002: Purchase Weight and Quality Certificate Details

Basic Information
Purpose: To add purchase weight and quality certificate details
Cross Reference: UI- FDIS -003
Pre Condition:
2. The user will press the add button.
3. The user will fill in the district, center name and other relevant details.
4. The user will press save button; information will be added into database when the
user presses the ok button of the confirmation box.
Alternate 1 Step 3:
1a) If any of the filed is mandatory and is not filled the system will not allow the user to
save data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that the
following information is already into the database.
Post Condition:
SRS-43
15.4.3 Update Purchase Weight and Quality Certificate Details
Use Case FDIS-003: Update Purchase Weight and Quality Certificate Details
Basic Information
Purpose: To update purchase weight and quality certificate details
Pre Condition:
Use Case FDIS-001: View Purchase Weight and Quality Certificate Details
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to update.
3. The user will press the update button and the fields will change into edit mode.
4. The user will make the required changes.
5. The user will press the save button and the information will be saved into the
Alternate 1 Step 2:
1a) If the record is not found the system will show the message that no record exists.
Alternate 2 step 5:
2a) If the user will press the cancel button of the confirmation box the information will
not be saved into the database.
Post Condition:
15.4.4 Delete Purchase Weight and Quality Certificate Details
Use Case FDIS-004 : Delete Purchase Weight and Quality Certificate Details
Basic Information
Purpose: To delete purchase weight and quality certificate details
Pre Condition:
Use Case FDIS-001: View Purchase Weight and Quality Certificate Details
2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (not
physically/permanently) from the database after user presses the ok button of the
confirmation box.
Alternate 1 Step 3:
not be deleted from the database.
Post Condition:
SRS-44
15.5 Bill Purchase of Wheat Detail Use Cases
Add Bill Purchase of Wheat Details
Update Bill Purchase of Wheat Delete Bill Purchase of Wheat

Data Entry
Details Details
Operator (DEO)
View Bill Purchase of Wheat Details
15.5.1 View Bill Purchase of Wheat Details
Use Case FDIS–005: View Bill Purchase of Wheat Details

Basic Information
Purpose: To view wheat purchase bill details.
Pre Condition:
2. The user will fill in the seller/grower name and purchaser details.
the user.
6. The detailed information of the seller/grower name or purchaser will be displayed on
the screen.
SRS-45
Alternate 1 Step 3:
Post Condition:
15.5.2 Add Bill Purchase of Wheat Details
Use Case FDIS-006: Add Bill Purchase of Wheat Details

Basic Information
Purpose: To add wheat purchase bill details.
Pre Condition:
3. The user will fill in the seller/grower name, father’s name, address and other relevant
details of the seller/grower name and the details of the purchaser.
Alternate 1 Step 3:
Alternate 2b step 4:
2b) If the user will press the cancel button of the confirmation box the information will
not be added into the database.
Post Condition:
15.5.3 Update Bill Purchase of Wheat Details
Use Case FDIS-007: Update View Wheat Purchase Bill Details

Basic Information
Purpose: To update wheat purchase bill details.
Cross Reference: UI- FDIS-005
Pre Condition:
Use Case FDIS-005: View Bill Purchase of Wheat Details
SRS-46

Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.5.4 Delete Bill Purchase of Wheat Details
Use Case FDIS-008 : Delete Wheat Purchase Bill Details

Basic Information
Purpose: To delete wheat purchase bill details.
Pre Condition:
Use Case FDIS-005: View Bill Purchase of Wheat Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-47
15.6 Daily Register of Un-Disbursed Bill Details Use Cases
Add Daily Register of Un-Disbursed

Bills Details
Update Daily Register of Delete Daily Register of

Data Entry
Un-Disbursed Bills Details Un-Disbursed Bills Details
Operator (DEO)
View Daily Register of Un-Disbursed

Bills Details
15.6.1 View Daily Register of Un-Disbursed Bill Details
Use Case FDIS–009: View Daily Register of Un-Disbursed Bill Details

Basic Information
Purpose: To view un-disbursed bill details
Pre Condition:
2. The user will select district and the purchasing center and date in the form.
the user.
SRS-48
6. The detailed information of the particular purchasing center will be displayed on the
screen.
Alternate 1 Step 3:
Post Condition:
15.6.2 Add Daily Register of Un-Disbursed Bill Details
Use Case FDIS-010: Add Daily Register of Un-Disbursed Bill Details

Basic Information
Purpose: To add un-disbursed bill details
Pre Condition:
3. The user will fill in the payees name, date, amount and other details of the unpaid
bills.
Alternate 1 Step 3:
Post Condition:
15.6.3 Update Daily Register of Un-Disbursed Bill Details
Use Case FDIS-011: Update Daily Register of Un-Disbursed Bill Details

Basic Information
Purpose: To update un-disbursed bill details
SRS-49
Pre Condition:
Use Case FDIS-009: View Daily Register of Un-Disbursed Bill Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.6.4 Delete Daily Register of Un-Disbursed Bill Details
Use Case FDIS-012 : Delete Daily Register of Un-Disbursed Bill Details

Basic Information
Purpose: To delete un-disbursed bill details
Pre Condition:
Use Case FDIS-009: View Daily Register of Un-Disbursed Bill Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-50
15.7 Grain Paper (Godown Register) Use Cases
Add Grain Paper (Godown Register)

Details
Update Grain Paper (Godown Delete Grain Paper (Godown

Data Entry
Register) Details Register) Details
Operator (DEO)
View Grain Paper (Godown Register)

Details
15.7.1 View Grain Paper (Godown Register) Details
Use Case FDIS–013: View Grain Paper (Godown Register) Details

Basic Information
Purpose: To view grain paper details
Pre Condition:
2. The user will fill in the PR center, Locality and other relevant details.
SRS-51
the user.
6. The detailed information of the particular PR center will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.7.2 Add Grain Paper (Godown Register) Details
Use Case FDIS-014: Add Grain Paper (Godown Register) Details

Basic Information
Purpose: To add grain paper details
Pre Condition:
3. The user will fill in the PR center name, locality and other relevant details.
Alternate 1 Step 3:
Post Condition:
15.7.3 Update Grain Paper (Godown Register) Details
Use Case FDIS-015: Update Grain Paper (Godown Register) Details

Basic Information
Purpose: To update grain paper details
Pre Condition:
SRS-52

Use Case FDIS-013: View Grain Paper (Godown Register) Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.7.4 Delete Grain Paper (Godown Register) Details
Use Case FDIS-016 : Delete Grain Paper (Godown Register) Details

Basic Information
Purpose: To delete grain paper details
Pre Condition:
Use Case FDIS-013: View Grain Paper (Godown Register) Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-53
15.8 Godown Card Details Use Cases
Add Godown Card Details
Update Godown Card Details Deleta Godown Card Details

Data Entry
Operator (DEO)
View Godown Card Details
15.8.1 View Godown Card Details
Use Case FDIS–017: View Godown Card Details

Basic Information
Purpose: To view the information about the particular godown.
Pre Condition:
2. The user will fill in the godown no., date of fumigation or any other information.
the user.
SRS-54
6. The detailed information of the particular godown will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.8.2 Add Godown Card Details
Use Case FDIS-018: Add Godown Card Details

Basic Information
Purpose: To add information about the particular godown.
Pre Condition:
3. The user will fill in the godown No. and other information of the particular godown.
Alternate 1 Step 3:
Post Condition:
15.8.3 Update Godown Card Details
Use Case FDIS-019: Update Godown Card Details

Basic Information
Purpose: To update information about the particular godown.
Pre Condition:
Use Case FDIS-017: View Godown Card Details
SRS-55

Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.8.4 Delete Godown Card Details
Use Case FDIS-020: Delete Godown Card Details

Basic Information
Purpose: To delete godown details
Pre Condition:
Use Case FDIS-017: View Godown Card Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-56
15.9 Dispatch Report Use Cases
Delete Whe at Dis patch Repo rt
Update Wheat Dispatch Report View Wheat Dispatch Report

Data Entry
Operator
Add Wheat Dispatch Report
15.9.1 View Wheat Dispatch Report
Use Case FDIS–017A: View Wheat Dispatch Report

Basic Information
Purpose: To view the information about the wheat dispatched through the truck.
Cross Reference: UI-FDIS-019 A
Pre Condition:
2. The user will fill in the dispatching center name, date or any other information.
the user.
SRS-57
6. The detailed information of the particular report will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.9.2 Add Wheat Dispatch Report
Use Case FDIS-018A: Add Wheat Dispatch Report

Basic Information
Purpose: To add the information about the wheat dispatched through the truck..
Pre Condition:
3. The user will fill in the dispatching center name and other information of the
particular godown.
Alternate 1 Step 3:
Post Condition:
15.9.3 Update Wheat Dispatch Report
Use Case FDIS-019A: Update Wheat Dispatch Report

Basic Information
Purpose: To update the information about the wheat dispatched through the truck.
Pre Condition:
SRS-58

Use Case FDIS-017A: View Wheat Dispatch Report
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.9.4 Delete Wheat Dispatch Report
Use Case FDIS-020A: Delete wheat Dispatch Report

Basic Information
Purpose: To delete the information about the wheat dispatched through the truck.
Pre Condition:
Use Case FDIS-017A: View Wheat Dispatch Report
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-59
15.10 Dispatch of Wheat from P.R. to P.R. Basis Use Case
Add Dispatch of Wheat from PR to

PR Basis Details
Upadet Dispatch of Wheat from PR Delete Dispatch of Wheat from PR to

Data Entry
to PR Basis Details PR Basis Details
Operator (DEO)
View Dispatch of Wheat from PR to

PR Basis Details
15.10.1 View Dispatch of Wheat from P.R. to P.R. Basis Details
Use Case FDIS–021: View Dispatch of Wheat from P.R. to P.R. Basis Details
Basic Information
Purpose: To view details about the wheat dispatched from one PR center to another
Pre Condition:
2. The user will fill in the dispatching center name, receiving center name.
SRS-60
the user.
6. The detailed information of the dispatching end and the receiving end will be
displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.10.2 Add Dispatch of Wheat from P.R. to P.R. Basis Details
Use Case FDIS-022: Add Dispatch of Wheat from P.R. to P.R. Basis Details
Basic Information
Purpose: To add details about the wheat dispatched from one PR center to another
Pre Condition:
3. The user will fill in the dispatching end details and the receiving end details.
Alternate 1 Step 3:
Alternate 2 step 4:
Post Condition:
15.10.3 Update Dispatch of Wheat from P.R. to P.R. Basis Details
Use Case FDIS-023: Update Dispatch of Wheat from P.R. to P.R. Basis Details
Basic Information
Purpose: To update details about the wheat dispatched from one PR center to another
Pre Condition:
Use Case FDIS-021: View Dispatch of Wheat from P.R. to P.R. Basis Details
SRS-61

Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.10.4 Delete Dispatch of Wheat from P.R. to P.R. Basis Details
Use Case FDIS-024 : Delete Dispatch of Wheat from P.R. to P.R. Basis Details
Basic Information
Purpose: To details about the wheat dispatched from one PR center to another
Pre Condition:
Use Case FDIS-021: View Dispatch of Wheat from P.R. to P.R. Basis Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-62
15.11 Wheat Stock Register Details Use Cases
Add Wheat Stock Register Details
Update Wheat Stock Register Details Delete Wheat Stock Register Details
Data Entry
Operator (DEO)
View Wheat Stock Register Details
15.11.1 View Wheat Stock Register Detail
Use Case FDIS–025: View Wheat Stock Register Detail

Basic Information
Purpose: To view wheat stock detail as per the certain scheme.
Pre Condition:
2. The user will fill in the scheme year and other particular details of the wheat stock.
SRS-63
the user.
6. The detailed information of the wheat stock will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.11.2 Add Wheat Stock Register Details
Use Case FDIS-026: Add Wheat Stock Register Details

Basic Information
Purpose: To add wheat stock details as per the certain scheme.
Pre Condition:
3. The user will fill in the scheme details and other relevant details on the screen.
Alternate 1 Step 3:
Post Condition:
15.11.3 Update Wheat Stock Register Details
Use Case FDIS-027: Update Wheat Stock Register Details

Basic Information
Purpose: To update wheat stock details as per the certain scheme.
SRS-64
Pre Condition:
Use Case FDIS-025: View Wheat Stock Register Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.11.4 Delete Wheat Stock Register Details
Use Case FDIS-028: Delete Wheat Stock Register Details

Basic Information
Purpose: To update wheat stock details as per the certain scheme.
Pre Condition:
Use Case FDIS-025: View Wheat Stock Register details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-65
15.12 Stock Article Register Use Cases
Add Stock Article Register Details
Update Stock Article Register Details Delete Stock Article Register Details
Data Entry
Operator (DEO)
View Stock Article Register Details
15.12.1 View Stock Article Register Details
Use Case FDIS–029: View Stock Article Register Details

Basic Information
Purpose: To view basic information about the certain stock in a center.
Pre Condition:
2. The user will fill in the center name, article name or other relevant details.
SRS-66
the user.
6. The detailed information of the stock at a certain center will be displayed on the
screen.
Alternate 1 Step 3:
Post Condition:
15.12.2 Add Stock Article Register Details
Use Case FDIS-030: Add Stock Article Register Details

Basic Information
Purpose: To add basic information about the certain stock in a center
Pre Condition:
3. The user will fill in the center name and other relevant details on the screen.
Alternate 1 Step 3:
Post Condition:
15.12.3 Update Stock Article Register Details
Use Case FDIS-031: Update Stock Article Register Details

Basic Information
Purpose: To update basic information about the certain stock in a center
SRS-67
Pre Condition:
Use Case FDIS-029: View Stock Article Register Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.12.4 Delete Stock Article Register Details
Use Case FDIS-032 : Delete Stock Article Register Details

Basic Information
Purpose: To delete basic information about the certain stock in a center
Pre Condition:
Use Case FDIS-029: View Stock Article Register Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-68
15.13 Wheat Sale Use Cases
Add Wheat Sale Details
Update Wheat Sale Details Delete Wheat Sale Details

Data Entry
Operator (DEO)
View Wheat Sale Details
15.13.1 View Wheat Sale Details
Use Case FDIS–033: View Wheat Sale Details

Basic Information
Purpose: To view wheat sale details of a particular center.
Pre Condition:
2. The user will fill select the scheme year.
SRS-69
the user.
6. The detailed information of the sale of wheat will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.13.2 Add Wheat Sale Details
Use Case FDIS-034: Add Wheat Sale Details

Basic Information
Purpose: To add wheat sale details of a particular center.
Pre Condition:
3. The user will fill in the scheme year and other details on the screen.
Alternate 1 Step 3:
Post Condition:
15.13.3 Update Wheat sale Details
Use Case FDIS-035: Update Wheat Sale Detail

Basic Information
Purpose: To update wheat sale details of a particular center.
Pre Condition:
SRS-70

Use Case FDIS-033: View Wheat Sale Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.13.4 Delete Wheat Sale Details
Use Case FDIS-036 : Delete Wheat Sale Details

Basic Information
Purpose: To delete update wheat sale details of a particular center.
Pre Condition:
Use Case FDIS-033: View Wheat Sale Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-71
15.14 Inventory of Bardana Use Cases
Add Inventory of Bardana Details
Update Inventory of Bardana Details Delete Inventory of Bardana Details

Data Entry
Operator (DEO)
View Inventory of Bardana Details
15.14.1 View Inventory of Bardana Details
Use Case FDIS–037: View Inventory of Bardana Details

Basic Information
Purpose: To view bardana inventory details
Pre Condition:
2. The user will fill in the center name, month, district or any other relevant details.
SRS-72
the user.
6. The detailed information of the bardana inventory will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.14.2 Add Inventory of Bardana Details
Use Case FDIS-038: Add Inventory of Bardana Details

Basic Information
Purpose: To add bardana inventory details
Pre Condition:
3. The user will fill in the center name, district and other fields on the screen.
Alternate 1 Step 3:
Post Condition:
15.14.3 Update Inventory of Bardana Details
Use Case FDIS-039: Update Inventory of Bardana Details

Basic Information
Purpose: To update bardana inventory details
SRS-73
Pre Condition:
Use Case FDIS-037: View Inventory of Bardana Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.14.4 Delete Inventory of Bardana Details
Use Case FDIS-040 : Delete Invetory of Bardana Details

Basic Information
Purpose: To delete bardana inventory details
Pre Condition:
Use Case FDIS-037: View Inventory of Bardana Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-74
15.15 Purchase and Dispatch Form Details Use Cases
Add Purchase and Dispatch Form

Details
Update Purchase and Dispatch Delete Purchase and Dispatch Form

Data Entry
Form Details Details
Operator (DEO)
View Purchase and Dispatch Form

Details
15.15.1 View Purchase and Dispatch Form Details
Use Case FDIS–041: View Purchase and Dispatch Form Details

Basic Information
Purpose: To view details of the wheat dispatched or purchased at a particular PR Center.
Pre Condition:
2. The user will fill in the PR center name and other relevant details.
SRS-75
the user.
6. The detailed information of the center will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.15.2 Add Purchase and Dispatch Form Details
Use Case FDIS-042: Add Purchase and Dispatch Form Details

Basic Information
Purpose: To add details of the wheat dispatched or purchased at a particular PR Center.
Pre Condition:
3. The user will fill in the center name, grower name and other relevant details on the
screen.
Alternate 1 Step 3:
Post Condition:
15.15.3 Update Purchase and Dispatch Form Details
Use Case FDIS-043: Update Purchase and Dispatch Form Details

Basic Information
Purpose: To update details of the wheat dispatched or purchased at a particular PR
Center.
SRS-76

Pre Condition:
Use Case FDIS-041: View Purchase and Dispatch Form Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.15.4 Delete Purchase and Dispatch Form Details
Use Case FDIS-044 : Delete Purchase and Dispatch Form Details

Basic Information
Purpose: To delete details of the wheat dispatched or purchased at a particular PR Center.
Pre Condition:
Use Case FDIS-041: View Purchase and Dispatch Form Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-77
15.16 Sample Slip Use Cases
Add Sample Slip Details
Update Sample Slip Details Delete Sample Slip Details

Data Entry
Operator (DEO)
View Sample Slip Details
15.16.1 View Sample Slip Details
Use Case FDIS–045: View Sample Slip Details

Basic Information
Purpose: To view the information about the sample slip.
Pre Condition:
2. The user will fill in the required fields in the form.
the user.
SRS-78
6. The detailed information will be displayed on the screen.

Alternate 1 Step 3:
Post Condition:
15.16.2 Add Sample Slip Details
Use Case FDIS-046: Add Sample Slip Details

Basic Information
Purpose: To add the information about the sample slip.
Pre Condition:
3. The user will fill in the different fields on different on the screen.
Alternate 1 Step 3:
Post Condition:
15.16.3 Update Sample Slip Detail
Use Case FDIS-047: Update Sample Slip Detail

Basic Information
Purpose: To update the information about the sample slip.
Pre Condition:
Use Case FDIS-045: View Sample Slip Details
SRS-79

Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.16.4 Delete Sample Slip Detail
Use Case FDIS-048 : Delete Sample Slip Detail

Basic Information
Purpose: To delete the information about the sample slip.
Pre Condition:
Use Case FDIS-045: View Sample Slip Detail
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-80
15.17 Purchased Wheat Details Use Cases
Add Purchased Wheat Details
Update Purchased Wheat Details Delete Purchased Wheat Details

Data Entry
Operator (DEO)
View Purchased Wheat Details
15.17.1 View Purchased Wheat Details
Use Case FDIS–049: View Purchase Wheat Details

Basic Information
Purpose: To view detail information of the wheat purchased at a PR center
Pre Condition:
2. The user will select the particular PR center and the particular month.
SRS-81
the user.
6. The detailed information of the particular month will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.17.2 Add Purchased Wheat Details
Use Case FDIS-050: Add Purchase Wheat Details

Basic Information
Purpose: To add detail information of the wheat purchased at a PR center
Pre Condition:
3. The user will fill in PR center and other details on the screen.
Alternate 1 Step 3:
Post Condition:
15.17.3 Update Purchased Wheat Details
Use Case FDIS-051: Update Purchase Wheat Details

Basic Information
Purpose: To update detail information of the wheat purchased at a PR center
Pre Condition:
SRS-82

Use Case FDIS-049: View Purchased Wheat Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.17.4 Delete Purchased Wheat Details
Use Case FDIS-052 : Delete Purchase Wheat Details

Basic Information
Purpose: To delete detail information of the wheat purchased at a PR center
Pre Condition:
Use Case FDIS-049: View Purchased Wheat Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-83
15.18 Miscellaneous Item Sale Register Use Cases
Add Miscellaneous Item Sale

Register Details
Update Miscellaneous Item Sale Delete Miscellaneous Item Sale

Data Entry
Register Details Register Details
Operator (DEO)
View Miscellaneous Item Sale

Register Details
15.18.1 View Miscellaneous Item Sale Register Details
Use Case FDIS–053: View Miscellaneous Item Sale Register Details

Basic Information
Purpose: To view general information about the miscellaneous item sold in the
department.
Pre Condition:
2. The user will fill in the item name, quantity or other relevant details.
SRS-84
the user.
6. The detailed information of the items will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.18.2 Add Miscellaneous Item Sale Register Details
Use Case FDIS-054: Add Miscellaneous Item Sale Register Details

Basic Information
Purpose: To add general information about the miscellaneous item sold in the
department.
Pre Condition:
3. The user will fill in the item, quantity, amount received and other relevant details.
Alternate 1 Step 3:
Post Condition:
15.18.3 Update Miscellaneous Item Sale Register Details
Use Case FDIS-055: Update Miscellaneous Item Sale Register Details

Basic Information
Purpose: To update general information about the miscellaneous item sold in the
department.
SRS-85

Pre Condition:
Use Case FDIS-053: View Miscellaneous Item Sale Register Details
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.18.4 Delete Miscellaneous Item Sale Register Details
Use Case FDIS-056 : Delete Miscellaneous Item Sale Register Details

Basic Information
Purpose: To delete general information about the miscellaneous item sold in the
department.
Pre Condition:
Use Case FDIS-053: View Miscellaneous Item Sale Register Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-86
15.19 Sale of Unserviceable Stock Articles Use Cases
Add Sale of Unserviceable Stock

Articles Details
Update Sale of Unserviceable Stock Delete Sale of Unserviceable Stock

Data Entry
Articles Details Articles Details
Operator (DEO)
View Sale of Unserviceable Stock

Articles Details
15.19.1 View Unserviceable Stock Articles Data
Use Case FDIS–057: View Unserviceable Stock Articles Data

Basic Information
Purpose: To view details about the unserviceable stock.
Pre Condition:
2. The user will fill in the district, center name.
SRS-87
the user.
6. The detailed information of the particular unserviceable stock will be displayed on the
screen.
Alternate 1 Step 3:
Post Condition:
15.19.2 Add Unserviceable Stock Articles Data
Use Case FDIS-058: Add View Unserviceable Stock Articles Data

Basic Information
Purpose: To add details about the unserviceable stock.
Pre Condition:
3. The user will fill in the center name, districts and other relevant details on the screen.
Alternate 1 Step 3:
Post Condition:
15.19.3 Update Unserviceable Stock Articles Data
Use Case FDIS-059: Update Unserviceable Stock Articles Data

Basic Information
Purpose: To update details about the unserviceable stock.
SRS-88

Pre Condition:
Use Case FDIS-057: View Unserviceable Stock Articles Data
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.19.4 Delete Unserviceable Stock Articles Data
Use Case FDIS-060 : Delete Unserviceable Stock Articles Data

Basic Information
Purpose: To delete details about the unserviceable stock.
Pre Condition:
Use Case FDIS-057: View Unserviceable Stock Articles Data
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-89
15.20 Receipt and Sale of Wheat Use Cases
Add Receipt and Sale of Wheat

Details
Upadet Receipt and Sale of Wheat Delete Receipt and Sale of Wheat
Data Entry
Details Details
Operator (DEO)
View Receipt and Sale of Wheat

Details
15.20.1 View Receipt and Sale of Wheat Details
Use Case FDIS–061: View Receipt And Sale Of Wheat Details

Basic Information
Purpose: To view receipt and sale of wheat data at a particular center.
Pre Condition:
2. The user will fill in the particular district, center name. etc.
the user.
SRS-90
6. The detailed information of the center will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.20.2 Add Receipt and Sale of Wheat Details
Use Case FDIS-062: Add Receipt And Sale Of Wheat Details

Basic Information
Purpose: To add receipt and sale of wheat data at a particular center.
Pre Condition:
3. The user will fill in the district, center name and other relevant details on the screen.
Alternate 1 Step 3:
Post Condition:
15.20.3 Update Receipt and Sale of Wheat Details
Use Case FDIS-063: Update Receipt And Sale Of Wheat Details

Basic Information
Purpose: To update receipt and sale of wheat data at a particular center.
Pre Condition:
SRS-91
Use Case FDIS-061: View Receipt And Sale Of Wheat Details

Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.20.4 Delete Receipt and Sale of Wheat Details
Use Case FDIS-064 : Delete Receipt And Sale Of Wheat Details

Basic Information
Purpose: To delete receipt and sale of wheat data at a particular center.
Pre Condition:
Use Case FDIS-061: View Receipt And Sale Of Wheat Details
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-92
15.21 Stock Receipt Information Use Cases
Add Stock Receipt Information
Update Stock Receipt Information Delete Stock Receipt Information

Data Entry
Operator (DEO)
View Stock Receipt Information
15.21.1 View Stock Receipt Information
Use Case FDIS–065: View Stock Receipt Information

Basic Information
Purpose: To view stock information of a particular scheme at a particular center.
Pre Condition:
2. The user will fill in the scheme year, center or any relevant details.
the user.
SRS-93
6. The detailed information of that particular scheme will be displayed on the screen.
Alternate 1 Step 3:
Post Condition:
15.21.2 Add Stock Receipt Information
Use Case FDIS-066: Add Stock Receipt Information

Basic Information
Purpose: To add stock information of a particular scheme at a particular center.
Pre Condition:
3. The user will fill in the scheme year, district, and center and any other relevant details
on different on the form.
Alternate 1 Step 3:
Post Condition:
15.21.3 Update Stock Receipt Information
Use Case FDIS-067: Update Stock Receipt Information

Basic Information
Purpose: To update stock information of a particular scheme at a particular center.
Pre Condition:
SRS-94

Use Case FDIS-065: View Stock Receipt Information
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.21.4 Delete Stock Receipt Information
Use Case FDIS-068 : Delete Stock Receipt Information

Basic Information
Purpose: To delete stock information of a particular scheme at a particular center.
Pre Condition:
Use Case FDIS-065: View Stock Receipt Information
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-95
15.22 Gate Pass Use Cases
Add Gate Pass Information
Update Gate Pass Information Delete Gate Pass Information

Data Entry
Operator (DEO)
View Gate Pass Information
15.22.1 View Gate Pass Information
Use Case FDIS–069: View Gate Pass Information

Basic Information
Purpose: To view the gate pass information
Pre Condition:
2. The user will fill in the center name, date or any other relevant information etc.
SRS-96
the user.
6. The detailed information of the gate pass for a particular day will be displayed on the
screen.
Alternate 1 Step 3:
Post Condition:
15.22.2 Add Gate Pass Information
Use Case FDIS-070: Add Gate Pass Information

Basic Information
Purpose: To add the gate pass information
Pre Condition:
3. The user will fill in the all relevant information on the screen.
Alternate 1 Step 3:
Post Condition:
15.22.3 Update Gate Pass Information
Use Case FDIS-071: Update Gate Pass Information

Basic Information
Purpose: To update the gate pass information
SRS-97
Pre Condition:
Use Case FDIS-069: View Gate Pass Information
Alternate 1 Step 2:
Alternate 2 step 5:
Post Condition:
15.22.4 Delete Gate Pass Information
Use Case FDIS-072: Delete Gate Pass Information

Basic Information
Purpose: To delete the gate pass information
Pre Condition:
Use Case FDIS-069: View Gate Pass Information
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-98
15.23 Employee Personal Information:
Delete Employee Personal

Information
Add Employee Personal Information Update Employee Personal

Data Entry
Information
Operator (DEO)
View Employee Personal Information
15.23.1 View Employee Personal Information:
UC-FDIS-073: View Employee’s Personal Information

Basic Information:
Purpose: To enter an employee’s personal information in the system.
Pre-Conditions:
SRS-99

2) The user will fill in the employee id or any other information.
3) The user will press view button.
4) The similar records as per the step 2 criteria will be shown in a new popup
window to the user.
5) User will select the specific record and presses the ok button.
Alternate 1:
Post-Condition:
Employee’s personal information record is present in the system.
15.23.2 Add Employee Personal Information:
UC-FDIS-074: Add Employee’s Personal Information

Basic Information:
Purpose: To add an employee’s personal information in the system.
Pre-Conditions:
2) The user will press the add button.
3) The user will fill in all the information regarding employee like name, father’s
name, NIC card number, addresses, domicile etc.
4) The user will press save button; information will be added into database when
the user presses the ok button of the confirmation box.
Alternate 1:
Post-Condition:
Employee’s personal information record is added in the system.
15.23.3 Update Employee Personal Information
UC-FDIS-075: Update Employee’s Personal Information

Basic Information:
Purpose: To Update an employee’s personal information in the system.
Pre-Conditions:
SRS-100

Alternate 1:
Post-Condition:
15.23.4 Delete Employee Personal Information
UC-FDIS-076: Delete Employee’s Personal Information

Basic Information:
Purpose: To delete an employee’s personal information in the system.
Cross References: UI-FDIS-020
Pre-Conditions:
2) The user will retrieve the record that he wants to delete
3) The user will press the delete button; information will be deleted (not
physically/permanently) from the database after user presses the ok button of
the confirmation box.
Alternate 1:
Post-Condition:
15.24 Employee Leave Approval / Rejection
Administrator Enter Em pl oyee's Leave Approval / Rejection
SRS-101
UC-FDIS-077: Enter Employee’s Leave Approval / Rejection

Basic Information:
Actors: Administrator
Purpose: To approve / reject an employee’s leave request along with the comments.
Cross References: UI-FDIS-021
Pre-Conditions:
1) The user accesses the appropriate Main Menu of the Food Department and
selects the HRMS link on the Main Menu.
2) The user selects the employee Leave Approval / Rejection link on the HRMS
Main Menu.
3) The system provides an appropriate interface to the user to specify the employee
id.
4) The system displays the employee particulars and an option to enter remarks for
leave approval / rejection.
Post-Conditions:
The leave is either approved / rejected along with the remarks.
15.25 Cane Commissionerate User Login
Login
Cane Commissioner Sugar Mill
Use Case UL-CC: User Login

Basic Information
Actor: Sugar Mill, Cane Commissioner
Purpose: To Login to the system
Cross Reference:
Pre Condition:
Typical Course Of Events:
1) User will run the program.
2) User will enter the user name and password.
3) The user will click the sign in button.
4) System will verify the username and password and check the privilege level of the
user and enable menus accordingly.
Alternate:
Post Condition:
SRS-102
15.26 Cane Commissionerate SCR II
View SCR II
Update SCR II Add SCR II

Sugar Mill Data
Entry Operator
Delete SCR II
15.26.1 View Cane Commissionerate SCR II
Use Case UC-FDIS- View SCR II

Basic Information
Actor: Sugar Mill Data Entry Operator
Purpose: To view SCR II
Cross Reference:
Pre Condition:
2. The user will fill in all the mandatory information.
SRS-103
the user.
6. The SCR II will be displayed on the screen.
Alternate 1
Post Condition:
15.26.2 Add Cane Commissionerate SCR II
Use Case UC-FDIS- Add SCR II

Basic Information
Purpose: To add SCR II
Cross Reference:
Pre Condition:
3. The user will fill in all the mandatory fields; if no field is filled then remark against
the field must be filled.
Alternate 1
Post Condition:
15.26.3 Update Cane Commissionerate SCR II
Use Case UC-FDIS- Update SCR II

Basic Information
Cross Reference:
Pre Condition:
2) The user will retrieve the record that he wants to update.
SRS-104
Alternate 1
Post Condition:
15.26.4 Delete Cane Commissionerate SCR II
Use Case UC-FDIS- Delete SCR II

Basic Information
Cross Reference:
Pre Condition:
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-105
15.27 Cane Commissionerate SCR I
View SCR I
Add SCR I Update SCR I

Sugar Mill Data
Entry Operator
Delete SCR I
15.27.1 View Cane Commissionerate SCR I
Use Case UC-FDIS- View SCR I

Basic Information
Purpose: To view SCR I
Cross Reference:
Pre Condition:
SRS-106

2) The user will fill in all the mandatory information.
3) The user will press view button.
4) The similar records as per the step 2 criteria will be shown in a new popup window to
the user.
5) User will select the specific record and presses the ok button.
6) The SCR I will be displayed on the screen.
Alternate 1
Post Condition:
15.27.2 Add Cane Commissionerate SCR I
Use Case UC-FDIS- Add SCR I

Basic Information
Purpose: To add SCR I
Cross Reference:
Pre Condition:
2) The user will press the add button.
3) The user will fill in all the mandatory fields; if no field is filled then remark against
the field must be filled.
4) The user will press save button; information will be added into database when the
Alternate 1
Post Condition:
15.27.3 Update Cane Commissionerate SCR I
Use Case UC-FDIS- Update SCR I

Basic Information
Cross Reference:
Pre Condition:
SRS-107
2) The user will retrieve the record that he wants to update.

Alternate 1
Post Condition:
15.27.4 Delete Cane Commissionerate SCR I
Use Case UC-FDIS- Delete SCR I

Basic Information
Cross Reference:
Pre Condition:
confirmation box.
Alternate 1 Step 3:
Post Condition:
SRS-108
15.28 Send Intimation Report
Send Intimation Report

Cane Commissioner
Use Case UC-FDIS- Send Intimation Report

Basic Information
Actor: Cane Commissioner
Purpose: To send warning to the Sugar Mills that have not sent their SCR I or SCR II
Cross Reference:
Pre Condition:
2) The user will press the report generation button.
3) The list of all the Sugar Mills will be shown that have not sent their SCR I or SCR II
4) The user will select the Sugar Mills to send the warning
5) The user will press the send mail button to send the warning to the selected Sugar
Mills
Alternate 1 Step 3:
1a) If the user will press the clear button the list will be cleared from the report
Post Condition:
15.29 Print Intimation Report
Print Intimation Report

Cane Commissioner
SRS-109
Use Case UC-FDIS- Print Intimation Report

Basic Information
Actor: Cane Commissioner
Purpose: To print warning for the Sugar Mills that have not sent their SCR I or SCR II
Cross Reference:
Pre Condition:
2) The user will press the report generation button.
3) The list of all the Sugar Mills will be shown that have not sent their SCR I or SCR II
4) The user will select the Sugar Mills to send the warning
5) The user will press the print button to print the warning for the selected Sugar Mills
Alternate 1
Post Condition:
SRS-110
16. User Interface
16.1 User Login
User Login GUI

Interface No. UI-A
Cross Reference Use Case. UC-A
Description: Screen will be used for Signing in to the Food Department

software / system for the desired purpose.
SRS-111
16.2 Group Management

Group Management GUI
Interface No. UI-B
Cross Reference Use Case. UC-D to G
Food Department Government of the Punjab-Group Management
Group Management
User Name: Assign Password
Group Name Group Type [Select Group ]
Interface Priviliges Privileges
Insert Delete Update View Print
Clear View Add Update Delete Save Exit
Description: The screen will be used to assign the privileges to a particular

group.
SRS-112
16.3 Food Department (Main Menu)

Food Department (Main Menu) GUI
Interface No. UI-FDIS -001
Cross Reference Use Case.
Food Department Information System (FDIS)-Main Menu
Food Department Information

System
Main Menu
Purchase and Dispatch Form Purchase Weight and Quality Certificate Help
Sample Slip Bill Purchase of Wheat
Food Details of Purchased Wheat Daily Register of Un Disbursed Bills
Statement of Purchase and Payment of Stock Report

Wheat (Weekly)
Grain Paper (Godown Register) Godown Card
Dispatch of Wheat from P.R. to P.R.Basis Dispatch Report
Wheat Stock Register Final Result of Storage Wheat in Godown.
Stock Article Register Inventory of Bardana
Sale of Unserviceable Stock Articles Receipt and Sale of Wheat
Stock Receipt Information Wheat Sale Information
Gate Pass Wheat Stock Register
Miscellaneous Things Sale Register Sugar Cane Commissioner
Financial Management System Human Resource Management System
Description: Screen will allow users to navigate through an form to add, update, delete and
view the records etc.
SRS-113
16.4 Purchase and Dispatch Form

Purchase and Dispatch Form GUI
Interface No. UI-FDIS-002
Cross Reference Use Case. UC-FDIS-041 to 044
Description: Screen will be used to view, add, update and delete wheat
purchase and dispatch record.
SRS-114
16.5 Purchase Weight and Quality Certificate

Purchase Weight and Quality Certificate GUI
Cross Reference Use Case. UC-FDIS-001-004
Description: Screen will be used to add, update delete and view purchase
details and quality certificate details.
SRS-115
16.6 Sample Slip

Sample Slip GUI
Food Department Government of the Punjab-GP-16
Sample Slip
Sample Slip
District [Select District] Center [Select Center]
Lot No.
Type [Select District] No. of Bags
Seller Grower Name Dispatching End
Recipient End Receiver Name
Wagon/Truck No. No. of Bags
R.R. No. R.R. Date [Select Date]
Invoice No. Invoice Date [Select Date]
Date of Sampling [Select Date] Laboratory Sent Date [Select Date]
Military Credit Note No. Classification of Bags [Select]
Godown No.
Description: Screen will be used to add, update delete and view the of wheat
sampling details.
SRS-116
16.7 Bill Purchase of Wheat

Bill Purchase of Wheat GUI
Food Department Government of the Punjab-Form-2
Bill Purchase of Wheat

Seller/Grower Details
Name Fathers Name
Address
Owner of Land Consignment No.
Village Name Chuck No.
Old N.I.C. No. New N.I.C No.
Lot No.
GP-16 Reference GP-05 Reference
GP-6 Reference
Destination/ Station Name Wagon No./Truck No.
Bility No.
Purchaser Details
No. of Bag Quantity of Wheat

Rate of Wheat /1000kg Wheat Price
Delivery Charges Commission/Agent
Extra Charges Details of Extra Charges
Total Amount Deduction of Amount
Net Amount for Payment (in figure)
(in words)
Amount Recommended (in figure)
(in words)
Bank Name
Description: Screen will be used to add, update delete and view wheat bill
purchase details.
SRS-117
16.8 Purchased Wheat Details

Purchased Wheat Details GUI
Description: Screen will be used to add, update delete and view the details of
Wheat Purchase in a particular PR center.
SRS-118
16.9 Daily Register of Un-Disbursed Bills

Daily Register of Un-Disbursed Bills GUI
Description: Screen will be used to add, update delete and view the information
about the un-disbursed wheat bills.
SRS-119
16.10 Miscellaneous Item Sale Register

Miscellaneous Item Sale Register GUI
Food Department Government of the Punjab-SF-27
Miscellaneous Item Sale Register

Date 20/12/2004
Name of
Stock Treasury
Details of
Received Loss If Challan Challan Reason For
S.No. Things Quantity Received Where
At the Amount Any No. Date Loss
Rate Amount Amount
Rate Of Deposited
Total
Auction Commission
In Case of Approval
Price After Commission
miscellaneous items sold.
SRS-120
16.11 Grain Paper (Godown Register)

Grain Paper (Godown Register) GUI
Grain at a certain center
SRS-121
16.12 Godown Card

Godown Card GUI
Godown like Mass of Godown, Date of Stock Starting, Storage Capacity,
Stock Completion Date etc.
SRS-122
16.13 Dispatch of Wheat from P.R. to P.R. Basis

Dispatch of Wheat from P.R. to P.R. Basis GUI
wheat dispatched form one P.R. to another.
SRS-123
16.14 Stock Article Register

Stock Article Register GUI
Food Department Government of the Punjab-Stock Article Register
Stock Article Register

Date 20/12/2004

Article Name [Select Article] Previous Balance
Receiving
Date of Receiving [Select Date] Place Received From
Quantity Received Completion Date of Storage
Release
By Order of Reference SF-27
Date SF-27 [Select Date] Quantity
Sale
By Order of Reference SF-27
Date SF-27 [Select Date] Quantity
Bank Name Amount Deposited in Bank
Challan No. Challan Date [Select Date]
Transfer
By Order of Destination
Reference No. of Dispatch Report [Select Date] Date of Dispatching Report [Select Date]
Quantity
Balance at the End of Month
Description: Screen will be used to add, update delete and view the wheat stock
article details.
SRS-124
16.15 Sale of Unserviceable Stock Articles

Sale of Unserviceable Stock Articles GUI
Description: Screen will be used to add, update delete and view the information
about the unserviceable stock article.
SRS-125
16.16 Receipt and Sale of Wheat

Receipt and Sale of Wheat GUI
Interface No. UI-RSW-014
Cross Reference Use Case. UC-FDIS-061-064
Food Department Government of the Punjab-Gate In Register
Receipt and Sale of Wheat

Instructions
Receipt and Sale of Wheat
G.P. 13
Serial No Date Dispatching Center Truck/ wagon No. Wheat Quality of Bardana Comments
No. Date
Date Indigenous
Imported Date Insert Quality
Description: Screen will be used to add, update delete and view the Receipt and
Sale of wheat details.
SRS-126
16.17 Inventory of Bardana

Inventory of Bardana GUI
Food Department Government of the Punjab-Inventory of Bardana
Inventory of Bardana
Date 20/12/2004
Inventory of Bardana
Center [Select Center] District [Select District]
Monthly Map [Select Moth] Related (Godown)
Bardana [Select Bardana] Month [Select Bardana]
Previous Balance
Bales Empty Bags
Filled Bags
Receiving
Truck/Train(Biility No) Scheme Year [Select Year]
Date 20/12/2004 Bales
Empty Bags Filled Bags
Consignment No.
Local Purchase price

By Order of Reference No.
Date [Select Date] Reference of Expenses
Income
Destination Station
Destination Station Dispatch Report (G.P.6)
Report No. Report Date [Select Date]
Bales Filled Bags
Empty Bags Date [Select Date]
Sale Center
Sale center By Order of and S.F. 21
Reference No. Reference Date [Select Date]
Bales Filled Bags
Empty Bags Rate
Bank Challan
Treasure Challan No. Date [Select Date]
Received Amount By
The Bank
Auctioned Bags
By Order of and S.F. 27 Reference No.
Reference Date [Select Date] Bales
Filled Bags Empty Bags
Remarks
Bardana.
SRS-127
16.18 Stock Receipt Information

Stock Receipt Information GUI
Instructions
Stock Receipt Information
Commodity Scheme Year [Select Year] Date [Select Date]
Center [Select Center] District [Select District] Stock Report No
Consignment No.
Senders Description
Senders Dispatch Dispatch G.P. 13 Railway Wagon No.

Serial No Dispatching Center Quality of Bardana
Description Report No. Report Date No. Date Truck No.
[Select Center] Indigenous

Date Date Insert Quality
Weight Description
Dispatched Weight Received Weight Excess Short Godown No.Where Stock Report GP-5 Quality of Bardana/
No. Of bags Matric Tons No. Of bags Matric Tons Weight Weight Stock Stored No. Date Remarks
Date
Total (Today)
Previous Toatal
Grand Total
wheat stock for a particular scheme.
SRS-128
16.19 Wheat Sale Information

Wheat Sale Information GUI
wheat sale.
SRS-129
16.20 Gate Pass

Gate Pass GUI
Food Department Government of the Punjab-Gate Pass
Gate Pass
Gate Pass Date 20/12/2004
Consignment No. Type of Gate Pass IGP

S. No. P.R. Center [Select P.R.Center]
Name of R.L. Authority No.
Permit No. Quantity
Gate Register No. Godown No.
Issuing Authority Passing Autority
Description: Screen will be used to add, update delete and view gate pass
detail.
SRS-130
16.21 Wheat Stock Register

Wheat Stock Register GUI
Food Department Government of the Punjab-SR-9
Wheat Stock Register

Date 20/12/2004
District [Select District] P.R. Center [Select P.R.Center] Scheme Year 20/12/2004
To Indicate Consolidated Position Of Wheat Stock Fall Schemes in Tons
Closing Balance Receipt Total
S. No. Date Indigenous Imported Indigenous Imported Indigenous Imported
Bags Tons Bags Tons Bags Tons Bags Tons Bags Tons Bags Tons
30/12/2004
Total Issues Closing Balance GPS Number

Local Sales Dispatches Total Indigenous Imported
Indigenous Imported Indigenous Imported Indigenous Imported Bags Tons
wheat stock like Closing Balance, Receipt, Total Issues etc.
SRS-131
16.22 Wheat Stock Register

Wheat Stock Register GUI
Interface No. UI-FDIS-019 A
Cross Reference Use Case. UC-FDIS-017A to 019A
Instructions
Dispatching End
Dispatch Report Date 20/12/2004
Dispatching Center [Select Center] District [Select District]

Date of Dispatch [Select Date] Scheme Year [Select Year]
Consignment No.
Sr. No. Reference District/Regional Lot No. Godown No. Dispatching Station Truck Invoice No.
/Directorate Office
Wagon No.- Truck No. Dispatch Bags Weight in GP-13 Railway Fare Remarks
Bags Weight
stock dispatched daily through trucks.
SRS-132
16.23 Employee Personal Information

Employee Personal Information
Description: This screen is used to add, view, update and delete the personal
information of the employee by using relevant buttons.
SRS-133
16.24 Employee Leave Approval / Rejection

Employee Leave Approval / Rejection
Cross Reference Use Case. UC-FDIS-077
Food Department Government of the Punjab - HRMS
Leave Approval / Rejection

ID : FD001118 Post / Designation : Additional Director Food
Name : Muhammad Kaeem
Leave Information
Leave From : 11/11/2003 To : 15/11/2003 Days : 5
Leave Type : Casual Remaining Leaves : 2
Reason : Work at Home
Address (during Leave) :

House No. 11, F 10/2,
Islamabad
Phones : 042-4353456, 0300-23453533
Remarks : Rejected due to ISO audit coming in the next week project evaluations required urgently. He
may apply for leave after a week.
Save Close
Description: This screen is used by the leave-granting officer to either approve / reject the leave
request of an employee along with the remarks.
SRS-134
16.25 HRMS Main Menu

HRMS Main Menu
Food Department Information System (FDIS)-Main Menu HRMIS
HRMS
Main Menu
Personal Information Leave Approval / Rejection
Description: This screen is used to access the HRMS module.
SRS-135
16.26 Cane Commissioner Login

HRMS Main Menu
Cane Commissioner Module
User Name Cane Commissioner
Password **************
Remember Password
Forget Password
Sign In Cancel
Description: This screen is used to access Cane Commissioner module.
SRS-136
16.27 Cane Commissioner SCR II

HRMS Main Menu
Description: This screen is used to enter data in SCR II.
SRS-137
16.28 Cane Commissioner SCR I

HRMS Main Menu
Description: This screen is used to enter data in SCR I.
SRS-138
16.29 Cane Commissioner Intimation Report

HRMS Main Menu
Description: This screen is used to send Intimation Report to the Sugar Mills.
SRS-139
17. Reports
17.1 Receipt and Sale of Wheat Report (Date Wise)
Receipt and Sale of Wheat Report (Date Wise)
Government of Punjab
Food Department
Receipt and Sale of Wheat Report

(Date Wise)
Sale Center: _______________________________
Receipt Center: ____________________________
Truck/ Indigenous Imported

S. No. Date Dispatching Center Wheat
Wagon No Wheat
Total
SRS-140
17.2 Receipt and Sale of Wheat Report (Center Wise)

Receipt and Sale of Wheat Report (Center Wise)
SRS-141
17.3 Grower / Agency Report

Grower / Agency Report
SRS-142
17.4 Purchase Bill Report (Center Wise)
Purchase Bill Report (Center Wise)
SRS-143
17.5 Purchase Bill Report (Seller Wise)

Purchase Bill Report (Seller Wise)
Food Department
Purchase Bill Report

(Seller Wise)
Seller/Grower Name: _______________________ Address: ____________________________
Owner of land: _____________________________ Village Name: _________________________
Chuck No.: _________________________________
G.P.06 G.P.05 G.P.16

Lot NIC No. NIC No. Reference Reference Reference Destination Wagon/
Bility No.
No. (New) (Old) No. No. No. Station Name Truck No.
SRS-144
17.6 Undisbursed Bills Report

Un-Disbursed Bills Report
Food Department
Un-Disbursed Bills Report
Date: _______________________________
Actual Date
No. of Unpaid Amount Center Incharge
S.No. Date of Bill Name of Payee of Payment
Purchase Bill (Rs) Name
by Bank
Total
SRS-145
17.7 Dispatch of Wheat from P.R. to P. R. Basis (Dispatching Wise)

Report
Dispatch of Wheat from P.R. to P. R. Basis (Dispatching Wise) Report
SRS-146
17.8 Dispatch of Wheat from P.R. to P. R. Basis (Receiving Wise) Report

Dispatch of Wheat from P.R. to P. R. Basis (Receiving Wise) Report
SRS-147
17.9 Wheat Stock Register Report

Wheat Stock Register Report
SRS-148
17.10 Final Result of Storage Wheat in Godown Report (Storage and

Issuance) Report
Final Result of Storage Wheat in Godown Report (Storage and Issuance) Report
SRS-149
17.11 Employee Education Qualification
Employee Education Qualification
Food Department
Educational Qualification
S. No. Qualification Year Institution Subjects
1 MSc Public Health 1998 Punjab University Nutrition
SRS-150
17.12 Employee Language Proficiency

Employee Language Proficiency
Food Department
Language Proficiency
S. No. Language Read Write Speak
1 Urdu Excellent Excellent Excellent
2 English Excellent Excellent Excellent
SRS-151
17.13 Employee Timings

Employee Timing
Food Department
Trainings
S. No. TitleTitle Particulars Start Date Duration
1 Public
Public Health
Health Harvard University 11/11/2003 2 Months
SRS-152
17.14 Employee Posting History

Employee Posting History
Food Department
Posting History
Sr. No Joining Date Department Designation BPS
1 11/11/2003 Food Department DDF D.G Khan XYZ
SRS-153
17.15 Employee Inquiry History / Annual Confidential Report

Employee Inquiry History / Annual Confidential Report
Food Department
Inquiry History / Annual Confidential Report (ACR)
Sr. No Inquiry Date Department Designation Inquiry Officier Remarks
He was found clean and no

1 11/11/2003 Food Department DDF D.G Khan XYZ
action was taken against him.
ACR 1998
He is a very diligent personnel of the Food Department and has never been found involved in any fraud or wrongdoing. His conduct has
been satisfactory and he proved himself to be an asset of the Food Department
SRS-154
18. Appendix A
Glossary of Terms
Term Description
FDIS Food Department Information System
DEO Data Entry Operator
PR Provincial Reserve
LAN Local Area Network
ICDS Integrated Central Depository System
OGP Outward Gate Pass
IGP In Gate Pass
DFC District Food Controller
C&W Construction & Works
FD Food Department
HRMS Human Resources Management System
EDO Executive District Officer
WAN Wide Area Network
LAN Local Area Network
DFC District Food Controller
FDIS Food Department Information System
FTP File Transfer Protocol
IP Internet Protocol
NIC National Identity Card
IGP Inward Gate Pass
OGP Outward Gate Pass
P&D Planning and Development
SRS-155
19. Appendix B
19.1 Sample Scanned Documents
19.1.1 Form SF-26 (Page 1)
Form SF-26 (Page 1)
SRS-156
19.1.2 Form SF-26 (Page 2)
Form SF-26 (Page 2)
SRS-157
19.1.3 Form 2 (Page 1)
Form 2 (Page 1)
SRS-158
19.1.4 Form 2 (Page 2)
Form 2 (Page 2)
SRS-159
19.1.5 Form GP-6
Form GP-6
SRS-160
19.1.6 District Inventory of Bardana Filled
District Inventory of Bardana Filled
SRS-161
19.1.7 District Inventory of Bardana Empty
District Inventory of Bardana Empty
SRS-162
19.1.8 Stock Article Register
SRS-163
19.1.9 Stock Ledger
Stock Ledger
SRS-164
19.1.10 Sample Slip
Sample Slip
SRS-165
19.1.11 Form 3
Form 3
SRS-166
19.1.12 Form SF-24
Form SF-24
SRS-167
19.1.13 Form SF-28
Form SF-28
SRS-168
19.1.14 Form GP-3
Form GP-3
SRS-169
19.1.15 Form GP-5
Form GP-5
SRS-170
19.1.16 Form GP-7
Form GP-7
SRS-171
19.1.17 Form GP-8
Form GP-8
SRS-172
19.1.18 Form GP-13 (Page 1)
Form GP-13 (Page 1)
SRS-173
19.1.19 Form GP-13 (Page 2)
Form GP-13 (Page 2)
SRS-174
19.1.20 Gate Pass
Gate Pass
SRS-175
19.1.21 Gate Register PR Center
Gate Register PR Center
SRS-176
19.1.22 Purchase and Dispatch Information Form
Purchase and Dispatch Information Form
SRS-177
19.1.23 Wheat Purchase
Wheat Purchase
SRS-178
19.1.24 Form SF-21
Form SF-21
SRS-179
19.1.25 Stock Articles
Stock Articles
SRS-180
19.1.26 Form SF-27
Form SF-27
SRS-181
19.1.27 Form SCR I
Form SCR I
SRS-182
19.1.28 Form SCR II
Form SCR II
SRS-183
SRS-184

SRS Food Department 19-1-05

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SRS Food Department 19-1-05

Diunggah oleh

Hak Cipta:

Format Tersedia

Table of Contents (SRS)

2. INTRODUCTION TO FOOD DEPARTMENT SRS-2

3. ORGANIZATIONAL STRUCTURE SRS-2

4. VISION STATEMENT SRS-4

5. PROJECT SCOPE SRS-5

6. EXISTING SYSTEM SRS-5

7. OVERALL DESCRIPTION OF THE PROPOSED SYSTEM SRS-17

8. HIGH LEVEL SYSTEM ARCHITECTURE SRS-19

9. ASSUMPTIONS AND DEPENDENCIES SRS-20

10. DESIGN AND IMPLEMENTATION CONSTRAINTS SRS-22

11. PROPOSED SYSTEM WORKFLOW SRS-23

12. SYSTEM FEATURES SRS-25

13. NON FUNCTIONAL REQUIREMENTS SRS-37

14. NON-TECHNICAL ISSUES SRS-38

15. USE CASE MODEL SRS-39

16. USER INTERFACE SRS-111

17. REPORTS SRS-140

18. APPENDIX A SRS-155

19. APPENDIX B SRS-156

1.1 Intended Audience and Reading Suggestions

2. Introduction to Food Department

Food Department is responsible for regulating business of food grains including

Food Department deals with procurement, storage and transportation of wheat. It

It also supplies wheat to other provinces and agencies.

Food Department is also responsible for monitoring and co-ordination of sugarcane

• Administration deals with human resource management of the Food

Food Department Information

Deputy Director Deputy Director

Asstt. Director Asstt. Director ACI

FDIS : Food Department Information System AFC

The Cane Commissionerate

• Cane Commissioner (Chairman)

The basic vision behind the ‘Computerization of Food Department’ Project is to

Currently, there is no online inter-division communication and the officials have to

The main functions of the Food Department comprises of:

• Setting the targets for wheat procurement

In addition to the expenditure incurred on purchase of wheat, the following extra

Food Department Directorate Wise Segregation

All the 8 Divisions reports

Storage Center 1 Storage Center 5 1 to 4 Storage Center 1 Storage Center 5

Storage Center 1 Storage Center 5

The Cane Commissioner administers two acts:

1. Sugar Factories Control Act 1950 and its rules (1950)

1. Examination of weighbridges and purchasing centers

1. Levy of Sugarcane (Dev) Cess

6.1 Wheat Procurement

Wheat Procurement Process Flow

Bill for payment is forwarded

1. The Incoming wheat is accompanied by a GP-13. All the trucks coming in

5. If there is difference in the weight of the wheat received as opposed to the

Receipt At Provincial Reserve Process Flow

Daily consolidated reports of

6.3 Dispatch of wheat from PR & Flag Center

5. At the end of the day, PR Incharge prepares GP-5 (Stock Report).

6. Godown card i.e., GP-9 is also prepared which is replica of GP-8.

Wheat Dispatch Process Flow

DFC Food Directorate Contractor

6.4 Sale of Wheat

2. The mill deposits the required funds in the government treasury.

4. The PR Incharge updates the Gate Register.

7. After the issuance of the authority letter, DFC

Wheat Sale to Flour Mills Process Flow

Request for the issuance of Verifies amount deposited