srs food department 19-1-05
TRANSCRIPT
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 1/185
1. INTRODUCTION SRS-1
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 2/185
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 specificconstraints 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 afterthe Contractor carries out a detailed system analysis. Similarly Use Case Models and
Graphical User Interfaces are of a preliminary nature and are provided only tofacilitate 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 incollaboration 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 3/185
Food Department Information System
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. Itissues 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 asselection 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. Eachdistrict 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 procurementand 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 againstemployees of the Food Department staff of the entire province.
SRS-2
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 4/185
Food Department Information System
• 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.
Secretary
Food
Food Department Information
System (FDIS)
Organizational Chart
Cane Commissioner Deputy Secretary-3Director
Food
FDIS : Food Department Information System
Deputy Director
(Directorate-4)Deputy Director
(Field-8)Addl. Director
Asstt. Director
(Directorate-4)
Asstt. Director
(Field-8)
DFC
(Field-31)
AFC
Food grainsInsp.
ACI
(10)
SRS-3
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 5/185
Food Department Information System
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 isas 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 itsrecommendations 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 theprocurement and release operations of wheat and to facilitate the CaneCommissionerate 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 releaseof 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 6/185
Food Department Information System
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 anyinformation 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. Theproject also includes developing an online facility for the sugarcane mill owners to
submit their reports to the Cane Commissionrate. The IT Infrastructure will be builtin 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 isbasically 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 torely 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 arealso 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 forthe 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 governmentneeds to supply the Wheat to the mills at a lower rate in order to curtail the rise in
SRS-5
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 7/185
Food Department Information System
wheat prices. In order to set the targets the directorate in consultation with theAgriculture 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. Healso 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 ingeneral. The DFC then forwards this information to the Directorate who thenarranges 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. Thistarget 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 fixedby 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 fromOctober 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 thestaff 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 8/185
Food Department Information System
In addition to the expenditure incurred on purchase of wheat, the following extraexpenditure is incurred on the day-to-day requirements in the wheat operation.
i. Purchase of gunny bags
ii. Bank Commissioniii. Delivery charges
iv. Taxes & Dutiesv. Transportation Chargesvi. Handling Charges
vii. Godown Expenses
viii. Establishment Charges
ix. Mark Up
Food Directorate
Division
District 1
Storage Center 1 Storage Center 5
Flag Center 1 Flag Center 10
District 4
Storage Center 1 Storage Center 5
Flag Center 1 Flag Center 10
1 to 4Districts
Division
District 1
Storage Center 1 Storage Center 5
Flag Center 1 Flag Center 10
District 4
Storage Center 1 Storage Center 5
Flag Center 1 Flag Center 10
1 to 4District
1 t o 8 D i v i s i o n s
Food Department Directorate Wise Segregation
All the 8 Divisions reportsto the Directorate
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 9/185
Food Department Information System
The Salient Features of the Punjab Sugar Factories Control Rules 1950 are asfollows:
1. Examination of weighbridges and purchasing centers2. Intimation regarding starting and termination of crushing
3. Elimination of middleman4. Prohibition of price below minimum price5. 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 grower3. Collection and payment by the mills
4. Purpose/utilization of cess
5. Exemption of cess6. 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 accounts10. Constitution of sugarcane (dev) fund
11. Fund to be operated by the DCOs
12. Appointment of funds (district/mill wise) after deducting 2% collectioncharges
13. Constitution of Provincial Committee14. Constitution of District Committee
Each Sugar Mill operating within Punjab is required to submit two sugar canereports (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 wasnot the case in the past when a sugar cane mill owner could only purchase sugar
cane from within his own zone.
SRS-8
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 10/185
Food Department Information System
6.1 Wheat Procurement
Procurement of wheat is made according to the targets fixed by the FederalGovernment/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 whichis 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 Governmenton 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 areset up in addition to the permanent centers.
1. Wheat Seller (Farmer) brings the wheat that he wants to sell to the centreincharge 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 thefarmer.
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 contractorwould have received.
SRS-9
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 11/185
Food Department Information System
8. If the wheat is received at the flag center, then it needs to be transported to thePR. 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 thisconfirmation.
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 thenthe 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 daywhich is forwarded to the District Office.
15. At the centre GP-5 also known as the Stock Report is also prepared whichcontains 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 isstoredat 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 fromthe centers.
18. Copies of the GP-4 are then sent to the divisional office from where theinformation is forwarded to the directorate for further compilation.
SRS-10
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 12/185
Food Department Information System
Seller/Grower
Wheat Procurement Process Flow
1
Requests for bardana against
CDR or personal surety2
1. Issue bardana
2. The wheat has to be
returned by the seller/ grower
with in 7 days of issuance of
bardana
Provincial Reserve
(PR) (Storage
Center)
Flag Center
3
Checking for weight and
quality of food, and after
checking the wheat is stored
in a PR or a Flag center
4Bill for payment is forwarded
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 13/185
Food Department Information System
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 othercopy of GP-5 is given to the respective DFC.
A process flow / workflow which clearly shows the whole process is as below. Thiswill 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 14/185
Food Department Information System
Receipt At Provincial Reserve Process Flow
Provincial Reserve
(Storage Center)
Wheat received for storage from other PR
or flag center to another PR center
1 3
2
Daily consolidated reports of
flag center and storage center
are dispatched to the District
offices
Daily consolidated reports of
District offices are sent to the
Divisional office
Daily consolidated reports of
Divisional offices are sent to
the Directorate
Flag Center
Provincial Reserve
(PR) (Storage
Center)
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 tosend 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 thetransporter 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 isdispatched.
SRS-13
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 15/185
Food Department Information System
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
DFC Food Directorate
1
Proposes Surplus stock to be
transported
Allocates and awards
contract
Contractor
2
Approaches DFC for
Contract signing
DFC specify quantity of
wheat to dispatch
Storage Center
(PR or Flag Center)
4
5
Loading of stocks
3
6
DestinationSends acknowledgement to the Provincial
Reserve center or the Flag Center through
contractor
7
SRS-14
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 16/185
Food Department Information System
6.4 Sale of Wheat
The wheat is sold to the flourmills according to their allocated quota. The mill canalso 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 perallocated 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 PRIncharge 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/FlagCenter 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 alsohelp in understanding the requirements. The whole process ‘Wheat Sale’ is
graphically represented below:
SRS-15
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 17/185
Food Department Information System
Wheat Sale to Flour Mills Process Flow
DFC
Allows release of wheat as
per Gov. policy
Flour Mill
1
Request for the issuance of
the wheat as per the allotted
quota
2
3
Deposits payments at banks
as per the rates specified
4Submits challan copy to DFC
5
Verifies amount deposited
through bank scroll
Storage Center
(PR or Flag Center)
6Bank challan copy is send tothe PR or Flag center to issue
wheat
7
Issue wheat to flour Mills
SRS-16
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 18/185
Food Department Information System
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
ors of the
software
(level-4)
The administrator has full control over the system. He
is responsible for creating groups / users, giving them
access rights, modifying groups / users, creating,
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
officials of
Food
Department
(level-3)
Read privilege for user management interfaces
Report generation
Officials
restricted
Officials of
lower grades
of Food
Department(level-2)
Read privileges for authorized interfaces.
Report generating facilities
Write privileges to a few restricted interfaces for
quality assurance
Operators Data entry
for
documents
(level-1)
Read privileges for User Management interfaces.
Read/write (as per the group/security policy) for all
interfaces.
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 houseaccording to the given solution. Application should be compatible with Internet
Explorer version 6 or higher.
SRS-17
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 19/185
Food Department Information System
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 purchasedincludes 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
Food Department
Information System
(FDIS)
All Divisions
All PR Centers
Cane
Commissioner
Higher Staff
Data Flow Diagram
Higher Staff includes the
Secretary, Director, Deputy
Director, etc
Retrieve
Store
Retrieve
Store
R e t r i e v e
S t o r e
R e t r i e v e
S t o r e
R e t r i e v e
General Public
SRS-18
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 20/185
Food Department Information System
8. High Level System Architecture
Service
Provider
High Level Network Architecture Diagram
Information Technology
Department (ITD)
Router
IS D N / DS L
Food Directorate
Application ServerRawalpindi Division
Application ServerSarghoda Division
I S
D N / D S L
I SD N / D i a l U p D ia l U p
Storage Center
I S D N / D i a l U p
1 t o 8 D i v i s i o n s
D i a l U p
Cane Commissionrate
SRS-19
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 21/185
Food Department Information System
9. Assumptions and Dependencies
9.1 Integration with ICDSThe 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 wouldalso 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 assumedthat the Bidder would have thoroughly read the “Law of Fire Arms and Explosives”
before submitting the proposal.
9.3 Data Collection from Existing WebsiteThe contractor will collect the data for the development of FDIS from the existing
website, www.punjab.gov.pk/food. This information would be of primaryimportance 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 theFDIS.
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 aconnection 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 thecommunication 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 beexported from one office to the other manually (e.g. on a compact disc etc.) as wellas 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 22/185
Food Department Information System
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 isenvisioned 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 WANThis project is closely linked with Lahore WAN as the data collected from differentstorage units will be made available to other departments through it.
9.8 Deployment & InstallationThe 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 FutureThe Contractor should also keep into consideration the fact that in near future the
wireless connectivity will be available everywhere in Punjab. This will be reallybeneficial 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 ModuleThe 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 laterstage. 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 FutureThe system must provide the facility to have an interface with the allocated banks sothat as soon as the payments are made to the seller/grower, it should also be updated
in the FDIS.
SRS-21
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 23/185
Food Department Information System
10. Design and Implementation Constraints
1. It is assumed that all the employees of the Food Department will have access tothe 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 bydefault.
7. ACRs etc related to any employee should only be accessible to the high levelusers 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 easyextension 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 24/185
Food Department Information System
SRS-23
11. Proposed System Workflow
D i a l u
p
D i a l u p
L A N
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 25/185
Food Department Information System
11.1 Proposed System for Cane Commissionerate
Cane Commissionrate
Sugar Mills (39)
3. In case of noncompliance issue
warnings to Sugar Mills.1. Send sugar cane
Reports to CaneCommissionrate (Daily
Basis Reports and
Fortnightly Reports)
2. Acknowledgement ofsugar cane report is
displayed.
FoodDepartment
4. Exchange latestReports
SRS-24
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 26/185
Food Department Information System
12. System Features
12.1 Application Features
1. Ability to create, edit and view different user groups. A user group is assignedprivileges 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 providesthe 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 everyscreen.
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 27/185
Food Department Information System
15. The system should have the ability of intelli-sense in which e.g., if an id of anemployee 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 lossof data.
2. When necessary, full data recovery must be made possible
3. The system should have an emergency / contingency module that captures anydata 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 acomprehensive 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 28/185
Food Department Information System
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 thatthe 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
• User name
• EncryptedPassword
• Read
Permission
• Write
Permission
• Distribute
Permission• Delete
Permission
• PrintPermission
• Supervise
Permission
Interface level security
• ReadPermission
• WritePermission
Permission
• DeletePermission
• ViewPermission
Group level security
• ReadPermission
• WritePermission
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 requiressome 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 29/185
Food Department Information System
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 DepartmentInformation System.
• Custom: Choice base installation by manually selecting each moduleseparately.
12.2 Generic Features
1. The system must have the ability to generate a tracking number/consignmentnumber from the central database with each consignment being transported.
2. This system must have the ability to determine the exact position of theconsignment being delivered.
3. The system must have the ability to generate separate web pages for CaneCommisionerate, 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 procuredand 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 wheatrequired 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 30/185
Food Department Information System
11. The system must have the ability to maintain record of capacity of each storagehouse.
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 toassign format of reports at storage, district and divisional levels.
16. The system must have the ability to interface and provide information to the FoodDepartment, 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 asper 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., thewheat procured for the current fiscal year for any storage center etc.
SRS-29
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 31/185
Food Department Information System
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 storageunit reports.
30. The system must have the ability to generate storage unit capacityand 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 FoodDepartment 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 acknowledgementslip (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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 32/185
Food Department Information System
10. The system must have the ability to transfer remaining amount from any head toanother 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 onefinancial year.
14. The system must have the ability to keep record of all the vouchers generated bythe system.
15. The system must have the ability to do account management with respect to allthe 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 33/185
Food Department Information System
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, jutebags, 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 rejectedwheat.
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 wheatseller/grower.
12. The system must have the ability to do maintain the information regarding thebags issued to the farmers and update it on daily basis.
SRS-32
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 34/185
Food Department Information System
13. The system must have the ability to ability to enter the information on Form -2 inthe 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 ratesannounced 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 35/185
Food Department Information System
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 wheatloaded, 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 36/185
Food Department Information System
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 andfortnightly 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 andSCR-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 andhave sent their forms via fax or regular mail.
9. The system must have the ability to allow the DFC to submit online applicationreport.
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 carriedout 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 37/185
Food Department Information System
2. The system must have the ability to have administrative privileges like: definemulti-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 anemployees 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 predefinedformat 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 actionsconducted 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 veryconfidential 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 theleave quota and leaves still available.
SRS-36
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 38/185
Food Department Information System
12. The system must have the ability to generate at least the following reports:
• Report containing a list with employee name, number, designation etc ismade 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 givenperiod 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 hisname, age, department served and tenure and any complaints against him
etc.
• Report containing the names of all employees against whom any criminalhas 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 theSoftware 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, whichis to be followed.
SRS-37
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 39/185
Food Department Information System
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 becompromised.
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 Bidderis 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 thenew system happens in an organized and planned manner without disrupting the day
to day operations.
SRS-38
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 40/185
Food Department Information System
15. Use Case Model
15.1 Hierarchy Management Use Cases
15.1.1
User Login
LogoutUser
Login
Use Case UL-A: User Login
Basic Information
Actor: Data Entry OperatorPurpose: 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
Update User GroupAssign User GroupAdministrator
SRS-39
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 41/185
Food Department Information System
15.3 User Group Management Use Case
Update Group
Add Group
Delete GroupAdministrator
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 theno information found.
Post Condition:
SRS-40
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 42/185
Food Department Information System
15.3.2 Add Group Privileges Use Case
Use Case UG-E: Add Group Privileges
Basic InformationActor: Administrator
Purpose: To Add the new user and to assign the privileges to the group.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 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
Actor: AdministratorPurpose: To update the user privileges
Cross Reference: UI-BPre Condition:
Use Case UI-A: User LoginUse Case UI-D: View Group Privileges
Primary Course of Events:
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 43/185
Food Department Information System
15.3.4 Delete Group Privileges Use Case
Use Case UG-G: Delete Group Privileges
Basic InformationActor: Administrator
Purpose: To delete the user privilegesCross Reference: UI-B
Pre Condition:
Use Case UI-A: User LoginUse Case UI-D: View Group Privileges
Primary Course Of Events:1) The user will access relevant interface.
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 bedeleted (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
Update Purchase Weight and Quality
Certificate Details
Add Purchase Weight and Quality
Certificate Details
Delete Purchase Weight and Quality
Certificate Details
View Purchase Weight and Quality
Certificate Details
Data Entry
Operator (DEO)
SRS-42
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 44/185
Food Department Information System
15.4.1 View Purchase Weight and Quality Certificate Details
Use Case FDIS–001: View Purchase Weight and Quality Certificate Details
Basic InformationActor: Data Entry Operator
Purpose: To view purchase weight and quality certificate detailsCross Reference: UI-FDIS-003
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
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 tothe 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 thescreen.
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:
15.4.2 Add Purchase Weight and Quality Certificate Details
Use Case FDIS-002: Purchase Weight and Quality Certificate Details
Basic Information
Actor: Data Entry OperatorPurpose: To add purchase weight and quality certificate details
Cross Reference: UI- FDIS -003
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
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 thefollowing information is already into the database.
Post Condition:
SRS-43
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 45/185
Food Department Information System
15.4.3 Update Purchase Weight and Quality Certificate Details
Use Case FDIS-003: Update Purchase Weight and Quality Certificate Details
Basic InformationActor: Data Entry Operator
Purpose: To update purchase weight and quality certificate detailsCross Reference: UI- FDIS -003
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-001: View Purchase Weight and Quality Certificate Details
Primary Course of Events: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
database after user presses the ok button of the confirmation box.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 InformationActor: Data Entry Operator
Purpose: To delete purchase weight and quality certificate details
Cross Reference: UI- FDIS -003
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-001: View Purchase Weight and Quality Certificate Details
Primary Course Of Events:1. The user will access relevant interface.
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 theconfirmation box.
Alternate 1 Step 3:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-44
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 46/185
Food Department Information System
15.5 Bill Purchase of Wheat Detail Use Cases
Update Bill Purchase of WheatDetails
Add Bill Purchase o f Wheat Details
Delete Bill Purchase of WheatDetails
View Bill Purchas e of Wheat Details
Data EntryOperator (DEO)
15.5.1 View Bill Purchase of Wheat Details
Use Case FDIS–005: View Bill Purchase of Wheat Details
Basic Information
Actor: Data Entry OperatorPurpose: To view wheat purchase bill details.
Cross Reference: UI- FDIS -005
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the seller/grower name and purchaser 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 seller/grower name or purchaser will be displayed on
the screen.
SRS-45
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 47/185
Food Department Information System
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:
15.5.2 Add Bill Purchase of Wheat Details
Use Case FDIS-006: Add Bill Purchase of Wheat Details
Basic InformationActor: Data Entry Operator
Purpose: To add wheat purchase bill details.
Cross Reference: UI- FDIS -005
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.2. The user will press the add button.
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.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 thefollowing information is already into the database.
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 DetailsBasic Information
Actor: Data Entry OperatorPurpose: To update wheat purchase bill details.
Cross Reference: UI- FDIS-005
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-005: View Bill Purchase of Wheat Details
SRS-46
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 48/185
Food Department Information System
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.5.4 Delete Bill Purchase of Wheat Details
Use Case FDIS-008 : Delete Wheat Purchase Bill Details
Basic InformationActor: Data Entry Operator
Purpose: To delete wheat purchase bill details.
Cross Reference: UI- FDIS -005
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-005: View Bill Purchase of Wheat Details
Primary Course Of Events:1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. The user will press the delete button; information will be deleted (not
physically/permanently) from the database after user presses the ok button of theconfirmation box.
Alternate 1 Step 3:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-47
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 49/185
Food Department Information System
15.6 Daily Register of Un-Disbursed Bill Details Use Cases
Update Daily Register of
Un-Disbursed Bills Details
Add Daily Register of Un-Disbursed
Bills Details
Delete Daily Register of
Un-Disbursed Bills Details
View Daily Register of Un-Disbursed
Bills Details
Data Entry
Operator (DEO)
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
Actor: Data Entry OperatorPurpose: To view un-disbursed bill details
Cross Reference: UI- FDIS-007
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will select district and the purchasing center and date in the form.
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.
SRS-48
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 50/185
Food Department Information System
5. User will select the specific record and presses the ok button.
6. The detailed information of the particular purchasing center will be displayed on the
screen.
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:
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
Actor: Data Entry Operator
Purpose: To add un-disbursed bill details
Cross Reference: UI- FDIS-007Pre Condition:Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will press the add button.
3. The user will fill in the payees name, date, amount and other details of the unpaidbills.
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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.6.3 Update Daily Register of Un-Disbursed Bill Details
Use Case FDIS-011: Update Daily Register of Un-Disbursed Bill Details
Basic InformationActor: Data Entry Operator
Purpose: To update un-disbursed bill details
Cross Reference: UI- FDIS-007
SRS-49
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 51/185
Food Department Information System
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-009: View Daily Register of Un-Disbursed Bill Details
Primary Course of Events: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
database after user presses the ok button of the confirmation box.
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.6.4 Delete Daily Register of Un-Disbursed Bill Details
Use Case FDIS-012 : Delete Daily Register of Un-Disbursed Bill Details
Basic InformationActor: Data Entry Operator
Purpose: To delete un-disbursed bill details
Cross Reference: UI-FDIS-007
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-009: View Daily Register of Un-Disbursed Bill Details
Primary Course Of Events:
1. The user will access relevant interface.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:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-50
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 52/185
Food Department Information System
15.7 Grain Paper (Godown Register) Use Cases
Update Grain Paper (GodownRegister) Details
Add Grain Paper (Godown Register)
Details
Delete Grain Paper (GodownRegister) Details
View Grain Paper (Godown Register)
Details
Data Entry
Operator (DEO)
15.7.1 View Grain Paper (Godown Register) Details
Use Case FDIS–013: View Grain Paper (Godown Register) Details
Basic Information
Actor: Data Entry Operator
Purpose: To view grain paper details
Cross Reference: UI-FDIS-009
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the PR center, Locality 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
SRS-51
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 53/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the particular PR center will be displayed on the screen.
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:
15.7.2 Add Grain Paper (Godown Register) Details
Use Case FDIS-014: Add Grain Paper (Godown Register) Details
Basic Information
Actor: Data Entry Operator
Purpose: To add grain paper details
Cross Reference: UI-FDIS-009Pre Condition:Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will press the add button.
3. The user will fill in the PR center name, locality 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.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.7.3 Update Grain Paper (Godown Register) Details
Use Case FDIS-015: Update Grain Paper (Godown Register) Details
Basic Information
Actor: Data Entry OperatorPurpose: To update grain paper details
Cross Reference: UI- FDIS-009
Pre Condition:
SRS-52
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 54/185
Food Department Information System
Use Case UL-A: User Login
Use Case FDIS-013: View Grain Paper (Godown Register) Details
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.7.4 Delete Grain Paper (Godown Register) Details
Use Case FDIS-016 : Delete Grain Paper (Godown Register) Details
Basic Information
Actor: Data Entry OperatorPurpose: To delete grain paper details
Cross Reference: UI-FDIS-009
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-013: View Grain Paper (Godown Register) DetailsPrimary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. 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:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-53
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 55/185
Food Department Information System
15.8 Godown Card Details Use Cases
Update Godown Card Details
Add Godown Card Details
Deleta Godown Card Details
View Godown Card Details
Data Entry
Operator (DEO)
15.8.1 View Godown Card Details
Use Case FDIS–017: View Godown Card Details
Basic Information
Actor: Data Entry Operator
Purpose: To view the information about the particular godown.
Cross Reference: UI-FDIS-010
Pre Condition:
Use Case UL-A: User LoginPrimary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the godown no., date of fumigation 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.
SRS-54
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 56/185
Food Department Information System
6. The detailed information of the particular godown will be displayed on the screen.
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:
15.8.2 Add Godown Card Details
Use Case FDIS-018: Add Godown Card Details
Basic Information
Actor: Data Entry OperatorPurpose: To add information about the particular godown.
Cross Reference: UI-FDIS-010
Pre Condition:
Use Case UL-A: User LoginPrimary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the godown No. and other information of the particular godown.
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 thefollowing information is already into the database.
Alternate 2b step 4:
2b) If the user will press the cancel button of the confirmation box the information willnot be added into the database.
Post Condition:
15.8.3 Update Godown Card Details
Use Case FDIS-019: Update Godown Card DetailsBasic Information
Actor: Data Entry OperatorPurpose: To update information about the particular godown.
Cross Reference: UI-FDIS-010
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-017: View Godown Card Details
SRS-55
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 57/185
Food Department Information System
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.8.4 Delete Godown Card Details
Use Case FDIS-020: Delete Godown Card Details
Basic Information
Actor: Data Entry Operator
Purpose: To delete godown details
Cross Reference: UI-FDIS-010
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-017: View Godown Card Details
Primary Course Of Events:
1. The user will access relevant interface.2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (notphysically/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 information will
not be deleted from the database.
Post Condition:
SRS-56
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 58/185
Food Department Information System
15.9 Dispatch Report Use Cases
Add Wheat Dispatch Report
View Wheat Dispatch ReportUpdate Wheat Dispatch Report
Delete Wheat Dis patch Report
Data Entry
Operator
15.9.1 View Wheat Dispatch Report
Use Case FDIS–017A: View Wheat Dispatch Report
Basic Information
Actor: Data Entry Operator
Purpose: To view the information about the wheat dispatched through the truck.
Cross Reference: UI-FDIS-019 A
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the dispatching center name, date 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.
SRS-57
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 59/185
Food Department Information System
5. User will select the specific record and presses the ok button.
6. The detailed information of the particular report will be displayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.9.2 Add Wheat Dispatch Report
Use Case FDIS-018A: Add Wheat Dispatch Report
Basic InformationActor: Data Entry Operator
Purpose: To add the information about the wheat dispatched through the truck..
Cross Reference: UI-FDIS-019 A
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will press the add button.
3. The user will fill in the dispatching center name and other information of the
particular godown.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.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.9.3 Update Wheat Dispatch Report
Use Case FDIS-019A: Update Wheat Dispatch Report
Basic Information
Actor: Data Entry OperatorPurpose: To update the information about the wheat dispatched through the truck.
Cross Reference: UI-FDIS-019 A
Pre Condition:
SRS-58
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 60/185
Food Department Information System
Use Case UL-A: User Login
Use Case FDIS-017A: View Wheat Dispatch Report
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.9.4 Delete Wheat Dispatch Report
Use Case FDIS-020A: Delete wheat Dispatch Report
Basic Information
Actor: Data Entry OperatorPurpose: To delete the information about the wheat dispatched through the truck.
Cross Reference: UI-FDIS-019 A
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-017A: View Wheat Dispatch ReportPrimary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. 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:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-59
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 61/185
Food Department Information System
15.10 Dispatch of Wheat from P.R. to P.R. Basis Use Case
Upadet Dispatch of Wheat from PR
to PR Basis Details
Add Dispatch of Wheat from PR to
PR Basis Details
Delete Dispatch of Wheat from PR to
PR Basis Details
View Dispatch of Wheat from PR to
PR Basis Details
Data EntryOperator (DEO)
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
Actor: Data Entry Operator
Purpose: To view details about the wheat dispatched from one PR center to another
Cross Reference: UI-FDIS-011Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the dispatching center name, receiving center name.
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
SRS-60
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 62/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the dispatching end and the receiving end will bedisplayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
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
Actor: Data Entry Operator
Purpose: To add details about the wheat dispatched from one PR center to anotherCross Reference: UI- FDIS -011
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the dispatching end details and the receiving end 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 tosave data into the database.
Alternate 2 step 4:
2a) If the user will press the cancel button of the confirmation box the information willnot be added into the database.
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 DetailsBasic Information
Actor: Data Entry OperatorPurpose: To update details about the wheat dispatched from one PR center to another
Cross Reference: UI- FDIS -011
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-021: View Dispatch of Wheat from P.R. to P.R. Basis Details
SRS-61
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 63/185
Food Department Information System
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
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
Actor: Data Entry Operator
Purpose: To details about the wheat dispatched from one PR center to another
Cross Reference: UI- FDIS -011
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-021: View Dispatch of Wheat from P.R. to P.R. Basis Details
Primary Course Of Events:
1. The user will access relevant interface.2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (notphysically/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 information will
not be deleted from the database.
Post Condition:
SRS-62
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 64/185
Food Department Information System
15.11 Wheat Stock Register Details Use Cases
Update Wheat Stock Regis ter Details
Add Wheat Stock Register Details
Delete Wheat Stock Register Details
View Wheat Stock Register Details
Data Entry
Operator (DEO)
15.11.1 View Wheat Stock Register Detail
Use Case FDIS–025: View Wheat Stock Register Detail
Basic InformationActor: Data Entry Operator
Purpose: To view wheat stock detail as per the certain scheme.Cross Reference: UI- FDIS -019
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the scheme year and other particular details of the wheat stock.3. The user will press view button.
SRS-63
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 65/185
Food Department Information System
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 wheat stock will be displayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.11.2 Add Wheat Stock Register Details
Use Case FDIS-026: Add Wheat Stock Register Details
Basic Information
Actor: Data Entry Operator
Purpose: To add wheat stock details as per the certain scheme.Cross Reference: UI- FDIS -019
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the scheme details and other relevant details on the screen.
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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.11.3 Update Wheat Stock Register Details
Use Case FDIS-027: Update Wheat Stock Register Details
Basic InformationActor: Data Entry Operator
Purpose: To update wheat stock details as per the certain scheme.
Cross Reference: UI- FDIS -019
SRS-64
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 66/185
Food Department Information System
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-025: View Wheat Stock Register Details
Primary Course of Events: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
database after user presses the ok button of the confirmation box.
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.11.4 Delete Wheat Stock Register Details
Use Case FDIS-028: Delete Wheat Stock Register Details
Basic InformationActor: Data Entry Operator
Purpose: To update wheat stock details as per the certain scheme.
Cross Reference: UI- FDIS -019
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-025: View Wheat Stock Register details
Primary Course Of Events:
1. The user will access relevant interface.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:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-65
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 67/185
Food Department Information System
15.12 Stock Article Register Use Cases
Update Stock Article Register Details
Add Stock Article Register Details
Delete Stock Article Register Details
View Stock Article Register Details
Data Entry
Operator (DEO)
15.12.1 View Stock Article Register Details
Use Case FDIS–029: View Stock Article Register Details
Basic Information
Actor: Data Entry Operator
Purpose: To view basic information about the certain stock in a center.
Cross Reference: UI- FDIS -012Pre Condition:Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will fill in the center name, article name or 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
SRS-66
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 68/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the stock at a certain center will be displayed on thescreen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.12.2 Add Stock Article Register Details
Use Case FDIS-030: Add Stock Article Register Details
Basic Information
Actor: Data Entry Operator
Purpose: To add basic information about the certain stock in a centerCross Reference: UI- FDIS -012
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the center name and other relevant details on the screen.
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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.12.3 Update Stock Article Register Details
Use Case FDIS-031: Update Stock Article Register Details
Basic InformationActor: Data Entry Operator
Purpose: To update basic information about the certain stock in a center
Cross Reference: UI- FDIS -012
SRS-67
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 69/185
Food Department Information System
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-029: View Stock Article Register Details
Primary Course of Events: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
database after user presses the ok button of the confirmation box.
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.12.4 Delete Stock Article Register Details
Use Case FDIS-032 : Delete Stock Article Register Details
Basic InformationActor: Data Entry Operator
Purpose: To delete basic information about the certain stock in a center
Cross Reference: UI- FDIS -012
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-029: View Stock Article Register Details
Primary Course Of Events:
1. The user will access relevant interface.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:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-68
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 70/185
Food Department Information System
15.13 Wheat Sale Use Cases
Update Wheat Sale Details
Add Wheat Sale Details
Delete Wheat Sale Details
View Wheat Sale Details
Data Entry
Operator (DEO)
15.13.1 View Wheat Sale Details
Use Case FDIS–033: View Wheat Sale Details
Basic Information
Actor: Data Entry Operator
Purpose: To view wheat sale details of a particular center.
Cross Reference: UI- FDIS -017Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill select the scheme year.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
SRS-69
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 71/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the sale of wheat will be displayed on the screen.
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:
15.13.2 Add Wheat Sale Details
Use Case FDIS-034: Add Wheat Sale Details
Basic Information
Actor: Data Entry OperatorPurpose: To add wheat sale details of a particular center.
Cross Reference: UI- FDIS -017Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will press the add button.
3. The user will fill in the scheme year and other details on the screen.
4. The user will press save button; information will be added into database when theuser 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 thefollowing information is already into the database.
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.13.3 Update Wheat sale Details
Use Case FDIS-035: Update Wheat Sale Detail
Basic InformationActor: Data Entry Operator
Purpose: To update wheat sale details of a particular center.
Cross Reference: UI- FDIS -017
Pre Condition:
SRS-70
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 72/185
Food Department Information System
Use Case UL-A: User Login
Use Case FDIS-033: View Wheat Sale Details
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.13.4 Delete Wheat Sale Details
Use Case FDIS-036 : Delete Wheat Sale Details
Basic Information
Actor: Data Entry OperatorPurpose: To delete update wheat sale details of a particular center.
Cross Reference: UI- FDIS -017
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-033: View Wheat Sale DetailsPrimary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. 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:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-71
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 73/185
Food Department Information System
15.14 Inventory of Bardana Use Cases
Update Inventory of Bardana Details
Add Inventory of Bardana Details
Delete Inventory of Bardana Details
View Inventory of Bardana Details
Data EntryOperator (DEO)
15.14.1 View Inventory of Bardana Details
Use Case FDIS–037: View Inventory of Bardana Details
Basic InformationActor: Data Entry Operator
Purpose: To view bardana inventory details
Cross Reference: UI- FDIS -015
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the center name, month, district or any other relevant details.
3. The user will press view button.
SRS-72
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 74/185
Food Department Information System
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 bardana inventory will be displayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.14.2 Add Inventory of Bardana Details
Use Case FDIS-038: Add Inventory of Bardana Details
Basic Information
Actor: Data Entry Operator
Purpose: To add bardana inventory detailsCross Reference: UI- FDIS -015
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the center name, district and other fields on the screen.
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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.14.3 Update Inventory of Bardana Details
Use Case FDIS-039: Update Inventory of Bardana Details
Basic InformationActor: Data Entry Operator
Purpose: To update bardana inventory details
Cross Reference: UI- FDIS -015
SRS-73
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 75/185
Food Department Information System
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-037: View Inventory of Bardana Details
Primary Course of Events: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
database after user presses the ok button of the confirmation box.
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.14.4 Delete Inventory of Bardana Details
Use Case FDIS-040 : Delete Invetory of Bardana Details
Basic InformationActor: Data Entry Operator
Purpose: To delete bardana inventory details
Cross Reference: UI- FDIS -015
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-037: View Inventory of Bardana Details
Primary Course Of Events:
1. The user will access relevant interface.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:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-74
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 76/185
Food Department Information System
15.15 Purchase and Dispatch Form Details Use Cases
Cross Reference: UI- FDIS -002
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
Update Purchase and Dispatch
Form Details
Add Purchase and Dispatch Form
Details
Delete Purchase and Dispatch Form
Details
View Purchase and Dispatch Form
Details
Data Entry
Operator (DEO)
15.15.1 View Purchase and Dispatch Form Details
Use Case FDIS–041: View Purchase and Dispatch Form Details
Basic Information
Actor: Data Entry Operator
Purpose: To view details of the wheat dispatched or purchased at a particular PR Center.
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will fill in the PR center name and other relevant details.
SRS-75
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 77/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the center will be displayed on the screen.
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:
15.15.2 Add Purchase and Dispatch Form Details
Use Case FDIS-042: Add Purchase and Dispatch Form Details
Basic Information
Actor: Data Entry OperatorPurpose: To add details of the wheat dispatched or purchased at a particular PR Center.
Cross Reference: UI- FDIS -002Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will press the add button.
3. The user will fill in the center name, grower name and other relevant details on the
screen.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 tosave 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.
Alternate 2b step 4:
2b) If the user will press the cancel button of the confirmation box the information willnot be added into the database.
Post Condition:
15.15.3 Update Purchase and Dispatch Form Details
Use Case FDIS-043: Update Purchase and Dispatch Form Details
Basic Information
Actor: Data Entry Operator
Purpose: To update details of the wheat dispatched or purchased at a particular PRCenter.
SRS-76
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 78/185
Food Department Information System
Cross Reference: UI- FDIS -002
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-041: View Purchase and Dispatch Form Details
Primary Course of Events:
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
database after user presses the ok button of the confirmation box.
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.15.4 Delete Purchase and Dispatch Form Details
Use Case FDIS-044 : Delete Purchase and Dispatch Form Details
Basic InformationActor: Data Entry Operator
Purpose: To delete details of the wheat dispatched or purchased at a particular PR Center.
Cross Reference: UI- FDIS -002
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-041: View Purchase and Dispatch Form Details
Primary Course Of Events:1. The user will access relevant interface.
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 theconfirmation box.
Alternate 1 Step 3:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.Post Condition:
SRS-77
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 79/185
Food Department Information System
15.16 Sample Slip Use Cases
Add Sample Slip Details
Update Sample Slip Details Delete Sample Slip Details
View Sample Slip Details
Data Entry
Operator (DEO)
15.16.1 View Sample Slip Details
Use Case FDIS–045: View Sample Slip Details
Basic Information
Actor: Data Entry OperatorPurpose: To view the information about the sample slip.
Cross Reference: UI- FDIS -004
Pre Condition:
Use Case UL-A: User LoginPrimary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the required fields in the form.
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 tothe user.
5. User will select the specific record and presses the ok button.
SRS-78
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 80/185
Food Department Information System
6. The detailed information will be displayed on the screen.
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:
15.16.2 Add Sample Slip Details
Use Case FDIS-046: Add Sample Slip Details
Basic Information
Actor: Data Entry OperatorPurpose: To add the information about the sample slip.
Cross Reference: UI- FDIS -004
Pre Condition:
Use Case UL-A: User LoginPrimary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the different fields on different on the screen.
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 thefollowing information is already into the database.
Alternate 2b step 4:
2b) If the user will press the cancel button of the confirmation box the information willnot be added into the database.
Post Condition:
15.16.3 Update Sample Slip Detail
Use Case FDIS-047: Update Sample Slip DetailBasic Information
Actor: Data Entry OperatorPurpose: To update the information about the sample slip.
Cross Reference: UI- FDIS -004
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-045: View Sample Slip Details
SRS-79
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 81/185
Food Department Information System
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.16.4 Delete Sample Slip Detail
Use Case FDIS-048 : Delete Sample Slip Detail
Basic Information
Actor: Data Entry Operator
Purpose: To delete the information about the sample slip.
Cross Reference: UI- FDIS -004
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-045: View Sample Slip Detail
Primary Course Of Events:
1. The user will access relevant interface.2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (notphysically/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 information will
not be deleted from the database.
Post Condition:
SRS-80
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 82/185
Food Department Information System
15.17 Purchased Wheat Details Use Cases
Add Purchased Wheat Details
Update Purchased Wheat Details Delete Purchased Wheat Details
View Purchased Wheat Details
Data Entry
Operator (DEO)
15.17.1 View Purchased Wheat Details
Use Case FDIS–049: View Purchase Wheat Details
Basic Information
Actor: Data Entry Operator
Purpose: To view detail information of the wheat purchased at a PR center
Cross Reference: UI- FDIS -006Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will select the particular PR center and the particular month.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
SRS-81
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 83/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the particular month will be displayed on the screen.
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:
15.17.2 Add Purchased Wheat Details
Use Case FDIS-050: Add Purchase Wheat Details
Basic Information
Actor: Data Entry Operator
Purpose: To add detail information of the wheat purchased at a PR center
Cross Reference: UI- FDIS -006Pre Condition:Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will press the add button.
3. The user will fill in PR center and other details on the screen.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.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.17.3 Update Purchased Wheat Details
Use Case FDIS-051: Update Purchase Wheat Details
Basic Information
Actor: Data Entry OperatorPurpose: To update detail information of the wheat purchased at a PR center
Cross Reference: UI- FDIS -006
Pre Condition:
SRS-82
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 84/185
Food Department Information System
Use Case UL-A: User Login
Use Case FDIS-049: View Purchased Wheat Details
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.17.4 Delete Purchased Wheat Details
Use Case FDIS-052 : Delete Purchase Wheat Details
Basic Information
Actor: Data Entry OperatorPurpose: To delete detail information of the wheat purchased at a PR center
Cross Reference: UI- FDIS -006
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-049: View Purchased Wheat DetailsPrimary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. 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:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-83
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 85/185
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 86/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the items will be displayed on the screen.
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:
15.18.2 Add Miscellaneous Item Sale Register Details
Use Case FDIS-054: Add Miscellaneous Item Sale Register Details
Basic Information
Actor: Data Entry Operator
Purpose: To add general information about the miscellaneous item sold in the
department.Cross Reference: UI- FDIS -008
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the item, quantity, amount received 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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.18.3 Update Miscellaneous Item Sale Register Details
Use Case FDIS-055: Update Miscellaneous Item Sale Register Details
Basic InformationActor: Data Entry Operator
Purpose: To update general information about the miscellaneous item sold in the
department.
SRS-85
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 87/185
Food Department Information System
Cross Reference: UI- FDIS -008
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-053: View Miscellaneous Item Sale Register Details
Primary Course of Events:
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
database after user presses the ok button of the confirmation box.
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.18.4 Delete Miscellaneous Item Sale Register Details
Use Case FDIS-056 : Delete Miscellaneous Item Sale Register Details
Basic InformationActor: Data Entry Operator
Purpose: To delete general information about the miscellaneous item sold in the
department.
Cross Reference: UI- FDIS -008Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-053: View Miscellaneous Item Sale Register Details
Primary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (notphysically/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 information willnot be deleted from the database.
Post Condition:
SRS-86
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 88/185
Food Department Information System
15.19 Sale of Unserviceable Stock Articles Use Cases
Update Sale of Unserviceable Stock
Articles Details
Add Sale of Unserviceable Stock
Articles Details
Delete Sale of Unserviceable Stock
Articles Details
View Sale of Unserviceable Stock
Articles Details
Data Entry
Operator (DEO)
15.19.1 View Unserviceable Stock Articles Data
Use Case FDIS–057: View Unserviceable Stock Articles Data
Basic Information
Actor: Data Entry OperatorPurpose: To view details about the unserviceable stock.
Cross Reference: UI- FDIS -013
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the district, center name.
3. The user will press view button.
SRS-87
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 89/185
Food Department Information System
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 particular unserviceable stock will be displayed on the
screen.
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:
15.19.2 Add Unserviceable Stock Articles Data
Use Case FDIS-058: Add View Unserviceable Stock Articles Data
Basic Information
Actor: Data Entry OperatorPurpose: To add details about the unserviceable stock.
Cross Reference: UI- FDIS -013
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will press the add button.
3. The user will fill in the center name, districts and other relevant details on the screen.
4. The user will press save button; information will be added into database when theuser 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.
Alternate 2b step 4:
2b) If the user will press the cancel button of the confirmation box the information willnot be added into the database.
Post Condition:
15.19.3 Update Unserviceable Stock Articles Data
Use Case FDIS-059: Update Unserviceable Stock Articles Data
Basic Information
Actor: Data Entry Operator
Purpose: To update details about the unserviceable stock.
SRS-88
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 90/185
Food Department Information System
Cross Reference: UI- FDIS -013
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-057: View Unserviceable Stock Articles Data
Primary Course of Events:
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
database after user presses the ok button of the confirmation box.
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.19.4 Delete Unserviceable Stock Articles Data
Use Case FDIS-060 : Delete Unserviceable Stock Articles Data
Basic InformationActor: Data Entry Operator
Purpose: To delete details about the unserviceable stock.
Cross Reference: UI- FDIS -013
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-057: View Unserviceable Stock Articles Data
Primary Course Of Events:1. The user will access relevant interface.
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 theconfirmation box.
Alternate 1 Step 3:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.Post Condition:
SRS-89
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 91/185
Food Department Information System
15.20 Receipt and Sale of Wheat Use Cases
Upadet Receipt and Sale of Wheat
Details
Add Receipt and Sale of Wheat
Details
Delete Receipt and Sale of Wheat
Details
View Receipt and Sale of Wheat
Details
Data Entry
Operator (DEO)
15.20.1 View Receipt and Sale of Wheat Details
Use Case FDIS–061: View Receipt And Sale Of Wheat Details
Basic InformationActor: Data Entry Operator
Purpose: To view receipt and sale of wheat data at a particular center.
Cross Reference: UI- FDIS -014
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the particular district, center name. etc.
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 tothe user.
SRS-90
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 92/185
Food Department Information System
5. User will select the specific record and presses the ok button.
6. The detailed information of the center will be displayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.20.2 Add Receipt and Sale of Wheat Details
Use Case FDIS-062: Add Receipt And Sale Of Wheat Details
Basic InformationActor: Data Entry Operator
Purpose: To add receipt and sale of wheat data at a particular center.
Cross Reference: UI- FDIS -014
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will press the add button.
3. The user will fill in the district, center name and other relevant details on the screen.
4. The user will press save button; information will be added into database when theuser 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 tosave 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.
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.20.3 Update Receipt and Sale of Wheat Details
Use Case FDIS-063: Update Receipt And Sale Of Wheat Details
Basic InformationActor: Data Entry Operator
Purpose: To update receipt and sale of wheat data at a particular center.
Cross Reference: UI- FDIS -014
Pre Condition:Use Case UL-A: User Login
SRS-91
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 93/185
Food Department Information System
Use Case FDIS-061: View Receipt And Sale Of Wheat Details
Primary Course of Events:
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
database after user presses the ok button of the confirmation box.
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.20.4 Delete Receipt and Sale of Wheat Details
Use Case FDIS-064 : Delete Receipt And Sale Of Wheat Details
Basic Information
Actor: Data Entry Operator
Purpose: To delete receipt and sale of wheat data at a particular center.
Cross Reference: UI- FDIS -014
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-061: View Receipt And Sale Of Wheat Details
Primary Course Of Events:1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete
3. The user will press the delete button; information will be deleted (notphysically/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 information willnot be deleted from the database.
Post Condition:
SRS-92
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 94/185
Food Department Information System
15.21 Stock Receipt Information Use Cases
Update Stock Receipt Information Delete Stock Receipt Information
View Stock Receipt Information
Add Stock Receipt Information
Data EntryOperator (DEO)
15.21.1 View Stock Receipt Information
Use Case FDIS–065: View Stock Receipt Information
Basic InformationActor: Data Entry Operator
Purpose: To view stock information of a particular scheme at a particular center.
Cross Reference: UI- FDIS -016
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will fill in the scheme year, center or any 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 tothe user.
SRS-93
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 95/185
Food Department Information System
5. User will select the specific record and presses the ok button.
6. The detailed information of that particular scheme will be displayed on the screen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.21.2 Add Stock Receipt Information
Use Case FDIS-066: Add Stock Receipt Information
Basic InformationActor: Data Entry Operator
Purpose: To add stock information of a particular scheme at a particular center.
Cross Reference: UI- FDIS -016
Pre Condition:Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.2. The user will press the add button.
3. The user will fill in the scheme year, district, and center and any other relevant details
on different on the form.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.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.21.3 Update Stock Receipt Information
Use Case FDIS-067: Update Stock Receipt Information
Basic Information
Actor: Data Entry OperatorPurpose: To update stock information of a particular scheme at a particular center.
Cross Reference: UI- FDIS -016
Pre Condition:
SRS-94
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 96/185
Food Department Information System
Use Case UL-A: User Login
Use Case FDIS-065: View Stock Receipt Information
Primary Course of Events:
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 thedatabase after user presses the ok button of the confirmation box.
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 willnot be saved into the database.
Post Condition:
15.21.4 Delete Stock Receipt Information
Use Case FDIS-068 : Delete Stock Receipt Information
Basic Information
Actor: Data Entry OperatorPurpose: To delete stock information of a particular scheme at a particular center.
Cross Reference: UI- FDIS -016
Pre Condition:Use Case UL-A: User Login
Use Case FDIS-065: View Stock Receipt InformationPrimary Course Of Events:
1. The user will access relevant interface.
2. The user will retrieve the record that he wants to delete3. 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:1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-95
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 97/185
Food Department Information System
15.22 Gate Pass Use Cases
Update Gate Pass Information
Add Gate Pass Information
Delete Gate Pass Information
View Gate Pass Information
Data Entry
Operator (DEO)
15.22.1 View Gate Pass Information
Use Case FDIS–069: View Gate Pass Information
Basic Information
Actor: Data Entry Operator
Purpose: To view the gate pass information
Cross Reference: UI- FDIS -018Pre Condition:Use Case UL-A: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will fill in the center name, date or any other relevant information etc.
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
SRS-96
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 98/185
Food Department Information System
the user.
5. User will select the specific record and presses the ok button.
6. The detailed information of the gate pass for a particular day will be displayed on thescreen.
Alternate 1 Step 3:
1a) If the required record not found the system will give the information message that theno information found.
Post Condition:
15.22.2 Add Gate Pass Information
Use Case FDIS-070: Add Gate Pass Information
Basic Information
Actor: Data Entry Operator
Purpose: To add the gate pass informationCross Reference: UI- FDIS -018
Pre Condition:
Use Case UL-A: User Login
Primary Course of Events:
1. The user will access the relevant interface.
2. The user will press the add button.3. The user will fill in the all relevant information on the screen.
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 tosave data into the database.
Alternate 2a step 4:
2a) If the information entered already exists the system will give the message that thefollowing information is already into the database.
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.22.3 Update Gate Pass Information
Use Case FDIS-071: Update Gate Pass Information
Basic InformationActor: Data Entry Operator
Purpose: To update the gate pass information
Cross Reference: UI- FDIS -018
SRS-97
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 99/185
Food Department Information System
Pre Condition:
Use Case UL-A: User Login
Use Case FDIS-069: View Gate Pass Information
Primary Course of Events: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
database after user presses the ok button of the confirmation box.
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.22.4 Delete Gate Pass Information
Use Case FDIS-072: Delete Gate Pass Information
Basic InformationActor: Data Entry Operator
Purpose: To delete the gate pass information
Cross Reference: UI- FDIS -018
Pre Condition:
Use Case UL-A: User LoginUse Case FDIS-069: View Gate Pass Information
Primary Course Of Events:
1. The user will access relevant interface.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:
1a) If the user will press the cancel button of the confirmation box the information will
not be deleted from the database.
Post Condition:
SRS-98
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 100/185
Food Department Information System
15.23 Employee Personal Information:
Delete Employee Personal
Information
Add Employee Personal Information
View Employee Personal Information
Update Employee Personal
InformationData Entry
Operator (DEO)
15.23.1 View Employee Personal Information:
UC-FDIS-073: View Employee’s Personal Information
Basic Information:
Actor: Data Entry OperatorPurpose: To enter an employee’s personal information in the system.
Cross Reference: UI-FDIS-020Pre-Conditions:
Use Case UL-A: User Login
SRS-99
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 101/185
Food Department Information System
Primary Course of Events:
1) The user will access the relevant interface.
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:Actor: Data Entry Operator
Purpose: To add an employee’s personal information in the system.
Cross Reference: UI-FDIS-020
Pre-Conditions:Use Case UL-A: User Login
Primary Course of Events:1) The user will access the relevant interface.
2) The user will press the add button.
3) The user will fill in all the information regarding employee like name, father’sname, NIC card number, addresses, domicile etc.
4) The user will press save button; information will be added into database whenthe 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:
Actor: Data Entry OperatorPurpose: To Update an employee’s personal information in the system.
Cross Reference: UI-FDIS-020
Pre-Conditions:
Use Case UL-A: User LoginUC-FDIS-073: View Employee’s Personal Information
SRS-100
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 102/185
Food Department Information System
Primary Course of Events:
1) The user will access relevant interface.
2) The user will press the update button and the fields will change into edit mode.3) The user will make the required changes.
4) 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:
Post-Condition:Employee’s personal information record is present in the system.
15.23.4 Delete Employee Personal Information
UC-FDIS-076: Delete Employee’s Personal Information
Basic Information:
Actor: Data Entry Operator
Purpose: To delete an employee’s personal information in the system.
Cross References: UI-FDIS-020
Pre-Conditions:
Use Case UL-A: User Login
UC-FDIS-073: View Employee’s Personal Information
Primary Course Of Events:
1) The user will access relevant interface.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:
Employee’s personal information record is present in the system.
15.24 Employee Leave Approval / Rejection
Administrator Enter Employee's Leave Approval / Rejection
SRS-101
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 103/185
Food Department Information System
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:Use Case UL-A: User Login
Primary Course of Events:
1) The user accesses the appropriate Main Menu of the Food Department andselects 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 forleave approval / rejection.
Post-Conditions:The leave is either approved / rejected along with the remarks.
15.25 Cane Commissionerate User Login
Cane Commissioner Login 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 theuser and enable menus accordingly.
Alternate:
Post Condition:
SRS-102
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 104/185
Food Department Information System
15.26 Cane Commissionerate SCR II
Update SCR II
View SCR II
Add SCR II
Delete SCR II
Sugar Mill Data
Entry Operator
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 IICross Reference:
Pre Condition:Use Case UL-CC: User Login
Primary Course of Events:1. The user will access the relevant interface.
2. The user will fill in all the mandatory information.
3. The user will press view button.
SRS-103
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 105/185
Food Department Information System
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 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 InformationActor: Sugar Mill Data Entry Operator
Purpose: To add SCR II
Cross Reference:
Pre Condition:Use Case UL-CC: User Login
Primary Course of Events:
1. The user will access the relevant interface.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
user presses the ok button of the confirmation box.
Alternate 1
Post Condition:
15.26.3 Update Cane Commissionerate SCR II
Use Case UC-FDIS- Update SCR II
Basic Information
Actor: Sugar Mill Data Entry Operator
Purpose: To add SCR II
Cross Reference:
Pre Condition:
Use Case UL-CC: User Login
Primary Course of Events: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.
SRS-104
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 106/185
Food Department Information System
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
Post Condition:
15.26.4 Delete Cane Commissionerate SCR II
Use Case UC-FDIS- Delete SCR II
Basic Information
Actor: Sugar Mill Data Entry Operator
Purpose: To add SCR II
Cross Reference:
Pre Condition:
Use Case UL-CC: User Login
Primary Course Of Events:1) The user will access relevant interface.
2) The user will retrieve the record that he wants to delete
3) The user will press the delete button; information will be deleted (notphysically/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:
SRS-105
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 107/185
Food Department Information System
15.27 Cane Commissionerate SCR I
Add SCR I Update SCR I
View SCR I
Delete SCR I
Sugar Mill Data
Entry Operator
15.27.1 View Cane Commissionerate SCR I
Use Case UC-FDIS- View SCR I
Basic Information
Actor: Sugar Mill Data Entry Operator
Purpose: To view SCR I
Cross Reference:
Pre Condition:
Use Case UL-CC: User Login
Primary Course of Events:
SRS-106
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 108/185
Food Department Information System
1) The user will access the relevant interface.
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 InformationActor: Sugar Mill Data Entry Operator
Purpose: To add SCR I
Cross Reference:
Pre Condition:Use Case UL-CC: User Login
Primary Course of Events:
1) The user will access the relevant interface.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 againstthe field must be filled.
4) The user will press save button; information will be added into database when theuser presses the ok button of the confirmation box.
Alternate 1
Post Condition:
15.27.3 Update Cane Commissionerate SCR I
Use Case UC-FDIS- Update SCR I
Basic Information
Actor: Sugar Mill Data Entry OperatorPurpose: To add SCR I
Cross Reference:
Pre Condition:Use Case UL-CC: User Login
Primary Course of Events:
1) The user will access relevant interface.
SRS-107
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 109/185
Food Department Information System
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
database after user presses the ok button of the confirmation box.
Alternate 1Post Condition:
15.27.4 Delete Cane Commissionerate SCR I
Use Case UC-FDIS- Delete SCR I
Basic InformationActor: Sugar Mill Data Entry Operator
Purpose: To add SCR I
Cross Reference:Pre Condition:
Use Case UL-CC: User Login
Primary Course Of Events:1) The user will access relevant interface.
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 theconfirmation 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:
SRS-108
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 110/185
Food Department Information System
15.28 Send Intimation Report
Send Intimation ReportCane Commissioner
Use Case UC-FDIS- Send Intimation Report
Basic InformationActor: Cane Commissioner
Purpose: To send warning to the Sugar Mills that have not sent their SCR I or SCR II
Cross Reference:
Pre Condition:
Use Case UL-CC: User Login
Primary Course of Events:
1) The user will access the relevant interface.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 warning5) 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 reportPost Condition:
15.29 Print Intimation Report
Print Intimation ReportCane Commissioner
SRS-109
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 111/185
Food Department Information System
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:Use Case UL-CC: User Login
Primary Course of Events:1) The user will access the relevant interface.
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 II4) 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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 112/185
Food Department Information System
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 113/185
Food Department Information System
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 ManagementFood Department Government of the Punjab-Group Management
Group Management
UpdateClear Add Save ExitDeleteView
Interface Priviliges
Insert Delete Update View Print
Privileges
User Name:
Group Name Group Type [Select Group ]
Assign Password
Description: The screen will be used to assign the privileges to a particulargroup.
SRS-112
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 114/185
Food Department Information System
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 MenuFood Department Information System (FDIS)-Main Menu
Food Department Information
System
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 ReportWheat (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
Main Menu
Description: Screen will allow users to navigate through an form to add, update, delete and
view the records etc.
SRS-113
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 115/185
Food Department Information System
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 wheatpurchase and dispatch record.
SRS-114
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 116/185
Food Department Information System
16.5 Purchase Weight and Quality Certificate
Purchase Weight and Quality Certificate GUI
Interface No. UI-FDIS-003
Cross Reference Use Case. UC-FDIS-001-004
Description: Screen will be used to add, update delete and view purchasedetails and quality certificate details.
SRS-115
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 117/185
Food Department Information System
16.6 Sample Slip
Sample Slip GUI
Interface No. UI-FDIS-004
Cross Reference Use Case. UC-FDIS-045 to 048
Food Department Government of the Punjab-GP-16Food Department Government of the Punjab-GP-16
Sample Slip
Clear Add Update Delete Save ExitView
Lot No.
Type No. of Bags
Seller Grower Name Dispatching End
Recipient End Receiver NameWagon/Truck No. No. of Bags
R.R. No.
Invoice No.
R.R. Date [Select Date]
[Select District]
Invoice Date [Select Date]
Date of Sampling [Select Date] Laboratory Sent Date [Select Date]
Military Credit Note No. Classification of Bags [Select]
Godown No.
Sample Slip
District Center[Select District] [Select Center]
Description: Screen will be used to add, update delete and view the of wheatsampling details.
SRS-116
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 118/185
Food Department Information System
16.7 Bill Purchase of Wheat
Bill Purchase of Wheat GUI
Interface No. UI-FDIS-005
Cross Reference Use Case. UC-FDIS-005 to 008
Food Department Government of the Punjab-Form-2Food Department Government of the Punjab-Form-2
Seller/Grower Details
Clear Add Update Delete Save ExitView
Name Fathers Name
Address
Owner of Land
Old N.I.C. No.Village Name Chuck No.
Bill Purchase of Wheat
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 words)
(in figure)
Bank Name
District [Select District] Center [Select Center]
Consignment No.
Description: Screen will be used to add, update delete and view wheat billpurchase details.
SRS-117
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 119/185
Food Department Information System
16.8 Purchased Wheat Details
Purchased Wheat Details GUI
Interface No. UI-FDIS-006
Cross Reference Use Case. UC-FDIS-049 to 052
Description: Screen will be used to add, update delete and view the details of
Wheat Purchase in a particular PR center.
SRS-118
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 120/185
Food Department Information System
16.9 Daily Register of Un-Disbursed Bills
Daily Register of Un-Disbursed Bills GUI
Interface No. UI-FDIS-007
Cross Reference Use Case. UC-FDIS-009 to 012
Description: Screen will be used to add, update delete and view the informationabout the un-disbursed wheat bills.
SRS-119
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 121/185
Food Department Information System
16.10 Miscellaneous Item Sale Register
Miscellaneous Item Sale Register GUI
Interface No. UI-FDIS-008
Cross Reference Use Case. UC-FDIS-053 to 056
Food Department Government of the Punjab-SF-27Food Department Government of the Punjab-SF-27
Clear Add Update Delete Save ExitView
Miscellaneous Item Sale RegisterDate 20/12/2004
S.No. Things QuantityAt the
Rate OfRate
StockReceivedAmount
Loss IfAny
Details ofReceivedAmount
ChallanNo.
ChallanDate
Name ofTreasuryWhereAmount
Deposited
Reason ForLoss
Total
Auction Commission
In Case of Approval
Price After Commission
Description: Screen will be used to add, update delete and view the details of miscellaneous items sold.
SRS-120
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 122/185
Food Department Information System
16.11 Grain Paper (Godown Register)
Grain Paper (Godown Register) GUI
Interface No. UI-FDIS-009
Cross Reference Use Case. UC-FDIS-013 to 016
Description: Screen will be used to add, update delete and view the details of Grain at a certain center
SRS-121
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 123/185
Food Department Information System
16.12 Godown Card
Godown Card GUI
Interface No. UI-FDIS-010
Cross Reference Use Case. UC-FDIS-017 to 020
Description: Screen will be used to add, update delete and view the details of Godown like Mass of Godown, Date of Stock Starting, Storage Capacity,
Stock Completion Date etc.
SRS-122
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 124/185
Food Department Information System
16.13 Dispatch of Wheat from P.R. to P.R. Basis
Dispatch of Wheat from P.R. to P.R. Basis GUI
Interface No. UI-FDIS-011
Cross Reference Use Case. UC-FDIS-021 to 024
Description: Screen will be used to add, update delete and view the details of
wheat dispatched form one P.R. to another.
SRS-123
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 125/185
Food Department Information System
16.14 Stock Article Register
Stock Article Register GUI
Interface No. UI-FDIS-012
Cross Reference Use Case. UC-FDIS-029 to 032
Food Department Government of the Punjab-Stock Article RegisterFood Department Government of the Punjab-Stock Article Register
Stock Article Register
Clear Add Update Delete Save ExitView
Stock Article RegisterDate 20/12/2004
Previous BalanceArticle Name
Place Received From
[Select Article]
Date of Receiving
Quantity Received Completion Date of Storage
Receiving
[Select Date]
Reference SF-27By Order of
Date SF-27 Quantity
Release
[Select Date]
Reference SF-27By Order of
Date SF-27 Quantity
Sale
[Select Date]
Amount Deposited in Bank Bank Name
Challan No. Challan Date [Select Date]
DestinationBy Order of
Reference No. of Dispatch Report Date of Dispatching Report
Transfer
[Select Date]
Quantity
[Select Date]
Balance at the End of Month
District [Select District] Center [Select Center]
Description: Screen will be used to add, update delete and view the wheat stock
article details.
SRS-124
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 126/185
Food Department Information System
16.15 Sale of Unserviceable Stock Articles
Sale of Unserviceable Stock Articles GUI
Interface No. UI-FDIS-013
Cross Reference Use Case. UC-FDIS-057 to 060
Description: Screen will be used to add, update delete and view the information
about the unserviceable stock article.
SRS-125
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 127/185
Food Department Information System
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 RegisterFood Department Government of the Punjab-Gate In Register
Receipt and Sale of Wheat
Clear Add Update Delete Save ExitView
Receipt and Sale of WheatInstructions
No. Date
G.P. 13
DateIndigenous
Serial No Date Dispatching Center Truck/ wagon No. Wheat Quality of Bardana Comments
Date Imported Insert Quality
District [Select District] Center [Select Center]
Description: Screen will be used to add, update delete and view the Receipt and
Sale of wheat details.
SRS-126
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 128/185
Food Department Information System
16.17 Inventory of Bardana
Inventory of Bardana GUI
Interface No. UI-FDIS-015
Cross Reference Use Case. UC-FDIS-037 to 040
Food Department Government of the Punjab-Inventory of BardanaFood Department Government of the Punjab-Inventory of Bardana
Inventory of Bardana
Clear Add Update Delete Save ExitView
Inventory of Bardana
Center [Select Center]
Date 20/12/2004
Monthly Map
District
Scheme Year
[Select District]
Truck/Train(Biility No)
Date Bales
Receiving
Reference No.By Order of
Date Reference of Expenses
Local Purchase price
[Select Date]
Dispatch Report (G.P.6)Destination Station
Report No. Report Date
Destination Station
[Select Date]
Filled BagsBales
Empty Bags Date [Select Date]
[Select Moth] Related (Godown)
Bardana [Select Bardana] Month [Select Bardana]
Empty BagsBales
Filled Bags
Previous Balance
[Select Year]
20/12/2004
Filled BagsEmpty Bags
Income
By Order of and S.F. 21Sale center
Reference No. Reference Date
Sale Center
[Select Date]
Filled BagsBales
Empty Bags Rate
DateTreasure Challan No.Received Amount By
The Bank
Bank Challan
[Select Date]
By Order of and S.F. 27 Reference No.
Reference Date
Auctioned Bags
[Select Date]
Filled Bags
Bales
Empty BagsRemarks
Consignment No.
Description: Screen will be used to add, update delete and view the details of
Bardana.
SRS-127
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 129/185
Food Department Information System
16.18 Stock Receipt Information
Stock Receipt Information GUI
Interface No. UI-FDIS-016
Cross Reference Use Case. UC-FDIS-065 to 068
Food Department Government of the Punjab-GP-7Food Department Government of the Punjab-GP-7
Senders Description
Clear Add Update Delete Save ExitView
Stock Receipt InformationInstructions
Scheme Year [Select Year]
Center [Select Center] District [Select District]
Commodity Date [Select Date]
Stock Report No
Serial NoSenders
DescriptionDispatching Center
DispatchReport No.
DispatchReport Date
Quality of BardanaRailway Wagon No.
Truck No.No. Date
G.P. 13
DateIndigenous Insert QualityDate
Weight Description
[Select Center]
ExcessWeight
ShortWeight
Godown No.WhereStock Stored
Quality of Bardana/ RemarksNo. Of bags Matric Tons
Dispatched Weight
No. Of bags Matric Tons
Received Weight
No. Date
Stock Report GP-5
Date
Total (Today)
Previous Toatal
Grand Total
Consignment No.
Description: Screen will be used to add, update delete and view the details of wheat stock for a particular scheme.
SRS-128
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 130/185
Food Department Information System
16.19 Wheat Sale Information
Wheat Sale Information GUI
Interface No. UI-FDIS-017
Cross Reference Use Case. UC-FDIS-033 to 036
Description: Screen will be used to add, update delete and view the details of
wheat sale.
SRS-129
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 131/185
Food Department Information System
16.20 Gate Pass
Gate Pass GUI
Interface No. UI-FDIS-018
Cross Reference Use Case. UC-FDIS-069 to 072
Food Department Government of the Punjab-Gate PassFood Department Government of the Punjab-Gate Pass
Gate Pass
Clear Add Update Delete Save ExitView
Gate Pass
S. No.
Date 20/12/2004
Name of R.L.
P.R. Center [Select P.R.Center]
Authority No.
Permit No. Quantity
Gate Register No. Godown No.
Issuing Authority Passing Autority
Consignment No. Type of Gate Pass IGP
Description: Screen will be used to add, update delete and view gate passdetail.
SRS-130
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 132/185
Food Department Information System
16.21 Wheat Stock Register
Wheat Stock Register GUI
Interface No. UI-FDIS-019
Cross Reference Use Case. UC-FDIS-025 to 028
Food Department Government of the Punjab-SR-9Food Department Government of the Punjab-SR-9
Clear Add Update Delete Save ExitView
Wheat Stock RegisterDate 20/12 /2004
To Indicate Consolidated Position Of Wheat Stock Fall Schemes in Tons
S. No. Date
30/12/2004
Bags Tons Bags Tons Bags Tons Bags Tons Bags Tons
Indigenous Imported ImportedIndigenous
Bags Tons
IndigenousImported
Closing Balance Receipt Total
Scheme YearDistrict [Select District] P.R. Center [Select P.R.Center] 20/12/2004
GPS Number
Bags TonsIndigenous Imported
Closing BalanceTotal Issues
Indigenous Imported Indigenous Imported Indigenous ImportedLocal Sales Dispatches Total
Description: Screen will be used to add, update delete and view the details of wheat stock like Closing Balance, Receipt, Total Issues etc.
SRS-131
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 133/185
Food Department Information System
16.22 Wheat Stock Register
Wheat Stock Register GUI
Interface No. UI-FDIS-019 A
Cross Reference Use Case. UC-FDIS-017A to 019A
Food Department Government of the Punjab-GP-6Food Department Government of the Punjab-GP-6
Dispatching End
Clear Add Update Delete Save ExitView
Dispatch Report
Dispatching Center [Select Center]
Date 20/12/2004
Date of Dispatch [Select Date]
District
Scheme Year
[Select District]
Instructions
[Select Year]
Sr. No.
/Directorate Office
Reference District/Regional Lot No. Godown No. Dispatching Station T ruck Invoice No.
Wagon No.- Truck No.
Bags Weight
Dispatch Bags Weight in GP-13 Railway Fare Remarks
Consignment No.
Description: Screen will be used to add, update delete and view the details of
stock dispatched daily through trucks.
SRS-132
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 134/185
Food Department Information System
16.23 Employee Personal Information
Employee Personal Information
Interface No. UI-FDIS-020
Cross Reference Use Case. UC-FDIS-073 to 076
Description: This screen is used to add, view, update and delete the personalinformation of the employee by using relevant buttons.
SRS-133
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 135/185
Food Department Information System
16.24 Employee Leave Approval / Rejection
Employee Leave Approval / Rejection
Interface No. UI-FDIS-021
Cross Reference Use Case. UC-FDIS-077
Food Department Government of the Punjab - HRMSFood Department Government of the Punjab - HRMS
Leave Approval / Rejection
ID :
Name :
Post / Designation :FD001118
Leave From :
Leave Type :
Reason :
Address (during Leave) :
Leave Information
To : Days :
Phones :
Remaining Leaves :
Remarks : Rejected due to ISO audit coming in the next week project evaluations required urgently. Hemay apply for leave after a week.
Save Close
5
Casual
Islamabad
042-4353456, 0300-23453533
House No. 11, F 10/2,
Work at Home
2
Muhammad Kaeem
Additional Director Food
11/11/2003 15/11/2003
Description: This screen is used by the leave-granting officer to either approve / reject the leaverequest of an employee along with the remarks.
SRS-134
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 136/185
Food Department Information System
16.25 HRMS Main Menu
HRMS Main Menu
Interface No. UI-FDIS-026
Cross Reference Use Case.
Food Department Information System (FDIS)-Main Menu HRMISFood Department Information System (FDIS)-Main Menu HRMIS
HRMSMain Menu
Personal Information Leave Approval / Rejection
Description: This screen is used to access the HRMS module.
SRS-135
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 137/185
Food Department Information System
16.26 Cane Commissioner Login
HRMS Main Menu
Interface No. UI-FDIS-027
Cross Reference Use Case.
Cane Commissioner ModuleCane Commissioner Module
User Name
Password
Cane Commissioner
**************
Sign In Cancel
Remember PasswordForget Password
Description: This screen is used to access Cane Commissioner module.
SRS-136
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 138/185
Food Department Information System
16.27 Cane Commissioner SCR II
HRMS Main Menu
Interface No. UI-FDIS-028
Cross Reference Use Case.
Description: This screen is used to enter data in SCR II.
SRS-137
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 139/185
Food Department Information System
16.28 Cane Commissioner SCR I
HRMS Main Menu
Interface No. UI-FDIS-029
Cross Reference Use Case.
Description: This screen is used to enter data in SCR I.
SRS-138
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 140/185
Food Department Information System
16.29 Cane Commissioner Intimation Report
HRMS Main Menu
Interface No. UI-FDIS-030
Cross Reference Use Case.
Description: This screen is used to send Intimation Report to the Sugar Mills.
SRS-139
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 141/185
Food Department Information System
17. Reports
17.1 Receipt and Sale of Wheat Report (Date Wise)
Receipt and Sale of Wheat Report (Date Wise)
Government of PunjabFood Department
Receipt and Sale of Wheat Report(Date Wise)
Sale Center: _______________________________
S. No. Date Dispatching Center
Receipt Center: ____________________________
Total
Truck/
Wagon No
Indigenous
WheatImported
Wheat
SRS-140
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 142/185
Food Department Information System
17.2 Receipt and Sale of Wheat Report (Center Wise)
Receipt and Sale of Wheat Report (Center Wise)
SRS-141
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 143/185
Food Department Information System
17.3 Grower / Agency Report
Grower / Agency Report
SRS-142
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 144/185
Food Department Information System
17.4 Purchase Bill Report (Center Wise)
Purchase Bill Report (Center Wise)
SRS-143
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 145/185
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 146/185
Food Department Information System
17.6 Undisbursed Bills Report
Un-Disbursed Bills Report
Government of PunjabFood Department
Un-Disbursed Bills Report
S.No.No. of Unpaid
Purchase Bill
Center Incharge
NameAmount
(Rs)Name of Payee
Actual Date
of Payment
by BankDate of Bill
Total
Date: _______________________________
SRS-145
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 147/185
Food Department Information System
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 148/185
Food Department Information System
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 149/185
Food Department Information System
17.9 Wheat Stock Register Report
Wheat Stock Register Report
SRS-148
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 150/185
Food Department Information System
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
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 151/185
Food Department Information System
17.11 Employee Education Qualification
Employee Education Qualification
Government of PunjabFood Department
Educational Qualification
S. No. Qualification Year Institution Subjects
MSc Public Health 1998 Punjab University Nutrition1
SRS-150
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 152/185
Food Department Information System
17.12 Employee Language Proficiency
Employee Language Proficiency
Government of Punjab
Food Department
Language Proficiency
S. No. Language Read Write Speak
English
ExcellentUrdu Excellent Excellent
Excellent Excellent Excellent
1
2
SRS-151
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 153/185
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 154/185
Food Department Information System
17.14 Employee Posting History
Employee Posting History
Government of PunjabFood Department
Posting History
Sr. No Joining Date Department Designation BPS
11/11/2003 Food Department DDF D.G Khan XYZ1
SRS-153
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 155/185
Food Department Information System
17.15 Employee Inquiry History / Annual Confidential Report
Employee Inquiry History / Annual Confidential Report
Government of PunjabFood Department
Inquiry History / Annual Confidential Report (ACR)
Sr. No Inquiry Date Department Designation Inquiry Officier
11/11/2003 Food Department DDF D.G Khan XYZ1
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
Remarks
He was found clean and no
action was taken against him.
SRS-154
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 156/185
Food Department Information System
18. Appendix A
Glossary of Terms
Term DescriptionFDIS 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 CardIGP Inward Gate Pass
OGP Outward Gate Pass
P&D Planning and Development
SRS-155
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 157/185
Food Department Information System
19. Appendix B
19.1 Sample Scanned Documents
19.1.1 Form SF-26 (Page 1)
Form SF-26 (Page 1)
SRS-156
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 158/185
Food Department Information System
19.1.2 Form SF-26 (Page 2)
Form SF-26 (Page 2)
SRS-157
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 159/185
Food Department Information System
19.1.3 Form 2 (Page 1)
Form 2 (Page 1)
SRS-158
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 160/185
Food Department Information System
19.1.4 Form 2 (Page 2)
Form 2 (Page 2)
SRS-159
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 161/185
Food Department Information System
19.1.5 Form GP-6
Form GP-6
SRS-160
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 162/185
Food Department Information System
19.1.6 District Inventory of Bardana Filled
District Inventory of Bardana Filled
SRS-161
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 163/185
Food Department Information System
19.1.7 District Inventory of Bardana Empty
District Inventory of Bardana Empty
SRS-162
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 164/185
Food Department Information System
19.1.8 Stock Article Register
Stock Article Register
SRS-163
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 165/185
Food Department Information System
19.1.9 Stock Ledger
Stock Ledger
SRS-164
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 166/185
Food Department Information System
19.1.10 Sample Slip
Sample Slip
SRS-165
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 167/185
Food Department Information System
19.1.11 Form 3
Form 3
SRS-166
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 168/185
Food Department Information System
19.1.12 Form SF-24
Form SF-24
SRS-167
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 169/185
Food Department Information System
19.1.13 Form SF-28
Form SF-28
SRS-168
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 170/185
Food Department Information System
19.1.14 Form GP-3
Form GP-3
SRS-169
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 171/185
Food Department Information System
19.1.15 Form GP-5
Form GP-5
SRS-170
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 172/185
Food Department Information System
19.1.16 Form GP-7
Form GP-7
SRS-171
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 173/185
Food Department Information System
19.1.17 Form GP-8
Form GP-8
SRS-172
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 174/185
Food Department Information System
19.1.18 Form GP-13 (Page 1)
Form GP-13 (Page 1)
SRS-173
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 175/185
Food Department Information System
19.1.19 Form GP-13 (Page 2)
Form GP-13 (Page 2)
SRS-174
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 176/185
Food Department Information System
19.1.20 Gate Pass
Gate Pass
SRS-175
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 177/185
Food Department Information System
19.1.21 Gate Register PR Center
Gate Register PR Center
SRS-176
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 178/185
Food Department Information System
19.1.22 Purchase and Dispatch Information Form
Purchase and Dispatch Information Form
SRS-177
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 179/185
Food Department Information System
19.1.23 Wheat Purchase
Wheat Purchase
SRS-178
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 180/185
Food Department Information System
19.1.24 Form SF-21
Form SF-21
SRS-179
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 181/185
Food Department Information System
19.1.25 Stock Articles
Stock Articles
SRS-180
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 182/185
Food Department Information System
19.1.26 Form SF-27
Form SF-27
SRS-181
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 183/185
Food Department Information System
19.1.27 Form SCR I
Form SCR I
SRS-182
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 184/185
Food Department Information System
19.1.28 Form SCR II
Form SCR II
SRS-183
8/8/2019 SRS Food Department 19-1-05
http://slidepdf.com/reader/full/srs-food-department-19-1-05 185/185
Food Department Information System