Table of Contents (SRS

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

Food Department Information System

1.

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

1.1 Intended Audience and Reading Suggestions
Food Department Information Technology Department Bidding Contractor

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

SRS-1

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. It issues wheat to the mills at subsidized rates to ensure adequate supplies and stable price of flour throughout the year. It also supplies wheat to other provinces and agencies. Food Department is also responsible for monitoring and co-ordination of sugarcane sector with reference to payment of dues of sugarcane growers and sugarcane cess fund. A Cane Commissioner heads the Provincial Committee whose functions include the appointment of cess fund among districts and releases as well as selection of development schemes and their execution.

3.

Organizational Structure
Food Department is headed by Secretary Food. The Directorate Food has 8 divisions i.e., Gujranwala, Rawalpindi, Lahore, Faisalabad, Sargodha, Bahawalpur, D.G Khan and Multan working under him. Each division is headed by Deputy Director. Each district has DFCs (District Food Controllers). Each DFC has a Storage Office working under him.

There are four Deputy Directors in the Food Directorate with each being incharge of one section there. These four sections are as follows: • • • Purchase deals with wheat procurement and its release. The wheat procurement and its release are discussed in detail later in the document. General deals with the supplies for procurement of wheat, weighing scale, PP bags, jute bags, pesticides, Polythene Sheets etc Administration deals with human resource management of the Food Department staff. It keeps a complete record of postings, transfers, promotions, ACRs, departmental proceedings, criminal actions and inquiries against employees of the Food Department staff of the entire province.

SRS-2

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.

Food Department Information System (FDIS) Organizational Chart
Secretary Food

Cane Commissioner

Deputy Secretary-3

Director Food

Deputy Director (Directorate-4)

Deputy Director (Field-8)

Addl. Director

Asstt. Director (Directorate-4)

Asstt. Director (Field-8)

ACI (10)

DFC (Field-31)

FDIS : Food Department Information System

AFC

Food grains Insp.

SRS-3

Food Department Information System

The Cane Commissionerate
The Provincial Committee for the monitoring of sugar cane sector includes the following members: • • • • • • • • Cane Commissioner DCO-District concerned Chairman PSMA/nominee Member (Tech) P&D Rep of FD Rep of C&W Rep of growers Any other person co-opted by Chairman (Chairman) (Member) (Member) (Member) (Member) (Member) (Member) (Member)

The composition of the District Committee for the monitoring of sugar cane sector is as follows: • • • • • • • • • • • DCO (Chairman) EDO (Works & Services) (Member / Secy) EDO (Agriculture) (Member) EDO (F&P) (Member) Deputy Director Food (Member) DFC (Member) 2 Reps of sugar mills (Member) 2 Reps of growers in area of each sugar mills (Member) Rep of Zila Nazim (Member) Rep of P&D (Member) Any other person co-opted by Chairman (Member)

The District Committees formulate and initiate development schemes and submit its recommendations to Provincial Committee for final approval.

4.

Vision Statement
The basic vision behind the ‘Computerization of Food Department’ Project is to develop an IT enabled environment at the Food Department to ease out the procurement and release operations of wheat and to facilitate the Cane Commissionerate in acquiring the sugarcane reports directly from the sugarcane mill owners. This includes developing an inventory management information system for tracking of all operational activities of the department from procurement to release of wheat to prevent fraud and forgery as well as developing Financial Management System for release of payments to the sellers/farmers. This will also enable the food department to do statistical analysis for increasing the annual wheat production. SRS-4

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 any information for decision support system. The central database will be updated with each truck routing especially for import of wheat transaction, hence the Food Department to track down the exact position of the trucks and its delivery time. The project also includes developing an online facility for the sugarcane mill owners to submit their reports to the Cane Commissionrate. The IT Infrastructure will be built in all the offices at 34 Districts and 8 Regions.

6.

Existing System
The existing processes at the Food Department are completely manual. The paper forms being currently used for wheat procurement, releases etc are in Urdu language. They have about eight computers in the Directorate whose usage is basically restricted for data typing, compilation of data, accounts and stock article. At present, there is no Local Area Network (LAN) in the Food Department. Currently, there is no online inter-division communication and the officials have to rely on faxes for this purpose. e.g. if the wheat is being dispatched from Karachi, they will first inform the Directorate office in Lahore which in turn is responsible for informing the corresponding district office. Figures regarding the sale of wheat are also given to the regions by the districts and the regions forwards them to the Directorate via telephone or fax. The main functions of the Food Department comprises of: • • • • • Setting the targets for wheat procurement Procurement of wheat Dispatch of wheat from Purchase point or PR Storage of wheat from Other Divisions Issuance/Sale of Wheat to the authorized Flour Mills

The Food Directorate sets two types of targets. One is procurement of the wheat for the province. The other for the mill as to how much quantity will be issued. They are both briefly discussed below: The directorate sets a target based on historical data as to how much wheat will be required in the province for the next year. This target is also in consideration of the fact that the free market starts to run dry after a few months and then the government needs to supply the Wheat to the mills at a lower rate in order to curtail the rise in

SRS-5

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. After setting the targets for wheat procurement. The bank basically matches the statements to check the payments that it has made to the sellers. This target is set on milling capacity per day. Government of the Punjab is unable to meet the target that it has set. the Food Department may need to set up some temporary centers known as Flag Centers. Once a district wise target has been set it is forwarded to the related DFC. The wheat procurement season is from April to June and wheat is released to Flour Mills from October onwards.Food Department Information System wheat prices. The Flour Mills deposits the required amount along with the authorized letter to the bank. The mills set targets based on their milling capacity. it may need to import wheat. The Stock register is maintained by the staff at the center and prints consolidated statement (Form 3) and sends it to banks. 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. However. Sometimes. the Food Department sets up approximately 400-450 centers all across the province. The Purchase centers are made and their targets are set fixed by the Food Department. The DFC then forwards this information to the Directorate who then arranges funds to be transferred to the respective bank branches. 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. In order to set the targets the directorate in consultation with the Agriculture Department estimates as to how much wheat can be acquired from each district. 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. He is at liberty to choose the bank based on the past history and willingness of the bank in general. In case of a district facing any shortage of the wheat. He also identifies the bank that will support the center in making payments. Some mills will have more target than the other simply because it can mill more wheat than the others. The related DFC then sets up the targets for each center that he will establish. the wheat stocks in the surplus districts are shifted/transported to the deficit districts by the following means: • Pakistan Railways • Through NLC Vehicles • Private Transport Contractor (through tenders) SRS-6 . In that case. Depending upon the requirement. The Challan Form for buying the wheat from the Food Department also As the wheat is sold to the flourmills on the subsidized rates. This target can be increased or decreased according to the season or other factors.

Establishment Charges ix. the following extra expenditure is incurred on the day-to-day requirements in the wheat operation. Taxes & Duties v. Transportation Charges vi.Food Department Information System In addition to the expenditure incurred on purchase of wheat. Bank Commission iii. i. 2. Handling Charges vii. Godown Expenses viii. Delivery charges iv. Purchase of gunny bags ii. Mark Up Food Department Directorate Wise Segregation Food Directorate All the 8 Divisions reports to the Directorate Division Storage Center 1 Flag Center 1 Storage Center 5 Flag Center 10 1 to 4 Districts Storage Center 1 Flag Center 1 Storage Center 5 Flag Center 10 District 1 1 to 8 Divisions District 4 Division 1 to 4 District Storage Center 1 Flag Center 1 Storage Center 5 Flag Center 10 Storage Center 1 Flag Center 1 Storage Center 5 Flag Center 10 District 1 District 4 The Cane Commissioner administers two acts: 1. Sugar Factories Control Act 1950 and its rules (1950) Finance Act 1964 and the Sugar Cane Development Rules 1964 SRS-7 .

The amount deposited in the treasury is verified by the District Food Controller and District Account Officer. SRS-8 . However this was not the case in the past when a sugar cane mill owner could only purchase sugar cane from within his own zone. These reports are to be submitted fortnightly as well as on a daily basis. 5. There are about 39 sugar mills operating within Punjab covering 19 districts. Constitution of District Committee Each Sugar Mill operating within Punjab is required to submit two sugar cane reports (SCR I & SCR II). 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. The reports/statements at present are being submitted directly to the office of the Cane Commissioner through fax.Food Department Information System The Salient Features of the Punjab Sugar Factories Control Rules 1950 are as follows: 1. 4. A sugar cane mill owner can purchase sugar cane from any district. The cess collected by the sugar mills (50% of cess comes from the grower and the other 50% from the mill owner). 3. 12. 10. The Salient Features of the Punjab Finance Act 1964 are as follows: 1. 9. 6. 7. Constitution of Provincial Committee 14. 3. Levy of Sugarcane (Dev) Cess Equal sharing by mill and grower Collection and payment by the mills Purpose/utilization of cess Exemption of cess Time and manner of payment Determination of correct deposit of cess by Cane Commissioner Penalty by Cane Commissioner not exceeding the amount due Inspection / audit of accounts Constitution of sugarcane (dev) fund Fund to be operated by the DCOs Appointment of funds (district/mill wise) after deducting 2% collection charges 13. 8. 11. 6. In case of non compliance. 4. 5. the Cane Commissioner can hold the sugar cane mills liable to pay a penalty. Examination of weighbridges and purchasing centers Intimation regarding starting and termination of crushing Elimination of middleman Prohibition of price below minimum price Payments to growers within 15 days & imposition of interest @ 11% Cane Commissioner sole interpreter of these rules. 2. 2.

the targets are handed over to the DFCs.e. For this he is then paid the amount that the transport contractor would have received. Farmer fills his wheat in these bags and takes them to the purchase point i.. 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). 6. Flag Center or the Provincial Reserve (PR). Wheat Seller (Farmer) brings the wheat that he wants to sell to the centre incharge and tells him about the quantity of wheat that he has to sell. 2. Unsatisfactory wheat is rejected and bardana is also taken back. Cash Credit Limit on commodity is sanctioned by the Federal Government on the basis of value of stocks expected to be held in the Provincial Reserve to facilitate the accounting system. A copy of GP 16 is sent to the laboratory for analysis along with the sample and one copy is sent to the DFC. Each DFC’s further sets the target for each purchase centre.Food Department Information System 6. 1. The above operation of procurement is made through State Trading in wheat which is financed by short term loan advances obtained from the Commercial Banks on the cash credit commodity. Centre Incharge determines the number of bardana that needs to be issued to the farmer.1 Wheat Procurement Procurement of wheat is made according to the targets fixed by the Federal Government/Punjab Government for which necessary arrangements are made by the Punjab Food Department. After setting the wheat procurement targets. The Office Incharge at the center accepts the wheat if he thinks it is according to the standards prescribed by law. 7. the seller may be asked to clean the wheat and present it again. 4. temporary flag stations as per requirement required are set up in addition to the permanent centers. The seller himself is responsible for unloading and stacking of the wheat. The borrowed amounts are re-paid to the banks along with mark-up. The Incharge officer takes a sample of the wheat to check out its quality of wheat and prepares GP 16. 5. 3. For Procurement of wheat. If the wheat needs cleaning. SRS-9 .

The transporting party brings this confirmation. permission of the DFC is required. 11. then it needs to be transported to the PR. Incase of delay of month. 14. 15. At the centre GP-5 also known as the Stock Report is also prepared which contains the sale and purchase details 16. 13. If the seller does not draw amount from the bank within a week then he has to draw permission for extension of payment date. 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. then the receiving PR will issue his bill after an acknowledgement of GP-13. 17. If the wheat is accepted. If the payment of wheat is of less than 50 bags then the bank may pay in cash. The Incharge Officer also prepares GP 6. Each Bill Form -2 is entered in Form-3 and copy of each bill is attached. Copies of the GP-4 are then sent to the divisional office from where the information is forwarded to the directorate for further compilation. 10. 12.Food Department Information System 8. 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. which is issued for each lot purchased. 18. Form-2 acts like a payee’s account cheque. then incharge issues a bill on Form-2. The district office then prepares Form 9 based on all the GP 4’s received from the centers. The Incharge Officer at the end of the day prepares Form 4 which contains all the Bill details which are cleared along with un-disbursed bills during the day which is forwarded to the District Office. If the seller transports the wheat to the PR. SRS-10 . A separate GP 6 is prepared for each different destination PR. 9. The farmer submits his bill at the prescribed bank for collection. copies of which are forwarded to the District Office and to the PR to which wheat is dispatched (incase the wheat is storedat a remote PR). The Incharge center fills out GP-13 and sends it along with the wheat to the PR. If the wheat is received at the flag center.

1.Food Department Information System Wheat Procurement Process Flow Seller/Grower 1. All the trucks coming in carries GP-13 where as the last truck will carry GP-6. which is a center wise consolidated report. The PR Incharge fills in the GP-7. and after checking the wheat is stored in a PR or a Flag center Bank 6. others PR’s as well as imported wheat.2 Receipt at PR The PR can receive wheat from the flag centers. The Incoming wheat is accompanied by a GP-13. The wheat has to be returned by the seller/ grower with in 7 days of issuance of 2 bardana Requests for bardana against 1 CDR or personal surety Flag Center Provincial Reserve (PR) (Storage Center) Bill for payment is forwarded 4 to bank where grower/seller receives payment $ 3 Checking for weight and quality of food. Regardless of where the wheat is coming from. GP-13 contains the information regarding the incoming goods. Every center fills in its own GP-7. SRS-11 . GP-6 and GP-7 are compared to check what was dispatched and what was received. 2. A copy of this is sent with the stock report. following is the procedure that is followed by the PR In charge. related to wheat. This is also consolidated from GP 13. The receiving PR In charge enters the information about the incoming wheat in the incoming register. Issue bardana 2.

This will facilitate the contractor to easily understand the current system and will also help in understanding the requirements. A GP-8. which describes the stock status of the day and hands it over to the Regional Accounts Office. 6. 7. is prepared separately for each godown. A process flow / workflow which clearly shows the whole process is as below.Food Department Information System 3. Any transit loss will be recovered from the transport. The other copy of GP-5 is given to the respective DFC. The incoming GP-13 is counter filled as acknowledgement for the sending party. The whole process ‘Receipt at PR’ is graphically represented below: SRS-12 . 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. Recovered transit loss is when the number of bags received is less than the ones sent. This filled GP-13 is handed over to the transporter for him to return at the starting point. PR Incharge prepares a GP-5. GP-8 and GP-5 are also compared with each other. 4. as their totals should tally. which is a goodown wise report. The wheat is then unloaded and stacked in the godown. At the end of the day.

The PR prepares GP-13 . SRS-13 . informs the transporter about the quantity of wheat that need to be transported and schedule. All the trucks carry GP13. 3. 4.3 Dispatch of wheat from PR & Flag Center If some region is facing a deficit in wheat. The PR also prepares GP-6 which is sent with the last truck and copies of which are also forwarded to the District Office and to the PR to which wheat is dispatched. 1. it requests the Food Directorate for additional supplies. 2. The DFC on receiving the work order from the Directorate. which is sent with the wheat.Food Department Information System Receipt At Provincial Reserve Process Flow Flag Center Provincial Reserve (PR) (Storage Center) Wheat received for storage from other PR or flag center to another PR center 1 Provincial Reserve (Storage Center) 2 Daily consolidated reports of District offices are sent to the Divisional office 3 Daily consolidated reports of flag center and storage center are dispatched to the District offices Daily consolidated reports of Divisional offices are sent to the Directorate 6. The Directorate may ask other PR where wheat is in surplus to send it to other PR in order to meet the shortfall. The Food Directorate allocates and award contract to the firm which transports wheat.

The form is then forwarded to the district office. If the godown is being cleared/ emptied. 6.e. Wheat Dispatch Process Flow 1 DFC 2 Food Directorate Allocates and awards contract Contractor Proposes Surplus stock to be transported 3 DFC specify quantity of wheat to dispatch 4 Approaches DFC for Contract signing Storage Center (PR or Flag Center) 5 Loading of stocks 6 7 Sends acknowledgement to the Provincial Reserve center or the Flag Center through contractor Destination SRS-14 . At the end of the day. SF-26 is prepared.Food Department Information System 5. Godown card i.. 7. GP-9 is also prepared which is replica of GP-8. PR Incharge prepares GP-5 (Stock Report).

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

policy Flour Mill 3 Deposits payments at banks as per the rates specified DFC Bank challan copy is send to the PR or Flag center to issue 6 wheat Storage Center (PR or Flag Center) 7 Issue wheat to flour Mills SRS-16 .Food Department Information System W Sale to Flour Mills Process Flow heat Request for the issuance of the wheat as per the allotted quota 1 4 Submits challan copy to DFC 5 Verifies amount deposited through bank scroll 2 Allows release of wheat as per Gov.

view and write privileges) of each interface. Operators 7. SRS-17 . Report generation Database backup Change tracking User Management ACRs/Inquiry Reports should be in encrypted format Read privilege for user management interfaces Report generation Senior Officials Officials restricted Higher officials of Food Department (level-3) Officials of lower grades of Food Department (level-2) Data entry for documents (level-1) Read privileges for authorized interfaces. Full control (Read. He is responsible for creating groups / users. 7. and deleting workflows and archival to CD or magnetic tapes. creating. delete. giving them access rights. editing. the anticipated users of the software and the known constraints. 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.1 User Characteristics and Roles Group Administrator Description Administrat ors of the software (level-4) Access Rights The administrator has full control over the system. Application should be compatible with Internet Explorer version 6 or higher.2 Operating Environment Microsoft Windows XP Professional will be the standard operating system for the staff whereas server operating system would be recommended by the software house according to the given solution. Report generating facilities Write privileges to a few restricted interfaces for quality assurance Read privileges for User Management interfaces. assumptions and dependencies.Food Department Information System 7. Read/write (as per the group/security policy) for all interfaces. modifying groups / users.

3 Hardware Some of the hardware for the project has been purchased. The hardware yet to be purchased includes the Application and Data base server.4 Input to ICDS As part of the Punjab Portal Project. The Intel based Pentium IV workstations. 7. Director. UPS. etc Retrieve Cane Commissioner SRS-18 Store .5 Data Flow Diagram Data Flow Diagram All Divisions General Public Retrieve Re tri ev e Retrieve All PR Centers Store Store Food Department Information System (FDIS) Retrieve Higher Staff Store Higher Staff includes the Secretary. 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). ICDS will require input from FDIS. 7. Deputy Director. printers have been bought. an Integrated Central Depository System (ICDS) is to be setup for inter-department information sharing.Food Department Information System 7.

Food Department Information System 8. High Level System Architecture High Level Network Architecture Diagram Food Directorate Router ISDN/DSL ISDN/DSL Information Technology Department (ITD) Cane Commissionrate al Di Up ISDN/D ia l Up Service Provider Dial Up Storage Center 1 to 8D ivis ion s Application Server Sarghoda Division SRS-19 ISDN /Dial Up Application Server Rawalpindi Division .

Assumptions and Dependencies The Contractor is required to lay out a plan and strategy for interfacing the software with ICDS so that extractions cleaning and transformation operations could be performed by the contractor engaged for setting up the ICDS.g. 9. 9. This information would be of primary importance and the contractor will analyze this site contents and existing computerized data after careful study and planning.4 Food Department Website The contractor will re-design a new website incorporating all the features defined for the website.gov. The Contractor would also be required to distinguish and identify the public and confidential data. such as estimation of production of annual wheat production.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.) as well as through dialup modem connections with the storage houses. All the information would be extracted from the static site and the existing application will become part of the FDIS.punjab. FDIS should also allow data to be exported from one office to the other manually (e. SRS-20 .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. www. ISDN connections will be setup between the Directorate and the Regions which will facilitate fast communications. It is assumed that the data transfer process can be automated once the communication link is established. It is also assumed that the Bidder would have thoroughly read the “Law of Fire Arms and Explosives” before submitting the proposal. 9. 9.pk/food. FDIS should be flexible enough to allow the transfer of data from one office to the other.3 Data Collection from Existing Website The contractor will collect the data for the development of FDIS from the existing website. figures have to be transferred from the Agriculture Department to the Food Department.1 Integration with ICDS 9.Food Department Information System 9. When Punjab Intranet has been successfully deployed all of the Dial Ups will be terminated and this cost will be diverted towards establishing a connection between local storage center and the local terminal point of Punjab Intranet.g Agriculture Department. on a compact disc etc. For certain tasks.

the Cane Commissionerate module should be made in such a manner that it can be independently deployed anywhere. We may assume that it may be declared as an autonomous body at some later stage.11 Cane Commissionerate Module The Role of Cane Commissionerate role is not yet clearly defined for the past few years. In order to run the FDIS. SRS-21 . 9. It is envisioned that this project will form the basis for fully automated Government offices and will lead to paperless environment.12 Seller/Grower Payments in Future The system must provide the facility to have an interface with the allocated banks so that as soon as the payments are made to the seller/grower. it should also be updated in the FDIS. 9. 9. 9.8 Deployment & Installation The installation and deployment of the system in various offices of the Food Department cannot start before the implementation of internal Local Area Network within those offices. 9. This will be really beneficial for performing data entry at the Flag Centers. 9. which are set on temporal basis. the Food Department has shortage of technical staff. it is dependent on the new manpower hired that will need training. The current HRMS will be later integrated with the Office Automation project. The Information Technology Department is also implementing an “Office Automation” Project.6 Integration of HRM with Office Automation A Human Resource Module is being developed for FDIS.9 Human Resource Potential Currently.10 Wireless Connectivity in Future The Contractor should also keep into consideration the fact that in near future the wireless connectivity will be available everywhere in Punjab.7 Integration with Lahore WAN This project is closely linked with Lahore WAN as the data collected from different storage units will be made available to other departments through it.Food Department Information System 9. The contractor should keep a provision for this in the system. In any case.

7. 8. The application should be highly reliable and robust providing restrictions at all the access level. senior officials and even not to the Administrator. 9. 3. database availability. Design and Implementation Constraints 1. Data and systems would be at risk. alert notifications to administrators and system pop ups. SRS-22 . 4. The system should be able to retrieve data quickly and efficiently. Therefore. security. virus protection.. proper network support. so firm security against such threats are solicited. 5. The system should facilitate the users to search data with minimal response time. anywhere via the desktop or laptop. Unbreakable Security is required.e. 6. The contractor must keep the following provision in its design for future: • Efficient access to central database through WAP. It should be a collaborated system highly available and reliable for continuous Government operation offering Real-Time availability when necessary. 11. 10. The project should be written in an Object-Oriented language that allows for easy extension and maintenance of code. application crash and servers availability should be reported using a log. System should be secured by default. ACRs etc related to any employee should only be accessible to the high level users i. Errors occurring due to any reasons including network connectivity. • Wireless networking between districts & divisions as well as Food Directorate • Forecasting system to support Government pf Punjab’s planning activities. vulnerable to ever-present security breaches such as virus attacks and information theft. It is assumed that all the employees of the Food Department will have access to the system. quick response time and should be highly available to achieve the required reliability. Similarly all the other users of the system should only be able use the system as per their access levels. Likewise data should be updated and deleted by the Administrator. The system should be accessible anytime. 2. Languages like Java or Microsoft dot net platform may be used for high maintainability. Automatic error reporting is required.Food Department Information System 10. the system performance should not be degraded with increase in number of users.

Proposed System Workflow al Di up Di al up LA N SRS-23 .Food Department Information System 11.

In case of non compliance issue warnings to Sugar Mills.1 Proposed System for Cane Commissionerate 4. Sugar Mills (39) SRS-24 . Acknowledgement of sugar cane report is displayed.Food Department Information System 11. 1. Exchange latest Reports Cane Commissionrate Food Department 3. Send sugar cane Reports to Cane Commissionrate (Daily Basis Reports and Fortnightly Reports) 2.

The application to be developed must be compatible with the operating hardware and software purchased for this purpose.g. 11. This approach lays out the importance of particular activities to be carried out to ensure the quality of the automated system. Ability to provide login and logout facility to multiple concurrent users (this will be a multi user application). A user group is assigned privileges of reading.1 Application Features 1. and SMTP. 12. Web site must be built on a multi-tiered. 4. 9. Instructions for receiving help and for quitting from the system should appear on every screen. 10. This also provides the rudimentary schedule of activities with minimal set of deliverables. property information entry screen etc. 5. The system shall be available via local area networks as well as from the Internet. 3. The system should provide prompts to available commands or actions on every screen. FTP. 13. edit and view different user groups. System Features 12. including Telnet. Ability to create. writing application resources. user management screen. The system should be easy to use for first-time. 8. e. Software should support both old and new NIC number formats 6. Ability to authenticate and provide confined view to the user as per permitted privileges. SRS-25 . distributed architecture.Food Department Information System 12. or infrequent users. Must incorporate the latest in technological advances including object-oriented design. and transaction-based processing. event-driven programming design. The software developer will use the process-oriented approach as the basis for project planning. 14. 2. The proposed system shall include full TCP/IP support and capability. 7. Ability to create a new system user in an already created group and then to edit and view the user information. Software should have support to accept historical data. novice.

2. The system must have the facility to distinguish between the 20th and 21st century.3 Operations. authorized members activity log mechanism must be incorporated in the system..2 Performance Criteria 1.1. SRS-26 . The system should have the ability of intelli-sense in which e. When necessary.4 System Monitoring and Logging 1. which already persist in the database. 16. This trail ensures all information in the system is secure and can be used for accountability and proper monitoring of the system. 11.1.1. if an id of an employee is used in a form then all the related fields on the form. 11. 11. System should perform optimally during normal and peak workloads. Background processes. 2. should populate automatically. For the purpose of trouble shooting and performance analysis.1 Dynamic Report Engine The engine should facilitate the user in modifying the layout of already created reports according to requirements. The system must be designed for less than 1% downtime at normal load.g. 3. data integrity checking. data loading. This feature generates a comprehensive log of all actions undertaken by various users. added or deleted any data within any part of the system. full data recovery must be made possible 3. The system must be able to identify and reveal which individual has modified. The system should have an emergency / contingency module that captures any data input during a period of possible LAN failure and which permits the upload of such data to the central database once the LAN becomes operational. 11. data backup operations etc should not take a toll on the performance of the system. Backup and Recovery 1.1. Mechanisms and techniques must be devised to guard against unintentional loss of data. reporting. 2.Food Department Information System 15.

Food Department Information System 11. 5. FDIS also requires some reports and other related information online. delete. Access level of each user can be defined at the time of creating the user. Interface level security • Read Permission • Write Permission • Print Permission • Delete Permission • View Permission Group level security • Read Permission • Write Permission • Print Permission SRS-27 . Few of them are: User level security • User name • Encrypted Password • Read Permission • Write Permission • Distribute Permission • Delete Permission • Print Permission • Supervise Permission 11.) 2.7 Online Accessibility Internal work of FDIS will be performed offline on the LAN. 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. The module will control all the authorized users with their assigned rights and only authorized users can login to the software and can perform the tasks that the administrator of the software has allowed from menu-level up to the buttonlevel (add. edit.5 User Rights and Security Management 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.1. print. 11.1. post and view etc. Authentication of a user to a secure Web site via the Secure Sockets Layer (SSL) protocol with 128 bits encryption technique.1. 4. 3. Access level of each module / interface can be defined at the time of creation of the user. Food Department Information System (FDIS) should have multiple level security controls.

a food department employee will automatically be directed to the web pages for Food Department.e. The system must have the ability to perform wheat inventory management. district. The system must have the ability to perform statistical analysis of wheat procured and released by the Food Department in previous years and based on this analysis should be able to make predictions for the current year. which are required in Food Department Information System. 8. 2. The system must have the ability to automate information regarding inbound and outbound trucks and the quantities that they are carrying. The system must have the ability to see which districts are in shortage of wheat and where wheat is in surplus. • Typical: Install only the single system for any storage house. The system must have the ability to generate a tracking number/consignment number from the central database with each consignment being transported.2 Generic Features 1. 3.. 7. 6. 9. The type of web pages displayed will depend upon the access rights given to them. 5.8 Component Based Deployment Software should be installed through setup program providing at least following three installation options. 12.1. Food department and Sugar Mill owners. This system must have the ability to determine the exact position of the consignment being delivered. The system must have the ability to order/request wheat from other regions.g.Food Department Information System 11. The system must have the ability to do wheat order management i.. The system must have the ability to generate separate web pages for Cane Commisionerate. • Complete: Install all modules. The system must have the ability to update stocks on daily basis. the wheat required for one storage center to another storage center or so. 10. e. SRS-28 . • Custom: Choice base installation by manually selecting each module separately. 4.

16. 18. 14. The system must have the ability to interface and provide information to the Food Department. 27. I.Food Department Information System 11. The system must have the ability to generate district wise reports of the wheat transfer from one PR center to another. The system must be able to provide search the database according to the search as per the criteria specified by the user. 23. The system must have the ability to integrate the Financial Account System. The system must have the ability to generate wheat procurement reports i. The system will facilitate the administrator to use pre-defied access levels to assign format of reports at storage. The system must have the ability to track down the trucks carrying wheat. The system must have the ability to generate weekly. procurement of wheat etc. The system must facilitate the applicant by providing a provisional number for a defined period of time during delay in registration process. The system must have ability to generate reminders and warnings against late payments. 20. 24.e. 25.. district and divisional levels. the wheat procured for the current fiscal year for any storage center etc. 17. 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. The system must have the ability to generate progressive reports. The system must have the ability to track and maintain information about annual fees related to various transactional activities. The system must have the ability to maintain record of capacity of each storage house. 15. The system must have the ability to generate Sale and Transfer reports. 13. The system must have the ability to create different user groups. The contractor will suggest a tool for making annual wheat estimates. 21. Inventory & Procurement Management System and Gate Management System (GMS) 22. 26. SRS-29 . monthly revenue statements. 19. 12.T Department& Agriculture Department.

update and delete the different levels of account heads and their descriptions. item code. The system must have the ability to allow only authorized users to perform their related task. 29.Food Department Information System 28. name. update and delete the information of parties / suppliers/vendor. quantity. The system must have the ability to enter. 9. 12. 31. The system should have the ability to keep the codes of each account head. 2. The system must have the ability to prepare the vouchers against the purchase of different items. voucher number. Information includes. The system must have the ability to enter. 5. amount etc. 3. The system must have the ability to generate transactional account details reports. The system must have the ability to generate the transactional data and storage unit reports.) and can print the weekly / monthly / yearly statement of payment status against each token.3 Financial Accounting System Features 1. The system should provide the facility to authorized staff members of Food Department to view the summary of different account heads through LAN/internet. The system mush have the ability to keep the information of acknowledgement slip (token No. 4. 6. 32. 30. 7. The system must have the ability to send print out report in pre-defined format. SRS-30 . The system must have the ability to generate the revenue tracking and notifications reports. The system must have the ability to prepare the bill of different vouchers. The system must have the ability to enter. account heads code. 8. The system must have the ability to generate storage unit capacity and load reports. update and delete the opening budget balance of each head.

Food Department Information System 10. Regarding the Monthly Comparison ( actual) vii. district. Regarding the Trial Balance vi. The system must have the ability to do budget control estimates during one financial year. Regarding the Monthly Comparison ( budgeted v actual) viii. Regarding the Cash Flow Reports. Regarding the Invoices Registers SRS-31 . 18. 11. 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. Regarding the Transactions Registers ix. 12. Regarding the Account Status ii. The system must have the ability to generate complete information regarding receivable accounts in its database 13. 19. and division wise in the province. The system must have the ability to maintain the Invoices of various heads in the system. The system must have the ability to do account management with respect to all the storage centers. The system must have the ability to generate complete information regarding payable accounts in its database. The system must have the ability to generate the following reports i. The system must have the ability to check out the opening balances. The system must have the ability to keep record of all the vouchers generated by the system. 14. The system must have the ability to transfer remaining amount from any head to another head for re-appropriation at the end of year according to the government rules. Regarding the General Ledger v. 15. 16. 17. iv. Regarding the Cash Position iii.

10. 2. The system must have the ability to monitor the wheat stocks. SRS-32 . polythene sheets etc and must inform the user incase of low supplies. 9. The system must have the ability to directly enter the transactions from the storage houses. The system must have the ability to maintain the record of available PP bags. The system must have the ability to maintain record of sale/transfer of wheat to other provinces. 4. 7. The system must have the ability to maintain information of the wheat seller/grower. Regarding the Balance Sheet xii. The system must have the ability to maintain record of imported wheat. 12.Food Department Information System x. weighing bridges. jute bags. 5. 6. The system must have the ability to maintain information of available stocks. pesticides. The system must have the ability to maintain information regarding the rejected wheat. region or province. Regarding the Profit & Loss Statements xi. The system must have the ability to maintain the record of wheat transferred between storage houses of districts. 3. Regarding the Financial Statement 12. 8. The system must have the ability to maintain a quality report of the bardana for example indigenous wheat etc with respect to procured wheat. The system must have the ability to do maintain the information regarding the bags issued to the farmers and update it on daily basis.4 Procurement (PMS) & Inventory Management System (IMS) Features 1. 11. The system must have the ability to maintain the record of quantity of wheat issued and sold to the Flour Mills.

The system must have the ability to ability to enter the information on Form -2 in the system. 15. Customized reports as per the user defined format. The system must be able to generate at least the following reports. xiv. Regarding the competitive statements. x. vi.Food Department Information System 13. iii. Regarding the Received vs Rejected Wheat report and analysis report. Regarding the wheat re-order level report. Generate voucher reports. 14. viii. the details of the seller/ grower and the purchaser details are added into the system. SRS-33 .. Regarding the wheat purchased history report Regarding the rate analysis report. iv. xv. Regarding the project order/work order wise wheat movement report. Regarding the available wheat stock in each district & region. ii. ix. Regarding the wheat party ledger. i. 16. Regarding the Store/Item Ledger Regarding the wheat consumption report Regarding the wheat dead stocks Regarding the wheat purchased but not issued/consumed. xii. xiii. Regarding the purchase order status report. The system must have the ability to generate the wheat purchased receipt. The system must have the ability to maintain the history of wheat rates announced annually by Government of Punjab. v. Regarding the minimum & maximum stock level report. The system must have the ability to have complete record of its inventory 17. xvi. xi. vii.

PR center.e. The system should be able to perform comparison of wheat stocks at each PR with the OGPs and IGPs related to that PR. Regarding the Periodic information of IGP v. Regarding the Periodic information of OGP. The system must have the ability to enter all the information regarding the gate passes issued to the trucks. the route. Ability of the System to enter information like truck number. Regarding the Returnable Wheat ii. driver name etc. Ability of the System to integrate this Gate Management System with IMS. Regarding the Purchase Order Status Report iv. 9. 8. Ability of the System to issue an Outward Gate Pass (OGP). expected date of arrival. SRS-34 . quantity of wheat loaded. based on a tracking ID to the vehicle / truck carrying the load from any PR center. Ability of the System to generate at least the following reports i. 7. PMS and all other modules of the System. Ability of the System to issue an Inward Gate Pass (IGP) when a vehicle carrying the load reaches the destination i.Food Department Information System 12. 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.. Ability of the System to issue project order / work order Outward Gate Pass. 3. date of departure.5 Gate Management System Features 1. 2. 5. destination. Regarding the Wheat Movement History iii. 4.

The system must have the ability to allow the DFC to submit online application report. The system must have the ability to generate a unique receipt number automatically for sugar mills as soon as the sugar mills submits the SCR-I and SCR-II on the website. which has sent their SCR-I and SCR-II. 3. provinces. departments. districts. general integrities. and also of those mills that have yet to sent their forms.Food Department Information System 12. The system must have the ability to display to the cane commisionarate list of all those sugar mills. 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.6 Cane Commissionerate Features 1. divisions. SRS-35 . 4. 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. The system must aloe the cane commisionarate officials to enter the reports of SCR-1 and SCR-II for those sugar mills that may not have online facility and have sent their forms via fax or regular mail. entitled leaves. general negative characteristics. 7. 10. 8. 12. religions. The system must have the ability for commisionarate to login to the system.7 Human Resource Management System Features 1. The system must have the ability to enter basic data of the employee. qualifications. The system must have the ability for cane commisionarate officials to generate pre defined online reports (requirement analysis of these reports is o be carried out by the contractor). The system must have the ability for sugar mills to login to the Food Department website and enter the data of SCR-I and SCR-II on daily and fortnightly basis. domicile. occupational groups. 6. languages. payroll etc. 5. 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. Basic data includes personnel’s posts/designations. 2. 9.

retirement date. The system must have the ability to enter complete transfer & posting record of an employee.Food Department Information System 2. training particulars. chain of command. inside or outside the country including training title. permanent address. The system must have the ability to enter trainings attended by an employee. occupational group service. inquiry results. inquiry officer. leave approval authority within an office of the Food Department. seniority level. The system must have the ability to provide enter the leave record of employees. transfer date. 11. 3. 8. 7. employment type. This will be critical in deciding about his future promotions and appointments. if any. email addresses. telephone numbers. 5. joining date. domicile. present address. including the date. emergency contacts. department served. The database must have complete record of amount of leaves availed from the leave quota and leaves still available. father’s name. punishments if any etc. place of birth. 9. The system must allow the Administrator to update or delete the information related to the employees. joining date. scanned photograph. domicile. NIC number etc. The system should also save a scanned copy of all the required documents of any particular employee. marital status. The system must have the ability to search an employee record based on his/her designation. office location. grade level and training needs and to browse his details including resume etc. inquiry type. 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. BPS. post. etc. The system must have the ability to enter any inquiries or any disciplinary actions conducted on employee during his tenure. religion. BPS. inquiry detail. 10. date and duration (number of days) etc. The contractor must suggest a method to implement this feature. background. birth date. SRS-36 . The system must have the ability to enter and save the Annual Confidential Report (ACR) of the employee. institution. 4. The system must have the ability to store employee resumes in a predefined format and layout and link up with their individual records. The system must have the ability to have administrative privileges like: define multi-level hierarchy. including designation held. It should be kept in mind that ACR are very confidential and should only be accessed to some privileged users only and should in encrypted form to others including the System Administrator. 6. The system must have the ability to provide an interface for creating an employees profile including employee’s name.

Level 2: Minor Problem – some inconvenience for users. Level 3: Cosmetic Problem – spelling errors etc. number. Report containing the names of all employees against whom any criminal has been taken.2 Software Acceptance Criterion Bug Levels for FDIS should be classified according to the four level of severity scale developed by IBM. FDIS should be free of Level 0 and Level 1 bugs. department served and tenure and any complaints against him etc. Report containing a leave balance and record of an employee containing the list of updated leave balance record at any time. approving authority etc as well as listing the leaves taken against the quota. This is an initial guideline. These levels are: • • • • Level 0: Critical Problem – software does not work at all.. Non Functional Requirements 13. end date. SRS-37 .Food Department Information System 12. • • • • 13.1 Development Methodology Standard development methodologies as proposed by PITB in the “Manual for the Software Development Standardization” should be followed. Level 1: Significant Problem – major feature disabled or incorrect. which is to be followed.1. age. Report containing a Leave Record taken by an employee over a given period of time with the start date. no effect on operations. It can allow an officer to view at a glance the important particulars of everyone working in a particular office. designation etc is made with this report. The manual provides guidelines for designing. testing. Report containing the professional record of an employee containing his name. The system must have the ability to generate at least the following reports: • Report containing a list with employee name.1.1 Software Quality Attributes 13. coding and documentation 13. reason of leave.

The Bidder is also required to specify in detail the Disaster Recovery Procedures in his proposed solution. the system might not be 24/7 but it should easily be convertible to it. 14.3 Availability The system should be available and it should meet the availability requirements mentioned in SRS. 14. performance and security.4 Reliability The proposed solution should ensure the integrity and consistency of the application and all its transactions as the load increases. 14. The system should behave within norms reckoning the provided statistics. 14. 14. 14.5 Security The proposed solution should ensure that the system is secure and it cannot be compromised. Considering the scope and importance of the system it is important that the disaster recovery procedures should be performed using an automated approach. reliability.2 Performance The system should be proposed considering the performance requirements. To start with.8 System Transition The Contractor would be required to provide a detailed system transition plan prior to the approval of the FS. availability. It is important that the transition from the old system to the new system happens in an organized and planned manner without disrupting the day to day operations. 14.1 Scalability 14. Non-Technical Issues The system should be easily scalable and there should be no additional software or hardware cost associated to make it scalable. SRS-38 .6 Manageability The proposed system should be capable of managing the system to ensure the continued health with respect to scalability.7 Disaster from Recovery The Contractor would be required to provide detailed disaster recovery procedures.Food Department Information System 14.

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

2) The user will fill in the group name or group type.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. 3) The user will press view button and information will be shown to the user.3 User Group Management Use Case Add Group Update Group Administrator Delete Group View Group 15. Post Condition: SRS-40 . Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.Food Department Information System 15.3.

4) The user will make the required changes.3. 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. 3) The user will press the update button and the fields will change into edit mode. Alternate 1 Step 2: 1a) If record not found then system will show the message that no record found. 2) The user will retrieve the record that is to be updated.3 Update Group Privileges Use Case Use Case UG-F: Update Group Privileges Basic Information Actor: Administrator Purpose: To update the user privileges Cross Reference: UI-B Pre Condition: Use Case UI-A: User Login Use Case UI-D: View Group Privileges Primary Course of Events: 1) The user will access relevant interface. 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. Cross Reference: UI-B Pre Condition: Use Case UI-A: User Login Primary Course of Events: 1) The user will access the relevant interface. group type and will assign the privileges to the user.Food Department Information System 15. 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 . Post Condition: 15. 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.3. 2) The user will press the add button 3) The user will fill in the group name.2 Add Group Privileges Use Case Use Case UG-E: Add Group Privileges Basic Information Actor: Administrator Purpose: To Add the new user and to assign the privileges to the group.

4 Purchase Weight and Quality Certificate Use Cases Add Purchase Weight and Quality Certificate Details Update Purchase Weight and Quality Certificate Details Data Entry Operator (DEO) Delete Purchase Weight and Quality Certificate Details View Purchase Weight and Quality Certificate Details SRS-42 .Food Department Information System 15. 2) The user will retrieve the record that he wants to delete. 3) The user will select the relevant record and will press the delete button record will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. Post Condition: 15. 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.4 Delete Group Privileges Use Case Use Case UG-G: Delete Group Privileges Basic Information Actor: Administrator Purpose: To delete the user privileges Cross Reference: UI-B Pre Condition: Use Case UI-A: User Login Use Case UI-D: View Group Privileges Primary Course Of Events: 1) The user will access relevant interface.3.

seller/grower name. 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. The user will access the relevant interface.2 Add Purchase Weight and Quality Certificate Details Use Case FDIS-002: Purchase Weight and Quality Certificate Details Basic Information Actor: Data Entry Operator Purpose: To add purchase weight and quality certificate details Cross Reference: UI.4. 2. The user will press the add button.4. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. The detailed information of the weight and quality certificate will be displayed on the screen. 3. 3. The user will fill in the district.1 View Purchase Weight and Quality Certificate Details Use Case FDIS–001: View Purchase Weight and Quality Certificate Details Basic Information Actor: Data Entry Operator Purpose: To view purchase weight and quality certificate details Cross Reference: UI-FDIS-003 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 2. The similar records as per the step 2 criteria will be shown in a new popup window to the user.FDIS -003 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. Post Condition: 15. center name and other relevant details. The user will access the relevant interface. 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. The user will press save button. 4. 5. Post Condition: SRS-43 . User will select the specific record and presses the ok button. center and other relevant details.Food Department Information System 15. information will be added into database when the user presses the ok button of the confirmation box. 6. The user will fill in the district. 4. The user will press view button.

information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box.4. The user will press the update button and the fields will change into edit mode. The user will retrieve the record that he wants to update.FDIS -003 Pre Condition: Use Case UL-A: User Login Use Case FDIS-001: View Purchase Weight and Quality Certificate Details Primary Course Of Events: 1.4 Delete Purchase Weight and Quality Certificate Details Use Case FDIS-004 : Delete Purchase Weight and Quality Certificate Details Basic Information Actor: Data Entry Operator Purpose: To delete purchase weight and quality certificate details Cross Reference: UI.Food Department Information System 15. 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. 3. Post Condition: 15. 4. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. The user will access relevant interface. The user will retrieve the record that he wants to delete 3.FDIS -003 Pre Condition: Use Case UL-A: User Login Use Case FDIS-001: View Purchase Weight and Quality Certificate Details Primary Course of Events: 1. Post Condition: SRS-44 . 5. 2.3 Update Purchase Weight and Quality Certificate Details Use Case FDIS-003: Update Purchase Weight and Quality Certificate Details Basic Information Actor: Data Entry Operator Purpose: To update purchase weight and quality certificate details Cross Reference: UI.4. The user will access relevant interface. 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. The user will make the required changes. 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. 2. The user will press the delete button.

Cross Reference: UI. 5.5. The detailed information of the seller/grower name or purchaser will be displayed on the screen. The similar records as per the step 2 criteria will be shown in a new popup window to the user.Food Department Information System 15.5 Bill Purchase of Wheat Detail Use Cases Add Bill Purchase of Wheat Details Update Bill Purchase of Wheat Details Data Entry Operator (DEO) Delete Bill Purchase of Wheat Details View Bill Purchase of Wheat Details 15.1 View Bill Purchase of Wheat Details Use Case FDIS–005: View Bill Purchase of Wheat Details Basic Information Actor: Data Entry Operator Purpose: To view wheat purchase bill details. 2. 4.FDIS -005 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 6. SRS-45 . User will select the specific record and presses the ok button. The user will press view button. The user will access the relevant interface. The user will fill in the seller/grower name and purchaser details. 3.

FDIS-005 Pre Condition: Use Case UL-A: User Login Use Case FDIS-005: View Bill Purchase of Wheat Details SRS-46 .3 Update Bill Purchase of Wheat Details Use Case FDIS-007: Update View Wheat Purchase Bill Details Basic Information Actor: Data Entry Operator Purpose: To update wheat purchase bill details. address and other relevant details of the seller/grower name and the details of the purchaser.FDIS -005 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. The user will fill in the seller/grower name.2 Add Bill Purchase of Wheat Details Use Case FDIS-006: Add Bill Purchase of Wheat Details Basic Information Actor: Data Entry Operator Purpose: To add wheat purchase bill details. Post Condition: 15.5. Cross Reference: UI. 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. The user will press the add button. father’s name.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. 2. The user will access the relevant interface. 3. 4. Post Condition: 15.5. 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. 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. The user will press save button. Cross Reference: UI.

2. The user will access relevant interface. The user will retrieve the record that he wants to delete 3. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. Post Condition: 15. Post Condition: SRS-47 .5.FDIS -005 Pre Condition: Use Case UL-A: User Login Use Case FDIS-005: View Bill Purchase of Wheat Details Primary Course Of Events: 1. 2. 3.Food Department Information System Primary Course of Events: 1. The user will press the update button and the fields will change into edit mode. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 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. Cross Reference: UI. The user will access relevant interface. The user will make the required changes. The user will press the delete button. 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.4 Delete Bill Purchase of Wheat Details Use Case FDIS-008 : Delete Wheat Purchase Bill Details Basic Information Actor: Data Entry Operator Purpose: To delete wheat purchase bill details. 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. 4. 5. The user will retrieve the record that he wants to update.

6 Daily Register of Un-Disbursed Bill Details Use Cases Add Daily Register of Un-Disbursed Bills Details Update Daily Register of Un-Disbursed Bills Details Data Entry Operator (DEO) Delete Daily Register of Un-Disbursed Bills Details View Daily Register of Un-Disbursed Bills Details 15. The user will select district and the purchasing center and date in the form. The user will press view button.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 Operator Purpose: To view un-disbursed bill details Cross Reference: UI. 3.FDIS-007 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. The similar records as per the step 2 criteria will be shown in a new popup window to the user. The user will access the relevant interface. 4. 2. SRS-48 .Food Department Information System 15.6.

The user will press save button.FDIS-007 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 2. 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.Food Department Information System 5. Post Condition: 15.3 Update Daily Register of Un-Disbursed Bill Details Use Case FDIS-011: Update Daily Register of Un-Disbursed Bill Details Basic Information Actor: Data Entry Operator Purpose: To update un-disbursed bill details Cross Reference: UI. User will select the specific record and presses the ok button. 4.6. 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.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. 3. date. amount and other details of the unpaid bills. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. The user will fill in the payees name. The user will press the add button. 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.FDIS-007 SRS-49 . information will be added into database when the user presses the ok button of the confirmation box.6. The user will access the relevant interface. 6. The detailed information of the particular purchasing center will be displayed on the screen.

5. 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. 2. Post Condition: SRS-50 . The user will retrieve the record that he wants to delete 3. 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. Post Condition: 15. The user will make the required changes. The user will access relevant interface. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. The user will retrieve the record that he wants to update. 4. 3.4 Delete Daily Register of Un-Disbursed Bill Details Use Case FDIS-012 : Delete Daily Register of Un-Disbursed Bill Details Basic Information Actor: Data Entry Operator Purpose: To delete un-disbursed bill details Cross Reference: UI-FDIS-007 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 press the update button and the fields will change into edit mode.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. The user will press the delete button. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 2. 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.6.

3. The user will press view button.7.Food Department Information System 15. The user will fill in the PR center. 4. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-51 .7 Grain Paper (Godown Register) Use Cases Add Grain Paper (Godown Register) Details Update Grain Paper (Godown Register) Details Data Entry Operator (DEO) Delete Grain Paper (Godown Register) Details View Grain Paper (Godown Register) Details 15.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. 2. Locality and other relevant details. The user will access the relevant interface.

Food Department Information System the user. The detailed information of the particular PR center will be displayed on the screen. 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. The user will fill in the PR center name. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. The user will press save button. Post Condition: 15. 2. locality and other relevant details. User will select the specific record and presses the ok button. 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. 4. The user will press the add button. 6. information will be added into database when the user presses the ok button of the confirmation box.FDIS-009 Pre Condition: SRS-52 . 5.7. The user will access the relevant interface.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-009 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 3. 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.7.3 Update Grain Paper (Godown Register) Details Use Case FDIS-015: Update Grain Paper (Godown Register) Details Basic Information Actor: Data Entry Operator Purpose: To update grain paper details Cross Reference: UI.

7. 3. The user will retrieve the record that he wants to delete 3. The user will access relevant interface. The user will make the required changes. 4. The user will access relevant interface. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 2. The user will press the delete button.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 retrieve the record that he wants to update. 5. Post Condition: SRS-53 . 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. The user will press the update button and the fields will change into edit mode.4 Delete Grain Paper (Godown Register) Details Use Case FDIS-016 : Delete Grain Paper (Godown Register) Details Basic Information Actor: Data Entry Operator Purpose: 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) Details Primary Course Of Events: 1. Post Condition: 15. 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. 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. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 2.

3. The user will access the relevant interface. 2.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. User will select the specific record and presses the ok button. 5.8 Godown Card Details Use Cases Add Godown Card Details Update Godown Card Details Data Entry Operator (DEO) Deleta Godown Card Details View Godown Card Details 15.8..Food Department Information System 15. The user will press view button. 4. SRS-54 . The user will fill in the godown no. The similar records as per the step 2 criteria will be shown in a new popup window to the user. date of fumigation or any other information. Cross Reference: UI-FDIS-010 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.

Cross Reference: UI-FDIS-010 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 3. Post Condition: 15.2 Add Godown Card Details Use Case FDIS-018: Add Godown Card Details Basic Information Actor: Data Entry Operator Purpose: To add information about the particular godown.8. 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. Cross Reference: UI-FDIS-010 Pre Condition: Use Case UL-A: User Login Use Case FDIS-017: View Godown Card Details SRS-55 . 4. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. The detailed information of the particular godown will be displayed on the screen.3 Update Godown Card Details Use Case FDIS-019: Update Godown Card Details Basic Information Actor: Data Entry Operator Purpose: To update information about the particular godown. information will be added into database when the user presses the ok button of the confirmation box.8. 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. 2.Food Department Information System 6. The user will access the relevant interface. 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. and other information of the particular godown. The user will press the add button. Post Condition: 15. The user will fill in the godown No. The user will press save button.

3. 5. The user will retrieve the record that he wants to delete 3. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 2.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. 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. The user will retrieve the record that he wants to update. The user will access relevant interface. 2. Post Condition: 15.8. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. Post Condition: SRS-56 .Food Department Information System Primary Course of Events: 1. The user will press the update button and the fields will change into edit mode. The user will press the delete button. 4. 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. 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. The user will make the required changes. The user will access relevant interface.

2. date or any other information.Food Department Information System 15. 4. The user will fill in the dispatching center name. 3. The similar records as per the step 2 criteria will be shown in a new popup window to the user. The user will access the relevant interface.9 Dispatch Report Use Cases Delete Whe at Dis patch Repo rt Update Wheat Dispatch Report Data Entry Operator View Wheat Dispatch Report Add Wheat Dispatch Report 15. The user will press view button. SRS-57 . Cross Reference: UI-FDIS-019 A Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.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.

Post Condition: 15. 2. 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.. 4. The user will fill in the dispatching center name and other information of the particular godown. 3. 6. Post Condition: 15. 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. Cross Reference: UI-FDIS-019 A Pre Condition: SRS-58 . The user will press save button. information will be added into database when the user presses the ok button of the confirmation box.2 Add Wheat Dispatch Report Use Case FDIS-018A: Add Wheat Dispatch Report Basic Information Actor: Data Entry Operator Purpose: To add the information about the wheat dispatched through the truck.9.3 Update Wheat Dispatch Report Use Case FDIS-019A: Update Wheat Dispatch Report Basic Information Actor: Data Entry Operator Purpose: To update the information about the wheat dispatched through the truck. The detailed information of the particular report will be displayed on the screen. The user will press the add button.9. User will select the specific record and presses the ok button. 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. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.Food Department Information System 5. 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.

The user will access relevant interface. The user will retrieve the record that he wants to delete 3. 4.Food Department Information System Use Case UL-A: User Login Use Case FDIS-017A: View Wheat Dispatch Report Primary Course of Events: 1. 2. The user will make the required changes. 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. The user will press the delete button. The user will press the update button and the fields will change into edit mode. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 5. 2. The user will retrieve the record that he wants to update. Post Condition: SRS-59 . 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. 3. Cross Reference: UI-FDIS-019 A Pre Condition: Use Case UL-A: User Login Use Case FDIS-017A: View Wheat Dispatch Report Primary Course Of Events: 1. 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. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. The user will access relevant interface. Post Condition: 15.9.4 Delete Wheat Dispatch Report Use Case FDIS-020A: Delete wheat Dispatch Report Basic Information Actor: Data Entry Operator Purpose: To delete the information about the wheat dispatched through the truck.

2.10 Dispatch of Wheat from P.Food Department Information System 15.R. to P. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-60 .R. 4.R.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-011 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. Basis Details Use Case FDIS–021: View Dispatch of Wheat from P. The user will press view button. 3.1 View Dispatch of Wheat from P.R.10. receiving center name. The user will access the relevant interface. Basis Use Case Add Dispatch of Wheat from PR to PR Basis Details Upadet Dispatch of Wheat from PR to PR Basis Details Data Entry Operator (DEO) Delete Dispatch of Wheat from PR to PR Basis Details View Dispatch of Wheat from PR to PR Basis Details 15. to P.R. The user will fill in the dispatching center name. to P.

Post Condition: 15.R. Basis Details SRS-61 . User will select the specific record and presses the ok button. 4. Post Condition: 15. to P.2 Add Dispatch of Wheat from P. The user will fill in the dispatching end details and the receiving end details.Food Department Information System the user.R. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.R. The detailed information of the dispatching end and the receiving end will be displayed on the screen.R. 3. 6. to P. Basis Details Basic Information Actor: Data Entry Operator Purpose: To update details about the wheat dispatched from one PR center to another Cross Reference: UI. to P.R. 2. 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 2 step 4: 2a) If the user will press the cancel button of the confirmation box the information will not be added into the database. to P. 5.R. Basis Details Basic Information Actor: Data Entry Operator Purpose: To add details about the wheat dispatched from one PR center to another Cross Reference: UI.R. The user will press the add button.FDIS -011 Pre Condition: Use Case UL-A: User Login Use Case FDIS-021: View Dispatch of Wheat from P.10.R.R.3 Update Dispatch of Wheat from P.10. Basis Details Use Case FDIS-022: Add Dispatch of Wheat from P. The user will access the relevant interface. Basis Details Use Case FDIS-023: Update Dispatch of Wheat from P. to P.FDIS -011 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.R. The user will press save button. information will be added into database when the user presses the ok button of the confirmation box.

Basis Details Basic Information Actor: Data Entry Operator Purpose: To details about the wheat dispatched from one PR center to another Cross Reference: UI. 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. 2. The user will make the required changes.R.10. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists.R.R. 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. 5. to P. 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.R. The user will press the update button and the fields will change into edit mode. 3. to P.R. Basis Details Primary Course Of Events: 1.FDIS -011 Pre Condition: Use Case UL-A: User Login Use Case FDIS-021: View Dispatch of Wheat from P. 2.4 Delete Dispatch of Wheat from P. The user will retrieve the record that he wants to update. Post Condition: SRS-62 .R. Post Condition: 15. The user will retrieve the record that he wants to delete 3. Basis Details Use Case FDIS-024 : Delete Dispatch of Wheat from P.Food Department Information System Primary Course of Events: 1. 4. to P. The user will press the delete button. The user will access relevant interface. The user will access relevant interface. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box.

The user will press view button. SRS-63 . The user will access the relevant interface.FDIS -019 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.1 View Wheat Stock Register Detail Use Case FDIS–025: View Wheat Stock Register Detail Basic Information Actor: Data Entry Operator Purpose: To view wheat stock detail as per the certain scheme.11. 3. 2.11 Wheat Stock Register Details Use Cases Add Wheat Stock Register Details Update Wheat Stock Register Details Data Entry Operator (DEO) Delete Wheat Stock Register Details View Wheat Stock Register Details 15. The user will fill in the scheme year and other particular details of the wheat stock. Cross Reference: UI.Food Department Information System 15.

11. The user will access the relevant interface.3 Update Wheat Stock Register Details Use Case FDIS-027: Update Wheat Stock Register Details Basic Information Actor: Data Entry Operator Purpose: To update wheat stock details as per the certain scheme. 2. Post Condition: 15.Food Department Information System 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 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. 4. Post Condition: 15.FDIS -019 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.FDIS -019 SRS-64 . 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. 5. The user will fill in the scheme details and other relevant details on the screen. The detailed information of the wheat stock will be displayed on the screen. 6. The similar records as per the step 2 criteria will be shown in a new popup window to the user. User will select the specific record and presses the ok button. Cross Reference: UI. The user will press the add button. 3.11. Cross Reference: UI. 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 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.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.

The user will press the delete button. The user will access relevant interface. Cross Reference: UI. Post Condition: 15. 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.FDIS -019 Pre Condition: Use Case UL-A: User Login Use Case FDIS-025: View Wheat Stock Register details Primary Course Of Events: 1. 2. The user will retrieve the record that he wants to update.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. 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. 4. The user will access relevant interface. The user will make the required changes. Post Condition: SRS-65 .4 Delete Wheat Stock Register Details Use Case FDIS-028: Delete Wheat Stock Register Details Basic Information Actor: Data Entry Operator Purpose: To update wheat stock details as per the certain scheme. 5. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. The user will retrieve the record that he wants to delete 3. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 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. 3. 2.11. The user will press the update button and the fields will change into edit mode.

Cross Reference: UI.12. 2.12 Stock Article Register Use Cases Add Stock Article Register Details Update Stock Article Register Details Data Entry Operator (DEO) Delete Stock Article Register Details View Stock Article Register Details 15.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.Food Department Information System 15. The user will fill in the center name.FDIS -012 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. The user will press view button. article name or other relevant details. 3. 4. The user will access the relevant interface. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-66 .

Post Condition: 15. 4. 5. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. 2.12. The user will fill in the center name and other relevant details on the screen.Food Department Information System the user. The detailed information of the stock at a certain center will be displayed on the screen. The user will press the add button.3 Update Stock Article Register Details Use Case FDIS-031: Update Stock Article Register Details Basic Information Actor: Data Entry Operator Purpose: To update basic information about the certain stock in a center Cross Reference: UI.12. 3.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 center Cross Reference: UI. 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. Post Condition: 15.FDIS -012 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 6.FDIS -012 SRS-67 . 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. User will select the specific record and presses the ok button. information will be added into database when the user presses the ok button of the confirmation box. The user will access the relevant interface. 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. The user will press save button.

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 Information Actor: 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 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 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

Food Department Information System

15.13 Wheat Sale Use Cases

Add Wheat Sale Details

Update Wheat Sale Details

Data Entry Operator (DEO)

Delete Wheat Sale Details

View Wheat Sale Details

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 -017 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 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

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 Operator Purpose: To add wheat sale details of a particular center. Cross Reference: UI- FDIS -017 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 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.13.3

Update Wheat sale Details Use Case FDIS-035: Update Wheat Sale Detail

Basic Information Actor: Data Entry Operator Purpose: To update wheat sale details of a particular center. Cross Reference: UI- FDIS -017 Pre Condition: SRS-70

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. 2. Cross Reference: UI. 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.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 press the update button and the fields will change into edit mode. 5.4 Delete Wheat Sale Details Use Case FDIS-036 : Delete Wheat Sale Details Basic Information Actor: Data Entry Operator Purpose: To delete update wheat sale details of a particular center. Post Condition: SRS-71 . 4. The user will make the required changes. The user will access relevant interface. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. The user will retrieve the record that he wants to update. 3.13. The user will retrieve the record that he wants to delete 3. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. Post Condition: 15.FDIS -017 Pre Condition: Use Case UL-A: User Login Use Case FDIS-033: View Wheat Sale Details Primary Course Of Events: 1. 2. The user will press the delete button. 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. The user will access relevant interface.

month. The user will press view button.14 Inventory of Bardana Use Cases Add Inventory of Bardana Details Update Inventory of Bardana Details Data Entry Operator (DEO) Delete Inventory of Bardana Details View Inventory of Bardana Details 15.14. 3.1 View Inventory of Bardana Details Use Case FDIS–037: View Inventory of Bardana Details Basic Information Actor: Data Entry Operator Purpose: To view bardana inventory details Cross Reference: UI. district or any other relevant details. The user will fill in the center name. 2. The user will access the relevant interface.Food Department Information System 15.FDIS -015 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. SRS-72 .

14. 3.FDIS -015 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.Food Department Information System 4. 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.14. 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. district and other fields on the screen. Post Condition: 15. 2. information will be added into database when the user presses the ok button of the confirmation box.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 details Cross Reference: UI. The user will press save button. The user will fill in the center name.3 Update Inventory of Bardana Details Use Case FDIS-039: Update Inventory of Bardana Details Basic Information Actor: Data Entry Operator Purpose: To update bardana inventory details Cross Reference: UI. User will select the specific record and presses the ok button.FDIS -015 SRS-73 . The user will access the relevant interface. Post Condition: 15. 4. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. 5. The detailed information of the bardana inventory will be displayed on the screen. 6. The similar records as per the step 2 criteria will be shown in a new popup window to the user. 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. The user will press the add button.

The user will make the required changes. 2. Post Condition: SRS-74 . The user will retrieve the record that he wants to delete 3. The user will access relevant interface. Post Condition: 15. The user will press the update button and the fields will change into edit mode. 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. The user will access relevant interface. 2. 3. 5. 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. 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.FDIS -015 Pre Condition: Use Case UL-A: User Login Use Case FDIS-037: View Inventory of Bardana Details Primary Course Of Events: 1.4 Delete Inventory of Bardana Details Use Case FDIS-040 : Delete Invetory of Bardana Details Basic Information Actor: Data Entry Operator Purpose: To delete bardana inventory details Cross Reference: UI.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. 4. 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. The user will retrieve the record that he wants to update. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists.14.

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.15 Purchase and Dispatch Form Details Use Cases Add Purchase and Dispatch Form Details Update Purchase and Dispatch Form Details Data Entry Operator (DEO) Delete Purchase and Dispatch Form Details View Purchase and Dispatch Form Details 15.Food Department Information System 15. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-75 . Cross Reference: UI. The user will press view button. The user will fill in the PR center name and other relevant details.FDIS -002 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 3. The user will access the relevant interface. 2.15. 4.

The user will fill in the center name.FDIS -002 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. Post Condition: 15. 6.15.15. 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.Food Department Information System the user. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. User will select the specific record and presses the ok button. information will be added into database when the user presses the ok button of the confirmation box. 3. 5. The detailed information of the center will be displayed on the screen. The user will press the add button. Post Condition: 15. SRS-76 . Cross Reference: UI. 4. The user will press save button. The user will access the relevant interface. 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. 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.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 PR Center. 2. grower name and other relevant details on the screen.2 Add Purchase and Dispatch Form Details Use Case FDIS-042: Add Purchase and Dispatch Form Details Basic Information Actor: Data Entry Operator Purpose: To add details of the wheat dispatched or purchased at a particular PR Center.

The user will retrieve the record that he wants to update. The user will press the delete button. 3.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. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. Cross Reference: UI. 5. Post Condition: SRS-77 .4 Delete Purchase and Dispatch Form Details Use Case FDIS-044 : Delete Purchase and Dispatch Form Details Basic Information Actor: Data Entry Operator Purpose: To delete details of the wheat dispatched or purchased at a particular PR Center. The user will retrieve the record that he wants to delete 3. The user will access relevant interface. 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.Food Department Information System Cross Reference: UI. 4. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 2. The user will make the required changes. Post Condition: 15. 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. 2. The user will press the update button and the fields will change into edit mode. The user will access relevant interface. 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.15.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.

Food Department Information System 15.FDIS -004 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 2.16 Sample Slip Use Cases Add Sample Slip Details Update Sample Slip Details Data Entry Operator (DEO) Delete Sample Slip Details View Sample Slip Details 15. The user will fill in the required fields in the form. 3. User will select the specific record and presses the ok button. 4. 5. The user will access the relevant interface.1 View Sample Slip Details Use Case FDIS–045: View Sample Slip Details Basic Information Actor: Data Entry Operator Purpose: To view the information about the sample slip. The similar records as per the step 2 criteria will be shown in a new popup window to the user.16. The user will press view button. Cross Reference: UI. SRS-78 .

information will be added into database when the user presses the ok button of the confirmation box. 3. The user will press save button. Cross Reference: UI.Food Department Information System 6. The user will fill in the different fields on different on the screen. 4.16.3 Update Sample Slip Detail Use Case FDIS-047: Update Sample Slip Detail Basic Information Actor: Data Entry Operator Purpose: To update the information about the sample slip. 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. The user will press the add button. 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.16. Post Condition: 15. The detailed information will be displayed on the screen.FDIS -004 Pre Condition: Use Case UL-A: User Login Use Case FDIS-045: View Sample Slip Details SRS-79 . Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. 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. The user will access the relevant interface.2 Add Sample Slip Details Use Case FDIS-046: Add Sample Slip Details Basic Information Actor: Data Entry Operator Purpose: To add the information about the sample slip. Cross Reference: UI.FDIS -004 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. Post Condition: 15. 2.

Post Condition: 15. The user will press the delete button. 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. 5.FDIS -004 Pre Condition: Use Case UL-A: User Login Use Case FDIS-045: View Sample Slip Detail Primary Course Of Events: 1. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 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. The user will retrieve the record that he wants to update. The user will make the required changes. Cross Reference: UI.Food Department Information System Primary Course of Events: 1. Post Condition: SRS-80 . The user will press the update button and the fields will change into edit mode. 2. The user will access relevant interface. 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. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 4. 3. 2. The user will access relevant interface.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.16. The user will retrieve the record that he wants to delete 3.

17 Purchased Wheat Details Use Cases Add Purchased Wheat Details Update Purchased Wheat Details Data Entry Operator (DEO) Delete Purchased Wheat Details View Purchased Wheat Details 15. 3.Food Department Information System 15. The user will press view button. 2.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. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-81 . The user will access the relevant interface.FDIS -006 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. The user will select the particular PR center and the particular month. 4.

17.17. 4. 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.3 Update Purchased Wheat Details Use Case FDIS-051: Update Purchase Wheat Details Basic Information Actor: Data Entry Operator Purpose: To update detail information of the wheat purchased at a PR center Cross Reference: UI.FDIS -006 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 3.Food Department Information System the user. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. User will select the specific record and presses the ok button. Alternate 2a step 4: 2a) If the information entered already exists the system will give the message that the following information is already into the database. Post Condition: 15. 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. 5.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. The user will access the relevant interface. Post Condition: 15. The detailed information of the particular month will be displayed on the screen. The user will press the add button. The user will press save button. 6. information will be added into database when the user presses the ok button of the confirmation box.FDIS -006 Pre Condition: SRS-82 . 2. The user will fill in PR center and other details on the screen.

4 Delete Purchased Wheat Details Use Case FDIS-052 : Delete Purchase Wheat Details Basic Information Actor: Data Entry Operator Purpose: To delete detail information of the wheat purchased at a PR center Cross Reference: UI. The user will retrieve the record that he wants to update. The user will retrieve the record that he wants to delete 3. 4. 3. 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. 5. Post Condition: 15.17. 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. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 2.Food Department Information System Use Case UL-A: User Login Use Case FDIS-049: View Purchased Wheat Details Primary Course of Events: 1.FDIS -006 Pre Condition: Use Case UL-A: User Login Use Case FDIS-049: View Purchased Wheat Details Primary Course Of Events: 1. The user will make the required changes. The user will access relevant interface. 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. The user will press the delete button. Post Condition: SRS-83 . The user will press the update button and the fields will change into edit mode. The user will access relevant interface. 2.

2. 4. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-84 .18 Miscellaneous Item Sale Register Use Cases Add Miscellaneous Item Sale Register Details Update Miscellaneous Item Sale Register Details Data Entry Operator (DEO) Delete Miscellaneous Item Sale Register Details View Miscellaneous Item Sale Register Details 15. The user will press view button.18.FDIS -008 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 3.Food Department Information System 15. The user will access the relevant interface. Cross Reference: UI. The user will fill in the item name. quantity or other relevant details.1 View Miscellaneous Item Sale Register Details Use Case FDIS–053: View Miscellaneous Item Sale Register Details Basic Information Actor: Data Entry Operator Purpose: To view general information about the miscellaneous item sold in the department.

information will be added into database when the user presses the ok button of the confirmation box. Post Condition: 15.3 Update Miscellaneous Item Sale Register Details Use Case FDIS-055: Update Miscellaneous Item Sale Register Details Basic Information Actor: Data Entry Operator Purpose: To update general information about the miscellaneous item sold in the department. The user will access the relevant interface. Cross Reference: UI. 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.18. 6.18. 2. The user will fill in the item. The user will press save button. 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. 5. quantity. amount received and other relevant details. 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. 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.Food Department Information System the user. User will select the specific record and presses the ok button. Post Condition: 15. The user will press the add button. 3. SRS-85 .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.FDIS -008 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 4.

Post Condition: SRS-86 . 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. The user will press the update button and the fields will change into edit mode.18.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. 2. 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.4 Delete Miscellaneous Item Sale Register Details Use Case FDIS-056 : Delete Miscellaneous Item Sale Register Details Basic Information Actor: Data Entry Operator Purpose: To delete general information about the miscellaneous item sold in the department. 2. Post Condition: 15. 3. The user will access relevant interface. The user will press the delete button.Food Department Information System Cross Reference: UI. Cross Reference: UI. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 5. The user will access relevant interface.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. 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. The user will retrieve the record that he wants to delete 3. The user will make the required changes. The user will retrieve the record that he wants to update.

3. The user will access the relevant interface.19. center name. The user will press view button. Cross Reference: UI.1 View Unserviceable Stock Articles Data Use Case FDIS–057: View Unserviceable Stock Articles Data Basic Information Actor: Data Entry Operator Purpose: To view details about the unserviceable stock.FDIS -013 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. SRS-87 .Food Department Information System 15.19 Sale of Unserviceable Stock Articles Use Cases Add Sale of Unserviceable Stock Articles Details Update Sale of Unserviceable Stock Articles Details Data Entry Operator (DEO) Delete Sale of Unserviceable Stock Articles Details View Sale of Unserviceable Stock Articles Details 15. 2. The user will fill in the district.

information will be added into database when the user presses the ok button of the confirmation box. Cross Reference: UI. The similar records as per the step 2 criteria will be shown in a new popup window to the user. 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.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. 3. User will select the specific record and presses the ok button. districts and other relevant details on the screen. The user will access the relevant interface. 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. 6. The user will press the add button. SRS-88 .Food Department Information System 4. 2. The detailed information of the particular unserviceable stock will be displayed on the screen.2 Add Unserviceable Stock Articles Data Use Case FDIS-058: Add View Unserviceable Stock Articles Data Basic Information Actor: Data Entry Operator Purpose: To add details about the unserviceable stock.19. 4. 5. Alternate 2a step 4: 2a) If the information entered already exists the system will give the message that the following information is already into the database. Post Condition: 15. The user will press save button. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.FDIS -013 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. The user will fill in the center name. Post Condition: 15.19.

The user will retrieve the record that he wants to update. 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. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box.19. 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. The user will retrieve the record that he wants to delete 3.FDIS -013 Pre Condition: Use Case UL-A: User Login Use Case FDIS-057: View Unserviceable Stock Articles Data Primary Course of Events: 1.4 Delete Unserviceable Stock Articles Data Use Case FDIS-060 : Delete Unserviceable Stock Articles Data Basic Information Actor: Data Entry Operator Purpose: To delete details about the unserviceable stock. 2.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 press the update button and the fields will change into edit mode. The user will access relevant interface. The user will press the delete button. The user will make the required changes. The user will access relevant interface. 4. Cross Reference: UI. 5. Post Condition: 15. Post Condition: SRS-89 .Food Department Information System Cross Reference: UI. 2. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 3. 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.

The user will press view button.1 View Receipt and Sale of Wheat Details Use Case FDIS–061: View Receipt And Sale Of Wheat Details Basic Information Actor: Data Entry Operator Purpose: To view receipt and sale of wheat data at a particular center.FDIS -014 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.20. 4. The user will access the relevant interface. The user will fill in the particular district.Food Department Information System 15. SRS-90 . center name.20 Receipt and Sale of Wheat Use Cases Add Receipt and Sale of Wheat Details Upadet Receipt and Sale of Wheat Details Data Entry Operator (DEO) Delete Receipt and Sale of Wheat Details View Receipt and Sale of Wheat Details 15. Cross Reference: UI. 2. etc. 3. The similar records as per the step 2 criteria will be shown in a new popup window to the user.

2.FDIS -014 Pre Condition: Use Case UL-A: User Login SRS-91 . information will be added into database when the user presses the ok button of the confirmation box. Cross Reference: UI. 3. center name and other relevant details on the screen. The user will press save button. Post Condition: 15.2 Add Receipt and Sale of Wheat Details Use Case FDIS-062: Add Receipt And Sale Of Wheat Details Basic Information Actor: Data Entry Operator Purpose: To add receipt and sale of wheat data at a particular center. 4. 6. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found. The user will press the add button. Cross Reference: UI. 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. The detailed information of the center will be displayed on the screen. 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.3 Update Receipt and Sale of Wheat Details Use Case FDIS-063: Update Receipt And Sale Of Wheat Details Basic Information Actor: Data Entry Operator Purpose: To update receipt and sale of wheat data at a particular center. 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. User will select the specific record and presses the ok button. The user will fill in the district. Post Condition: 15.FDIS -014 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.20.20. The user will access the relevant interface.Food Department Information System 5.

The user will press the update button and the fields will change into edit mode. The user will retrieve the record that he wants to update. The user will retrieve the record that he wants to delete 3. 3. The user will access relevant interface. The user will access relevant interface. 5. 2.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. 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. 4.FDIS -014 Pre Condition: Use Case UL-A: User Login Use Case FDIS-061: View Receipt And Sale Of Wheat Details Primary Course Of Events: 1. The user will make the required changes. 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. 2. Cross Reference: UI.20.Food Department Information System Use Case FDIS-061: View Receipt And Sale Of Wheat Details Primary Course of Events: 1. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. Post Condition: SRS-92 . information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 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. The user will press the delete button. Post Condition: 15.

3. The user will fill in the scheme year.21 Stock Receipt Information Use Cases Add Stock Receipt Information Update Stock Receipt Information Data Entry Operator (DEO) Delete Stock Receipt Information View Stock Receipt Information 15. The user will access the relevant interface. 4.1 View Stock Receipt Information Use Case FDIS–065: View Stock Receipt Information Basic Information Actor: Data Entry Operator Purpose: To view stock information of a particular scheme at a particular center.Food Department Information System 15. The user will press view button. The similar records as per the step 2 criteria will be shown in a new popup window to the user. center or any relevant details. 2. Cross Reference: UI.FDIS -016 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1.21. SRS-93 .

6. 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. Post Condition: 15. User will select the specific record and presses the ok button.21. 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. information will be added into database when the user presses the ok button of the confirmation box. The user will access the relevant interface. Cross Reference: UI. and center and any other relevant details on different on the form. Post Condition: 15.FDIS -016 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 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. The detailed information of that particular scheme will be displayed on the screen. 2.21. The user will press save button.3 Update Stock Receipt Information Use Case FDIS-067: Update Stock Receipt Information Basic Information Actor: Data Entry Operator Purpose: To update stock information of a particular scheme at a particular center. The user will fill in the scheme year. Cross Reference: UI.Food Department Information System 5. 3. district. 4. Alternate 1 Step 3: 1a) If the required record not found the system will give the information message that the no information found.FDIS -016 Pre Condition: SRS-94 . The user will press the add button.2 Add Stock Receipt Information Use Case FDIS-066: Add Stock Receipt Information Basic Information Actor: Data Entry Operator Purpose: To add stock information of a particular scheme at a particular center.

Post Condition: 15. 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. 2. Post Condition: SRS-95 . 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. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. Cross Reference: UI. The user will make the required changes. The user will retrieve the record that he wants to update. The user will retrieve the record that he wants to delete 3.21. 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. The user will access relevant interface.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. 4.FDIS -016 Pre Condition: Use Case UL-A: User Login Use Case FDIS-065: View Stock Receipt Information Primary Course Of Events: 1. 5.4 Delete Stock Receipt Information Use Case FDIS-068 : Delete Stock Receipt Information Basic Information Actor: Data Entry Operator Purpose: To delete stock information of a particular scheme at a particular center. Alternate 1 Step 2: 1a) If the record is not found the system will show the message that no record exists. 3. The user will press the update button and the fields will change into edit mode. 2. The user will press the delete button.

FDIS -018 Pre Condition: Use Case UL-A: User Login Primary Course of Events: 1. 2. 4.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.22.Food Department Information System 15. 3. The similar records as per the step 2 criteria will be shown in a new popup window to SRS-96 . The user will fill in the center name. date or any other relevant information etc. The user will access the relevant interface. The user will press view button.22 Gate Pass Use Cases Add Gate Pass Information Update Gate Pass Information Data Entry Operator (DEO) Delete Gate Pass Information View Gate Pass Information 15.

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 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.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 information Cross 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 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.22.3

Update Gate Pass Information Use Case FDIS-071: Update Gate Pass Information

Basic Information Actor: Data Entry Operator Purpose: To update the gate pass information Cross Reference: UI- FDIS -018

SRS-97

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 Information Actor: Data Entry Operator Purpose: To delete the gate pass information Cross Reference: UI- FDIS -018 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 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

Food Department Information System

15.23

Employee Personal Information:

Delete Employee Personal Information

Add Employee Personal Information

Data Entry Operator (DEO)

Update Employee Personal Information

View Employee Personal Information

15.23.1

View Employee Personal Information:

UC-FDIS-073: View Employee’s Personal Information Basic Information: Actor: Data Entry Operator Purpose: To enter an employee’s personal information in the system. Cross Reference: UI-FDIS-020 Pre-Conditions: Use Case UL-A: User Login

SRS-99

4) The similar records as per the step 2 criteria will be shown in a new popup window to the user. domicile etc. 5) User will select the specific record and presses the ok button.23.Food Department Information System Primary Course of Events: 1) The user will access the relevant interface. 15. 3) The user will fill in all the information regarding employee like name. information will be added into database when the user presses the ok button of the confirmation box.23.3 Update Employee Personal Information UC-FDIS-075: Update Employee’s Personal Information Basic Information: Actor: Data Entry Operator Purpose: To Update an employee’s personal information in the system. 3) The user will press view button. Alternate 1: Post-Condition: Employee’s personal information record is added in the system. father’s name. 4) The user will press save button. Alternate 1: Post-Condition: Employee’s personal information record is present in the system. Cross Reference: UI-FDIS-020 Pre-Conditions: Use Case UL-A: User Login UC-FDIS-073: View Employee’s Personal Information SRS-100 . 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. addresses. 15. 2) The user will fill in the employee id or any other information.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. NIC card number.

24 Employee Leave Approval / Rejection Administrator Enter Em pl oyee's Leave Approval / Rejection SRS-101 . 15. 2) The user will retrieve the record that he wants to delete 3) The user will press the delete button. Alternate 1: Post-Condition: Employee’s personal information record is present in the system.23. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box. 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. 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. 3) The user will make the required changes. 2) The user will press the update button and the fields will change into edit mode. 15.Food Department Information System Primary Course of Events: 1) The user will access relevant interface. Alternate 1: Post-Condition: Employee’s personal information record is present in the system.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.

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 and selects the HRMS link on the Main Menu. Post-Conditions: The leave is either approved / rejected along with the remarks. 2) User will enter the user name and password. 4) System will verify the username and password and check the privilege level of the user and enable menus accordingly. Cane Commissioner Purpose: To Login to the system Cross Reference: Pre Condition: Typical Course Of Events: 1) User will run the program. 3) The user will click the sign in button. Alternate: Post Condition: SRS-102 . 3) The system provides an appropriate interface to the user to specify the employee id. 15.25 Cane Commissionerate User Login Cane Commissioner Login Sugar Mill Use Case UL-CC: User Login Basic Information Actor: Sugar Mill. 4) The system displays the employee particulars and an option to enter remarks for leave approval / rejection. 2) The user selects the employee Leave Approval / Rejection link on the HRMS Main Menu.

The user will press view button. SRS-103 .26. 3. The user will access the relevant interface.26 Cane Commissionerate SCR II View SCR II Update SCR II Sugar Mill Data Entry Operator Add SCR II Delete SCR II 15.Food Department Information System 15.View SCR II Basic Information Actor: Sugar Mill Data Entry Operator Purpose: To view SCR II Cross Reference: Pre Condition: Use Case UL-CC: User Login Primary Course of Events: 1. The user will fill in all the mandatory information. 2.1 View Cane Commissionerate SCR II Use Case UC-FDIS.

2.Add 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.2 Add Cane Commissionerate SCR II Use Case UC-FDIS. The user will access the relevant interface. 5.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. Alternate 1 Post Condition: 15.3 Update Cane Commissionerate SCR II Use Case UC-FDIS. 4. information will be added into database when the user presses the ok button of the confirmation box. The user will fill in all the mandatory fields. 3. The SCR II will be displayed on the screen. Alternate 1 Post Condition: 15. The similar records as per the step 2 criteria will be shown in a new popup window to the user. The user will press the add button. The user will press save button.Food Department Information System 4. SRS-104 . if no field is filled then remark against the field must be filled.26. 2) The user will retrieve the record that he wants to update. User will select the specific record and presses the ok button. 6.26. 3) The user will press the update button and the fields will change into edit mode. 4) The user will make the required changes.

Post Condition: SRS-105 . Alternate 1 Post Condition: 15. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box.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.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 Step 3: 1a) If the user will press the cancel button of the confirmation box the record will not be deleted from the database. 2) The user will retrieve the record that he wants to delete 3) The user will press the delete button.4 Delete Cane Commissionerate SCR II Use Case UC-FDIS.26.

Food Department Information System 15.1 View Cane Commissionerate SCR I Use Case UC-FDIS.27 Cane Commissionerate SCR I View SCR I Add SCR I Sugar Mill Data Entry Operator Update SCR I Delete SCR I 15.27.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 .

5) User will select the specific record and presses the ok button. information will be added into database when the user presses the ok button of the confirmation box.3 Update Cane Commissionerate SCR I Use Case UC-FDIS. The user will fill in all the mandatory information.Add SCR I Basic Information Actor: 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. if no field is filled then remark against the field must be filled. The similar records as per the step 2 criteria will be shown in a new popup window to the user. 4) The user will press save button. SRS-107 . 3) The user will fill in all the mandatory fields.27. The user will press view button.2 Add Cane Commissionerate SCR I Use Case UC-FDIS. 6) The SCR I will be displayed on the screen.27. Alternate 1 Post Condition: 15. 2) The user will press the add button.Update SCR I Basic Information Actor: 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.Food Department Information System 1) 2) 3) 4) The user will access the relevant interface. Alternate 1 Post Condition: 15.

2) The user will retrieve the record that he wants to delete 3) The user will press the delete button.Delete SCR I Basic Information Actor: 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.27.Food Department Information System 2) 3) 4) 5) The user will retrieve the record that he wants to update. The user will press the update button and the fields will change into edit mode. Alternate 1 Post Condition: 15. 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. information will be deleted (not physically/permanently) from the database after user presses the ok button of the confirmation box.4 Delete Cane Commissionerate SCR I Use Case UC-FDIS. The user will make the required changes. 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. Post Condition: SRS-108 .

Food Department Information System 15. 2) The user will press the report generation button.Send Intimation Report Basic Information Actor: Cane Commissioner Purpose: To send warning to the Sugar Mills that have not sent their SCR I or SCR II Cross Reference: Pre Condition: Use Case UL-CC: User Login Primary Course of Events: 1) The user will access the relevant interface.29 Print Intimation Report Cane Commissioner Print Intimation Report SRS-109 . 3) The list of all the Sugar Mills will be shown that have not sent their SCR I or SCR II 4) The user will select the Sugar Mills to send the warning 5) The user will press the send mail button to send the warning to the selected Sugar Mills Alternate 1 Step 3: 1a) If the user will press the clear button the list will be cleared from the report Post Condition: 15.28 Send Intimation Report Cane Commissioner Send Intimation Report Use Case UC-FDIS.

2) The user will press the report generation button.Food Department Information System Use Case UC-FDIS. 3) The list of all the Sugar Mills will be shown that have not sent their SCR I or SCR II 4) The user will select the Sugar Mills to send the warning 5) The user will press the print button to print the warning for the selected Sugar Mills Alternate 1 Post Condition: SRS-110 .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.

Description: Screen will be used for Signing in to the Food Department software / system for the desired purpose. Cross Reference Use Case.Food Department Information System 16. User Interface 16. SRS-111 .1 User Login User Login GUI UI-A UC-A Interface No.

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

to P. Food Department (Main Menu) GUI UI-FDIS -001 Food Department Information System (FDIS)-Main Menu Food Department Information System Main Menu Purchase and Dispatch Form Sample Slip Food Details of Purchased Wheat Statement of Purchase and Payment of Wheat (Weekly) Grain Paper (Godown Register) Dispatch of Wheat from P.3 Food Department (Main Menu) Interface No.Basis Wheat Stock Register Stock Article Register Sale of Unserviceable Stock Articles Stock Receipt Information Gate Pass Miscellaneous Things Sale Register Financial Management System Purchase Weight and Quality Certificate Bill Purchase of Wheat Daily Register of Un Disbursed Bills Stock Report Help Godown Card Dispatch Report Final Result of Storage Wheat in Godown. delete and view the records etc. update.Food Department Information System 16. SRS-113 .R. Inventory of Bardana Receipt and Sale of Wheat Wheat Sale Information Wheat Stock Register Sugar Cane Commissioner Human Resource Management System Description: Screen will allow users to navigate through an form to add. Cross Reference Use Case.R.

add. update and delete wheat purchase and dispatch record.Food Department Information System 16. UC-FDIS-041 to 044 Description: Screen will be used to view. SRS-114 . UI-FDIS-002 Cross Reference Use Case.4 Purchase and Dispatch Form Purchase and Dispatch Form GUI Interface No.

SRS-115 .Food Department Information System 16.5 Purchase Weight and Quality Certificate Purchase Weight and Quality Certificate GUI Interface No. update delete and view purchase details and quality certificate details. UI-FDIS-003 Cross Reference Use Case. UC-FDIS-001-004 Description: Screen will be used to add.

Date [Select Date] Invoice Date [Select Date] Laboratory Sent Date [Select Date] Classification of Bags [Select] Type [Select District] Seller Grower Name Recipient End Wagon/Truck No. Invoice No. update delete and view the of wheat sampling details. SRS-116 . R. of Bags Dispatching End Receiver Name No.R. Godown No. Sample Slip GUI UI-FDIS-004 UC-FDIS-045 to 048 Food Department Government of the Punjab-GP-16 Sample Slip Sample Slip District [Select District] Lot No. Clear View Add Update Delete Save Exit Description: Screen will be used to add. Cross Reference Use Case. Date of Sampling [Select Date] Military Credit Note No.Food Department Information System 16. of Bags R.R. Center [Select Center] No.6 Sample Slip Interface No. No.

No. GP-05 Reference Wagon No.7 Bill Purchase of Wheat Interface No. Chuck No.Food Department Information System 16. of Bag Rate of Wheat /1000kg Delivery Charges Extra Charges Total Amount Net Amount for Payment Amount Recommended Bank Name Clear View Add Update Quantity of Wheat Wheat Price Commission/Agent Details of Extra Charges Deduction of Amount (in figure) (in words) (in figure) (in words) Delete Save Exit Description: Screen will be used to add.C. GP-16 Reference GP-6 Reference Destination/ Station Name Bility No. New N. update delete and view wheat bill purchase details.I. Purchaser Details Center [Select Center] Fathers Name Consignment No. No. Cross Reference Use Case. Bill Purchase of Wheat GUI UI-FDIS-005 UC-FDIS-005 to 008 Food Department Government of the Punjab-Form-2 Bill Purchase of Wheat Seller/Grower Details District [Select District] Name Address Owner of Land Village Name Old N. SRS-117 ./Truck No. Lot No.I.C No.

8 Purchased Wheat Details Interface No. update delete and view the details of Wheat Purchase in a particular PR center.Food Department Information System 16. Purchased Wheat Details GUI UI-FDIS-006 UC-FDIS-049 to 052 Description: Screen will be used to add. SRS-118 . Cross Reference Use Case.

update delete and view the information about the un-disbursed wheat bills. UC-FDIS-009 to 012 Description: Screen will be used to add. SRS-119 .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.

UI-FDIS-008 Cross Reference Use Case. Challan Date Reason For Loss Total Auction Commission In Case of Approval Price After Commission Clear View Add Update Delete Save Exit Description: Screen will be used to add.Food Department Information System 16.No. UC-FDIS-053 to 056 Food Department Government of the Punjab-SF-27 Miscellaneous Item Sale Register Date 20/12/2004 Stock S. SRS-120 . update delete and view the details of miscellaneous items sold. Things Quantity At the Rate Of Rate Received Amount Loss If Any Details of Received Amount Name of Treasury Where Amount Deposited Challan No.10 Miscellaneous Item Sale Register Miscellaneous Item Sale Register GUI Interface No.

Food Department Information System 16. update delete and view the details of Grain at a certain center SRS-121 . UI-FDIS-009 Cross Reference Use Case.11 Grain Paper (Godown Register) Grain Paper (Godown Register) GUI Interface No. UC-FDIS-013 to 016 Description: Screen will be used to add.

12 Godown Card Interface No. Stock Completion Date etc.Food Department Information System 16. Godown Card GUI UI-FDIS-010 UC-FDIS-017 to 020 Description: Screen will be used to add. Cross Reference Use Case. SRS-122 . update delete and view the details of Godown like Mass of Godown. Storage Capacity. Date of Stock Starting.

R.R.R. update delete and view the details of wheat dispatched form one P.Food Department Information System 16. UC-FDIS-021 to 024 Description: Screen will be used to add. to P. UI-FDIS-011 Cross Reference Use Case. SRS-123 . to P. Basis Dispatch of Wheat from P.R.R. Basis GUI Interface No.13 Dispatch of Wheat from P. to another.

Food Department Information System

16.14 Stock Article Register
Interface No. Cross Reference Use Case. Stock Article Register GUI UI-FDIS-012 UC-FDIS-029 to 032

Food Department Government of the Punjab-Stock Article Register

Stock Article Register
Stock Article Register

Date 20/12/2004

District [Select District]
Article Name
Receiving

Center [Select Center]
Previous Balance Place Received From Completion Date of Storage

[Select Article]

Date of Receiving [Select Date] Quantity Received
Release

By Order of Date SF-27 [Select Date]
Sale

Reference SF-27 Quantity

By Order of Date SF-27 [Select Date] Bank Name Challan No.
Transfer

Reference SF-27 Quantity Amount Deposited in Bank Challan Date [Select Date]

By Order of Reference No. of Dispatch Report [Select Date] Quantity Balance at the End of Month

Destination Date of Dispatching Report [Select Date]

Clear

View

Add

Update

Delete

Save

Exit

Description: Screen will be used to add, update delete and view the wheat stock

article details.

SRS-124

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

Food Department Information System

16.16 Receipt and Sale of Wheat
Interface No. Cross Reference Use Case. Receipt and Sale of Wheat GUI UI-RSW-014 UC-FDIS-061-064

Food Department Government of the Punjab-Gate In Register

Instructions
Receipt and Sale of Wheat

Receipt and Sale of Wheat
Center [Select Center]
Truck/ wagon No. Wheat No. Imported Indigenous G.P. 13 Date Date Insert Quality Quality of Bardana Comments

District [Select District]
Serial No Date Date Dispatching Center

Clear

View

Add

Update

Delete

Save

Exit

Description: Screen will be used to add, update delete and view the Receipt and Sale of wheat details.

SRS-126

SRS-127 . Inventory of Bardana GUI UI-FDIS-015 UC-FDIS-037 to 040 Food Department Government of the Punjab-Inventory of Bardana Inventory of Bardana Date 20/12/2004 Inventory of Bardana Center [Select Center] Monthly Map [Select Moth] Bardana [Select Bardana] Previous Balance District Related (Godown) Month Empty Bags [Select District] [Select Bardana] Bales Filled Bags Receiving Truck/Train(Biility No) Date 20/12/2004 Empty Bags Consignment No. update delete and view the details of Bardana.Food Department Information System 16. 21 Reference Date Filled Bags Rate [Select Date] Treasure Challan No.17 Inventory of Bardana Interface No. Bales Empty Bags Clear View Add Update Delete Save Exit Description: Screen will be used to add.6) Report Date Filled Bags Date [Select Date] [Select Date] Sale center Reference No. 27 Reference Date Filled Bags Remarks [Select Date] Reference No. Received Amount By The Bank Auctioned Bags Date [Select Date] By Order of and S. Bales Empty Bags Sale Center Dispatch Report (G. Bales Empty Bags Bank Challan By Order of and S.F.P. Cross Reference Use Case. Reference of Expenses Destination Station Report No. Scheme Year Bales Filled Bags [Select Year] Local Purchase price By Order of Date [Select Date] Income Destination Station Reference No.F.

13 No. Of bags Matric Tons Received Weight No.18 Stock Receipt Information Interface No. update delete and view the details of wheat stock for a particular scheme.Where Stock Stored Stock Report GP-5 No. [Select Center] Indigenous Date Weight Description Dispatched Weight No. Date Date Quality of Bardana/ Remarks Total (Today) Previous Toatal Grand Total Clear View Add Update Delete Save Exit Description: Screen will be used to add.P. Stock Receipt Information GUI UI-FDIS-016 UC-FDIS-065 to 068 Food Department Government of the Punjab-GP-7 Instructions Commodity Center [Select Center] Stock Receipt Information Scheme Year District [Select Year] [Select District] Date [Select Date] Stock Report No Consignment No. Date Date Insert Quality Quality of Bardana Railway Wagon No. Cross Reference Use Case. Truck No.Food Department Information System 16. SRS-128 . Of bags Matric Tons Excess Weight Short Weight Godown No. Dispatch Report Date G. Senders Description Serial No Senders Description Dispatching Center Dispatch Report No.

update delete and view the details of wheat sale. SRS-129 . Cross Reference Use Case. Wheat Sale Information GUI UI-FDIS-017 UC-FDIS-033 to 036 Description: Screen will be used to add.19 Wheat Sale Information Interface No.Food Department Information System 16.

R. Permit No. Gate Pass GUI UI-FDIS-018 UC-FDIS-069 to 072 Food Department Government of the Punjab-Gate Pass Gate Pass Consignment No.R. Name of R. update delete and view gate pass detail.L. Quantity Godown No. No. Center Authority No. Cross Reference Use Case.Food Department Information System 16. Issuing Authority Gate Pass Date 20/12/2004 Type of Gate Pass IGP P.20 Gate Pass Interface No.Center] Clear View Add Update Delete Save Exit Description: Screen will be used to add. S. SRS-130 . Gate Register No. Passing Autority [Select P.

Center [Select P.21 Wheat Stock Register Interface No.Center] Scheme Year 20/12/2004 20/12/2004 To Indicate Consolidated Position Of Wheat Stock Fall Schemes in Tons Closing Balance S.R. No. Wheat Stock Register GUI UI-FDIS-019 UC-FDIS-025 to 028 Food Department Government of the Punjab-SR-9 Wheat Stock Register Date District [Select District] P. Receipt. SRS-131 .Food Department Information System 16. Date Indigenous Bags 30/12/2004 Tons Imported Bags Tons Indigenous Bags Tons Receipt Imported Bags Tons Indigenous Bags Tons Total Imported Bags Tons Total Issues Closing Balance Indigenous Bags Imported Tons GPS Number Local Sales Indigenous Imported Total Dispatches Indigenous Imported Indigenous Imported Clear View Add Update Delete Save Exit Description: Screen will be used to add. update delete and view the details of wheat stock like Closing Balance. Cross Reference Use Case.R. Total Issues etc.

Wagon No. Wheat Stock Register GUI UI-FDIS-019 A UC-FDIS-017A to 019A Food Department Government of the Punjab-GP-6 Instructions Dispatching End Dispatching Center [Select Center] Date of Dispatch [Select Date] Consignment No. Reference District/Regional /Directorate Office Dispatch Report Date 20/12/2004 District [Select District] Scheme Year [Select Year] Lot No. Godown No.. SRS-132 . Cross Reference Use Case.Truck No. No.22 Wheat Stock Register Interface No. Sr.Food Department Information System 16. Dispatch Bags Bags Weight Weight in GP-13 Railway Fare Remarks Clear View Add Update Delete Save Exit Description: Screen will be used to add. Dispatching Station Truck Invoice No. update delete and view the details of stock dispatched daily through trucks.

Food Department Information System 16. Cross Reference Use Case. Employee Personal Information UI-FDIS-020 UC-FDIS-073 to 076 Description: This screen is used to add. view. SRS-133 . update and delete the personal information of the employee by using relevant buttons.23 Employee Personal Information Interface No.

F 10/2. Cross Reference Use Case. Employee Leave Approval / Rejection UI-FDIS-021 UC-FDIS-077 Food Department Government of the Punjab . 11. He may apply for leave after a week. SRS-134 .Food Department Information System 16. Save Close Description: This screen is used by the leave-granting officer to either approve / reject the leave request of an employee along with the remarks.24 Employee Leave Approval / Rejection Interface No. Islamabad Phones : 042-4353456. 0300-23453533 Remarks : Rejected due to ISO audit coming in the next week project evaluations required urgently.HRMS Leave Approval / Rejection ID : Name : FD001118 Muhammad Kaeem Post / Designation : Additional Director Food Leave Information Leave From : Leave Type : Reason : 11/11/2003 Casual Work at Home To : 15/11/2003 Days : Remaining Leaves : 5 2 Address (during Leave) : House No.

HRMS Main Menu UI-FDIS-026 Food Department Information System (FDIS)-Main Menu HRMIS HRMS Main Menu Personal Information Leave Approval / Rejection Description: This screen is used to access the HRMS module. SRS-135 .Food Department Information System 16.25 HRMS Main Menu Interface No. Cross Reference Use Case.

SRS-136 .26 Cane Commissioner Login Interface No. Cross Reference Use Case. HRMS Main Menu UI-FDIS-027 Cane Commissioner Module User Name Cane Commissioner Password ************** Remember Password Forget Password Sign In Cancel Description: This screen is used to access Cane Commissioner module.Food Department Information System 16.

Food Department Information System 16.27 Cane Commissioner SCR II Interface No. SRS-137 . Cross Reference Use Case. HRMS Main Menu UI-FDIS-028 Description: This screen is used to enter data in SCR II.

Food Department Information System 16. HRMS Main Menu UI-FDIS-029 Description: This screen is used to enter data in SCR I.28 Cane Commissioner SCR I Interface No. Cross Reference Use Case. SRS-138 .

HRMS Main Menu UI-FDIS-030 Description: This screen is used to send Intimation Report to the Sugar Mills.29 Cane Commissioner Intimation Report Interface No. SRS-139 .Food Department Information System 16. Cross Reference Use Case.

Reports 17. Date Dispatching Center Truck/ Wagon No Indigenous Wheat Imported Wheat Total SRS-140 . No.Food Department Information System 17.1 Receipt and Sale of Wheat Report (Date Wise) Receipt and Sale of Wheat Report (Date Wise) Government of Punjab Food Department Receipt and Sale of Wheat Report (Date Wise) Sale Center: _______________________________ Receipt Center: ____________________________ S.

2 Receipt and Sale of Wheat Report (Center Wise) Receipt and Sale of Wheat Report (Center Wise) SRS-141 .Food Department Information System 17.

3 Grower / Agency Report Grower / Agency Report SRS-142 .Food Department Information System 17.

4 Purchase Bill Report (Center Wise) Purchase Bill Report (Center Wise) SRS-143 .Food Department Information System 17.

G. NIC No.P.06 Reference No. G.16 Wagon/ Reference Destination Station Name Truck No.P. No.P.5 Purchase Bill Report (Seller Wise) Purchase Bill Report (Seller Wise) Government of Punjab Food Department Purchase Bill Report (Seller Wise) Seller/Grower Name: _______________________ Owner of land: _____________________________ Chuck No.05 Reference No.: _________________________________ Address: ____________________________ Village Name: _________________________ Lot No. (Old) G. Bility No. SRS-144 . (New) NIC No.Food Department Information System 17.

of Unpaid Purchase Bill Date of Bill Name of Payee Amount (Rs) Center Incharge Name Actual Date of Payment by Bank Total SRS-145 .6 Undisbursed Bills Report Un-Disbursed Bills Report Government of Punjab Food Department Un-Disbursed Bills Report Date: _______________________________ S.Food Department Information System 17.No. No.

R. Basis (Dispatching Wise) Report SRS-146 .R.Food Department Information System 17. to P.R. R.7 Dispatch of Wheat from P. Basis (Dispatching Wise) Report Dispatch of Wheat from P. to P.

Basis (Receiving Wise) Report Dispatch of Wheat from P. to P.R. to P. R.R.8 Dispatch of Wheat from P. Basis (Receiving Wise) Report SRS-147 . R.Food Department Information System 17.

9 Wheat Stock Register Report Wheat Stock Register Report SRS-148 .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 .Food Department Information System 17.

No.11 Employee Education Qualification Employee Education Qualification Government of Punjab Food Department Educational Qualification S. 1 Qualification MSc Public Health Year 1998 Institution Punjab University Subjects Nutrition SRS-150 .Food Department Information System 17.

12 Employee Language Proficiency Employee Language Proficiency Government of Punjab Food Department Language Proficiency S. 1 2 Language Urdu English Read Excellent Excellent Write Excellent Excellent Speak Excellent Excellent SRS-151 .Food Department Information System 17. No.

No.13 Employee Timings Employee Timing Government of Punjab Food Department Trainings S. 1 Title Title Public Health Public Health Particulars Harvard University Start Date 11/11/2003 Duration 2 Months SRS-152 .Food Department Information System 17.

No 1 Joining Date 11/11/2003 Department Food Department Designation DDF D.Food Department Information System 17.14 Employee Posting History Employee Posting History Government of Punjab Food Department Posting History Sr.G Khan BPS XYZ SRS-153 .

G Khan ACR 1998 He is a very diligent personnel of the Food Department and has never been found involved in any fraud or wrongdoing.15 Employee Inquiry History / Annual Confidential Report Employee Inquiry History / Annual Confidential Report Government of Punjab Food Department Inquiry History / Annual Confidential Report (ACR) Sr.Food Department Information System 17. His conduct has been satisfactory and he proved himself to be an asset of the Food Department SRS-154 . Food Department DDF D. No 1 Inquiry Date 11/11/2003 Department Designation Inquiry Officier XYZ Remarks He was found clean and no action was taken against him.

Food Department Information System 18. Appendix A Glossary of Terms Term FDIS DEO PR LAN ICDS OGP IGP DFC C&W FD HRMS EDO WAN LAN DFC FDIS FTP IP NIC IGP OGP P&D Description Food Department Information System Data Entry Operator Provincial Reserve Local Area Network Integrated Central Depository System Outward Gate Pass In Gate Pass District Food Controller Construction & Works Food Department Human Resources Management System Executive District Officer Wide Area Network Local Area Network District Food Controller Food Department Information System File Transfer Protocol Internet Protocol National Identity Card Inward Gate Pass Outward Gate Pass Planning and Development SRS-155 .

1 Form SF-26 (Page 1) Form SF-26 (Page 1) SRS-156 .1 Sample Scanned Documents 19. Appendix B 19.1.Food Department Information System 19.

2 Form SF-26 (Page 2) Form SF-26 (Page 2) SRS-157 .Food Department Information System 19.1.

1.3 Form 2 (Page 1) Form 2 (Page 1) SRS-158 .Food Department Information System 19.

Food Department Information System 19.4 Form 2 (Page 2) Form 2 (Page 2) SRS-159 .1.

Food Department Information System 19.1.5 Form GP-6 Form GP-6 SRS-160 .

6 District Inventory of Bardana Filled District Inventory of Bardana Filled SRS-161 .Food Department Information System 19.1.

1.7 District Inventory of Bardana Empty District Inventory of Bardana Empty SRS-162 .Food Department Information System 19.

8 Stock Article Register Stock Article Register SRS-163 .Food Department Information System 19.1.

9 Stock Ledger Stock Ledger SRS-164 .Food Department Information System 19.1.

1.Food Department Information System 19.10 Sample Slip Sample Slip SRS-165 .

11 Form 3 Form 3 SRS-166 .Food Department Information System 19.1.

Food Department Information System 19.1.12 Form SF-24 Form SF-24 SRS-167 .

1.Food Department Information System 19.13 Form SF-28 Form SF-28 SRS-168 .

14 Form GP-3 Form GP-3 SRS-169 .1.Food Department Information System 19.

15 Form GP-5 Form GP-5 SRS-170 .1.Food Department Information System 19.

Food Department Information System 19.1.16 Form GP-7 Form GP-7 SRS-171 .

1.17 Form GP-8 Form GP-8 SRS-172 .Food Department Information System 19.

Food Department Information System 19.18 Form GP-13 (Page 1) Form GP-13 (Page 1) SRS-173 .1.

19 Form GP-13 (Page 2) Form GP-13 (Page 2) SRS-174 .1.Food Department Information System 19.

20 Gate Pass Gate Pass SRS-175 .Food Department Information System 19.1.

Food Department Information System 19.21 Gate Register PR Center Gate Register PR Center SRS-176 .1.

1.Food Department Information System 19.22 Purchase and Dispatch Information Form Purchase and Dispatch Information Form SRS-177 .

Food Department Information System 19.1.23 Wheat Purchase Wheat Purchase SRS-178 .

1.24 Form SF-21 Form SF-21 SRS-179 .Food Department Information System 19.

25 Stock Articles Stock Articles SRS-180 .Food Department Information System 19.1.

Food Department Information System 19.1.26 Form SF-27 Form SF-27 SRS-181 .

Food Department Information System 19.27 Form SCR I Form SCR I SRS-182 .1.

28 Form SCR II Form SCR II SRS-183 .Food Department Information System 19.1.

Food Department Information System SRS-184 .

Sign up to vote on this title
UsefulNot useful