Department of Agriculture & Cooperation 2012 Service 1...2012 Agricultural Informatics Division National Informatics Centre Department of Information Technology Ministry of Communications

SOFTWARE REQUIREMENTS SPECIFICATION

2012

Agricultural Informatics Division National Informatics Centre Department of Information Technology Ministry of Communications & Information Technology Government of India

Department of Agriculture & Cooperation Ministry of Agriculture Government of India

Agricultural Mission Mode Project

under National e-Governance Plan

Information System for Seed (Service 1) Software Requirement Specifications

Ag

ricultu

ral M

ission

Mod

e Pro

ject un

der N

atio

na

l e-Go

vern

an

ce Pla

n

Sahara India Center 2, Kapoorthala Complex, Aliganj Lucknow – 226002, India

Version 1.1

Amendment Log

Version Number

Date Change Number

Brief Description Sections change

0.01 Draft

13/01/2012

-

Draft

All.

0.02Draft 21/01/2012 - Draft

Addition of use cases- Create Role, Create User Group,

Create Users and Accessibility Rights, Seed Certification and

QA, Suspension of License, Request for duplicate License, Auto trigger, Manual Trigger,

Attach Document, Drop Document , Relevant Entities

0.03 Draft

24/01/2012 Draft

Changes in license and Seed Certification Workflow, Use

Cases of Expert Advisory and GMS (as suggested by NIC HQ), Responsibility Matrix

GMS, Dealership Registration & License Use case

0.03Revised

29/01/2012

Revised

Changes in Notified Seed Varieties Work Flow, Use

Cases: Dealers stock details, Seed Testing and Quality

Assurance

0.04

Revised 03/02/2012

Revised All Transactional Use cases

0.05 Revised

15/02/2012

Revised

RACI Chart amendment, GAP Analysis w.r.t 7 States, Actors and the As-Is processes of 7

states, formatting etc.

1.00

29/03/2012 Revised

Additions of parameters of PoPs,

1.1

13/04/2012 Revised

Improvements and Suggestions provided by NIC

HQ, integration with SeedNet Portal etc. Deletion of FAQ

Manager, Expert Advisory and Grievance Redressal use cases

Software Requirement Specification Ver 1.1 Information on Seeds

Sahara Next January 2012 1

CONTENTS

RACI CHART ............................................................................................................................ 5

1. INTRODUCTION ............................................................................................................ 7

1.1 PURPOSE ................................................................................................................... 7 1.1.1 Intended Audience ........................................................................................................ 7

1.2 SCOPE ....................................................................................................................... 8 1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS .................................................... 10

1.3.1 Abbreviations ............................................................................................................. 10

1.4 REFERENCES ........................................................................................................... 11

1.5 OVERVIEW .............................................................................................................. 12 1.5.1 Problems / Issues addressed by Agriculture MMP ..................................................... 12 1.5.2 Causes & Effects of Problems / Issues ........................................................................ 13 1.5.3 Proposed Solutions Provided by the MMP ................................................................. 14 1.5.4 Structure of this document ......................................................................................... 16

2. OVERALL DESCRIPTION ................................................................................................ 17

2.1 PRODUCT PERSPECTIVE .......................................................................................... 17 2.2 PRODUCT FUNCTIONS ............................................................................................. 17

2.2.1 Information System for Seed ...................................................................................... 18

2.2.1.1 Current (AS-IS) Business Processes ............................................................................... 18

2.2.1.2 Proposed (To-Be) Business Processes and Functional Requirements .......................... 34

2.2.1.2.1 High Level view of Functional Requirements: .......................................................... 50 2.2.2 System Interfaces ........................................................................................................ 50

2.2.2.1 System Architecture Diagram ....................................................................................... 51

2.2.2.1.1 Responsibility Matrix for Content Management ...................................................... 51

2.2.2.1.2 Responsibility Matrix for Document Management .................................................. 52

2.2.2.2 Gap Analysis between existing and proposed system .................................................. 52

2.2.2.3 Gap Analysis w.r.t 7 States ............................................................................................ 53

2.3 USER CHARACTERISTICS ........................................................................................ 55 2.4 CONSTRAINTS ......................................................................................................... 56

2.5 ASSUMPTIONS AND DEPENDENCIES ........................................................................ 57 2.6 ACCEPTANCE CRITERIA .......................................................................................... 57

3. SPECIFIC REQUIREMENTS ............................................................................................. 58

3.1 EXTERNAL INTERFACE REQUIREMENTS .................................................................. 58 3.1.1 User Interfaces ........................................................................................................... 58 3.1.2 Hardware Interfaces ................................................................................................... 58 3.1.3 Software Interfaces .................................................................................................... 58

3.2 SOFTWARE PRODUCT FEATURES ............................................................................ 58 3.2.1 Common Use Cases .................................................................................................... 61

3.2.1.1 Log in ............................................................................................................................. 62

3.2.1.2 Select Season ................................................................................................................. 65

3.2.1.3 Log Out .......................................................................................................................... 67

3.2.1.4 Change Password .......................................................................................................... 69

3.2.1.5 Switch Language ............................................................................................................ 72

3.2.1.6 Payment Gateway ......................................................................................................... 74

3.2.1.7 Attach Documents ......................................................................................................... 77



3.2.1.8 Drop Attachment ........................................................................................................... 81

3.2.1.9 Auto Trigger ................................................................................................................... 82

3.2.1.10 Manual Trigger .............................................................................................................. 83 3.2.2 Knowledge Management System ............................................................................... 85

3.2.2.1 User Management/System Administration .................................................................. 85

3.2.2.1.1 Create Role ................................................................................................................ 85

3.2.2.1.2 Create User Group .................................................................................................... 88

3.2.2.1.3 User Creation and Accessibility Rights ...................................................................... 92

3.2.2.2 Master Data Management .......................................................................................... 105

3.2.2.2.1 Managing Released Varieties .................................................................................. 106

3.2.2.2.2 Managing Seed Prices ............................................................................................ 109 3.2.3 Transactions and Work Flow .................................................................................... 111

3.2.3.1 Seed Availability .......................................................................................................... 111

3.2.3.1.1 Dealer Registration Process .................................................................................... 112

3.2.3.1.2 Updating Daily stock details over the Web ............................................................. 115

3.2.3.1.3 Recording Historical Database of the licensed dealers .......................................... 118

3.2.3.1.4 Development of SMS application based on NIC SMS gateway............................... 122

3.2.3.2 License Application ...................................................................................................... 126

3.2.3.2.1 Application Form to obtain Dealers License (Form A) ............................................ 129

Application Form to obtain Dealers License (Form A) .................................................................. 129

3.2.3.2.2 Application Acceptance .......................................................................................... 135

3.2.3.2.3 Forward Application for Physical Inspection of Site ............................................... 138

3.2.3.2.4 Physical Verification Report .................................................................................... 140

3.2.3.2.5 Issue Dealership License in Seed ............................................................................. 143

3.2.3.2.6 Endorsement in License .......................................................................................... 146

3.2.3.2.7 Application for Renewal of Dealership Licence (Form C) ...................................... 146

3.2.3.2.8 Application for obtaining Dealership Licence At Range Level ............................... 154

3.2.3.2.9 Request for Duplicate License ................................................................................. 162

3.2.3.2.10 Cancellation/Suspension of the License ............................................................... 165

3.2.3.3 Seed Certification ........................................................................................................ 168

3.2.3.3.1 Seed Grower Registration ....................................................................................... 169

3.2.3.3.2 Application Acceptance .......................................................................................... 174

3.2.3.3.3 Registration Acknowledgement .............................................................................. 177

3.2.3.3.4 Inspection Report Form .......................................................................................... 179

3.2.3.3.5 Processing Information for Seeds of a Grower ....................................................... 185

3.2.3.3.6 Sampling Information ............................................................................................. 189

3.2.3.3.7 Seed Test Results .................................................................................................... 190

3.2.3.3.8 Generate Release Order.......................................................................................... 191

3.2.3.3.9 Packaging and Tagging ............................................................................................ 196

3.2.3.4 Seed Quality Testing and Assurance Process .............................................................. 199

3.2.3.4.1 Sample Collection Details........................................................................................ 200

3.2.3.4.2 Sample Acceptance ................................................................................................. 203

3.2.3.4.3 Sample testing details at seed laboratories ............................................................ 206

3.2.3.4.4 Generate Test Card ................................................................................................. 209

3.2.3.4.5 Generating Test Reports ......................................................................................... 210

3.3 PERFORMANCE REQUIREMENTS ............................................................................ 211 3.3.1 Scalability Requirements .......................................................................................... 211 3.3.2 Response Time .......................................................................................................... 211

3.4 SOFTWARE SYSTEM ATTRIBUTES ......................................................................... 212



3.4.1 Usability .................................................................................................................... 212 3.4.2 Reliability .................................................................................................................. 212 3.4.3 Availability ................................................................................................................ 212 3.4.4 Security ..................................................................................................................... 212 3.4.5 Maintainability ......................................................................................................... 213 3.4.6 Portability ................................................................................................................. 213 3.4.7 Language Support .................................................................................................... 213 3.4.8 Interoperability ......................................................................................................... 214

3.5 LOGICAL DATABASE REQUIREMENTS ................................................................... 214 3.5.1 Data entities ............................................................................................................. 214

3.5.1.1 Entity Name: Season ................................................................................................... 214

3.5.1.2 Entity Name: Variety_Prices ........................................................................................ 215

3.5.1.3 Entity Name: Area Codes ............................................................................................. 215

3.5.1.4 Entity Name: FAQ Category ......................................................................................... 215

3.5.1.5 Entity Name: Add New Query ..................................................................................... 216

3.5.1.6 Entity Name: Add FAQ ................................................................................................. 216

3.5.1.7 Entity Name: QueryAdvice_Status .............................................................................. 216

3.5.1.8 Entity Name: Expert_Advice ........................................................................................ 217

3.5.1.9 Entity Name: Complaint Form Details ......................................................................... 218

3.5.1.10 Entity Name: Grievance View ...................................................................................... 218

3.5.1.11 Entity Name: Complaint Status ................................................................................... 219

3.5.1.12 Entity Name: Grievance Response .............................................................................. 219

3.5.1.13 Entity Name: Form A Details ....................................................................................... 220

3.5.1.14 Entity Name: Payment Details ..................................................................................... 221

3.5.1.15 Entity Name: Payment Gateway ................................................................................. 222

3.5.1.16 Entity Name: Application Status .................................................................................. 222

3.5.1.17 Entity Name: License Details ....................................................................................... 223

3.5.1.18 Entity Name: Dealers Register ..................................................................................... 223

3.5.1.19 Entity Name: Dealers Stock Availability ...................................................................... 224

3.5.1.20 Entity Name: Grower ................................................................................................... 225

3.5.1.21 Entity Name: Seed ....................................................................................................... 225

3.5.1.22 Entity Name: Offices .................................................................................................... 226

3.5.1.23 Entity Name: Employees ............................................................................................. 226

3.5.1.24 Entity Name: Processing_Center ................................................................................. 227

3.5.1.25 Entity Name: Producing_Agency ................................................................................. 228

3.5.1.26 Entity Name: Registering_Organization ...................................................................... 229

3.5.1.27 Entity Name: Lots ........................................................................................................ 229

3.5.1.28 Entity Name: Sample ................................................................................................... 230

3.5.1.29 Entity Name: Sample_Result ....................................................................................... 231

3.5.1.30 Entity Name: Laboratory ............................................................................................. 231

3.5.1.31 Entity Name: Sg_Registration ...................................................................................... 231

3.5.1.32 Entity Name: Grower_Seed ......................................................................................... 232

3.5.1.33 Entity Name: Inspection_Report ................................................................................. 233

3.5.1.34 Entity Name: Reg_Officers .......................................................................................... 234

3.5.1.35 Entity Name: Parent_Seed .......................................................................................... 234

3.5.1.36 Entity Name: Grower_Seed_Lot .................................................................................. 235

3.6 OTHER REQUIREMENTS ........................................................................................ 236 3.6.1 Backup ...................................................................................................................... 236 3.6.2 Recovery ................................................................................................................... 236



3.6.3 Data Retention ......................................................................................................... 236 3.6.4 Customer/User Training ........................................................................................... 236 3.6.5 Audit Trail ................................................................................................................. 236

4. ANNEXURES ............................................................................................................. 237

4.1 ANNEXURE-1 ........................................................................................................ 237 4.1.1 System-Use Case Diagram ........................................................................................ 237

4.2 ANNEXURE-2 ........................................................................................................... 238 4.2.1 Enclosure Form-A ..................................................................................................... 238 4.2.2 Enclosure Form-B ...................................................................................................... 240 4.2.3 Enclosure Form V ...................................................................................................... 241 4.2.4 Enclosure Form VIII ................................................................................................... 242 4.2.5 Enclosure Test Card .................................................................................................. 243 4.2.6 Enclosure Certified Sample Reports .......................................................................... 244 4.2.7 Enclosure Official Sample Report ............................................................................. 245 4.2.8 Enclosure Service Sample Report ............................................................................. 246 4.2.9 Enclosure City Wise Monthly Report ........................................................................ 247 4.2.10 Enclosure Crop Wise Monthly Report ................................................................... 248 4.2.11 Enclosure Sample Wise Monthly Report .............................................................. 249 4.2.12 Enclosure Certified Seed Sample Collection Form-1 ............................................. 250 4.2.13 Enclosure Certified Seed Sample Collection Form-2 ............................................. 251



RACI Chart

RACI Chart for This Document RACI stands for Responsible, Accountable, Consulted, and Informed these are the main

Codes that appear in a RACI chart, used here to describe the roles played by team members

and stakeholders in the production of the SRS. The following table describes the full list

of codes used in the table:

* - Authorize has ultimate signing authority for any changes to the document. R - Responsible, Responsible for creating this document. A - Accountable, Accountable for accuracy of this document (for example, the project manager). S - Supports, Provides supporting services in the production of this document. C - Consulted, Provides input (such as an interviewee). I - Informed, Must be informed of any changes.

Name Position * R A S C I

Sunita Bhatia Sr. Business Analyst X NIC State Nodal Officer

Technical Director, NIC, Bhopal X X

NIC State Nodal Officer

Technical Director, NIC, Shimla X X

Sri. Verghese Abhraham

PSA, NIC, Bhopal X X

Mr. Thomre State Seed Certification Agency, Bhopal, M.P X Sri H.Omkar Singh Assist. Director of Agriculture, Seed X

Sri Anand Badonia State Nodal Officer, IT X

Dr. A.K Rai Head, Instrumentation, JNKVV X

Dr. S.N. Murty Ret. Director of Instrumentation, JLNKVV X

Mrs. Arunima Sen Asst. Director of Agriculture, Jabalpur District X

Mr. Ajay Bhonsle Regional Coordinator, KCC, Indian Society of Agribusiness Professionals

X

Mr. A.D. Galitkar Seed Testing Officer, State Seed Testing Lab, Maharashtra

X

Mr. J.P. Salve District Seed Certification Officer, Maharashtra X

Mr. R.M. Kawade Chief Inspector (Seed), Maharashtra X

Mr. Sameer Sharma

State Agriculture Information officer, Agriculture Secretariat, Shimla, H.P State

X

Mr. Sushil Kumar Seed certification officer, Agriculture Secretariat ,Shimla,H.P

X

J.C. Dharmani Senior Analyst Chemist, Agriculture Secretariat, Shimla, H.P State

X

Mr. Mahendra Bhawani

ADO/Analyst – SPTL, Agriculture Secretariat, Shimla, H.P State

X

Mr. R. N. Thakur Plant protection officer, Shimla, H.P State X

Dr. Raghveer Singh Deputy Director, Shimla District X



Thakur

Mr. Munish Sood ADO, Deputy Director Office, District Shimla X

Mr. Joginder Sharma

AEO, Deputy Director Office, District Shimla X

Dr. Hemraj Thakur Subject Matter Specialist, DD Office, District Shimla

X

Ms. Rajeshwari Kotiah First Division Assistant, Seeds Section, Karnataka X Mr .Ravi In charge Deputy Director, Seeds Section, Karnataka X Mr. Jai Prakash Assistant Director, Seed certification agency

X

Nalini Devi Data entry operator, Seed certification agency X Iftekhar Ulla Assistant Director, Seed Certification Agency X Director of KSSCA Bangaluru, Karnataka X Shri Hemant H Prabal

Jt. Director of Agriculture, Jharkhand X

Shri K Gari Dy Director – Farm, Jharkhand X Shri Harman Minz Dy. Director, Jharkhand X Shri Ravish Chandra Asst. Director, Jharkhand X Shri Bimal Baxla DAO, Jharkhand X Mrs. K. Barkakaty Technical Director, NIC, Guwahati X X Shri P. Saikia JDA (Pulse) X Shri D. Tharkura DDA (Seeds) X Mr. M. Sarmah Scientist X



1. INTRODUCTION

1.1 Purpose

The purpose of this document is to unambiguously specify the software requirements for a web based application system providing disseminated information on quality seeds to be accessible through State Agricultural Portal (SAP) from now on, based on the requirements received from Ministry of Agriculture. The requirements stated in this SRS document should be read in conjunction with enterprise-wide requirements to be commonly implemented across all Central Agricultural Portal (CAP) applications.

1.1.1 Intended Audience

The Intended Audience for this project can be broadly classified under four main categories, these are:

1. Farmers

a. Individual farmers

b. Farmer groups

c. Farmer cooperatives

2. Central Government

a. Department of Agriculture & Cooperation

b. Attached Offices & Directorates

c. Testing Labs

d. Academic & Research Institutions

e. National Seed Corporation

f. National Seed Research and Training Centre

g. State Farm Corporation of India

3. State Government

a. Department of Agriculture & Cooperation

b. Attached Offices & Directorates

c. State Testing Labs

d. State Seed Corporation

e. State Seed Certification Agency

f. Academic & Research Institutions

4. Private Sector

a. Manufacturers / Wholesalers / Dealers of inputs

b. Importers and exporters of agriculture produce



c. Traders, Buyers and Commodity Exchanges

d. Kissan Call Centers

e. Agricultural Business Clinics & Centers

1.2 Scope

The scope of this document is to identify the software requirement specifications relating to e-

enablement of one of the prioritized services i.e. Seed, their delivery through Citizen Service Center, and

the internet at Central Ministry (Department of Agriculture & Cooperation, GOI), State Agriculture

Department and Agencies, District and Block level Agriculture offices. The project would focus on

enabling electronic delivery of service, and does not include internal automation of agriculture

department / agencies.

a) This document would cover the software requirements specifications for the Services

Information System on Quality Seed

b) The service is further categorized under following service components;

Information System on Quality Seed

The proposed service aims at providing

Information on seed varieties

Information on the dealer network

Information on Seed Prices

Information on quality control and assurance mechanism such as easy to

comprehend seeds act, list of seed testing laboratories and notified seeds inspectors.

Automation of existing backend processes or sub services to decrease the lead time

in processing applications and to provide the most up to date information

a. license to retail

b. seed grower registration

c. seed certification

Expert advice on any specific issues related to seeds which would be answered by

appropriate domain experts

Mechanism for grievance management with regards to a specific activity / process

within the state and central government framework.



c) Further the service components are being mapped with the applications identified on the basis

of content management, transactions and workflow as specified below:

Service Component to Application Mapping

Content Based Components

Sl.No. Service Component Application

1. Package of Practices (For Seed) - Knowledge Management Application

- Seednet

2. Prices of Seed Products Knowledge Management Application

3. Dealer Network of Seeds - Knowledge Management Application

- License Application (L2) for Retailing

4. Quality Control & Assurance for Seeds - Knowledge Management Application

- License Application (L2) for Retailing

- Testing Lab Application

5. Seed Varieties - Knowledge Management Application

- Seednet

6. Quality of Crop Knowledge Management Application

7. MIS Reports Agri MMP Dashboard

Transaction Based Components


8. Grievance Management Grievance Management Application

9. Expert Advisory Expert Advisory Application

10. Seed Availability Dealer’s Stock Details

Workflow Based Components


11. License to Retail Seeds - License Application (L2) for Retailing




Workflow Based Components


12. Seed Certification - Seed Certification Application


d) The activities need to be performed under the scope are:

Creation of databases with respect to the service components and their applications.

Daily/weekly/Monthly updation of the databases

Retrieval of information through Graphical User Interface (GUI) based user-friendly

queries.

Generation and issue of periodic reports (Daily/weekly/Monthly/Quarterly/ Annually) to

Headquarters using the computerized system.

Initiation of service requests through service delivery channels (CSC, Department, KCC,

SCC, Private Kiosks, Mass Mobile, IVRS, Agri-clinics and Agri-business centers); which

would be processed by the Central and State Agriculture Portals (depending on the level

of service request generation and processing location).

1.3 Definitions, acronyms, and abbreviations

1.3.1 Abbreviations

SRS Software Requirement Specification

ISS Information System for Seed

CAP Central Agriculture Portal

SAP State Agriculture Portal

GAP Good Agriculture Practice

IT Information Technology

IVRS Interactive Voice Response Service

JD Joint Director

KCC Kissan Call Center

KKMS Kissan Knowledge Management System

KVK Krishi Vigyan Kendra

MIS Management Information System

MMP Mission Mode Project

MSP Minimum Support Price



NeGP National e-Governance Plan

NIC National Informatics Centre

POP Package of Practice

SAP State Agriculture Portal

SAU State Agriculture University

SMS Short Message Service

ICAR Indian Council of Agricultural Research

JDA Joint Director of Agriculture

ADA Assistant Director of Agriculture

SADO Senior Agriculture Divisional Officer

DAO Directorate of Agriculture

SME Subject Matter Experts

1.4 References

For Information on Seed

Final Detailed Project Report

Package of Practices (From JLNKVV) - Technologies for Productivity Improvement - Crop Production Techniques - Diary 2012 - Kharif Special Edition - Rabi Special Edition

Seed Control Orders, 1983 (DOA, Seed)

Seed net Portal (DOA, Seed)

http://mpsc.mp.nic.in/mpssca

http://mpkrishi.org

Discussion with Mr. Rajesh Paliwal, JDA, Seed and Mr. H. Omkar Singh, ADA, Seed

Material From NIC, Bhopal

www.bau-eagriculture.com

http://mahaagri.gov.in,

www.dbskkv.org (Dr Balasaheb Sawant Konkan Krishi Vidyapeeth)

http://www.pdkv.ac.in (Dr Panjabrao Deshmukh Krishi Vidyapeeth)

http://mpkv.mah.nic.in, (Mahatma Phule Krishi Vidyapeeth)

http://www.mkv2.mah.nic.in (Marathwada Agricultural University)

http://seednet.gov.in

http://kssca.kar.nic.in

AS-IS and TO-BE report

http://mpsc.mp.nic.in/mpssca

http://mpkrishi.org/

http://www.bau-eagriculture.com/

http://mahaagri.gov.in/

http://www.dbskkv.org/

http://www.pdkv.ac.in/

http://mpkv.mah.nic.in/

http://www.mkv2.mah.nic.in/

http://seednet.gov.in/

http://kssca.kar.nic.in/



1.5 Overview

1.5.1 Problems / Issues addressed by Agriculture MMP

Key limitation in the delivery of services in the agriculture sector has been the availability of, and access

to multiple service delivery channels that are there in the vicinity of the farmers and the private sector

at the grass root level.

The Agriculture MMP has been designed with a view to provide end to end services to the farmers and

private sector. During the Phase I and initial stages of the Phase II of the project, the project team

interacted with the above identified stakeholders through structured discussion to understand their

needs, key problems & issues faced and their requirements / expectations from the proposed solution.

The following section provides a detailed analysis of the key problems and issues faced by these

stakeholders that the proposed project is designed to address. These problems and issues have been

classified with regards to individual services that are proposed to be delivered through the Agriculture

MMP. The following table details the key problems and issues faced by the stakeholders.

SN Service Issues / Problems (Lack Of / Unavailability of / Access to)

1. Providing information

on quality seeds

- Localized GAPs & POPs in vernacular languages

- Multiple GAPs & POPs from a variety of sources across India

with not necessarily uniform information

- Timely information on GAPs and POPs

- Searchable information on region wise best-fit seed varieties

- Information on regional dealer network of seed suppliers

- Information on seed availability in the region

- Information on seed grower registration procedure

- Status update on seed grower registration applications

- Status update on seed certification applications

- Status update on licensing to sell applications

- Personalized resolution of queries related to seeds

- Time taken to process registration / certification / licensing

applications



1.5.2 Causes & Effects of Problems / Issues

To summarize, the key problems and issues with regards to the delivery of need based services, the

following can be identified / classified as the broad problem areas to be addressed under the

Agriculture MMP:

1. Content Capture / Generation

2. Content Processing / Customization / Localization

3. Content Storage / Archival

4. Information Dissemination

5. No IT enablement in processes

6. Inadequate Manpower

This section provides a detailed analysis of the above identified broad problem areas to articulate their

root causes and subsequent effects on the service delivery in the Indian agriculture sector.

Table 1: Root causes & effects of key problem areas

SN Problem Area Root Causes Effects

1

Content

Capture /

Generation

Lack of standardized

processes at State level

Varied process times which are inconsistent with

the needs of the farmers

2 Content

Customization

No clarity on roles and

responsibilities

Content customization not happening on time/ as

per need of the farmers

Timely access to

generated content Up-to-date information not available

3 Content Storage

/ Archival

Content mainly stored

as manual record

Not easily searchable & accessible

Limited circulation of documents

Limited & costly information dissemination

4 Information

dissemination

Lack of standardized

formats at the state

level

Differentiated quality of content across states

Lack of adequate

dissemination channel

/ training programs

Farmers ignorant of latest technology &

techniques

Loss of opportunity of better production

Farmers not getting right price for their



SN Problem Area Root Causes Effects

produce

5 Manual

processes

No IT enablement of

processes

Time consuming processes

Record management becomes difficult

No proper content management

Challenge to develop MIS

6 Inadequate

Manpower

Financial burden

Lack of trained

manpower

Large number of

villages

Content generation / processing is not on time

Agriculture productivity gets affected

Lack of guidance to farmers

Lack of training programs

1.5.3 Proposed Solutions Provided by the MMP

Keeping the limitations in mind the proposed technology solution strategically places key ICT

interventions to be used at the central, state levels separately and together, and aligns them with the

service delivery channels through appropriate networking and connectivity.

In addition, some of the existing ICT interventions that can be used for the delivery of the identified services have also been integrated in the proposed scenario. The proposed solutions under the identified service components are specified bellow:

Service Components Proposed Solutions

Information on - Good Agriculture Practices - Package of Practices

Online - Information updated every season - Changes uploaded - Available instantaneously

Information on - Prices of Inputs - Dealer Network & Seed Availability - Quality Control & Assurance - Seed Varieties -

Online - Information updated every season - Changes uploaded - Available instantaneously

- Online video - Front line demonstration

Online - Available instantaneously - Changes uploaded - To follow prescribed format



- Grievance Management - Expert Advisory

Status Tracking Online - Immediate Acknowledgement - Immediate Reference No. - Status change

Grievance Redressal Online - Initial response time - Redressal of grievance

Availability of forms Online Availability of service Online - 24 x 7 - 99.9% uptime

- License to manufacture, wholesale & retail - Registration of seed growers - Seed Certification

Application Submission Online - Immediate Acknowledgement - Application Reference No.

Availability of Forms Online - Available 24 x7

Status Tracking Online - Status Change

Verification of documents Online - Documents verified within 24 hrs of

application submission with Payment Physical verification / Field Visit - Parallel activity while documents scrutinized

at office - Inspection report submitted online Payment - Through Online Payment Gateway and - Draft and Challan



Availability of Service - Online, 24 x 7 - 99.9% uptime

1.5.4 Structure of this document

This document provides a detailed overview and purpose of the requirement specification of service 1 components. This document also discusses on AS –IS and TO-BE business processes.

This document provides the Overall Description about the project that includes product prospective and context, product functions, user characteristics, general and design constraints, assumptions & dependencies and acceptance criteria.

This document describes the Specific Requirements that include External Interface Requirements, Software Product Features, Performance Requirements, Design Constraints, Software System Attributes, Logical Database Requirements and Other Requirements. The workflow of the identified applications along with flow of actions will also to be described in the next sections.

External Interface Requirements of the software include user interfaces, hardware and communication interfaces, and interfaces with other software.

Software Product Features include all the functions that are required to be performed by the software and further for each of the functions the input required, processing involved, outputs and validation checks, if any. The functional requirements have been described in the form of use cases that depict the interaction between the actors and the system. Each use case includes preconditions for execution of the use case, triggering conditions that initiate the use case, post-conditions of the system after the use case is executed, normal and alternate flows, business rules, relationships with other use-cases, assumptions and special requirements, if any.

Design Constraints include standards, hardware limitations, etc.

Software system attributes include features like user-friendliness, Reliability, maintainability, security etc.

Logical Database Requirements include any information that is to be placed into a database, including

types of information used by various functions

frequency of use

accessing capabilities

data entities and their relationships

integrity constraints

data retention requirements

Data Requirements include a description of various entities in the system and their attributes.



2. OVERALL DESCRIPTION

2.1 Product Perspective

ISS (Information System for Seed) is one of the 12 Core software applications envisaged as part of

Phase II of the National e-Government Plan under Mission Mode project (MMP) initiated by the Ministry

of Agriculture which aims service orientation to farmers no matter if the services originate from the

central or the state government, they would be provided through a single delivery interface.

ISS will be a generic and Open Source software that capture the information and automation of

registration, licensing and certification processes for the manufacturing and marketing of agriculture

inputs and generates the reports in the pre define formats. The framework product would be prepared

under the sponsorship of Ministry of Agriculture, Government of India. The software would provide a

holistic view of the Processes involved in delivery of inputs followed by different Agencies (both Public

and Private) with respect to the Seed, for a better decision making and information delivery.

2.2 Product Functions

ISS will capture the details of the sub services specified in Chapter 1 under Scope section for the specified service components in the country. ISS will be divided into the major Sub Service:

Information System for Seed



2.2.1 Information System for Seed

2.2.1.1 Current (AS-IS) Business Processes State Department of Agriculture is having following business processes being managed manually:

Package of Practices

Notified seed varieties

Seed Prices

Stock Availability

Registration process to obtain new/renew/duplicate dealership license in seed

Seed Certification

Quality Control and Assurance Mechanism

Expert Advisory System

Grievance Management Existing process of each section is described below:

Package of Practices: The high power committee consisting of officials of agriculture and official of State Agriculture universities approves the content. After the approval, the contents on POP are published by Department Of Agriculture.

a. Notified seed varieties: The names of the seed varieties notified by Central Seed Committee applicable for the state fall under this category. Central Seed Committee notifies the released seed varieties by the State Seed Committee of the state. Seed database has been developed for seed division and available for access on seed net portal. This database is for all the varieties notified by Central Variety Release Committee.

The parameters of notified seed varieties covered under the seed net portal are: Crop Name, Variety Name, State & year of release, Notification Date, Notification Number, Institution responsible for developing breeder seed, Percentage, Agency maintaining breeder seed, Resemblance to variety, Adaptation and recommended ecology, Maturity, Maturity Group, Agronomic Features, Quality of produce, Morphological characteristics, Reaction to stress, Description of variety, Description of parents, Reaction to major diseases, Reaction to major pests, Average yield.

b. Seed Prices: Prices of the seed varieties applicable for the particular state falls under this category. The seed prices of the Government agencies are monitored by the state government but for private agencies/dealers, MRP of seed prices are being monitored and no dealer can sale the seed varieties more than the specified MRP.

c. Stock Availability: The quantity of the seed varieties available in the daily stock of the dealer falls under this category. At district level, the dealers are liable to maintain their daily stock details in a specific format.

d. Licensing Process to obtain dealership license in Seed: The applications submitted by agencies/persons who desires to obtain a dealership license to run a selling business in seed, falls under this category.



Workflow of the Dealership License Process is mentioned below:

Person/Agency/Manufacturer who

wishes to obtain dealership license

Fill application Form-A to

apply for registration

Deposit License Fee in

Bank/Treasury

Submit Form-A with

challan details and other

verification documents

mentioned in the form

check listVerify form details and

documents submitted

Approve

Form-A

details

Documents verified

successfully

Y

N

Reject Form

Issue dealership

license-Form B

Process Description:



Candidates willing to deal with seeds apply to ADO for their dealership in FORM-A detailing their name & address, place of business, capacity (proprietor/partner/Manager/Karta), details of seed to be handled etc (Form A-enclosed in Annexure 2.

e. Renewal of the dealership license: The dealers/wholesalers/retailers whose dealership license has been expired or about to be expire, falls under this category. The expired license has to be renewed within 30 days of its expiry date.

License fee for seeds are –

New License – Rs. 50/- Renewal of License – Rs. 20/- Actors Involved in MP:

Dealers License for seeds (at District level)

S. No Actor Activity performed

1. Applicant Fill Form A, along with initial details for issue the license

2. Assistant Official (ADO) Physical verification & Acceptance of documents

3. DAO (Dy. Director) Assign the inspector for site inspection & Issue License

Actors Involved in Jharkhand

Dealers License for seeds (at state level)


1. Applicant Fill Form A, along with initial details required for issue license

2. Assistant Official Physical verification & Acceptance of documents

3. Field Inspector Physical verification

4. DOA Assign the inspector for site inspection & Issue License

Dealers License for seeds (at range level)




3. JDA Assign the inspector for site inspection & Issue License

Dealers License for seeds License (at District level)






3. DAO (Dy. Director) Assign the inspector for site inspection & Issue License

Actors Involved in Karnataka:


1. Applicant (Dealer) Fill Form A, along with fee at Taluk ADA Office

2. Taluk ADA/ RSK Officer Physical verification & Acceptance of documents, Sale Point Inspection and Sending Recommendations to JDA at District level.

3. District JDA Issue License (New & Renew)

Actors Involved in Assam:

Dealers License for seeds (at state level)


1. SDAO Fills the document like storage capacity Inspector report

2. Director Agriculture Approves application for new license Reject licenses application with reason

3. JDA(pulse) Put Comments Forwards document to DDA(seeds) Forward documents to Director Agriculture

4. DDA(pulse) Put Comments Forwards document Dealing Assistant and JDA(pulse)

5. Dealing Assistant Puts comments Sends document back to DDA(seeds)

Dealers License for seeds (for a particular region)


1. ADO Fills the document like storage capacity Inspector report

2. SDAO Approves application for new license Reject licenses application with reason

Actors Involved in HP


1 Additional Director of Agriculture License Issuing authority 2 ADO and DDA Verification of documents and



application acceptance 3 Seed Inspector Inspection Report Submission 4

f. Seed Certification & Quality Control Mechanism: The seed varieties which are available to be

maintained and make available through certification, high quality seeds and propagating materials of notified kind and varieties so grown and distributed as to ensure genetic identity and genetic purity up to certain prescribed standards of physical purity, physiological quality and health in seed or in propagating materials falls under this category. As is Process of M.P

Functioning Seed Certification Agency is an organization directly under the control of state government. This organization is authorized to certify the seeds before coming into the market. This agency certifies seeds in three ways. The three ways are –

1. Seed Certification of fresh seeds. 2. Re-Processing and Certification of rejected seeds. 3. Re - Validation of Certified seeds whose validity period has expired.

These three ways of seed certification is briefly described below: -

S.No Actor Activity Performed

1. Seed Grower/Producer Submit Form-1

2. SCO Receives Form-1, Accepts Form-1, Issue Inspection dates to the inspectors, Issue tags

3. Field Inspector Inspects fields, fill inspection report, Issue Threshing Certificate, Process seeds at the Processing Center, Sample collection at Processing Center

4. Concerned officer of SCA-HO

Generate Certificate No , Packaging & Tagging & Sign Off

1) Seed Certification of fresh seeds:

The certification involves several phases described below by the block diagram –

Sample

Procurement

Registration

Field

Inspection



ocess for Issuing Seed Certificate

Registration Phase

The Seed Certification Agency certifies two categories of seeds. They are – Foundation Seed Certified Seed

These categories are further divided into several stages like F1, F2, and F3…. etc and C1, C2, C3…etc for Foundation Seed and Certified Seed respectively. The color of tag attached to seeds is white for Foundation Seed and blue for Certificate Seed. Any farmer who is interested to cultivate the certified seed can register himself directly or through Seed Production Company. The farmer has to register for each season viz. Summer, Kharif and Rabi. There is no minimum or maximum limit of proposed land for which the farmer can register. The farmer has to fill the registration form and submit it along with the registration fees to the inspector at the field level if he is directly registering. If he wants to go through the Seed Production Company then he submits the form to the company and then the company compiles all its registration form, received from the farmers under the given division, and submits it to the inspector. The farmer has to submit a new registration form for each type of crops and for different varieties. But a one-time registration fee will only be charged from the farmer for a given season.

After getting registration form the inspector at field level gives a registration no. to the farmer which is unique for a season. All the crops of different varieties for a given farmer are registered under this unique registration no. for a season. The inspector then sends the Registration Form to the concerned Division and to the Head Office.

At the divisional Office a register is maintained which records the summary of all the registration done under that division. The registration Form entries are done in this register. After this Divisional Office send the notification of the recorded Registration to the Head Office, Inspector, and the farmer who has been registered.

The notification of the registration is sent to the inspector who is supposed to inspect the field. The notification is generated according to the inspector wise i.e. if the inspector brings collection of Registration Form, and then notification will contain the records of all the producers whose application was brought by him. At this stage when the inspector receives the Notification of registration he enters this information in his Crop Register.

Field Inspection

After the farmer is registered the inspector at the field level inspects the field to check the physical controls affecting the crop. During inspection of the field the inspector inspects each unit separately. A unit is composed of maximum of 10 hectares of land and if land separation is more then it can be considered as separate unit and moreover a unit should have crop of same type and variety. Each unit can be inspected at most four times. During inspection the inspector identifies whether the said seed is sown or not. For each crop the Seed Certification agency has set prescribed methods and standard of cultivating it that has to be adopted by the farmer. The inspector also checks these norms during the inspection. If the inspector feels unsatisfied with the field condition he can reject the field fully or partially for seed certification program. Besides getting rejected a field can also be fully or partially

Sample

Processing

Sampling

&

Testing

Packaging

&

Tagging



failed by the inspector due to damage caused to the crop by the weather and other natural calamity. Depending on the crop there can be at most four inspections. The inspection report will be sent to the Head Office, Seed grower and Divisional Office. The inspector will keep one copy of the report himself. After the final inspection the inspector enters the important information of the inspection in his Crop Register and also generates the Lot No. For a single farmer many inspection reports can be generated because one inspection report is generated for each inspection unit and a farmer can have many units. The inspector issues Lot No to seeds for each crop of same type and same variety and whose quantity is within the max limit set by the seed certification agency. The Lot Number are generated after the last inspection according to the rule –

Month of Harvesting - Year – State Code – Processing Plant no. – Registration No. – S.No of Different crop of same farmer - Seed Stage – Different lot of same crop

After the Lot No is given to the seed they are always marked with this Lot No, wherever they are sent, so that identity of the seed is maintained throughout the process of seed certification. The Lot No are sent to the Processing Center and to the divisional office. The inspector also keeps one copy of the Lot No.

Sample Procurement

The seed certification agency has set several standards and processes for each crop to be followed by the farmer during the Harvesting & Threshing of the crop. The farmer should follow the guidelines to maintain the high quality of the seed being generated. The farmer should inform the concerned officer of the seed certification department at least three days in advance. So that if the concerned officer feels it necessary he may visit the field. After the threshing is complete and the inspector is satisfied with the entire method he issues “Threshing Certificate”. The seeds are kept in a clean bag and are sealed by the farmer in presence of the concerned officer. The farmer marks the seed bags with his name and Registration no and transports it to the Processing Center, which he has mentioned in the Registration Form. The Seed Processing Center must be authorized by the Seed Certification agency.

Processing

At seed processing center the inspector is present who monitors the processing process and records the result of the processing. The processing of the seed includes Drying, Cleaning, Grading and Treatment of the seed. After the entire processing is over the quantity that is found to be of required standard is kept separate.

Sampling & Testing After the seed processing is over three samples are taken from each processed seed Lot. These samples are send to the Head Office and Seed Grower. The inspector keeps one sample. The procedure of sampling should be done according to the standards prescribed by the seed certification agency. These samples should be send to the Laboratory within three working days by the Head Office. Packaging & Tagging



After getting the results from the Seed Testing Laboratory the Seed Certification agency issues a certificate to the seed. The main copy of the Certificate is sent to the seed grower and one copy is kept at the Head Office and at the concerned Divisional Office. After the certificate is issued the seeds are packed in the small bags in which they are supposed to be sold. The tags are put on the bags and the bags are sealed so that after the tagging nobody tampers with the seed and hence causing damage to the seed's quality. The concerned officer, of the Seed Certification agency, present during the packaging and tagging also puts his signature on the tag.

1) Re-Processing and Certification of rejected seeds:

The farmer whose lots have been rejected due to negative results can apply for Re-Processing. For this he writes an application to the Seed Certification Office. If the farmer gets permission for Re-Processing his whole lot is again processed. For this entire process Re-Processing & Seed Test Fees is charged from the farmer. After the processing is over a sample is taken from each lot and sent to the Laboratory for testing. The Lot No is the old one but the Sample Coupon with new Sample Coupon No is generated. After getting the seed results the process of Packaging and Tagging is followed as was done previously. If the seed are rejected during the Re-Processing then they get permanently rejected and the farmer can’t apply for Re-Processing it again.

2) Re -Validation of Certified seeds whose validity period has expired:

The seeds are certified only for restricted period. After this period the seed owner has to apply for Revalidation. For this the seed owner has to fill the Revalidation Application Form and submit it along with Revalidation Fees to the Head Office of SSCA. At the Head Office if the request for Revalidation us approved then the seed again goes through the seed processing and seed-testing phase. The seed following the prescribed standard are revalidated. The revalidated seed is either given new tags or the extended date is stamped on the old tags. As Is Process of Jharkhand


1. Applicant Submits Form-1 for Registration

2. SCO Received Form-1 and sends it to HQ, Inspects farm, collects samples for testing

3. Dy. Director, SCA Issue Certificate of Registration

4. STL Test Samples and send testing report to SCO, HQ-SCA

5. SCA-HQ Issue Certificate

SCO inspects the farming of Seed

as per rule.

Filling of

Application Form

for Seed Grower

Registration-

(Annexure A)

Receipt of Source

of Seed, Plant

Description

(Annexure B1, 2)

Submit the form,DD

& Documents to

Seed Certification

Officer

SCO send one Copy to HQ and

copy remains with Him

HQ issues Crop Reg. Certificate & inspection letter to Seed Certification



As Is Process of Maharashtra

SEED CERTIFICATION PROCESS - By District Seed Certification Officer Ahmed Nagar



As Is Process of Karnataka

Phases of Seed Certification

Certification shall be completed in six broad phases listed under

Receipt and scrutiny of application.

SEED GROWER

APPLY FOR SOURCE VERIFICATION (

RECEIPT OF PURCHASE,CROP VARIETY ,STAGE, NAME OF PRODUCER,

QUANTITY)

SOURCE VERIFICATION BY DISTRICT SEED

CERTIFICATION OFFICER (DSCO ) (FORMAT)

REGISTRATION

(CERTIFICATE FORMAT )

FIELD INSPECTION

REPORT (FIR) (FORMAT )

SEND TO PROCESSING PLANT

ALONG WITH FIR & T.C

(MALANI CERTIFICATE)

CODING & SAMPLING

BY COMMITEE

FORMED BY DSCO

QUALITY PROCESSING

CLEANING & GRADING FIELD TRIAL (FT) (TO FARM DECIDED BY DIRECTOR OF SEED

CERTIFICATION AGENCY

( ONLY FOR FOUNDATION SEEDS) GOOD LOWER

SEED TEST LAB

PASS FAIL

PASS FAIL

Release Order (

Format)



Verification of seed source, class and other requirements of the seed used for raising the seed crop.

Field inspections to verify conformity of the standing crop to the prescribed field standards. Supervision at post harvest stages including processing and packing.

Seed sampling and analysis, including genetic purity test and / or seed health test, if any, in order to verify conformity to the prescribed standards and

Grant of certificate and certification tags, bagging and sealing.

Seed Certification Procedures

All the seed material to be used for seed production programme is subject to verification by the Agency. The seed producer should submit to the Agency relevant evidence such as certification tags, seals, labels, seed containers, purchase records, sales records etc., as may be demanded by the Agency during scrutiny of the application and/or during the first inspection of the seed crop in order to confirm that the seed used for raising the crop has been obtained from a source approved by the Agency and conforms to the class of seed required for seed production. A source-verification register containing relevant information as prescribed should be maintained by the seed producer for verification by Agency staff.

After source verification application for certification should be submitted in the prescribed FORM-1 in triplicate to the concerned Assistant Director of Seed Certification. FORM-1 is available with the divisional and zonal offices of the Agency.

FORM-1 should be submitted within 30 days from the date of sowing or 15 days from the date of transplanting as the case may be.

The relevant seed certification charges such as Registration fee, inspection fee grow out test charges (wherever necessary), seed testing charges, etc. should be remitted along with FORM-1, (See Annexure-1)

Separate FORM-1 should be submitted for certification of each variety. The FORM-1 should contain complete details of the name and address of the seed producer; season of production; name and address of the grower; location of the seed plot; crop/ variety and class of seed to be produced; area under seed production; details of parental seed materials used with lot number; date of sowing and the particulars of seed certification charges remitted.

In a single application, the maximum area that can be offered for certification is 25 acres. Additional area will require separate application.

No refund of inspection and registration fee will be made once the seed plot has been visited / inspected by the Seed Certification Officer.

The seed producer should assist the Agency staff in locating the seed plots during the first inspection.

Seed producers should guide their growers in agronomic practices, pest/disease control etc., for seed production.

Only seed from plots meeting all the prescribed field standards for certification is accepted for processing at the recognised seed processing plants.

All the necessary care should be taken to avoid admixture during harvesting, threshing and transportation.

Harvested seed produce from the approved fields should be brought to the seed processing unit and seeds are certified within 2 1/2 months from the date of harvest.



Certification of a seed lot will be taken up only if the seed lots has met the prescribed field and seed standards.

Work Flow:

As Is Process of Assam Actors involved:-


1 Applicant Fills the form 8/86

2 ASCO

Registration of Farmer as seed grower



Inspection report

Certification of seeds

3 Director ASCO

This process is sub-divided into three sub-processes as all three sub-processes are independent but occur sequentially, though it is not mandatory that after one process another must occur. The Following are three sub-processes:-

Registration of Farmer

Inspection of Farmer crop & Seed Certification

Registration of Farmer / Institutional as seed growers:-

Actor involved:-

Applicant; ASCO; Director ASCO


1 Farmer Gives application

2 Institutional Gives application

3 ASCO Register Farmer

4 Director ASCO Generate Lot No

Here applicant means Farmer / institutional.

Input:

Registration form given to applicant –Form no 8/86

Process:

The applicant fills the registration form and pays the registration fees.

The ASCO (HQ) shall enter the farmer/institutional details mentioned on the form

The ASCO (HQ) shall also enter Type of seed, payment detail - Application Fees; MR No, Bill No, Date

The Director of the ASCO generates the Lot No.

Output:

The Farmer is registered and its detail is stored in the database.

Application Register1

1 Note: Seed Type this have three values that are F-C1; B-F; C1-C2

BUSINESS RULE FOR REGISTARTION FORM

Rule Business Rule

1 Note : Seed Type this has three values that are F-C1;B-F;C1-C2



ID #

1 On a single registration form a farmer can register up to 10 hectare of land for a single variety of a crop.

2 For a farmer/ Institution Registration fees of Rs 10 per application upto 10 hectare in one variety of crop.

3 The Lot no is generated as follows :-

<Harvesting month of month of crop><harvesting year><state code><lab Code><ASCO Code><sequential number>

Note: ALL the ASCO belong to zone. At present there are three zones .these zones have the zone code.

Zone Codes are as follows:-

S.No Zone Name Zone Code

1 Guwahati 01

2 Jorhat 02

3 Silchur 03

ASCO also have ASCO code

The harvesting crops also have the harvesting month –details are with ASCO

Formats used by the stakeholder for Registration as seed growers are as follows:-

S.No Name of documents Document used by Purpose

1 Form 8/86 Farmer; Institutional seed growers

To give application for seed registration growers

Inspection & Certification of Farmer /Institutional Crop:- Farmer; Institutional grower; ASCO; Seed Analysts, Junior Scientific Assistant; Senior Scientific Assistant

Input:

Lot Number generated by ASCO Director

Process:

The Registered Farmer/ intuitional seed growers pays the inspection fees.

The ASCO does three inspections and generates three type of inspection report.

The Inspection is carried out in three stages these are as follows:-

Transplanting to Tailoring

Growing Stage to Flowering stage

Pre harvest Stage



The three crop Inspection reports are submitted to the director ASCO; these reports can also

be submitted individually.

Once the Inspection is done and the seed is collected by ASCO. (No charge for Testing of

seed).The ASCO makes entry on seed sample collection card. The ASCO gave the seed to

Junior Scientific Assistant.

The Seed Analysts test seeds.

The Junior Scientific Assistant / Senior Scientific Assistant / Seed Analysts make entry on the

Analysis sheet.

After the testing has been done the Junior Scientific Assistant / Senior Scientific Assistant /

Seed make seed analysis report.

This report is submitted to SDAO (Seed Testing officer).

The SDAO send this report to Applicant/ Concern ASCO.

After this the ASCO can give certificate- Rule number 3

The seeds are tested in the Lab.

Once Seeds are testified Ok the certificate is issued to the farmer.

Output:

The Seed Analysis report

Crop inspection report

Joint Inspection Note of seed production.

The Seed Certificate

BUSINESS RULES LIST

.

Rule ID #

Business Rule

1 For a institution registered growers the inspection change for foundation seed is Rs 225 and for Certificate Seed it is Rs 200

2 For a Farmer it is Rs 100 /10 hectare for single crop

3 Tagging Charge Rs 5/tag

Supervision charge Rs 4/ quintal

Sealing Charge Rs 1/bag

Formats used by the stakeholder for Seed Testing & Certificate as follows:-



S.No Name of documents Document used by Purpose

1 Sample Collection card ASSCO Details of the seed sample

2 Seed Analysis Report

Junior Scientific Assistant Senior Scientific Assistant; Seed Analysts ; SDAO(Seed Testing officer)

Contains details of seed analysis

3 Analysis sheet Junior Scientific Assistant Senior Scientific Assistant; Seed Analysts ; SDAO(Seed Testing officer)

This contains details of the analysis

As Is Process of Kerala

S. No Actor Activity Performed

1. Seed Grower/Producer

Submit Form-1

2. SCO Receives Form-1, Accepts Form-1, Issue Inspection dates to the inspectors, Issue tags

3. Field Inspector Inspects fields, fill inspection report, Issue Threshing Certificate, Process seeds at the Processing Center, Sample collection at Processing Center

4. Concerned officer of SCA-HO/ADSO

Generate Certificate No , Packaging & Tagging & Sign Off

As per the standard procedures laid down in the certification manual-

• The seed grower submits form-1 at the division level (ADSC). After scrutiny of the Form-1 the form is forwarded to the SCO () for approval and necessary sanctions. The SCO gives the field inspection dates to the divisional level. The field inspector (FI) at the division level inspects the field at regular intervals as per the details provided in Form-1. The FI prepares Field Inspection Report (FIR) recoding the observations made. The expected yield, area inspected, area rejected details is provided by the FI.

• After the production of seed, it goes for processing and then tagging and bagging. Quality seed is then packed by using the tags issued by the SCO/ADSO. After tagging and bagging, Form-2 certificate is issued to the seed grower.

g. Expert Advisory System: Presently, there is no automated system to provide expert advisory to

the farmers or the citizens. There are few KCC, who provide IVRS based expert advisory to the



farmers. Now days, expert advisory to the farmers is either provided by R.A.E.O in the fields or farmers calls at the KCCs to get advisory and recommendations. If the experts at the KCC don’t become able to provide recommendations to the farmers, calls are either forwarded to the SMEs of agriculture universities or other research institutes. Depending on the type of the query raised, it is also forwarded to the concerned department of the DOA.

h. Grievance Management: Presently, the grievances of the farmers/citizens are handled by the concerned departments manually. Farmers may approach to R.A.E.O, Kissan Call Centers, Block/division/district level agriculture departments or the Directorate of Agriculture, State to raise grievances related to various categories like seed prices, availability of stock nearest to the farmers’ area, subsidy details etc. The grievances of the farmers are addressed by the departments. If the grievance doesn’t belong to that department, they are directly rooted to the next concerned department. Similarly, KCC handles the grievances of the farmers telephonically. If they are unable to address the grievances of the farmers, they transfer that call to the next level.

2.2.1.2 Proposed (To-Be) Business Processes and Functional Requirements After the new system is in place; the high level interactions of all primary and secondary users with the

system will be as shown in the below diagram:

CAP/SAP Web

Page

Seed,Fertilizer,

Pesticide

Soil Health

Training, Farm

Machinery, GAPForecasted

Weather

Prices arrivals, Procurement

points, providing interaction

platformsImport/Export-e-

CertificationMarketing

Infrastructure

Monitoring

implementation/

Evaluation

Fishery

Irrigation

Infrastru

cture

Draught Relief

and Management

Live-

stock

Agriculture Dept. Workstation Server

Dealers/

Manufacturers/

Agencies/

Farmers/Citizens

Primary Users

Secondary Users

DOA

MOA

KCC

AU’s

Government and

Private Institutions

High level interactions of all primary and secondary users with the system



Each of the proposed new applications for the Agriculture MMP is envisioned to be constituted of

modules that are either core or configurable in nature.

A. Core Modules

Core modules can be identified as modules whose functionalities cannot be changed from application to

application. Their functionalities remain consistent irrespective of the application deployment location

or the users using them. From a functional perspective the following modules would be required as the

core modules in this application:

A1. User Management

The user management module would be used by the different stakeholders at various levels to log into

the portal and enable them to use functionalities such as user creation, user access controls and user

deletion.

Sub Modules to be covered under user management module are:

Role Management

User Group Management

User Creation and Authentication

A2. Payment Gateway

The payment gateway would be used by the end beneficiaries (farmers and the private/government

sector) to make payment towards conducting various activities like application for registration to get

dealership license and its renewal in seeds, fee for the tests for seeds samples that have been provided

to the testing labs. The module would allow for payments to be made through internet banking, debit

cards, credit cards, cash and direct debit.

A3. Status Tracking

The status tracking module would assist the farmers and private sector to track the status of their

current application for registration, licensing, certification and testing, which is assumed to be in

processing. The module would allow the user to trace the application using the unique application

reference number generated at the time of submission.

B. Configurable Modules



Configurable modules can be identified as those, whose functionalities can be altered to facilitate state

level variations in work-flows and transactions.

B1. Content Management

The content management module would assist the government and private agencies to specify the

content and its updates related to the specific service area, so that the information available on the

portal would remain dynamic and could be utilized for decision support system by the government.

Content management system hosted on CAP/SAP will facilitate the content creation & management and

searching of contents (for the contents like PoPs, testing manuals, Rules and Acts etc) based on

keywords as well as full search.

Package of Practices

Package of Practices are being described in the Service-3 « Providing information on Good

Agriculture Practices, Crops, Training and Farm Machinery.» However, seed related following

parameters should be considered while preparing structure of PoPs :

Crop Wise

Land/ Isolation Requirement

Nursery :

Land selection

Sowing time

Nursery bed preparation

No of seed beds

Nursery bed manuring

Seed source

Seed Treatment

Seed Quality (Moisture Content, Germination % and Seed Vigor)

Classes of Seed (Breeder Seed/Foundation Seed/ Certified Seed)

Notified Seed Variety

Seed rate

Sowing method

After-care

Seedlings uprooting



Transplanting & Management of crop :

Land preparation for transplanting

Fertilisation

Transplanting method

Spacing

Thinning

Water management

Weed control

Plant Protection

Rouging-Harvesting & Threshing

These parameters have been referred from the website of Tamilnadu Seed Certification Department

(http://www.seedtamilnadu.com)

Seed Processing : Information specified under seed processing is- Seed Processsing, Seed drying,

Seed cleaning & upgrading, Seed treatment, Seed packaging and Handling, Seed storage.

Seed Marketing : Information specified under seed marketing is- Selling, Purchasing, Company

Registration

Seed Testing : Information specified under seed testing is- Introduction, Receipt & Registration,

Sampling, Physical purity, Germination, Moisture, Seed health and Genetic purity results

Seed Testing Results : Information specified under seed testing results is- Lab test results and

Genetic puring results

Seed Certification Standards: Information specified under seed certification is- Notified Varieties,

Morphology of all varieties, Eligible varieties, Seed certification procedure, seed certification

standards, Morphology of specific varieties, Indian Minimum Seed Cerification Standards.

Seed Certification Standards are available on Seed Net Portal. A link will be provided on SAP to

navigate to the Seed Net Portal to access these standards.



Seed Legislations : Information specified under seed lagislation is- The Seed Act 1966, The Seed

Rules 1968, The Seed (Control) order 1983, PVP Act 2001, PVP Rules 2003, EPA 1986, EP Rules

1986, New Policy on Seed Development 1988

Integration with Seed Grid portal of Madhya Pradesh : SAP of MP should have a link to Seed Grid

portal for contents related to seed sampling, seed use and seed subsidy.

Managing Notified/De notified Seed Varieties

As the notified seed varieties are specified by Central Government. The workflow to access this

information from CAP or SAP to the application is given below:

Since notified seed variety database is already implemented database on Seed Net portal. It

should be integrated with CAP/SAP database through web services/replication of data.

However the existing database is having information on all notified seed varieties by center and

filtration of state wise seed varieties is need to be added.

Alternative Solution:

Released Seed Varieties

SA

PA

cto

rU

ser/

Citi

zen

ISS

Y

Notified seed varieties applicable for

the state through out the application

for maintaining dealers stock

information, Package of Practices,

issuing dealership license etc.

N Print DetailsModify seed

varieties Search Contents

Modify the Status of released seed

varieties (as Notified/De notified)

when notified/de notified by

gazette notification by center

Get deliverables

Is details verified

and approved?

Get the notified

seed varieties

details

Select Season i.e.

Rabi or Kharif

Actor logs into the CAP

with the assigned

privilege of specifying

notified seed varieties

Specify State released

seed variety details like

Crop Name, Seed Variety

Name



Managing Prices of Notified Seed Varieties

The workflow to access this information from CAP/ SAP to the citizen is given below:

Use

r/

Citiz

en

ISS

Acto

rC

AP

/SA

P

Actor logs into CAP/SAP

with the assigned

privilege of specifying

prices of notified seed

varieties

Specify prices of

notified seed varieties

Select Season i.e. Rabi

or Kharif

Prices of Notified seed

verities for state will be

displayed in the SAP in

local language.

Select State and notified seed

variety in local language

Are prices

verified and

approved?

Y

N Modify prices

Search Contents

Get the prices of

seed varieties

Print Details

Get deliverables

Prices of the seed varieties

will be accessible through

out the application

B2. Document Management

During the application process for the registration, licensing, testing of inputs and samples i.e. Seed. it

may also be required to manage pre-prepared documentation pertaining to the application. These

documents are envisaged to be handled by the document management module through functionalities

including document upload and download, document review & edit, and deletion of documentation for

re-submission (or as the case may be).

The document types to be managed are:

Add Attachement

Drop Attachement



B3. Managing availability of seed

Dealer Registration Process

SA

PL

ice

nse

d

De

ale

r Access SAP Home

Page through typing

URL on the browser

Access New

Dealer

Registration Form

Specify

registration details

Is detail Freeze

and Submit?

Auto Generate

Password

Send SMS/e-mail

alert to the dealer

Save Details

Send reference

link to the dealer

through e-mail for

updating and

freezing

registration details

Generate alert

message on the

screen regarding

reference link

NY

Dealer’s stock details application over the web

Maintaining Dealers Stock Details Over The Web

ISS

Lic

en

sed

De

ale

rsS

AP

Selects Stock

OB interface

Specify daily stock OB

details: Quantity

Received, Quantity

Sold and Sale Price

Save

Details

Edit Stock OB

Details

Freeze

Details

N

Y

Store Details

in the

database

Display dealer

wise-Area Wise

stock details

Y

N

Reminder to

update stock

details

Log on to the

SAP

Access ISS

application



Updating Historical Database of the Licensed Dealers Area wise dealer’s details are maintained by Dy. Director of Agriculture at the District level.

Sta

te

De

pa

rtm

en

t/

Ag

en

cy

ISS

SA

P

State Officer/Distribution

Company

Select dealers registration

form interface

Specify Existing dealer data in

dealer registration form

Generate dealership

unique id

Y

<Alert System> Send SMS

NFreeze

detailsSave Details Edit detailsY

Logon to SAP

home page

Access ISS application

Main Page

Alternative Solution: Dealer’s database is available on Seed Net portal. This database could be

accessed on SAP through web services/replication of data.

Dealer’s Stock Details application through NIC SMS Gateway (Mobile Application)



Updating Stock Details through Mobile Application

Lic

en

se

d

De

ale

rsS

AP

ISS

Mo

bile

Ap

plica

tio

nm

ISS

da

tab

ase

Access mobile

application installed

on his mobile

Update

information on

SAP database

Specify Dealership

Code and Register

Configure Database

Parameters

Send SMS to

the mISS

database

Y

N

Send SMS to the

farmer for stock

availability

Y

Is Register

Successfully

?

N Flash message for

wrong dealership

code

Successfully

Configured

Parameters?

Update Stock

details in the

application

Successfully Enter

4 digit PIN and

Saves data

B4. License Application Licensing module will facilitate the private/government agencies, whole sealers, dealers and retailers to submit their application forms to obtain various manufacturing and dealership licenses, certificate and test results against the given samples. The Modules to be managed are:

1. Application Form to obtain dealership license to carry on business in seed (Common for all States).



Note: The role of the acceptance officer is not mandatory for all states and application will be directly forwarded to the LIA. There will also be a configurable mechanism to process the application from one level to another or one authority to another.

B5. Seed Certification Process at SCA to obtain seed certification

Seed Certification & QA

SS

CA

Hea

d O

ffice

SA

PS

eed

Gro

wer

/

Pro

duce

r/Ins

pect

orD

ivis

iona

l/Dis

trict

See

d C

ertif

icat

ion

Offi

cer

Actor logs in to

SAP

Application

Receipt

Component

Payment

ComponentForm

Availability

Information

Component

Document

Verification and

application

acceptance for

Registration

Is application

accepted?

Reject

Component

SI inspects the seed

grower field mentioned

in Form 1

Generate Release

Order &

Certification No

Is processing

complete as per

norms?

Y

Enter FIR-

I,II,III,IV

Generate Lot

No and

Sample

Collection

N

Status Tracking

Component

Print

Y

HO Receives

Registration

Acknowledgement

Auto Generate

Registration No

Submit

Form1

HO issues order

for Field

Inspection

Seed Inspector

receives the

inspection order

N

Is Form-1 self

Submitted by

Grower?

Submit

Source

Verification

Report by

SCA

separately

Y

N (Form1 submitted by Producer/Inspector

Generate

Registration

Acknowledgement

Send Acknowledgement

Copy to SCA HO/

Producer/Grower/

Inspector as per scenario

Is Report OK?

Send Copy to the

Grower/Producer/District/

Divisional Office and HO

Send Copy to the Processing

Center/Grower/Producer/District/

Divisional Office and HO

N

Y

Specify/Upload

test card result

Note: Seed Certification Process has already been developed in Seed Net. It is a generalized G2G solution presently implemented in Karnataka. The same should be implemented in other states also. However, the existing system can be made more service oriented as per the proposed solution.



B6. Seed Testing Laboratory and Quality Assurance:

The process relates to the phases of the Seed Testing Laboratories.

Seed Testing Laboratory

Fie

ld

Insp

ecto

r/

SC

O/D

OA

ST

LS

AP

SC

A-H

O/D

OA

/

Insp

ecto

r

Actor logs on to the SAP

Specify Sample

collection details

Is result OK?

Verify Physical

Samples with

the specified

sample details

Sends results to

Divisional Office

YAccept and

send samples

for testing

Send SMS alert for Test

Card Generation to

Seed Grower/Producer

E-

Mail Test Card to

SCA-HO/ divisional

Office/Inspector

N

Rejection

Component

Status

TrackingPrint

Specify Test

Result Report

Generate Test

Card and MIS Test

Reports

B7. Manage FAQ FAQ should be a common module on SAP for handling FAQs of all categories. There should be three major categories i.e. seed. Pesticides and fertilizers w.r.t service-1 The manage FAQ module would facilitate the assigned FAQ manager/User to add the frequently asked questions related to the selected FAQ Category from the list of FAQ Category. The specified FAQs would be available for modification and deletion. This module will also provide a provision of adding a new query along with answers. The FAQs published by the assigned FAQ manager would be available on the portal. The farmer or the citizen can add a new query; the answers related to their queries are not available in the FAQ list. The newly added query would be forwarded to the SME of the respective sub service for his/her advices. The Sub Modules to be managed are:

Manage FAQ

Manage FAQ Category

Add New Query



Answer Query Workflow to add FAQs in the system is given below:

Save FAQ

Is

Answer

specified?

Forward to the

FAQ Manager to

verify and Publish

Is Publish N Modify FAQ

Y

FAQ Display on

SAP/IDSQSFP

Home Page in the

available link

Y

N

Select FAQ in Add

FAQ option

Citizen View

Answers in FAQ

Is Citizen Finds

Answer?Y Print Answer

N

Add New QueryForward to the

SME

Stop

Add Answer

Add FAQ

Actor logs on to

the SAP/

Application home

page

Start

Stop

B8. Expert Advisory It is proposed to be a common application hosted on SAP for all the services. The expert advisory module would facilitate the SMEs to provide the advices against the queries received from the farmers and citizens. If the query is not relevant to the SME, it could be forwarded to the concerned SME. In case the SME doesn’t become able to give advice within 24 hours of the query submission, it will automatically be forwarded to the next authorized expert for his/her advice. The Modules to be managed are:

1. Query Acceptance and Managing Expert Advisory



E1 Officer

receives query

details

Forwards to

concerned E1

Officer

Forwards to

concerned E3

Officer

Forwards to

concerned E2

Officer E1 Officer

answers the query

E2 Officer

receives query

details

E3 Officer

receives query

details

Uploads

information in SAP

Is the query for

his Department

Can the Query

be handled by

E1 Officer

Can the Query

be handled by

E2 Officer

User Registers

Query

SAP forwards

Query

Application

Receipt

Component

Form

Availability

Component

Status

Tracking

Component

Information

Component

Delivery

Component

Receives Status Print Responsestart stop

SAP forwards the

query to the E1

Officer

State

Agricultural

Portal

Kissan

Call

Centre

State/

Block/

District

Level

SAP

Level

User

Level

Best

Practices


KCC

CSC,SSC,Agri

Clinics, Agri

Business Centres

Mass

Mobile,

IVRS

SAP forwards

Query to State

Level Officials

State Level Official

answers the query

Uplioads

Information in SAP


Process of the Expert Advisory System

User logs into SAP and fills-up form in Query Management Application

Module generates a unique reference number and intimates user about successful registration of query.

It forwards query to the State Level.

State level officer will answer the query if possible otherwise State Level Officer is forward the query to

Level one office.

He will check for relevance of the query and if query is not for his department, he forwards query to

concerned department’s E1 officer



If E1 officer can resolve the query, he does so and uploads information on SAP/CAP. If he can’t resolve

the query, he forwards query to concerned E2 office.

If E2 officer can resolve the query, he does so and uploads information on SAP/CAP. If he can’t resolve

the query, he forwards query to concerned E3 officer.

E3 officer resolves the query and uploads the information on CAP/SAP.

User enquires about the status of query handling by entering reference number in the “status tracking”

module of the application.

User views answers to his/her queries by providing his unique reference number.

B8. Grievance Redressal It is proposed to be a common application hosted on SAP for all the services. The grievance management module would facilitate the farmers/general citizens to raise their grievances related to the selected sub service. The raised grievances would be forwarded to the assigned person to address the grievances. Grievance Redressal Management System Process Flow

Forwards to

concerned

Director of

Agriculture

Nodal Officer

answers the

Grievance

HOD receives

Grievance details

DOA receives

Grievance details

Uploads

information in SAP

Is the

Grievance for

his Department

User Registers

Grievance

Application

Receipt

Component

Form

Availability

Component

Status

Tracking

Component

Information

Component

Delivery

Component

Receives Status Print Responsestart stop

Y

SAP

Agricultural

Portal

KCC

State

Level

SAP

Level

User

Level

Grievance Redressal Management System

SAP forwards

Grievance to

Concerned

District Nodal

Officer

Uploads

information in SAP

Nodal Officer

Receives the

Grievance

CSC,SSC,Agri

Clinics, Agri

Business Centres

Mass

Mobile,

IVRS

Nodal Officer

solve the

grievance

If grievance

solved

Y

N

If grievance

solvedY

Forwards to the Nodal

Officer of concerned

department

N

Generates

Reference

No.

As per the above diagram, the User Registers a Grievance through the State Agricultural Portal.



From the State Agricultural Portal the Grievance is redirected to the District Nodal Officer. District Nodal Officer receives the grievance and solves the grievance if possible and uploads the information on SAP. District Nodal Officer will forward the grievance to the Nodal Officer of the concerned Department at the State level, if grievance is not resolved at District level. Concerned department Nodal officer solves the grievance and upload the information on SAP. If Nodal Officer cannot solve the grievance within the time frame then the grievance will forward to the Director of Agriculture at State level. Director of Agriculture receives the grievance and upload the information on SAP. The User can Login any time and check the Status of his or her Grievance. He or she will also receive an

email notification and an SMS alert once the Grievance is answered.

The higher level officers will also obtain reports on the Status of the Grievances.

C. Configurable but Repeated Modules are: C1. SMS Management

Information with regard to status and result of the license and registration application is proposed to be

sent via mobile in the form of SMS to the applicant retailers and farmers wherever required. The SMS

management module would provide functionalities of registration of recipients for SMS, creation of

scheduled tasks for auto SMS (e.g. current status of license application), creation of distribution list,

deletion from the distribution list, prices and availability of stock to the dealer nearest to their area.

C2. MIS Reports

The MIS reports module would primarily be used by the senior officers to track and monitor the

progress of the various testing labs to identify and pinpoint areas that need to be improved

operationally on a continuous basis. The officers would be able to set and select the input parameters

and derive the results in the form of MIS reports for each of the individual testing laboratories.

C3. Content Search

Three keywords that are continuously used synonymously with Agriculture MMP are localization,

customization and personalization of information. This information therefore needs to be made

searchable to the individual needs and conditions of the farmers. The content search module would

facilitate this by providing functionalities of selection of inputs parameters for search and content

display or download.

Some of the identified input parameters for content search are given below:

Season Wise Crop Verities

Crop Wise Recommendations



Agro-climatic Zone Wise Package of Practices

Notified Seed Varieties

o Maturity

o Variety Name

o Ecology Wise (Dryland, rainfed)

o State wise

o Resistant to pest/Disease Name

Prices of Notified Seed Varieties

List of Registered Dealers

Area Wise dealer’s network

Crop Wise dealer’s network

Contact Details and Addresses of the Dealers

Dealer Wise Availability of Stock

Area Wise Stock Availability with the dealers

Dealership Code/License No Wise stock Closing and Opening Balance

Registration Application Status using Application Reference No

Reference No Wise Expert Advice

Reference No Wise Query Status

Reference No Wise- Complaint Status

Reference No Wise- Grievance Response

Registered Farmers Mobile Numbers

Form Type Wise Fee structure of the Registration

Form Type Wise Fee structure of the Licensing

Form Type Wise Fee structure of the Certification

Addresses and Contact Details of the Certification Agencies

List of Certified Seeds

Details of Seed Testing Laboratories

Scheme Wise Subsidy Rates

Crop Wise Subsidy Rates

Subsidized Scheme Names

C4. Printing



The printing module is proposed to be a generic configurable module that would enable the users to print the information disseminated through search module, at any level.

2.2.1.2.1 HIGH LEVEL VIEW OF FUNCTIONAL REQUIREMENTS:

2.2.2 System Interfaces

The system shall so be designed that there shall be linkages with other existing systems. The applications shall be a web based application / interface which will be incorporated with features like online generation license, testing lab reports with the facility of viewing them online. These results shall be made available on SAP and CAP through web services for quick dissemination of results. All application shall also push SMSes to the farmers informing them about the status of application after issuance of the license within the system. In a similar manner information regarding Seed, Expert Advisory system can be pulled from other websites containing relevant information and pushed to SAP and CAP.



2.2.2.1 System Architecture Diagram

2.2.2.1.1 RESPONSIBILITY MATRIX FOR CONTENT MANAGEMENT

SN Content

Type Content Writer Service Level

Content Approval

Service Level

Content Reviewer

Service Level

I.1

Package of

Practices

& Good

Agriculture

Practices

As studied in

Service-3

As studied in

Service-3

As studied in

Service-3

As

studied

in

Service-3

As studied

in Service-3

As

studied

in

Service-

3

I.2

Price of

Seed

Varieties

GOI, State Seed

Corporation, State

DOA

As and When

Updated

GOI, State

Seed

Corporation,

State Dept

As and

When

updated

GOI, State

Seed

Corporation

, DOA

As and

When

update

d

I.3 Stock of

Seed

Mobile/Web

application for Immediate

Licensing

Application, Daily

Dy. Director

of

As and

When



SN Content

Type Content Writer Service Level

Content Approval

Service Level

Content Reviewer

Service Level

Availability stock availability

with Dealers

DOA.

Agriculture,

District

update

d

I.4

Quality

Control &

Assurance

DAC, State DOA.

Upload

changes in <

2 days

State DOA.

Upload

changes

in < 2

days

State DOA.

As and

When

update

d

I.5 Notified

Seed

Varieties

GOI Every Season GOI Every

Season

GOI As and

When

update

d

2.2.2.1.2 RESPONSIBILITY MATRIX FOR DOCUMENT MANAGEMENT

Sr. Activity Document Up loader

Service Level Document

Approver and

Publisher

Service Level

1. Document Uploading

Level 1 Officer As and When

Required Level 2 Officer

As and When

Updated

2. Document Dropping

Level 1 Officer As and When

Required Level 2 Officer

As and When

Updated

2.2.2.2 Gap Analysis between existing and proposed system

Service Existing System Proposed System

Licensing Information available but no online process

A online system for all type of Licensing (import, manufacture, distribute etc)

Status Tracking Manual (applicant has to visit or call respective office)

Applicant can check in the portal and send SMS

Alert system No alert system SMS will be sent to applicant’s registered mobile, e-mail etc

Testing (seed) Information available through testing labs

All information will be available in portal (form to be filled, sample to be tagged etc)

Manufacturer / Dealer information

Varied sources and not complete

All information will be available at single point (consolidated and classified)



Service Existing System Proposed System

Prices Information available through product distributors.

Manufacturer / Distributors can post prices through their login.

Stock Availability Information available through block office.

Manufacturer / Dealers can post their stock through their login

Proactive & Forewarning system

Any identified problems is documented in detail and mailed to the respective offices. And the control measures are taken after lot of damage.

2.2.2.3 Gap Analysis w.r.t 7 States GAP Analysis between as Is and to Be Process w.r.t. States

Application State Name As Is Process To Be Process

Issuing License in Seed MP In MP, the registration and license for selling seed is issued at District level.

The new web based system will allow dealer’s registration and issue license for selling seed at State level, District level and Range level.

Jharkhand In Jharkhand, registration and license for selling seed is issued at District level, Range Level and State Level

Karnataka Dealer’s Registration is done at the block level and license is issued at District level

Maharashtra Dealer’s Registration and License for selling seed is issued at State level as well as District level.

Assam Dealer’s Registration and License for selling seed is issued at State level as well as District level.

HP The dealer’s registration and selling license is issued at the State level after getting recommendations from Dy. Director of Agriculture



Seed Certification MP At Division level- 1. Seed Grower’s source

verification is done by seed producing agency. Seed producing agency, on behalf of seed grower apply for seed certification registration. If seed grower is filling registration details himself, he has to specify and attach the source verification certificate issued by seed processing center along the application Form-A. After successful verification, registration acknowledgement is issued.

2. Sample Procurement process is also considered in MP. (Extra step)

3. After field inspection, the inspection report is sent to the seed grower as well as concerned offices and the seed grower goes to Processing Center for seeds cleaning.

4. Sampling takes place at the Processing center.

5. State level- Codification of the collected samples is done by SCA-HO. Then these samples are sent to testing laboratory.

Follow To Be Process as mentioned above.

Jharkhand Division level- 1. There is no concept of

source verification. After submitting Form-A, the



registration acknowledgement is issued to the seed grower. The inspector verifies the details after field inspection.

2. The inspector in the field collects samples and sends them to the STL for testing.

3. There is no concept of Processing Center.

State level-Certificate/Release Order is issued at SCA-HO.

Karnataka The process is same as MP except point-2.

Assam Same as Jharkhand

Maharashtra 1. District level-The seed grower has to register him for the source verification Process at District Seed Certification Office (DSCO). Once it clears registration certificate/acknowledgement is issued to the seed grower.

2. Sampling and Sample Codification is done by District Seed Certification Office.

3. Seed Certificate is issued by DSCO.

Kerala Same as MP except point-2.

2.3 User Characteristics

ISS application will be primarily used by the farmers, officials of Village Panchayats, Block Panchayats, District Panchayats, State Agriculture Departments, Private and Government Institutions, agencies, dealers, Call Centers and Ministry of Agriculture. Apart from these users, some of the reports can be



viewed by other Central Line Ministries/Departments and also the common man for the purpose of social audit.

The Government and Private Institutions Officials are being provided with basic working knowledge of computers under various capacity building programs, however they are not very familiar with computer based applications. Accordingly, the ISS user interface should be intuitively designed so that it is fairly simple, easy to use and self-explanatory. The software should allow the users to switch-over to local language so that all the textual elements are displayed in local language for better understanding and effective use. The State and Central Ministry’s users are already working with computers and are fairly conversant with computer based applications.

The software will facilitate the farmers and the other users who are having any disability to read and understand the textual elements by receiving voice messages in their local language and the images related to the text mouse over.

2.4 Constraints

1. ISS will be an internet based application which will be designed, developed and hosted in Open

Source Environment in NIC’s State Data.

2. The users will be accessing the software application using various connectivity scenarios.

3. As the application will be used by all the villages (no of villages), State Agriculture Departments

(no of departments), Center and MoA, Government and Private Institutions, dealers, agencies,

KCCs, the no. of application users and concurrent users will be very high as mentioned in non-

Functional Requirements. The software has to take into account all sorts of communication

environments and slow communication links as specified in Chapter 6. The software should also

scale-up as per the requirements defined in Chapter 6.

4. The application will support only unicode enabled fonts for local language representation.

5. ISS will need to inter operate with other software applications which are being developed as part

of Mission Mode Project including Central Agriculture Portal and State Agriculture Portal

indicated in Non-Functional Requirements.

6. ISS will be constrained by the minimum hardware specifications that are likely to be available in

the production environment, the details of which are specified as part of Non-Functional

Requirements in Chapter 6.

7. The stakeholder groups (farmers, private sector and the government) could use the proposed

service delivery channels (CSC, Department, KCC, SCC, Private Kiosks, Mass Mobile, IVRS, Agri



clinics and agri business centers) to initiate service requests; which would be processed by the

Central and State Agriculture Portals (depending on the level of service request generation and

processing location).

8. There is requirement to develop an interface in regional languages for input and output

interfaces.

9. All the master data should follow Meta data standard.

2.5 Assumptions and Dependencies

Common features including Login, Logout, Forgot password, Change Password, User management features etc. which will be used across all software applications as part of Mission Mode Project will be developed commonly and uniformly.

The availability of software applications with which ISS would be interoperating will be crucial for smooth functioning of ISS

It is assumed that the third party tools and applications software wherever required to fulfill the functionality of ISS will be available on the machines where such features will be executed. These may include office tools for viewing the PDF and charts generated by the package. Further, a use case wise description of assumptions have been described, wherever applicable, as part of Functional Requirements in Chapter3.

Note: At a minimum Internet Explorer 6.0 + would be required on the client machines to access the software.

2.6 Acceptance Criteria

This SRS document will stand accepted once Nodal Officer from the Department of Agriculture and Cooperation accord a formal approval to this document.



3. SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

The user, hardware, software and communication interface requirements of the proposed ISS are listed below:

3.1.1 User Interfaces

The user interfaces need to be designed keeping in-line with the Usability requirements specified under

Non-Functional Requirements.

3.1.2 Hardware Interfaces

ISS does not envisage any specific external hardware interfaces. For updation of Dealer’s Stock and Price, hardware like mobile phone and network connection is required.

3.1.3 Software Interfaces

The software will interoperate with other software applications which are being developed under NeGP

(A) Mission Mode Project, in particular Central Agriculture Portal and State Agriculture Portal.

ISS will interoperate with SAP to get the information of the registered users on the SAP, their

registration and application forms to get licenses in Seed. It will display the status of the registered

applications on the SAP. It will also interoperate with the Registered Users Database to get the list of

users and Central Agriculture Portal to access the centrally monitored applications.

3.2 Software Product Features

The functional requirements of the proposed ISS are described below in terms of use cases. A use case may be defined as a particular activity that an actor can perform. An actor is a user with a specific role. The following table gives a brief description of each use case field in the use cases that follow:

Select Service

Overview: This activity enables the actor to select a service

Use Case ID: An ID assigned to the use case for cross reference purposes eg., UC-14

Use Case Name: A Name for the Use Case such as Add Package of Practice



Actors: An actor is a role assumed by a user while using the use case. A role defines what

activities the actor can perform in the application. Application will provide the

following roles to its users:

Joint Director of Agriculture

Assistant Director of Agriculture

Dy. Director of Agriculture

Central Administrator

State Administrator

Stake Holder:

Description: This section describes the use case in a few sentences that summarizes the interaction

between the actor and the system.

Trigger: This defines the action of the actor, which starts or triggers off the Use Case. A use case

may be triggered by more than one action of the actor.

Pre conditions: This section describes the state of the system, which is a pre-condition to starting the

use case.

Post conditions: This is a description of the state of the system after the successful completion of the

use case.

Input: This section describes the inputs to be required to generate the results.

Output: This section describes the outcome of the specified inputs.

Normal Flow: Actor Actions The actor logs in to the Portal The actor clicks on a link

System Responses Select Service page opens with links to

the services. The URL of the service provider opens

Alternative Flow: Actor Actions The actor clicks Home The actor clicks Logout

System Responses Go to Portal Home Page Logout of Portal

Exceptional Flow: Actor Actions Clicks link but the Service

Provider’s URL is unavailable Clicks link but the actor’s internet

access has been temporarily disabled

System Responses Standard internet message for URL not

found Standard internet message for

connection not found

Includes: other use case id



UI: required/not required

Required

Priority: Low/medium/high

This section defines the priority of implementation of the use cases. Use cases have

been assigned one of the three priorities: high, medium and low. These priorities are

defined as follows:

High –

Medium –

Low –

Frequency of Use: Continuous/ frequent/

medium/ less/ rare

Frequent

Business Rules: Any business rules that need to incorporated as part of the use case at the time of

implementation.

Special Requirements: These are primarily nonfunctional requirements that are related to the use case and

that need to be handled in subsequent stages such as analysis, design or

implementation.

Assumptions: Any assumptions that are made about the environment such as hardware, software,

network connectivity, user capabilities etc. in which the software is expected to

operate and which are necessary for the successful execution of the use case.

Dependency: This section defines the relationships that the use case has with other use cases. The

relationships have been defined in terms of three types:

Extends – This relationship means that the use case that is being described extends the

functionality of the use cases that are listed under this heading. Invariably, the

extended functionality is optional and the user may or may not use it.

Is Extended By – Under this heading are listed the use cases that extend the

functionality of this use case, implying that these use cases may be optionally executed

while executing the current use case.

Uses – This relationship means that the use case being described always uses the use

case listed under this heading to complete its functionality.

Notes and Issues: This will not be part of Phase 1. .

Use Case Fields and their Descriptions



3.2.1 Common Use Cases

This sub-section describes the use cases, which would be available to the actor belonging to any role. Refer to Annexure ----- for a diagrammatic representation of the relationships between actor and use cases and among different use cases. The set of common use cases are:

Use Case Name Purpose of the Use Case Actor

Login This use case will facilitate the registered user on the SAP to log on to the ISS application to access various online applications

All Registered users

Select Season This use case will facilitate the actor to select crop season corresponding to which he/she is going to record details.

Successfully logged in actors

Logout This use case will facilitate the actor to come out from the running session of the application. The actor would be brought back to the ISS home page.


Change Password This use case will facilitate the actor to change the existing password of the ISS application.


Switch Language This use case will facilitate the actor to select the language, in which he/she desires to access application and specification of details.

Citizen/ successfully logged in actors

Payment Gateway This use case will facilitate the actor to make online fund transactions using bank’s payment gateway service.

Actors authorized to access paid services like online license application process, seed certification process etc.

Attach File This use case will facilitate the actor to attach/upload files/forms/scan copies of documents/photographs in the application wherever this use case is being called

Actors authorized to access applications of ISS and uploading files.

Drop File This use case will facilitate the actor to drop/download files/forms/scan copies of documents/photographs from the application wherever this use case is being called

Actors authorized to access applications of ISS and downloading/dropping files.

Auto Trigger This use case will provide a mechanism to the actor to

System



generate auto triggers for sending SMS and Mails

Manual Trigger This use case will facilitate the actor to generate triggers as and when a manual command is provided to send SMS/Mail

Actor working on the respective application

3.2.1.1 Log in

Use Case ID: UC_01

Use Case Name: Log in

Actors: Primary Actor

SAP User who has been given privileges to access ISS Application.

Stake Holder: SAP User

Description: This use case would allow the actor to log on to ISS Application.

Trigger: The actor is prompted by the System to login (default scenario)

The actor may also be prompted to login if it attempts to take some actions, which

require special privileges i.e. by default the system would prompt the actor to

specify her Login ID and Password on the SAP/Home Page.

Pre conditions: Actor has invoked ISS home page URL over the web.

The actor is viewing the home page in English Language, the default language for

the application.

Post conditions: The system records the login details of the actor such as the time stamp in the

database.

Depending on the roles assigned to the actor, the actor would be able to access

various functionalities of ISS.

Input: User ID Password

Output: The actor will successfully be logged on to the Service.

Normal Flow: Actor actions

The actor may switch language by selecting the language of her choice.

The actor would then need to enter

The System would then display all labels and messages in the selected language.



the user id and password.

The actor chooses to Submit.

The actor may click the Reset

button, to reset the selected fields

to default.

On successful login the system would

display the select season page with the

list displaying crop seasons

corresponding to which the actor wants

to record details.

Alternative Flow: None

Exceptional Flow: 1. Username or Password is not correct

2. Actor is already Logged In

Actor chooses to login with incorrect

username or password.

System displays the message “Invalid

Login. Either Username or Password is

incorrect. “

Actor acknowledges the message.

System returns back to Pre Condition.

a. Actor chooses to invoke

multiple instances.

b. System displays the message

“User is already logged in. The

user cannot login while an

earlier session is active. Either

kill the session or wait for

system to inactivate the session.



3. User Account Details are being

modified.

4. Actor attempts to login with

incorrect user id, password or both

at least 5 times.

5. Actor attempts to login with

incorrect user id, password or both

at least 10 times.

c. Actor acknowledges the

message. System returns back

to Pre Condition.

Actor chooses to login with correct

authentication details

System displays the message,” You

cannot login now as your user account

details are being modified”.

Actor acknowledges the message.


The System would display a captcha

and prompt the user to enter

captcha after specifying correct log

in id and password to.

The System would respond with a

message, “Your Account is

temporarily blocked. Please try after 2

hours or contact to the State

Administrator”.

Actor acknowledges the message. (If

the account is not unblocked, the

actor should contact to the State

Administrator to unlock his account.)




6. Actor Clicks the Reset Link

The System would clear the username and password field and bring the Login Screen to the default scenario.



Required


High


medium/ less/ rare

High

Business Rules: 1. The attributes (user id and password) are mandatory.

2. At any point of time, the actor can access only one instance of ISS Package.

Special Requirements: None

Assumptions: None

Dependency: Extends :None

Is Extended By : None

Uses :None

Notes and Issues: Common use case shall be referred from CAP or SAP.

3.2.1.2 Select Season

Use Case ID: UC_02

Use Case Name: Select Season


SAP User who has successfully logged on to the ISS Home Page.


Description: This use case would allow the actor to select the season corresponding to which

he/she wants to specify the details.

Trigger: Actor chooses the Select Season Option

Pre conditions: Actor is logged in to ISS over the web.



Post conditions: Actor Submit these details. Depending on the role selected by the actor, the

system would provide access to various functionalities of ISS.

Input: Select Season

Output: The actor will be able to access main menu page to record details in to the system.

Normal Flow: Actor actions:

The actor has successfully logged on

to the system.

The actor Submits the details.

System Response: The System will prompt the actor to select crop season from the list enlisting two crop seasons i.e. Rabi and Kharif. The System will display the main menu page to specify the details belonging to the selected season.


Exceptional Flow: None


None


Required


High


medium/ less/ rare

High

Business Rules: It is mandatory to select Season.

Depending on the selected season, the system will display season specific contents

to the actor to specify the details.


Assumptions: None



Dependency: Extends

ISS Home Page

Is Extended By

None

Uses

Login


3.2.1.3 Log Out

Use Case ID: UC_03

Use Case Name: Log Out




Description: This use case would allow the actor to logout of ISS Application to which she is

already logged in.

Trigger: This use case would be triggered by either of the following actions of the actor:

1. The actor chooses to Logout.

2. The System times out the actor.

3. The browser window is closed.

Pre conditions: Actor is logged in to ISS over the web and the session has not times out.

Post conditions: The actor would be logged out and brought back to the home page of the ISS. The

actor would now be able to login again from the same or another computer.

The System would record the session details of the actor and do clear the session

details of the actor.

Input: Click on the link available.

Output: The actor will be able to access main menu page to record details in to the system.




The actor chooses to Logout.

System Response:

System displays the message “You have

successfully logged out. Thanks for using

ISS package”.

The System returns back to the Home

Page of ISS package.

Alternative Flow: If the actor chooses to close the browser window

1. System displays the message, “The currently logged in user was logged out. Thanks

for using the ISS package.

2. The System would close the ISS package.

If the actor is already logged in into ISS package and System times out the actor.

The system logs out the actor whenever the actor tries to click any option. The

System returns back to the Home page of ISS package.



None


Required


High


medium/ less/ rare

High

Business Rules:


Assumptions: None

Dependency: Extends

ISS Home Page

Is Extended By

None

Uses

Login




3.2.1.4 Change Password

Use Case ID: UC_04

Use Case Name: Change Password




Description: This use case will allow the actor to change her password. The actor has to be logged

in to be able to change the password.

Trigger: Actor selects the Change Password Option.

Pre conditions: Actor is logged in to ISS over the web.

Post conditions: The modified password details would be stored in the database.

Input: Old Password New Password Confirm Password

Output: Password Changed in to database


Once the Actor submits the new

password details,

Once the Actor acknowledges the

System Response:

1. The System would prompt the actor to

enter the old password.

2. The actor would then be prompted to

enter a new password (which should

different from the old password) and

confirm it by re-entering it in the

Confirm Password field.

The System would respond with the

message, “Your password has been

modified successfully”.



message, The System would return back to Pre

Condition.


Exceptional Flow: The actor attempts to save the changed

password without specifying the Old

Password.

The actor attempts to save the changed

password without specifying the New

Password.

The actor attempts to save the changed

password without specifying the Confirm

Password.

The length of the new password is less

than 8 characters.

The length of the new password is

greater than 12 characters.

The New Password is same as Old

Password.


message, “Please enter a password for

the user”.


message, “Please enter a confirmation

password for the user”.


message, “Please enter a confirmation

password for the user”.

The system would respond with the

message, “The length of the

password should be greater than 8

characters”.


message, “The length of the

password cannot be greater than 12

characters”.


message, “The new password you

have entered is same as old



The New Password is same as Previous

old Password

Confirm Password is different from New

Password.

The New Password is not a Strong

Password.

password. Please enter a different

value for new password”.


message, “New Password cannot be

same as previous old password”.


message, “Confirm Password should

be same as New Password”.

The System would respond with a message, “Please correct the problem (s) with your new password. Strong Passwords must include at-least one number and special character.”


None


Required


High


medium/ less/ rare

High



Business Rules: 1. The length of the new password should be greater than 8 and less than 12

characters.

2. Old Password, New Password and Confirm Password fields are Mandatory.

3. Confirm Password should be same as New Password.

4. The New Password should include at-least one number and one special

character.

5. The New Password should not be same as the Old Password & Previous Old

Password.


Assumptions: None

Dependency: Extends None Is Extended By None Uses Login


3.2.1.5 Switch Language

Use Case ID: UC_05

Use Case Name: Switch Language


SAP User who has accessed ISS Home Page.


Description: This use case will allow the actor to view the ISS in one of the supported languages

that is different from the language in which she is currently viewing. All fixed text on

screens, drop down list of values, any error or warning messages generated by ISS

application and help text will be displayed in the chosen language.

Trigger: The actor chooses a language from the list of languages supported by the ISS.

Pre conditions: The Actor is either viewing the default page of ISS or any of the screens of ISS (which

are available after login) in one of the languages supported by the package.

Post conditions: 1. The selected language becomes the current language of the ISS for the actor till

she switches to another language or quits the ISS by either by logging out or her



session times out.

2. This has the implication that all fixed text on screens; enlisted values, any error

or warning messages generated by ISS and help text will be displayed in the chosen

language. This of course applies only to those items that have been translated.

Input: Select Language

Output:


The actor would be able to select

one language from the list of

displayed languages.

System Response:

1. The system would display the list of all

languages supported by ISS.

2. The current page and all subsequent

pages will be displayed in the selected

language. All fixed text on screens, drop

down list of values, any error or warning

messages generated by ISS and help text

would be displayed in the chosen

language.

4. The system would issue an

informational message, “To enter data in

the selected language, please set the

language in your machine”.

6. In case any label is not available in the

selected language, the label will be

displayed in English.

7. In case help text is not available in the

selected language, then the help text will

be displayed in English.


Exceptional Flow:


None


Required




High


medium/ less/ rare

High

Business Rules: 1. ISS will display labels & help text as per the following logic to ensure that

labels/help text is always available in at least one language:

2. Display label/help text in the actor’s current user interface language.

3. In case no translation(s) is available in current language for some or all labels, then

display those label(s)/help text in default English language.

Special Requirements: 1. ISS will support entry and display of languages

a. That have UNICODE enabled fonts

b. Both Latin and non-Latin scripts such as Hindi, Tamil etc.

c. That read from left to write

Assumptions: None

Dependency: Extends None Is Extended By None Uses Login, if the actor has logged in to the package.

Notes and Issues: The Default language of the ISS would always be English. After specified translation

scripts in local language of the state, the local language will become the default

language for that state.

Common use case shall be referred from CAP or SAP.

3.2.1.6 Payment Gateway

Overview: Payment gateway facilitates the actor to deposit there fees through online transactions like internet banking, debit card or credit card. Payment gateway works as a bridge between the sender’s bank account and the recipient bank accounts.

Use Case Name: Payment Gateway




The person/agency who wishes to deposit fee charges for registration, licensing or

various activities through this application using internet banking or online

transactions.

Stake Holder: Government/Private Agencies

Licensed Dealers

Description: A payment gateway facilitates the transfer of information between a payment portal

(such as a website and mobile phone) and the Front End Processor or acquiring bank.

Trigger: The actor selects the option available as select Internet Banking/Debit Card/Credit Card options

Pre conditions: 1. The user must be registered on the SAP. He must be logged in, and should

have permissions to access ISS and making online payments for various

transactional activities.

2. The person/agency must be registered with their banks for availing online

transactions facility.

3. The person/agency must have Debit/Credit Card for online transactions.

Post conditions: 1. After successful transactions, the system will generate payment receipt details,

shown to the actor on the screen. The actor could print the Payment Receipt.

2. On successful transactions, the deposited amount should be stored in ISS

database.

Input: Debit Card Details Credit Card Details Internet Banking Details

Output: Successful Payment Transfer

Normal Flow: Actor Actions The actor clicks on the option

“Online Payments”.

System Responses The System will prompt the actor to

specify following details to communicate ISS system with the Payment Gateway’s API:

- Unique Application id - Amount being Paid - Applicant Name - Recipient Account No



The actor may choose one of the following options: Save Submit Save: The actor may click on the save option to save the recorded details Submit: The clicks on the Submit option to finally submit details to the bank’s payment gateway.

- Recipient Account Name The system will navigate the ISS application to the selected bank’s Payment Gateway.





Required


High


medium/ less/ rare

Medium

Business Rules: 1. All details are mandatory to specify. 2. Minimum amount to be specified for transaction must be 1 Rs.

3. There should be a mechanism to access the API of payment gateway.

Exceptions: None

Relationships Extends Application to Obtain Dealer’s License for Seed Renewal of Dealership License for Seed Is Extended By None Uses Login




Assumptions: a. The actor is registered either on SAP and access the application/service through single sign on.

b. Hardware like computer/laptop system and network connection is available to the actor.

c. The actor is having a valid mobile number. d. Actor is having an internet banking access or debit card or credit card

Dependency: None

Notes and Issues: None .

3.2.1.7 Attach Documents

Use Case Name: Attach Document

Actors: A person/agency that is uploading any document on the system.

Description: This use case allows the actor to add a new attachment to an item. The

attached file format and size limit would be governed by the system

parameters set in the ISS application from where the Add attachment has

been invoked by the actor.

The file to be attached may be located anywhere in a network of systems to

which the actor’s system is connected.

Trigger: The actor chooses to add an attachment.

Pre-conditions: Actor had logged into the ISS application and has chosen to Add attachment in a specific application module.

Post conditions: 1. The Attachments will take effect only if the user confirms the operation

from which this use case was called.

2. If the user confirms the uploaded attachments by submitting, then

linkages of the uploaded files with the item will be created and saved in

the respective ISS application database.

3. The uploaded attachments usage would then be governed by the

business rules/Use cases of the respective ISS applications.

Normal Flow: Actor Actions

1. Actor enters the Title of the

attachment.

System Responses

a. System would display

the Allowed File Type(s)

which can be uploaded by



2. Actor navigates through the

list of files and folders and

selects the file to be uploaded.

3. Actor chooses to upload. Actor

chooses to upload the allowed

file type and file size is within

the upload Limit.

the actor, along with File

Upload Limit, as defined in

the System Parameter of

the respective ISS

application.

b. The standard Operating

System dialogue Window

(which displays the list of

files currently available on

the local machine) is

displayed. The window also

provides option to select a

file available on another

system which may be

connected to the local

system, invariably in a LAN

c. The file selected for

attachment is scanned for

any virus at the time of

upload and if the virus

can’t be removed, the file

is not uploaded to the

server. The actor is

informed with the



4. The actor may choose to

drop the attachment, if

required, using Drop

Attachment use case.

message: "The selected file

could not be uploaded as it

was virus infected and

could not be cleaned. Pl.

selects another file".

d. The file is uploaded to the

system from which Add

Attachment was invoked

e. Once the file is successfully

uploaded, the system

displays the message “File

was attached successfully.”

Alternative Flow The actor may repeat steps 1 to 10 as many times as required

Exceptional Flow Network connection breaks while

uploading file to the PES system if

the system is on a network.

If, the Confirm button is clicked

without entering the title

In Step 5 of normal flow, if actor

chooses:

a) Selected File Type is not

under the list defined in

Allowed File Type(s),

a. The actor is brought back

to the Pre condition.

b. The actor will have to

begin the file upload

operation all over again

from Step 1.

The system would respond with the message “<<Title>> field cannot be left blank. Please enter the Title.”

On Save, System would prompt the

error message as “File Type not

allowed for upload,” Actor can then

choose to browse a different file type.



b) Sum total of File sizes of

all the file attachments

exceeds the Upload

Limit,

The file attachment selected for

uploading is virus infected and the

system is not able to clean it.

On Save, System would prompt the error message as “File Size(s) has exceeded the Upload Limit,” Actor can then choose to browse a different file(s).

The system would respond with the

message: "The selected file could not

be uploaded as it was virus infected

and could not be cleaned. Pl. selects

another file".


None

UI: required/not

required

Required


High

Frequency of Use: Continuous/

frequent/ medium/ less/ rare

Frequent

Business Rules: 1. There may be more than one file attached to an item.

2. Title of the attachment is a Mandatory field and should not be left

blank.

Special Requirements:

In case the connection breaks while uploading the file, the upload

process will have to begin all over again. However, if technology

permits, it will be preferred, if the system resumes the file upload from

the point where the connection was lost.

Assumptions: None



Dependency: Extends

All Use Case(s) which involve forms/pages with Add Attachment Option.

Is Extended By

None

Uses

Login

Notes and Issues: None

3.2.1.8 Drop Attachment

Use Case Name: Drop Attachment

Actors: A person/agency that is dropping any document from the system.

Description: This use case allows the actor to delete or drop a file attachment that is

associated with an item.

Trigger: The actor chooses to drop one or more attached files.

Pre-conditions: Actor had logged into specific CAP application and has chosen to Drop

attachment in a specific application module, provided at least one file is

attached with the item.

Post conditions: 1. The dropped files will be removed from the CAP application only if the

user confirms the dropping of attachments by submitting the changes.

2. All linkages of the item with the dropped attachments are removed

from the CAP application.


Actor confirms the drop operation.

System Responses

The System displays the message

“Proceed with dropping the selected

files?” to confirm the drop operation.

The selected files are marked as

dropped.



Alternative Flow None

Exceptional Flow None


None

UI: required/not

required

Required


High



Rare

Business Rules: The attachment will not get dropped, if it is the only element that

constitutes the item.


None

Assumptions: None

Dependency: Extends

All Use Case(s) which involve forms/pages with Drop Attachment Option

Is Extended By

None.

Uses

Login


3.2.1.9 Auto Trigger

Use Case ID: UC_

Use Case Name:

Auto – Trigger

Actors: System

Description: This is a use case for alert system

Trigger: Message from other use cases where auto trigger is being called.

Pre-conditions:

Message should comply with the alert system’s interface/api.

Post conditions:

1. On success, Trigger mail / msg sent to the respective stakeholders as received from the use case. 2. On failure, retries until success or drops the message and table is updated



Basic Flow: Actor Actions

Actor reads the message

and the details shall

contain;

-time stamp

-target mail id and mobile

no

-message

Stores the details in the

table

Sends the message to

target

System Responses


None

UI: required/not

required

Required


High



Continuous

Business Rules: 1. Should try for 24 hrs before dropping the message or as per system admin

policy

2. All acknowledgements could be auto-erased as per system admin policies


None

Assumptions: None

Dependency: Extends All the use cases where auto trigger is being called, Is Extended By None Uses Login


3.2.1.10 Manual Trigger



Use Case ID: UC_

Use Case Name: Manual – Trigger

Actors: All system users

Description: This is a use case for alert system which should be functioning when manual commands are given

Trigger: Actor clicks on the link available for alert

Pre-conditions: Actor logs on to the system based on the credentials assigned.

Post conditions: 1. On success, Trigger mail / msg sent to the respective stakeholders as received from the use case. 2. On failure, retries until success or drops the message and table is updated


Actor selects SMS / Mail

Actor types the message and

the details shall contain;

- purpose

-message

-target (other system users /

registered business users)

Clicks submit

System Responses

Captures the details and displays

confirmation dialogue

Stores the details in the table

Sends the message to target


None

UI: Required/not required

Required


High


medium/ less/ rare

Frequent

Business Rules: 1. Should try for 24 hrs before dropping the message or as per system admin

policy

2. All acknowledgements could be auto-erased as per system admin policies

3. Based on role the system should allow / restrict sending SMS to other officers.

4. Only registered dealers/farmers/manufacturers list will be available to send

SMS


Assumptions: None



Dependency: Extends Use cases where any alert could be generated Is Extended By None Uses Login

3.2.2 Knowledge Management System

Knowledge Management System will consist of following Core Modules:

3.2.2.1 User Management/System Administration


Create Role These use cases will facilitate the actor to Create New Role in database w.r.t. services/sub services

User Manager

Create User Group This use case will facilitate the actor to create a new user group.

User Manager

User Creation and Accessibility Rights

This use case will facilitate the actor to create new users and assigning privileges to them

User Manager

3.2.2.1.1 CREATE ROLE

Use Case ID: UC_

Use Case Name: Create Role

Actors: User with the assigned privilege of User Manager

Description: This use case allows the Actor to Create roles. Each role is given permission to access

forms/links/modules in the system while creating Users.

While on the SAP, field level permissions can also be assigned to the role.

Each application’s User Manager would be allowed to create their respective

application-specific Roles as per assigned privileges.

Trigger: Actor chooses to create a new role option available under System Administration Create Role.

Pre conditions: The actor is logged in and is viewing the System Administration Page of respective CAP

application or the SAP.



Post conditions: 1. The Role details would be saved in the database.

2. Created roles will be available for modification and deletion as soon as these

are created through Modify Role and Delete Role use cases respectively.

3. Created role will be available for further creating User Groups through Create

User Group Use Case.

4. Audit Log is updated with the operation.

Input:

Output:


The actor may choose one of the following options: Save Clear Close Cancel Edit

Actor fills in all mandatory fields clicks on Save,

If actor clicks on clear, If actor clicks on close,

System Responses

System prompts actor to fill in the following

fields:

1. Role Name: Actor enters the Role

Name.

2. Role Name (in Local Language)

3. Role Description: Actor enters the role

description.

New role is created and System displays

the message “New Role was created

successfully”.

The form details would be cleared. The form would be closed and the System

would return back to Pre Condition.



If the actor clicks the Cancel option, Actor clicks on the Edit option,

The system would respond with the message, “Would you like to discard the Role details?” If the actor responds with Yes, then the entered details would be lost and the System would return back to Pre Condition. ; if the actor responds with No, the actor would be returned back to the Create Role screen. Selected Role Details will be available for modifications.


Exceptional Flow: Actor Actions Actor attempts to save, without specifying the Role Name, then Actor attempts to save, when the

same Role Name already exists

within the selected CAP application.

System Responses The system would respond with an error

message “Role Name is not entered,

Please enter a role name”.

The system would respond with an error message “Role Name already exist, Please enter a different value”.

Includes: Other use case id


Required


High


medium/ less/ rare

Frequent



Business Rules: 1. Role Name is mandatory field.

2. Role name should be unique within a specific SAP application system.

3. User Manger of specific CAP application should be able to Create Role(s) under

his/her respective application only.

4. While User manager of SAP should be able to create role(s) under any CAP

application.

5. In case User Manager of specific CAP application has logged in, then the CAP

application drop box would populate the respective CAP application name(s)

for which actor has been assigned the User Manager.


Assumptions: None

Dependency: Extends

View System Administration Page of respective CAP application or SAP.

Is Extended By

None

Uses

Login


3.2.2.1.2 CREATE USER GROUP

Use Case ID: UC_

Use Case Name: Create User Group

Actors: User Manager or the person authorized with the assigned privileges of user group

creation.

Description: This use case would allow the actor to create/add new user group.

A user group will be created for respective CAP applications. Each application’s

User Manager at State level would be required to create their respective

application-specific user groups through SAP.

Firstly actor would form the roles as per the specific application need using Create Role Use Case, and then multiple roles can be grouped by the actor to form the User group through this Create User Group use case.

Trigger: Actor chooses to Create user group.



Pre conditions: The actor is logged in and is viewing the Create User Group page under System

Administration of the respective CAP application or SAP home page.

Post conditions: 1. Actor clicks on Save and all the mandatory details has been filled-in, she would

be able to save the user group and The System would respond with the

message, “The user group has been saved successfully.”

a. Created user group details would be stored in the database.

b. User group details would be available for modification, deletion and view

as per the assigned privileges.

2. All saved User Groups would be available to the User Manager to create the

users (through Create User use case).

3. Audit Log is updated with the operation.

4. In case the actor has not entered all mandatory fields, system would not allow

the actor to save the data.

5. If the actor clicked on the Cancel button, the system would respond with the

message, “Would you like to discard the user group details?” If the actor

responds with Yes, then the entered details would be lost; if the actor responds

with No, the actor would be returned back to the Create User Group screen.

When the actor acknowledges the message, the System would return back to Pre

Condition.

Input:

Output:


System Responses The system would prompt the actor to

enter the details as follows:

2. Name of the user group –Actor would

be required to enter the name of the

user group.

3. Name of the user group (in Local

Language)

4. Roles – The Create User Group page

will prompt the actor to select the

roles being assigned to the user group.



The actor may choose one of the following options: Save Clear Close Cancel Edit

Save: The actor may click the Save

option to save the User Group details.

Clear/Close: At any point of time, the

actor clicks the Clear button to

discard the details entered or clicks

the Close button to close the Create

User Group form.

Edit: The actor may click on the Edit link, to edit the user group details.

The actor may assign one or multiple

roles to the single user group.

5. Self Registration – This property

determines whether the site would

support self-registration by visitors

(users who are not logged in) to the

site i.e., whether visitors to the site

can create their own user id and

password. If the actor sets this

property to Yes, then the visitors who

self-register would be assigned this

user group. This field would be

enabled for the user groups like

farmers/citizen etc who may access

relevant information of their need.




Exceptional Flow: Actor Actions Clicks link but the Service URL is

unavailable

Clicks link but the actor’s internet access has been temporarily disabled

The actor attempts to save the user group details without specifying all mandatory fields.

The actor attempts to save user

group details when the user group name contains numbers only.

The actor attempts to save the

user group details when a user group name contains special characters only.


user group details when a user group name contains blank spaces only.


user group details when a user group name with the same name already exists.


found

Standard internet message for connection not found

The system should respond with the

message,” Please specify the <<field name>>”.

The System should respond with the message, “User Group Name should contain at least one alphabet.”



The System should respond with the message, “User Group with the same Name already exists. Please Enter a different Name”

Includes: Other use case id


Required


High


medium/ less/ rare

Frequent



Business Rules: 1) The following fields are mandatory to specify:

Name of the User Group.

Select Role

2) Maximum permissible length for the field Name User Group should not

exceed 20 characters including numbers (0-9), alphabets (a-z) and a set of 9

special characters / , - _ ( ) * & : and space.

3) Name of the User Group should contain at least one alphabet.

4) Name of the User Group should be unique.

5) Name of the User Group should not begin with blank space. If the first

character of the user group name is blank space, then while storing in the

database system, the character (other than space) should be considered as

first character.


Assumptions: None

Dependency: Extends

SAP home page

Is Extended By

None

Uses

SAP Login


3.2.2.1.3 USER CREATION AND ACCESSIBILITY RIGHTS

Use Case ID: UC_

Use Case Name: User Creation and Accessibility Rights

Actors: User Manager or the person authorized with the assigned privileges of user creation.



Description: This use case should allow the actor to create users based on the roles and privileges

assigned them for the CAP Applications.

The user created through this use case would be able to log onto the SAP portal or into

any specific CAP application directly.

Actor would mandatory specify whether user being created by him/her belong to

Centre level or state level. In case user belongs to the state, actor would also select the

State of the user, which would establish the list of enabled CAP applications for the

selected state. Refer Enable/Disable CAP application(s) Use case available under

Content Management System. Further user may optionally select the District, Tahseel,

Block, Panchayat and Village under the selected state.

Actor would be able to create users at the same level or below his level i.e. He/she

would be allowed to create users within his/her own state level or the level below

his/her state.

The actor could assign privileges to the users’ user group wise- role wise and

application wise. The user could assign privileges for multiple CAP applications.

Actor can also create multiple users in one go, through bulk users option.

The bulk users can be created for specific User Group, role and Entity Level.

Once bulk users are created these would be available for further modification, deletion

or viewing as similar to other normal users under Modify User, Delete User and or View

User use cases.

Trigger: Actor chooses Create User option available under System Administration-> Create

User.

Pre conditions: The actor is logged in to the portal having privileges of creating users under System

Administration Page.

If the pre define User Manager logs on to the portal for the very first time for user

creation, the User Manager should be required to change the password and again

logged on to the portal for user creation for various applications and assigning

privileges to them.



Post conditions: The user with the assigned privilege of user manager of the individual

service/application could modify the privileges assign to the selected user for that

application only.

Input:

Output:


1. Actor selects the User Type i.e.

whether he/she wishes to create

‘Specific user’ or ‘Bulk Users’

2. If, actor chooses to create ‘Specific

User’.

System Responses

The System will prompt the actor to specify following details:

3. Level – Centre /State: The system should

prompt the actor to select one of the

options i.e. Center or State, at which

he/she is going to create user.

4. Select State Name: In case actor selects

state, system should prompt the actor to

select the state name from the drop

down enlisting all the States of the

country. Select one state.

5. Select User Group: The System should

display a list of user groups. Actor will

select one user group.

6. Select Role: Based on the selected user

group, the system should display list of

all the roles. The actor will select the

role(s) which he/she wants to assign the

user. One user could assign multiple

roles.

Create User form would be partitioned



in to four sections:

I. User Account Details

II. Login Details

III. User Profile Details

IV. Assigning Privileges

7. The actor is prompted to enter the

following User account Details:

a. Select Level: The system

should prompt the actor to

select the level at which she

desires to create the user.

The levels could be Zilla,

tahseel, block or Village etc.

b. Select Entity: i. The System


specify the number of

entities for which the user

would be allowed to perform

activity. In other words for

how many districts, Blocks

and Villages the user is

authorized. ii. Based on the

selected State and the entity

levels, the System should

display list of Districts, Blocks

and Villages. iii. Depending

on the specified numbers,

the actor could select the

entity names for which the

created user would be

authorized to perform the



activities assigned to him.

8. In case, the actor selects level as Center,

then the actor would be required to

follow steps 5th and 6th only.

Login Details:

9. The System should prompt the actor to

specify following Login Details:

i. User Id

ii. Password

iii. Confirm Password

The ii. And iii. Fields would be entered by the

user himself/herself whose user id is being

created.

User Profile Details


specify following details related to the

User Profile:

i. Email – The actor should specify the

email address of the created

user or the email address to

which the intimation email of

the user creation is required to

send.

ii. Mobile Number – The actor should

specify the Mobile number of

the created user or someone to

whom an intimated SMS of the

user creation is required to

send.

iii. Default language – The actor should



select the default language for

the user from the drop box. The

system should display all labels

of the SAP and CAP applications

in the selected default language.

If the actor does not select any

language, SAP and CAP

applications should be displayed

in the default English language.

This default language could be

changed by the user while

logged on to the

portal/application using Switch

Language option available on

the home page.

Email Address and the mobile

number are mandatory to

specify.

Assigning Privileges:

11. The system will prompt the actor to

specify the Privileges being assigned to

the created user. The actor could assign

following privileges to the user:

a. CAP application: Actor would select

the CAP application from the set of

12 applications list and SAP (Only, if

the users are being created at the

State level) for which the user would

be authorized to perform various

activities

b. The SAP/System will prompt the



Actor fills all mandatory fields and saves the data. On successful save,

actor to select the privileges from

predefine set of privileges which

she wants to assign to the created

user. The actor could provide

authority of Addition, Modification,

Deletion, Freeze, Unfreeze, Publish

and View (links available on the

respective forms) as specified for

the selected forms/modules. The

actor could specify form/module/

link/options wise access rights. By

default, the user will have full

access rights of the selected

application for the selected entity.

12. System responds with the message

“User Account “<User id >“was created

successfully”.

13. Actor acknowledges the message.

14. System returns back to Pre Condition.

15. As soon as a user is successfully created,

system will trigger an email and SMS on

the specified email id and mobile

number specified above.

16. Through email, system will provide a link

of the page on SAP portal or specific CAP

application for setting his/her password

i.e. provide his/her Password and

Confirm Password values. The link

provided would be valid for 7 days only.

17. Through SMS, system will provide a Code



word to the user, through which user will

enter on the SAP portal or specific CAP

application for setting his/her password

i.e. provide his Password and Confirm

Password values. Similarly Code word

provided would also be valid for 7 days

only.

18. In case, the link provided on the email id

of the user gets expire after 7 days, the

user would be required to register

him/her (using Register New User use

case) for the re creation of new user

account.

Alternative Flow: 1. Actor chooses to create ‘Bulk Users’

in step 2 of Normal Flow.

2. Level – State: The system should prompt

the actor to select the option State, as

the bulk users should be allowed to

create at the State level only.

3. Select State Name: In case the actor

selects state, system should prompt the

actor to select the state name from the

drop down enlisting all the States of the

country. Select one state.

4. Select CAP application: The System

should prompt the actor to select the

CAP application from the set of 12

applications (which have been published

by the Content Management

Administrator of the

CAP for the respective State) for which

the bulk users are being created.

5. The system should prompt the actor to



select the User Group for which bulk

users are required to create.

6. The system should prompt the actor to

select the Role for which the bulk users

are required to create. Based on the

selected user group, a list of all the roles

belonging to that user group should be

displayed. The actor could select multiple

roles for multiple applications (two

different roles in different applications)

for one user.

7. The system will prompt the actor to

specify access rights for Addition,

Modification, Deletion, and View, which

she wants to assign to the created bulk

users under selected role for the selected

application. The actor could specify

form/link/ module wise access rights.

The System would prompt the actor to

specify the details belonging to the

following three sections:

i. User Account Details

ii. Login Details

iii. User Profile Details

8. The actor is prompted to enter the

following User account Details:

c. Select Level: The system


select the level at which she

desires to create bulk users.

The levels could be Zilla,



block or Village etc.

d. Select Entity: i. The System


specify the number of

entities for which the users

are being created. In other

words for how many

districts, Blocks and Villages

the user is authorized. ii.

Based on the selected State

and the entity levels, the

System should display list of

Districts, Blocks and Villages.

iii. Depending on the

specified numbers, the actor

could select the entity names

for which the users are being

created.

User Profile


specify following details related to the

User Profile:

i. Email – The actor should

specify the email address

of the administrator to

whom the intimation

email of the created user

ids and passwords could

be sent.

ii. Mobile Number – The actor

should specify the Mobile



number of the

administrator to whom

an intimated SMS of the

user creation could be

sent.

iii. Default Language- The actor

should select the default

language for the created

users from the drop box.

The system should

display all labels of the

SAP and CAP applications

in the selected default

language. If the actor

does not select any

language, SAP and CAP

applications should be

displayed in the default

English language. This

default language could

be changed by the user

while logged on to the

portal/application using

Switch Language option

available on the home

page.

Email Address and the mobile

number are mandatory to

specify.

10. System generates the bulk user ids

and passwords in a pre define



system generated format for all the

available parameters in the selected

criteria and user ids would be thrown

to the specified email id and the

mobile number of the administrator

specified in the User Profile and to

the pre defines User Manager for

maintaining records. The portal

displays the message “<User id

count> user ids and <Password

count> passwords are created

successfully.”

Actor acknowledges the message and


11. The users would be required to change

the system generated passwords while

logged in for the very first time on the

application through Change Password

use case. As the user changes the

password through Change Password use

case and log on to the system again, the

System will prompt the user to specify

the personal details through the Update

User Profile use case.

12. Bulk users will have all the privileges

(other than System Administration

and Content Management System)

based on the specified parameters

for bulk users creation. For System

Administration and Content

Management System the user with



the specific roles and privileges

should be created.


unavailable Clicks link but the actor’s internet







Required


High


medium/ less/ rare

Frequent

Business Rules: 1. In case of Specific User, Mobile number is mandatory to specify. 2. In case of Bulk Users creation, Email id is mandatory to specify. 3. A user should be assigned permission to access at least one

form/module under assign Privileges.


Assumptions: 1. All Privileges are being assigned at the user level.

2. Self Registered users like farmers, dealers who register themselves online through

specifying registration details on the SAP, would fall under self registered user

group and they would be called as External Users/Primary Users.

3. The Users which are created by the governing authorities without filling any

registration form will be processed through Alternative Flow mentioned in the Use

Case.



Dependency: Extends

SAP Home Page

New Farmer Registration

Is Extended By

Modify User (on Services/Applications)

Alert System

Update User Profile

Uses

Login


Other Configurable Modules are:

3.2.2.2 Master Data Management


Managing Released Seed Varieties

This use case will facilitate the actor to specify the released seed varieties by the State. There will be a provision to modify the status of the released seed varieties as notified or de notified for the respective state.

State Seed Committee

Managing Seed Prices This use case will facilitate the actor to specify seed prices decided by the State level authorities. The actor could perform various functions like add, modify, delete and view for managing prices of notified seed varieties.

Authorized Agency

Other Master Databases to be created in the ISS are:

Managing Bank Details

Managing Treasury Details

Service Authority (Approving Authority)

Registration Agencies

Registration issuing agencies

License issuing agencies

Seed Grower Registration Agencies



Seed Producing Agencies

Seed Processing Centers

Product code – inputs wise (crops, seeds)

Type of dealers

State

District

Employees

Designation

Department

Fee Criteria

Fee Structure

Lab test name

Office Type

Office Details

Block

Local Body Code

Welfare Schemes & implementation guidelines

Advisory units

3.2.2.2.1 MANAGING RELEASED VARIETIES Overview: The actor would be required to specify the names of the seed varieties released by the State Seed Committee of the State.

Use Case ID: UC_

Use Case Name: Managing Released Seed Varieties

Actors: State Seed Committee

Stakeholders Farmer/citizen

Description: This service enables the actor to enter the details of the state released seed varieties.

Trigger: Actor clicks the “Managing Released Varieties” link

Pre-conditions: Actor must be signed up on the State Agriculture Portal with valid user credentials.

Post conditions: 1. On success, Trigger mail / msg sent to the respective stakeholders and update the tables. 2. On failure, no table should be updated and appropriate error message should be displayed. 3. An email should be sent to specified email ids of the Center Seed Committee, providing details of the released Seed varieties by the State.

Basic Flow: Actor Actions Fills the forms with all mandatory fields like

Crop Name (for e.g. Paddy)

Variety Name (e.g. BPT5204, PUSA-44)

System Responses System shows the price entry page of seed for the respective season.



Institution Responsible for developing breeder seed

Parentage

Agency maintaining breeder seed

Resemblance to variety

Adaptation and recommended ecology

Maturity

Maturity Group

Quality of produce

Agronomic features

Morphological Characteristics

Reaction to stress

Description of Variety

Description of Parents

Reaction to major diseases

Reaction to major pests

Average yield

Status(Released/Notified/De notified)

Depending on the selected Status, the actor would be required to specify following details:

Year of Release (if selected status as “Released”)

Notification Number and Notification Date (if selected status as “Notified”)

Notification Number and De notification Date (if selected status as “De Notified”)

After specifying all the mandatory fields, the actor may choose one of the following options:

Save

Freeze

Edit

Delete

View

System captures the input and updates the database. The System will send an SMS alert to the farmer informing about new notified/de notified seed



Save: The actor may click on the save option to save the entered details. The saved details would be available for freezing, modification and deletion.

Freeze: The actor may choose this option, if the recorded released varieties have been verified and could be frozen for accessing them throughout the ISS application wherever required.

Edit: The actor may choose this option to modify the saved details. The actor could change the status of the released seed varieties as Notified/De notified.

Delete: The actor may choose this option to delete the specified details.

View: The actor may choose this option to view the status wise existing seed varieties.

varieties in the State.



Required


High


medium/ less/ rare

Rare

Business Rules: 1. Released varieties are notified/de notified under Gazette Notification issued by Central Seed Committee.

Special Requirements: Crop Name should be defined in master table.

Assumptions: None

Dependency: Extends ISS Home Page Is Extended By None Uses



Login


3.2.2.2.2 MANAGING SEED PRICES Overview: The actor would be required to specify the prices of notified seed varieties decided by the State Government.

Use Case ID: UC_

Use Case Name: Managing Seed Prices

Actors: State Seed Corporation/authorized agency

Stakeholders Farmer/citizen

Description: This service enables the actor to enter the Price of their product.

Trigger: Actor clicks the “Price Entry” link

Pre-conditions: Actor must be signed up on the State Agriculture Portal with valid user credentials.

Post conditions: 1. On success, Trigger mail / msg sent to the respective stakeholders and update the tables. 2. On failure, no table should be updated and appropriate error message should be displayed.

Basic Flow: Actor Actions Fills the forms with all mandatory fields like

Crop Name (for e.g. Paddy)

Crop Characteristics (e.g. Thick Paddy, Thin Paddy, Aroma Paddy)

Seed Class (Certified Seed/ Foundation Seed/Hybrid Seed)

Seed Variety (e.g. BPT5204, PUSA-44)

MRP / quantity

After specifying all the mandatory fields, the actor may choose one of the following options:

Save

Freeze

Edit

System Responses System shows the price entry page of seed for the respective season.



Delete

View

Save: The actor may click on the save option to save the entered details. The saved details would be available for freezing, modification and deletion.

Freeze: The actor may choose this option, if the recorded seed prices have been verified and could be frozen for accessing them throughout the ISS application wherever required.

Edit: The actor may choose this option to modify the saved details.

Delete: The actor may choose this option to delete the specified details.

View: The actor may choose this option to view the existing seed price.

System captures the input and updates the database

System to send mail to farmer and dealer with information captured.



Required


High


medium/ less/ rare

Frequent

Business Rules: As per Seed Control Order for Seeds

Special Requirements: -Crop Name, Crop Characteristics, Seed Class and Seed Varieties should be defined in master table.

Assumptions: None

Dependency: Extends ISS Home Page Is Extended By None Uses



Login


3.2.3 Transactions and Work Flow

3.2.3.1 Seed Availability Process Diagram

Licensed Dealer

State Agri. Dept

Seed Availability

Dealer Registration

Updating daily stock

details over the web

Recording historical

database on existing

dealers

Registering

Dealership Code

Configuring

Database Parameters

Updating Stock

Details


Dealer Registration Process This use case will facilitate the dealer to register on the SAP for obtaining system generated password. By using this unique password, the actor would be able to log on to the SAP for accessing various applications.

Licensed Dealer, who wishes to access online services of the SAP.

Updating Daily Stock Details over the Web

Users Registered on the SAP, would be able to update daily

Licensed Dealers



stock details of Seed under ISS application using this use case.

Recording Historical Database of the Licensed Dealers

This use case will facilitate the actor to record the database of existing licensed dealers of last two years.

State Agriculture Department/Seed Distribution Agency

Updating Daily Stock Details through Mobile Application

This application will facilitate the actor to update daily stock details by sending an SMS over the installed mobile application on his/her mobile phone. This use cases would be required to complete this process. They are :

Registering Dealership Code This use case will facilitate the actor to register him on his mobile application using dealership code.

Licensed Dealer

Configuring Database Parameters

This use case will facilitate the actor to configure database parameters required to update daily stock details.

Licensed Dealers

Updating Stock Details This use case will facilitate the actor to update daily stock details on his mobile handset by sending SMS to the mobile application.

Licensed Dealers

3.2.3.1.1 DEALER REGISTRATION PROCESS

Use Case ID: UC_

Use Case Name: Dealer’s Registration Process

Actors: Primary Actor Licensed Dealers

Stake Holder: Dealers

Description: This use case will facilitate the actor to register himself/herself on the SAP/CAP for accessing applications and various services.

Trigger: The actor accesses the SAP Home Page through URL http://stateagricultureportal.in or CAP home page through URL http://centralagricultureportal.in after typing in the browser.

Pre conditions: Actor must have accessed the portal’s home page.

http://state/

http://centralagricultureportal.in/



Post conditions: 1. The actor clicks on the link “Save” The System responds with the message,” Dealer’s Registration details saved successfully.” a. The information would be available to modify/delete/freeze.

2. Once the actor clicks on the link “Register”, b. The System responds with the message, ”Dealer has been registered

successfully.” c. A system generated Password will be sent to the dealer’s registered

mobile number or an e-mail would be sent to the recorded e-mail address of the dealer. Simultaneously, a mail will be sent to the system administrator (pre define e-mail id) for maintaining records.

d. Auto generated password will be stored in database and actor could log on to the portal using this password. The auto generated password could be changed by the actor using “Change Password” option.

e. The registered details would be allowed to be modified by the actor through “Change User Profile” use case.

f. Dealer’s Registration details will be stored in the database of User Manager of CAP/SAP.

Input: Registration Form Details

Output: Successfully Registration of a Dealer and providing system generated password.

sNormal Flow Actor Actions

The actor accesses “Dealer’s Registration” option available on the SAP Home Page.

System Responses The system will prompt the actor to

specify following details in the system:

- Full Name of the applicant (in English)

- Full Name of the applicant (in Local Language)

- User ID - Adhar Number (optional) - License Number - License Validity Period (From

Date and To Date) There should be a provision to add multiple license numbers in to the system.

- Postal Address - Valid Mobile Number - E-Mail Address (optional) - Type of Dealer (Seed/

Fertilizer/Pesticide). Multiple selections permissible.

- Type of Business (Wholesaler/Retailer)

Upload Photograph Upload Scanned Copy of existing License



After specifying all the mandatory details, the actor may choose one of the following options:

Save Register Save: Actor clicks on the Save option, if the details have been specified and the actor does not want to finally submit details. Register: Actor clicks on the Register option to finally submit the Registration details.

The system should validate the specified license numbers with the core database of license application while saving data. If the license number doesn’t match with the core database, the system should flash message,” License number doesn’t found” and system should not allow saving details in database.










Required


High


medium/ less/ rare

Medium

Business Rules: All fields except Adhar Number and Email are mandatory for the dealers to specify.

Maximum permissible length for the field Mobile Number should be 10 digits.

The System should check the validity and authentication of mobile number and e-mail (like online Railway Registration).



Relationships Extends SAP Home Page Is Extended By None Uses Login


Assumptions: 1. Hardware like mobile phone and network connection is available to the actor.

2. The actors are having a valid mobile number registered in the database.

Dependency: None


3.2.3.1.2 UPDATING DAILY STOCK DETAILS OVER THE WEB

Use Case ID: UC_

Use Case Name: Dealer’s Stock Details

Actors: Primary Actor Licensed Dealers

Stake Holder: Farmer/Citizen

Description: The actor could maintain their daily stock details online over the web by specifying sold quantity of seed varieties during the day.

Trigger: Actor Logs on to the Portal and selects the option available Seed->Knowledge Management System->Content Management System-> Dealer’s Stock Details

Pre conditions: 1. The actor must be registered either on the CAP or SAP. He must be logged in,

and should have permissions to access ISS and Dealer’s Stock Details page in it

2. Dealer’s license details should exists in the core database of license application

on SAP.



Post conditions: 3. The actor clicks on the link “Save” The System responds with the message,” Stock details saved successfully.” g. The information would be available to modify/delete/freeze.

4. Once the actor clicks on the link “Freeze”, h. The System responds with the message, ”Stock details have been frozen

successfully.” i. Dealer’s stock availability with sale price will be sent to his/her

registered Mobile Number. j. The freeze stock details will be allowed to unfreeze/modify/delete by

the authorized actor only. k. The frozen availability of stock items and their prices will be displayed

to the farmers/citizens on the SAP and the application Main Page. l. The displayed stock details could be shown area wise, through the GIS

on the SAP. m. The previous day stock details will not be allowed to modify. n. Daily Closing Balance of the dealer’s stock will be computed by the

System. o. Closing Balance of the previous day will be treated as available sock of

the next day (to be displayed on SAP) until it gets updated by the dealer.

p. A report showing the dealer’s details and numbers, who have not specified their stock details.

Input: Opening Balance Total Quantity of the crop variety received during the day Total Quantity of the crop variety sold during the day Sale Price

Output: Area Wise-Crop -Variety Wise available quantity of seed per day in the dealers stock will be displayed on the SAP in drill down report.

sNormal Flow Actor Actions The actor clicks on the option

“Dealer’s Stock Details”.

System Responses The System will prompt the actor to specify following details::

a. Crop Variety: The system will display a list of all the crop varieties, for which he/she has obtained dealership license.

b. Select Date: By default, current System date will be displayed.

c. Opening Stock for the selected crop variety (in Quintals): The actor would specify the available stock opening balance for the day. By default, previous day closing balance will be available as opening balance. The actor could modify the figure.

d. Crop Variety Received during the day (in Quintals)



e. Crop Variety Sold during the day (in Quintals)

f. Closing Balance for the selected crop variety

g. Sale Price The actor could specify stock opening balance details of the multiple crop varieties. Once the actor specify all the required information, he/she can choose one of the following links: Save Edit Delete Freeze Unfreeze Clear Close Save: The actor clicks on the save link to save data in the database. The save data will not be available to access throughout the application. Edit: The actor may click on the edit link to modify the saved information. Unfreeze: Once the details have been verified and confirmed, then only the authorized actor could unfreeze the freeze details and modify. Verify and Freeze: Once the actor has verified and frozen the specified details, the System will not allow modifying the entered details.












Required


High


medium/ less/ rare

Medium

Business Rules: If the actor doesn’t specify the stock details, System will send reminder SMS to update the details around 5.00PM.

Relationships Extends ISS Home Page Is Extended By SAP Uses Login


Assumptions: 1. The actor is registered either on CAP or SAP and access the application/service through single sign on.

2. Hardware like mobile phone and network connection is available to the actor.

3. The actor and farmers are having a valid mobile number registered in the database.

4. District Administration will be responsible for monitoring transactions and implementation of the application.

Dependency: None


3.2.3.1.3 RECORDING HISTORICAL DATABASE OF THE LICENSED DEALERS

Use Case ID: UC_

Use Case Name: Historical Database of Licensed Dealers

Actors: Primary Actor State Agriculture Department/Seed Distribution Agency

Stake Holder: Dealer

Description: This use case will facilitate the actor to specify the details of the existing licensed dealers in to the system.

Trigger: The actor Logs on to the Portal, accesses the ISS Home Page over the web and selects the option available Seed->Knowledge Management System->Content Management System-> Historical database of existing licensed dealers.



Pre conditions: 1. The actor must be registered either on the CAP or SAP. He must be logged in,

and should have permissions to access ISS and Historical database of licensed

dealer’s page in it.

3. The dealer being specified in the system must have dealership license issued

earlier.

Post conditions: 1. The actor clicks on the link “Save” The System responds with the message,” Dealer’s details saved successfully.” q. The information would be available to modify/delete/freeze.

2. Once the actor clicks on the link “Freeze”, r. The System responds with the message, ”Dealer’s details have been

frozen successfully.” s. The System will generate a unique dealership id in a pre define format

of <<Pin Code-Dealer Name>> of the sale address. t. Dealer’s name should be added in the dealer’s network being displayed

on the SAP home page under available link. u. The dealership code will be sent to the dealer’s registered mobile

number (if exists) and a consolidated report of dealership code will be generated by the system. This report will be sent to the State Agriculture Department as well as to the data entry agency for communicating it to the concerned dealer, through traditional method. Using this dealership code, the dealer would be able to update daily stock details through mobile application.

v. The freeze licensed dealer’s details will be allowed to unfreeze/modify/delete by the authorized actor only.

w. If the dealer’s Pin code gets changed in the system, a new dealership code will be generated by the system and an SMS will be thrown to the dealer’s registered mobile no.

Input: Dealer’s Licensing Details

Output: 1. Dealer’s details will be updated in to the core database of Dealers. 2. An auto generated dealership code should be communicated to the dealer.

sNormal Flow Actor Actions The actor clicks on the Historical

database of existing licensed dealers

option.

System Responses The System will prompt the actor to specify following license details of the dealers:

- Full Name of the dealer (in English)

- Full Name of the dealer (in Local Language)

- Adhar Number (optional) - License Type

(Original/Renewed/Duplicate - License Number



After specifying all the mandatory details, the actor may choose one

- License Validity Period (From Date and To Date)

- If license is renewed, then Renewal Number and Renewal Date

- If license id Duplicate, then Duplicate license Issuing Date.

- Postal Address - Valid Mobile Number

(Optional) - E-Mail Address (optional) - Place of Business (give exact

details including District, Block and PIN Code ) For Sale For Storage

- Type of Business (Wholesaler/Retailer).

- Type of Dealership (Proprietary/Partnership/ Limited Company/ Hindu undivided Family concern)

- Address of Proprietary/Partnership/ Limited Company/ Hindu undivided Family concern

- Capacity of the Application: Proprietor/Partner/Manager/Karta

- Was the applicant ever convicted under the Essential Commodities Act, 1955 (10 of 1955), or any order issued there under during the last three years preceding the date of the application? If Yes give details:

- Details of the Seed Handled: Name of the Seed/Variety Company Name

Other details, if any - Designation of the License

Issuing Authority (for the selected License Type)

- Name of the License Issuing Authority (for the selected License Type)



of the following options: Save: Actor clicks on the Save option,

if the details have been specified and the actor does not want to finally submit details.

Freeze: Actor clicks on the Freeze option to verify and freeze the details.

The recorded details will be stored in database.

The recorded details will be stored in database and the system will trigger the alert System.










Required


High


medium/ less/ rare

Medium

Business Rules:

Relationships Extends ISS Home Page Is Extended By SAP Uses Login

Special Requirements: Crop Varieties Should specify in Master Database.

Assumptions: 1. The actor is registered either on CAP or SAP and access the application/service through single sign on.

2. Hardware like mobile phone and network connection is available to the actor.

3. State Administration will be responsible for monitoring transactions and implementation of the application.

4. Email address of the State Agriculture Department’s concerned officer and the agencies should be stored in database for sending dealership codes.

Dependency: None




3.2.3.1.4 DEVELOPMENT OF SMS APPLICATION BASED ON NIC SMS GATEWAY

3.2.3.1.4.1 Dealers registration through mobile SMS

UC 3.1.1.1 Registering Dealership Code

Version:

Context:

This use case will be used to register the dealer to use the mobile application. The ID’s would be registered into the mobile device only for the first time of the launch of the application. It will not appear for the subsequent times of launching until mobile number doesn’t change.

Priority: High

Frequency: High. This is mandatorily required for the users.

Primary Actor: Wholesaler, Retailer

Preconditions:

The actor must have downloaded the application set up available on the SAP.

The actor must have transferred the application

Mobile application is installed and running at the user mobile handset (Note: The actor could transfer application set up either trough Bluetooth device or Data Cable from the desktop/laptop in to his/her mobile handset)

Actors have a valid (Pin Code/Dealer Name) dealer id received on his/her mobile number.

The actor using the same mobile number on which he/she has received dealership code.

Basic Flow: 1 Enter Registration data System presents with an interface of entering data. The system interface presents with following items:

- Dealership Code – The System will prompt the actor to enter his dealership in the available text

- User will instruct to save data and application will perform the following validation before saving into the local storage.

- Valid ID is entered and it is in the format <<Pin code/Dealer Name>> - Application saves data. Input interface will disappear.

The use case ends.

Alternative Flow: 1 Invalid data Application will check for any invalid ID and if data is not valid, it will flash message to user to enter correct data and no SMS will be sent to the web server. No data will be saved in the system.



Post Condition Data will be saved in the local mobile storage as well as core dealer’s database.

The System will generate a 4 digit numeric PIN, which would be required to submit details to the mobile application.


1 The dealer must have a GSM based mobile. Mobile application will not be accessible through CDMA mobile phones.

2 When the application is removed /uninstalled from the mobile system, the saved data (dealer ID) will also be removed from the mobile handset.

3 If a new dealership code has been sent to the dealer with the same mobile number <<refer use case Historical Data base of existing dealers>> , the new dealership code will automatically be synchronized with the dealer’s registered mobile application and the dealer would not be required to register his new dealership code in his/her mobile application.

4 If, the dealer’s registered mobile number has been changed, new dealership code will be generated by the web system, after its updation with the SAP <<refer use case Historical Data base of existing dealers>>. District Administrator would be responsible for updating dealer’s mobile number into his/her license database.

5 If the dealer’s mobile hand set gets changed, the dealer will have to again install the application in his handset and he/she will have to re register his dealer ship code in the installed application.

Unresolved Issues:

None

3.2.3.1.4.2 Configure Database Parameters

UC Name Configure Database Parameters

Version:

Context: This use case will be used to specify basic stock master database requirements in to the mobile application. Actors will be presented with an interface where they can enter data.

Priority: High

Frequency: When the crop variety already exists in the master database of core SAP database.

Primary Actor: Registered Dealer accessing mobile application

Preconditions:

The actor could configure only those crop’s varieties for which he/she has obtained license (these will be stored in SAP license dealer’s database)

The actor must have the seed variety codes available with him/her.

Actor has a valid dealer id and PIN.

Connectivity is good and no financial constraint is present to send the SMS from the mobile.



Trigger This use case starts when the actor runs the application set up and is prompted to configure database parameters.

Basic Flow: The system will prompt the actor to configure following parameters: Configure Crop Variety:

1 The actor would select the code of the Crop Variety, for which he/she is running selling business and would be required to update daily stock details.

2 The actor clicks on the save button to save the specified code variety in mobile application’s database.

3 The actor could configure multiple crop varieties upon selecting the appropriate menu.

Configure Units/Measure: 1 The actor would select the Units/Measures like Kg, Quintals etc, in which

the crop varieties are being sold. 2 The actor clicks on the save button to save the specified units in mobile

application’s database. 3 The actor could configure multiple units upon selecting the appropriate

menu.

Alternative Flow:

PIN Mismatch When PIN is wrongly sent with the transaction, mISS system will not process data and no data will be saved into the system.

Post Condition On BF1, AF4: The actor will send SMS to the mISS System. 16 digit transaction ID will be generated from the mISS system. Acknowledgement message (SMS) along with the transaction ID will be received by the sender on successful transactions. On AF 1,2: The system will halt and no SMS will be sent to the system. On AF 3: Response SMS will arrive from mobile application “crop variety code/unit already sent “information. No transaction ID will be generated. On AF5: As the mISS system will not process data, an SMS notifying wrong PIN will be sent to the sender.


Unresolved Issues:

3.2.3.1.4.3 Update Stock Details

UC Name Update Stock details.

Version:

Context: This use case will be used to enter daily stock details for different crop varieties. Actors will be presented with an interface where they can enter data.



Priority: Normal

Frequency: Daily, at the end of the day.

Primary Actor: Registered Dealer

Preconditions:

Actor’s mobile application should be functioning and installed.

Actor has a valid dealer id.

Actor has a valid PIN registered with the mISS system.

Actor should have configured the required database parameters (like Crop Variety and Unit) in the application.

Connectivity is good and no financial constraint is present to send the SMS from the mobile.

Basic Flow: 1 Enter Stock data System presents with an interface of entering detailed data of stocks. The system interface presents with following items: 1 (A) Basic Information entry.

a Date of sending – an input area where valid stock entry date is entered. Default value is current date in dd/mm/yyyy format.

1(B) Stock details entry

b Crop Variety: actor will be presented with an interface where the actor can select crop variety from the list.

c Unit or Measure: Actor will be presented with an interface where the user can enter Quantity in Kg or Quintals.

d Sale Price (Rs/Unit): Actor will specify sale price of the selected crop variety for the selected unit.

e Stock opening balance for the day (in Unit): Actor will specify the stock opening balance of the selected variety for the day.

f Crop Variety received during the day (in Unit): Actor will specify receipt quantity of the variety during the day.

g Crop Variety sold during the day (in Unit): Actor will specify sold quantity of the variety during the day. It would be mandatory to specify. The default value will be 0.

h Closing Balance: The System will compute stock closing balance for the day.

i Actor can enter stock details for multiple crop varieties with steps

mentioned in 1(B) upon selection of appropriate application menu.

j When sale transaction details are filled up completely, then the user will be asked for the valid PIN which is assigned to him/her.

Before sending data to the core ISS system ,application checks the validation as below:

- Valid stock entry date is entered in date format dd/mm/yyyy - Valid Sender Dealer ID is entered and it is 6 digit numeric - Valid crop varieties from the database. - Unit selected properly.



- 4 digit numeric PIN is entered

k Upon completion, mobile application will send an SMS to the core ISS system as an SMS and the stock details will get updated in the core database of SAP.

l The System will send SMS to the registered farmers belonging to the dealer’s location area (district/block) regarding available stock quantity of the crop varieties and their Sale Prices. Dealer’s location could be traced from the sale address specified in the dealer’s license details in the core SAP database.

The use case ends.

Alternative Flow:

1 Crop Variety/Date/Unit/Stock Opening Balance/Received 2 Quantity/Sold Quantity not specified When these are not selected properly, system will not proceed and inform the user to enter valid data, and use case ends. 3 Duplicate stock Stock update from same dealer for the same date and same crop variety will be considered as duplicate.SMS will be generated and sent to the system. Back end application will validate for duplicity checks for the system date. Last updated information would be considered as the final stock details for computation of the Stock Closing Balance for the day. 4 PIN Mismatch

When PIN is wrongly sent with the transaction, mISS system will not process data and no data will be saved into the system.

Post Condition On BF1, AF4: The actor will send SMS to the mISS System. 16 digit transaction ID will be generated from the mISS system. Acknowledgement message (SMS) along with the transaction ID will be received by the sender on successful transactions. On AF 1, 2: The system will halt and no SMS will be sent to the system. On AF 3: Response SMS will arrive from mobile application “Stock for this crop variety already sent “information. No transaction ID will be generated. On AF5: As the mISS system will not process data, an SMS notifying wrong PIN will be sent to the sender.


There will be database synchronization between core SAP database and mISS application. Date and Time of Last updation of stock details should also be displayed on SAP.

Unresolved Issues:

3.2.3.2 License Application



Process Diagram

Person/Agency

State Agriculture Dept

Licensed Dealer

District Agriculture DeptField Inspector

Range Agriculture Dept

Process for obtaining Dealership License in

Seed

Registration Form to

obtain dealership license

Application

Acceptance

Forward Application

for filed inspection

Site Inspection

Report

Issue Dealership

License

Request for

Duplicate License

Suspension/

Cancellation of

License

Application for

obtaining license at Range Level

Request for renewal of

license


Application Form to obtain Dealership License

This use case will facilitate the actor to apply for obtaining dealership license in seed at State level and District level

Person/Agency

Application Acceptance There will be a provision in the system to verify the submitted new/renewed/duplicate application form details and specifying the physically verified documents. After specifying verification details, the actor could specify application status as accepted/rejected.

State and District Agriculture Department For Range level applications, assigned authority at range level.

Forward Application for Physical Verification

This use case will facilitate the actor to forward the accepted

Empowered authority at State/District/Range level



applications for site inspection to the designated inspector.

Agriculture Department

Physical Verification Details This use case will facilitate the actor to specify site verification details. For applications at rage level, site inspection is an optional process depending on the satisfaction of the range level agriculture department.

Field Inspector

Issuing Dealership License This use case will facilitate the actor to issue a ne/renewed dealership license in seed based on the positive site verification details.

Empowered authority at State/District/Range level Agriculture Department

Endorsement in license If the actor wishes to apply for selling more crop varieties in the existing dealership license, he/she will submit a simple request for endorsement of license interface to the concerned license issuing authority, who issued the license earlier.

Licensed Dealer/Agency

Application for Renewal of Dealership license

This use case will facilitate the actor to submit application for obtaining renewed license.


Application for obtaining dealership license at Range Level

This use case will facilitate the actor to submit application for obtaining dealership license at range level. The actor could apply at range level only if, he/she has a dealership license issued at district covering under the selected range.


Application for Duplicate License This use case will facilitate the actor to apply for obtaining duplicate dealership license in case original license has been lost/damage/tear away.


License Suspension/Cancellation This use case will facilitate the actor to suspend/cancel the license and specifying details based on the negative test reports provided by the Seed Testing Laboratories against the suspicious activities of complaints received

Empowered authority at State/District/Range level Agriculture Department



3.2.3.2.1 APPLICATION FORM TO OBTAIN DEALERS LICENSE (FORM A)

Use Case Field Description

Use Case Name Application Form to obtain Dealers License (Form A)

Actor(s)

Primary Actor

A person/agency desiring to obtain a dealership license either at State level or

district level for seeds.

Secondary Actor

Payment Gateway

Description

This use case facilitates the actor of the belonging State who desires to obtain a

dealership license at State or at district level to submit an application form

online in request to obtain Dealers License. The application will be forwarded

to the authorized officer for physical verification of the documents.

Pre Conditions The user must be registered either on the CAP or SAP and should have

permissions to access the Form A.

Triggers The actor chooses to select Transactions-> Application Form to obtain Dealers

License (Form A)-> Apply

Normal Flow

On the top of the form, the System will display a Help option, which the actor

can select to seek guidance about how to specify information in various fields.

The System will prompt the actor to specify the following details in to the

System:

1. Full Name of the Applicant: The actor would specify his/her Full Name or

the agency name which he/she wants to print on the License.

2. Postal Address: The actor would specify the complete postal address.

3. Place of the Business (Please give exact address):

a. For Sale: The actor would specify the complete address of the place

where, he/she wants to sale the seeds. The actor could specify address

of one place only. To carry on business in multiple places, actor will

have to get separate licenses for each place.




b. For Storage: The actor would be specify the complete address of the

place where, he/she wants to Store seeds to be sell.

4. Type of the Dealership: The actor would select the dealership type from

the drop down enlisting following dealership types:

Proprietary/Partnership/ Limited Company/ Hindu undivided Family

concern.

5. Name and Address of the Proprietor/Partner/Manager/Karta: The actor

would specify names of the Proprietor/Partner/Manager/Karta. The actor

could specify multiple names and their addresses (State, District, Block,

and PIN Code).

6. In what capacity this application is made? - The actor would select

capacity of the application from the drop down enlisting following options:

Proprietor/Partner/Manager/Karta.

7. Was the applicant ever convicted under the Essential Commodities Act,

1955 (10 of 1955), or any order issued there under during the last three

years preceding the date of the application? If Yes give details: The actor

would specify the required details.

8. Details of the Seed handled: The actor would specify the details of the

seeds handled in the following fields:

Name of the Seed/Variety

Name of the Parent Agency

Address of the Agency

Other Details, if any…………….

The actor could specify details of multiple seeds.

9. Make Payments

The System will prompt the actor to select Mode of Payment.

I. The actor could select one of the following Mode of Payments:

Through Treasury

Through Bank




In bank, the actor could deposit payment using

- Demand Draft

- Cheque

- Online Payment- For online payment, the actor could choose one

of the following options:

Internet Banking

Debit Card

Credit Card

If actor selects Payment through Treasury, the System will prompt to

specify following details:

Challan No:

Date of Challan:

Treasury Name: The System will prompt the actor to select the

treasury name from the drop down enlisting all the treasuries

created under the State.

If actor selects Mode of Payment as Cheque, the System will prompt to


Check No:

Check Date:

Cheque Deposited In: Bank

If actor selects Bank, the System will prompt the actor to select the Bank

Name from the drop down enlisting all the

Central/State/Cooperative/Private banks specified in the database. Select

name of the bank in which the Cheque was deposited.

If the actor selects treasury,

If actor selects Mode of Payment as DD, the System will prompt to





DD issuing Bank Name

As the actor selects Bank, the System will prompt the actor to

select the Bank Name from the drop down enlisting all the

Central/State/Cooperative/Private banks specified in the database.

Select name of the bank in which the DD was deposited.

DD No

DD Date

Payable At: Account Holder Name

The System will prompt the actor to specify the Amount of the license fee

paid.

If actor selects Mode of Payment as Internet Banking/Debit Card/Credit

Card under online payment option,

The System will navigate the actor to the use case Payment Gateway to

make payment online.

10. The actor will go through the declarations specified on the form in read

only mode.

11. After that, the system will prompt the actor to upload the required

documents for verification through Attach Documents Use Case.

The actor will have to upload following documents:

a…………………..Upload

b…………………..Upload

c……………………Upload

12. Upload Photograph

13. The actor may drop the uploaded attachments by using the functionality

of Drop Documents Use Case.

14. After specifying all the mandatory information, the actor could select one




of the following links

Verify Check List

Submit Form

Save

Clear

Close

Verify Checklist: As the actor selects this link, the System will display a checklist

to the actor to verify the entered details and whether all the required

documents has been submitted or not.

Submit Form: The actor may click on the Submit link, once the Check list has

been verified successfully.

Save: The actor may click on the Save link, if he/she doesn’t wish to Submit the

application at that particular moment and wants to save the entered details.

Clear: The actor may click on the Clear link, if he wants to remove the entered

details.

Alternative Flows

1. Form A would also be available on the SAP for download. The actor

may download the form and submit it manually to the Directorate of

Agriculture, Seed after specifying all the mandatory details, depositing

fee of 50 Rs and attaching the required documents.

2. The System will also facilitate the actor to download the Verifying

Checklist in PDF format.

Post Conditions

1. If the Check list has been verified successfully, the System will respond

with an alert message,” Application has been verified successfully.

Please click on the Submit link to submit the application.”

2. If the actor clicks on the Submit link, the System will respond with an

alert message,” The application has been submitted successfully.”

a. The System will generate an application reference number in a

predefine format and an SMS/e-mail alert will be thrown to the

applicant on the registered Mobile Number.




b. The application Status in the System will be changed as “Pending for

physical verification “in database. The application status will be

displayed in the View Application Status use case.

c. Application Status will also be displayed on the SAP by clicking on the

link available.

d. The application will be forwarded to the assigned officer, Seed for the

physical verification of the documents through Application Acceptance

use case.

3. If the actor clicks on the Save link, all the entered information would

be stored in database and the actor can submit the application later on.

4. If the actor clicks on the Cancel link after saving the form earlier, the

Form A would be cancelled and the actor would be brought back to the

Main Manu Page without changing the data.

5. If the actor clicks on the Cancel link without saving the form once, the

System would respond with the message,” All entered details would be

lost. Do you still wish to continue?”

If the actor chooses yes, the Form A page would be cancelled with the

loss of entered details and the actor would be required to reenter the

details.

If the actor chooses No, the System will retain the Form A Page with the

entered details.

Exceptions

Priority High

Business Rules Seed Control Order 1983

Relationships

Extends

Attach Documents

Drop Documents

Is Extended By




Payment Gateway

Uses

Login

Special Requirements Fee shall be come from Fee Master.

Assumptions The interface will be designed separately for State level, District level and

Range level.

Note

3.2.3.2.2 APPLICATION ACCEPTANCE

Overview: The applications with the confirmed documents submitted will be forwarded to the actor for acceptance and field inspection.

Use Case Name: Application Acceptance

Actors: Primary Actor Officer authorized to physically verify the documents and application acceptance (Role assigned at State/District/Range level)

Stake Holder: Person/Agency who submitted the Form of application to obtain a Dealer’s License

Description: This use case will enable the actor to select the form of applications submitted by the person’s/agencies to obtain the dealer’s license (for Seed), whose documents have been physically verified and pending for acceptance/rejection of filed inspection. All the pending applications will be highlighted to the actor with a flag set as “Pending”.

Trigger: The actor selects the option available Transactions->Application Acceptance

Pre conditions: 1) The user must be registered either on the CAP or SAP. He must be logged in, and

should have permissions to access ISS and Acceptance Application page in it.

2) There must be at least one application available with the status “Pending”.

3) The actor must have received deposited fee draft/challan along with the photo

copy of the application form.



Post conditions: 1. Once the actor clicks on the link “Accepted”,

a. The System will respond with an alert message, “The application has been accepted successfully.”

b. An SMS alert in a pre define format will be thrown to the person’s/agencies mobile number which registered in our database.

c. The status of the accepted application will get updated with the status “Accepted” or “Rejected based on the selected link by the actor in the “View Status of the Application” page and on the SAP under the available link.

d. The accepted application will not be available to the actor for modification and deletion.

e. The accepted applications will be forwarded to the DOA for site inspection.

f. In case application type is “Renew”, Physical Verification of Site will be optional to specify, so the application will be directly available to the license issuing authority for issuing license.

g. In case applications have been received at Range Level, Physical Verification of Site will be optional to specify, so the application will be directly available to the license issuing authority for issuing license.

Input: 1. Select one application from the list of pending applications for field inspection and acceptance.

2. Verify the entered details and Click on the “Accept” link.

Output: The accepted application form will be forwarded to the assigned license issuing authority for moving it to the site inspection.


“Application Acceptance”.

The actor selects one of the application records to verify.

System Responses On the top of the form, the System will

display a Help option, which the actor can select to seek guidance about how to specify information in various fields.

The System will provide a list of all the pending applications for acceptance with the following information: S. No, Reference No, Application Submission Date, Application Type (New/Renew/Duplicate) and Application Status as Pending for field inspection.

The System will display all the information recorded in the application form through use case “Form of Application to obtain Dealer’s License” in read only mode. The actor



Once the actor verifies the

entered information, the actor may choose one of the following links: Accept Reject Close

The actor selects the “Accept” link to accept the application if all the details get verified.

The actor may select the “Reject” link, if the entered information doesn’t satisfy the acceptance criteria or the documents are incomplete.

The actor may click on the “Close” link to close the “Application Acceptance” page.

could either download/print/View the attached document by clicking on the respective links available for maintaining records and verification.

System captures the input, changes

the status to “Document

submission” as approved and

sends triggers to alert system.

The actor will specify the Remarks,

if any.





Required


High


medium/ less/ rare

Frequent



Business Rules: 1. The actor will not be allowed to drop/delete the attachments. 2. The attached documents could be in .txt, .pdf, .docx, .doc, .xls, .jpg, .grf,

.jpmg formats. 3. Only one record at one time could be allowed to select for acceptance. 4. Seed Control Order 1983 5. If the license of the applicant has been suspended earlier, the System should

generate an alert to the actor for not accepting the application. 6. If the duration between license cancellation date and re issuance of license

date is less than one year, the system should generate an alert to the actor for not accepting the application.

7. If the applicant is convicted under the Essential Commodities Act, 1955 (10 of 1955) or any order issued there under within three years preceding the date of application (as specified in the application form), system should generate an alert to the actor for not accepting the application.

Exceptions: The actor selects the attachment file for deletion The System responds with a message,” File cannot be deleted. You may either download/print or View the document.”

Relationships Extends

ISS Menu Page

Is Extended By Site Verification Uses Login


Assumptions: The actor is registered either on CAP or SAP and access the application/service through single sign on.

Hardware like computer/laptop system and network connection is available to the actor.

The actor is having a valid mobile number.

Dependency: None

Notes and Issues: The interface will be designed separately for State level, District level and Range level.

3.2.3.2.3 FORWARD APPLICATION FOR PHYSICAL INSPECTION OF SITE

Use Case Name: Forward Application for Site Inspection

Actors: Primary actor License Issuing Authority (LIA at State/Rage/District level).

Description: The System will facilitate the actor to forward the accepted physically verified document application to the field inspector for physical site inspection, incase he/she find anything suspicious about the applicant.

Trigger: The actor chooses to click on the link available under ISS Home Page->Transaction->License Application-> Forward Application for Site Inspection



Pre-conditions: Actor had logged into the ISS application and has chosen to forward applications to the site inspectors.

Post conditions: 1. If the application has been forwarded to the site inspector, “Trigger mail / msg will be sent to the field inspector and the applicant for information purpose.”

2. The status of the accepted application will be displayed on the SAP and the ISS service home page as “Pending for Site Inspection”.

3. The stakeholder could track the status of his/her application using application reference number on the SAP.

4. Saved details will be available for modification and deletion by the actor.


Actor clicks on the link “

Forward Application for Site

Inspection”

In case actor doesn’t satisfied

with the documents, the Actor

may select one or multiple

records to forward them to the

site inspector for field

inspection.

As the actor click on the link

available for the record, the

system will display the

application details specified by

the applicant in read only

mode. The actor could

download the attached

documents in PDF format for

record purpose.

The actor will select the Name

of the Field Inspector to who

he/she desires to forward

application.

System Responses

The System will display

all the accepted

applications forwarded

through the “Application

Acceptance” use case to

the actor for issuing

license.

The System will enlist

the names of the field

inspectors specified in

our master database.

Multiple applications



After specifying the required

details, the actor may click

on the “Forward” option, to

forward it to the selected

field inspector.

could be assigned to one

field inspector for site

inspection.

Before sending the data to

the core system needs to

validate the input fields

and also verify the check

list as below:


None


Required


High


medium/ less/ rare

Frequent

Business Rules: As per Seed Control Order 1983.

There should be at least one record selected for the field inspector.

Special Requirements: Field Inspector details should be specified in Master database.

Assumptions: None

Dependency: Extends ISS Home Page Is Extended By Physical Verification Report Uses Login

Notes and Issues: The interface will be designed separately for State level, District level

and Range level.

3.2.3.2.4 PHYSICAL VERIFICATION REPORT

Use Case Name: Physical/Site Verification Report

Actors: Primary actor The agriculture officer/field inspector

Description: The System will facilitate the actor to specify the site verification details.

Trigger: The actor chooses to click on the link available under ISS Home Page->Transaction->License Application-> Site Verification Report



Pre-conditions: Actor had logged into the ISS application and has chosen to specify site verification details of the applicant.

Post conditions: 5. If the physical verification details have been submitted by the actor, “Trigger mail / msg will be sent to the assigned authority and Dealer with the status of the physical verification” and recommendation will be forwarded to the concerned LIA for report verification.

6. The status of the physical verification of the application will be displayed on the SAP and the ISS service home page.

7. The stakeholder could track the status of his/her application using application reference number on the SAP.

8. Saved details will be available for modification and deletion by the actor.


Actor visits the applicant’s

site/shop and evaluates the

suitability.

Actor logins and System

presents the actor with an

interface with listing of ‘the

applications forwarded by

the license issuing authority

to him for physical/site

verification.

Actor enters the

recommendation and

submits, if the details have

System Responses

The System shows the

recommendation fields

to be filled by AO

If actor doesn’t find

physical verification

positive, the status of

the application will be

changed as “Rejected”

and an alert message

will be thrown to the

stakeholder’s registered

mobile no.



been confirmed by him/her.

Actor shall submit the data

related to inspection report

and also upload all scan copy

to system which is used

during the physical

verification.

The actor may click on the

“Save” option, if the entered

details could be modified by

the actor.

Before sending the data

to the core system

needs to validate the

input fields and also

verify the check list as

below:

a. The Physical Verification report must be uploaded.

b. Data shall not be blank.


None


Required


High


medium/ less/ rare

Frequent

Business Rules: As per Seed Control Order 1983.


Assumptions: None

Dependency: Extends ISS Home Page Is Extended By Issue Dealership License in Seed Uses Login




3.2.3.2.5 ISSUE DEALERSHIP LICENSE IN SEED

Overview: The site inspection reports submitted by the site inspector will be available to the actor for approval and issue a new dealership license in Seed.

Use Case ID: UC_31

Use Case Name: Issue Dealership License in Seed (Form B)

Actors: Primary Actor State/District /Range level official authorized to issue license.

Stake Holder: Person/Agency who submitted the Form of application to obtain a Dealer’s License (Form A)

Description: a. This use case will enable the actor to select the form of applications for which site inspection report has been positively verified by the field inspector through the use case Physical Verification Report. The applications which are pending for issue License will be highlighted to the actor with a flag set as “Pending”.

b. The applications to be applied at Range level would be optional to have physical site verification report. Depending on the sufficient attached supporting documents, the license issuing authority at range level may issue license.

c. If the actor has received a request application from the licensed

dealer to grant permission for selling more crop varieties, a letter for granting permission to sell more crop varieties will be issued to the requested dealer.

Trigger: The actor selects the option available Transactions->Issue Dealership License in Seed

Pre conditions: 1. The user must be registered either on the CAP or SAP. He must be logged in, and

should have permissions to access ISS and Issue Dealership License in Seed page in

it.

2. There must be at least one application available with the field inspection report

specified by field inspector.

Post conditions: 1. Once the actor clicks on the link “Issue License”, a. The System will generate a License in a predefine PDF format (Form

B) along with a License number, dealership code and an alert message stating, “The License has been generated successfully. License number is <License number> and Dealership Code is <Dealership Code>” Will be displayed to the actor.

b. An SMS alert in a pre define format including <License Number> and <Dealership Code> will be thrown to the person’s/agencies mobile



number which is registered in our database. Similarly, the License could be emailed to the person’s/agency’s registered email id registered in our database.

c. The status of those applications for which License has been issued will get updated with the status “License Issued along with its License number and dealership code” or “Issue of License Pending along with the application Reference No” in the “View Status of the Application” page and on the SAP under the available link.

d. If Site Verification Report is not approved by the AO, a 15 days grace period alert message will be sent to the applicant’s mobile no and e-mail id for re-verification of the site.

e. The applications with the 15 days grace period will be forwarded to the concerned site inspector for re verification within 15 days.

f. Based on the provided dealership code or the license number, the stakeholder can search the status of the License on SAP/Service home page.

g. For the renewed license applications, license renewal number will be thrown to the actor’s mobile number as an SMS.

h. The applications for which License has been issued will not be displayed to the actor for reissuing License.

i. The System should generate a monthly report displaying licensed dealers, whose site inspection time limit is exceeding more than one year till that month. Once the license validity period gets over, an SMS alert should be thrown to the dealer about the last date of validity of the license.

j. The licensed dealers should be added in the dealer’s database on CAP/SAP and will be displayed in the link “Licensed Dealers Network” on the SAP.

Input: 1. Select one application from the list of accepted applications for issuing dealership license.

2. Date on which License is being issued and the License Validity Period. 3. Click on the “Issue License” link.

Output: The System will generate a license along with the License number in a predefine PDF format.


“Issue of Dealership License in Seed”.



The System will provide a list of all the pending applications for issuing license with the following information: S. No, Reference No, Application Submission Date, Application Type (New/Renew/Duplicate) and Application Status as Issue of License Pending.



The actor selects one of the application records to issue certificate.

The actor may verify the entered information and may choose one of the following links: Issue License Reject Grace Period Close

The actor selects the “Issue License” link to generate a dealership license for seed.

The actor may select the “Reject” link, if the entered information doesn’t satisfy him/her to issue license.

The actor may select the “Grace Period” option, if he/she doesn’t find the site verification report satisfactory and the application will remain pending for 15 days until the site is again verified by

Applications with positive field inspection reports will be enabled for selection. Whereas the applications with negative field inspection reports will be disabled for selection and details will be available in read only mode.

The System will display all the information recorded in the application form through use case “Form of Application to obtain Dealer’s License” in read only mode along with the attached documents. The actor could either download/print/View the attached documents by clicking on the respective links available for maintaining records and verification.

The actor will specify Date on which license is being issued and Date of the License Valid up to.

In case selected application is for renewal for license, the actor will specify License Renewal Date and Date of the License Valid up to.



the inspector. The actor may click on the “Close”

link to close the “Issue of Dealership License in seed” page.





Required


High


medium/ less/ rare

Frequent

Business Rules: 1. The actor will not be allowed to drop/delete the attachments. 2. Only one record at one time could be allowed to issue license. 3. Seed Control Order 1983


Relationships Extends Physical Verification Report Is Extended By Alert System Uses Login

Special Requirements: -If the actor has received an application from the dealer to grant permission for selling more crop varieties, a permission letter will be issued by the license issuing authority in PDF format.



The actor is having a valid mobile number and e-Mail id.

Dependency: None


3.2.3.2.6 ENDORSEMENT IN LICENSE

3.2.3.2.7 APPLICATION FOR RENEWAL OF DEALERSHIP LICENCE (FORM C)

Overview: The dealer whose dealership license has been cancelled or about to be cancelled can



submit an online application for its renewal through the use case Application for Renewal of Dealership License in Seed (Form C).

Use Case Name: Application for Renewal of Dealership License in Seed (Form C)


A person/agency whose dealership license has been cancelled or a dealer whose

dealership license is about to be cancelled.

Secondary Actor

Payment Gateway

Stake Holder: A person/agency whose dealership license has been cancelled or a dealer whose

dealership license is about to be cancelled.

Description: This use case facilitates the actor of the belonging State/district to submit an

application form online to renew the dealership license.

Trigger: The actor selects the option available Transactions-> Application for Renewal of Dealership License in Seed (Form C)

Pre conditions: 1. The user must be registered on the SAP. He must be logged in, and should have

permissions to access ISS and Application for Renewal of Dealership License in Seed

(Form C) page in it.

2. The person/agency must have a dealership license earlier issued by the belonging

state.

3. If the actor has granted permission for selling more crop varieties, the permission

letter issued by the LIA must be attached with it to be added in the renewed

license.

Post conditions: 1. If the Check list has been verified successfully, the System will respond with an

alert message,” Application has been verified successfully. Please click on the

Submit link to submit the application.”

2. If the actor clicks on the Submit link, the System will respond with an alert

message,” The application has been submitted successfully.”




predefine format and an SMS alert will be thrown to the applicant on

the registered Mobile Number.


acceptance “in database. The application status will be displayed in the

View Application Status use case.

2. Application Status will also be displayed on the SAP by clicking on the link available.

3. The additional crop varieties will be added in the renewed license.

4. The actor is renewing a dealership license either at the state/district/range level;

the application will be forwarded to the assigned document verification authority

at the DOA for acceptance through Application Acceptance use case.

5. If the actor clicks on the Save link, all the entered information would be stored in

database and the actor can submit the application later on.

6. If the actor clicks on the Cancel link after saving the form earlier, the Form A would

be cancelled and the actor would be brought back to the Main Manu Page without

changing the data.

7. If the actor clicks on the Cancel link without saving the form once, the System

would respond with the message,” All entered details would be lost. Do you still

wish to continue?”

If the actor chooses yes, the Form A page would be cancelled with the loss of

entered details and the actor would be required to reenter the details.

If the actor chooses No, the System will retain the Form A Page with the entered

details.

Input: Existing License No

Output: The application form will be forwarded to the license DOA, Seed.


“Application for Renewal of License”.

The actor specifies License no.



The System will prompt the actor to specify the License no issued earlier which he/she desires to renew. If dealer’s license details are available in license database,



The System will prompt the actor to specify the payment details of the renewal fee.

Based on the specified license no the system will display all the details specified in the original application form applied earlier through Form of Application to obtain a dealer’s license use case in read only mode.

The System will facilitate the actor to change the entered details by clicking on the Change hyperlink except State Name or the District/Range Name or Storage location specified in the original license. The System will maintain the history of the original information.

Make Payments

The System will prompt the actor to

select Mode of Payment. The actor

could select one of the following Mode

of Payments:

Through Treasury

Through Bank

In bank, the actor could deposit

payment using

- Demand Draft

- Cheque

- Online Payment- For online

payment, the actor could

choose one of the following

options:

Internet Banking

Debit Card

Credit Card



If actor selects Mode of Payment “

Through Treasury”

The System will prompt to specify following

details:

Challan No:

Date of Challan:

Treasury Name: The System will

prompt the actor to select the

treasury name from the drop

down enlisting all the treasuries


If actor selects Mode of Payment as

Check

The System will prompt to specify

following details:

Check No:

Check Date:


If actor selects Bank, the System will prompt

the actor to select the Bank Name from the

drop down enlisting all the

Central/State/Cooperative/Private banks

specified in the database. Select name of the

bank in which the Cheque was deposited.




DD,




As the actor selects Bank, the

System will prompt the actor to

select the Bank Name from the


Central/State/Cooperative/Priva

te banks specified in the

database. Select name of the

bank in which the DD was

deposited.

DD No

DD Date

Payable At: Account Holder

Name


Internet Banking/Debit Card/Credit

Card under Online Payment option,

The System will navigate the actor to the use

case Payment Gateway to make payment

online.

After specifying all the details

belonging to the selected mode

of payment, the System will

prompt the actor to specify

Amount of the license fee paid.

The actor will go through the

declarations specified on the



form in read only mode.

After that, the system will

prompt the actor to upload the

required documents for

verification through Attach

Documents Use Case.

The actor will have to upload

following documents:




The actor may drop the

uploaded attachments by using

the functionality of Drop

Documents Use Case.

After specifying all the

mandatory information, the

actor could select one of the

following links

Verify Check List

Submit Form

Save

Clear

Close

Verify Checklist: As the actor selects

this link, the System will display a

checklist to the actor to verify the

details which have been changed by

him/her and whether all the relevant




Submit Form: The actor may click on

the Submit link, once the Check list has


Save: The actor may click on the Save

link, if he/she doesn’t wish to Submit

the application at that particular

moment and wants to save the entered

details.

Clear: The actor may click on the Clear

link, if he wants to remove the entered

details.

Alternative Flow: Alternative Flow-1

If the dealer’s license details are not available in the license database, the system will

prompt the actor to specify all the details required to submit Application Form for

dealership license.

Alternative Flow-2

1. Application Form for renewal of license would be available on the SAP for

download. The actor may download the form and submit it manually after

specifying all the mandatory details, depositing fee of 20 Rs and attaching

the documents, for which information has been changed.

2. The System will also facilitate the actor to download the Verifying Checklist

in PDF format.




Required


Medium


medium/ less/ rare

Medium



Business Rules: 1. The actor will not be allowed to drop/delete the existing attachments. 2. The actor may download the existing attachments. 3. The attached documents could be in .txt, .pdf, .docx, .doc, .xls, .jpg, .grf,

.jpmg formats. 4. Only one record at one time could be allowed to select for acceptance. 5. Seed Control Order 1983

Exceptions: The actor selects the attachment file for deletion The System responds with a message,” File cannot be deleted. You may either download/print or View the document.” Actor changes the details in the application form and click on the verify checklist link without attaching the required documents. The system responds with the message,” All supporting documents against which the information has been changed need to be uploaded. Please upload all the documents for verification.” The actor changes the details in the application form and click on the Submit link, without verifying checklist. The system responds with the message,” Please verify checklist before submitting the application.”

Relationships Extends Download attachment Drop Attachment Is Extended By Acceptance Application Payment Gateway SAP Uses Login


Assumptions: The actor is registered either on SAP and access the application/service through single sign on.



Dependency: None


3.2.3.2.8 APPLICATION FOR OBTAINING DEALERSHIP LICENCE AT RANGE LEVEL

Overview: The dealer who has obtained dealership license at the district level and now desires to obtain license at the range level may apply an online application through the use case Application for Obtaining Dealership License at Range Level.

Use Case Name: Application for obtaining Dealership License at Range Level




A person/agency that has a dealership license at district level and now wish to obtain

license at Range level.

Secondary Actor

Payment Gateway

Stake Holder: A person/agency that has a dealership license at district level and now wish to obtain

license at Range level.

Description: This use case facilitates the actor to submit an application form online to obtain

dealership license at range level.

Trigger: The actor selects the option available Transactions-> Application for obtaining Dealership License at Range level

Pre conditions: 1. The user must be registered on the SAP. He must be logged in, and should have

permissions to access ISS and Application for obtaining Dealership License at Range

level page in it.

2. The person/agency must have a dealership license earlier issued at the district

covered under the respective range.

Post conditions: 1. If the Check list has been verified successfully, the System will respond with an

alert message,” Application has been verified successfully. Please click on the

Submit link to submit the application.”

2. If the actor clicks on the Submit link, the System will respond with an alert

message,” The application has been submitted successfully.”


predefine format and an SMS alert will be thrown to the applicant on

the registered Mobile Number.


acceptance “in database. The application status will be displayed in the

View Application Status use case.

3. Application Status will also be displayed on the SAP by clicking on the link



available.

4. The actor is applying at the range level; the application will be forwarded to the

assigned document verification authority at range level for acceptance through

Application Acceptance use case.

5. If the actor clicks on the Save link, all the entered information would be stored in

database and the actor can submit the application later on.

6. If the actor clicks on the Cancel link after saving the form earlier, the details

would be cancelled and the actor would be brought back to the Main Manu

Page without changing the data.

7. If the actor clicks on the Cancel link without saving the form once, the System

would respond with the message,” All entered details would be lost. Do you still

wish to continue?”

If the actor chooses yes, the application page would be cancelled with the loss

of entered details and the actor would be required to reenter the details.

If the actor chooses No, the System will retain application Page with the

entered details.

Input: Existing License No

Output: The application form will be forwarded to the authorized person for documents verification and application acceptance.


The actor clicks on the option “Application for obtaining License at the Range level”.

The actor specifies License no.



The System will prompt the actor to specify the existing License no issued at the district level.

Based on the specified license no the system will display all the details specified in the original application form applied earlier through Form of Application to obtain a dealer’s license use case in read only mode.

The System will display the Range of



The System will prompt the actor

to specify the payment details for applying at the range level.

the belonging district from the Range master.

The System will display the “Amount” to be paid.

Make Payments


select Mode of Payment. The actor

could select one of the following Mode

of Payments:

Through Treasury

Through Bank

In bank, the actor could deposit

payment using

- Demand Draft

- Cheque

- Online Payment- For online

payment, the actor could

choose one of the following

options:

Internet Banking

Debit Card

Credit Card



If actor selects Mode of Payment “

Through Treasury”

The System will prompt to specify following

details:

Challan No:

Date of Challan:

Treasury Name: The System will

prompt the actor to select the

treasury name from the drop

down enlisting all the treasuries





Check

The System will prompt to specify

following details:

Check No:

Check Date:


If actor selects Bank, the System will prompt

the actor to select the Bank Name from the


Central/State/Cooperative/Private banks

specified in the database. Select name of the

bank in which the Cheque was deposited.


DD,




As the actor selects Bank, the

System will prompt the actor to

select the Bank Name from the


Central/State/Cooperative/Priva

te banks specified in the

database. Select name of the

bank in which the DD was

deposited.

DD No

DD Date

Payable At: Account Holder

Name




Internet Banking/Debit Card/Credit

Card under Online Payment option,

The System will navigate the actor to the use

case Payment Gateway to make payment

online.

The actor will go through the

declarations specified on the

form in read only mode.

After that, the system will

prompt the actor to upload the

required documents for

verification through Attach

Documents Use Case.

The actor will have to upload

following documents:




The actor may drop the

uploaded attachments by using

the functionality of Drop

Documents Use Case.

After specifying all the

mandatory information, the

actor could select one of the

following links

Verify Check List

Submit Form

Save

Clear

Close



Verify Checklist: As the actor selects

this link, the System will display a

checklist to the actor to verify the

details which have been changed by

him/her and whether all the relevant


Submit Form: The actor may click on

the Submit link, once the Check list has


Save: The actor may click on the Save

link, if he/she doesn’t wish to Submit

the application at that particular

moment and wants to save the entered

details.

Clear: The actor may click on the Clear

link, if he wants to remove the entered

details.

Alternative Flow: Application Form for obtaining license at range level would be available on the SAP for

download. The actor may download the form and submit it manually to the concerned

department after specifying all the mandatory details, depositing required fee,

attaching original license obtained at District level, affidavit provided by the concerned

license issuing authority at district level and Form O scanned copies. The System will

also facilitate the actor to download the Verifying Checklist in PDF format.




Required


Medium


medium/ less/ rare

Medium



Business Rules: 1. The actor will not be allowed to drop/delete the existing attachments. 2. The actor may download the existing attachments. 3. The attached documents could be in .txt, .pdf, .docx, .doc, .xls, .jpg, .grf, .jpmg

formats. 4. The actor may attach scan copies of the documents. 5. The district wise Range Offices must be defined in master database. 6. Fee must be specified in Fee Master. 7. Only one record at one time could be allowed to select for acceptance. 8. Seed Control Order 1983

Exceptions: The actor selects the attachment file for deletion The System responds with a message,” File cannot be deleted. You may either download/print or View the document.” The actor changes the details in the application form and click on the Submit link, without verifying checklist. The system responds with the message,” Please verify checklist before submitting the application.”

Relationships Extends Download attachment Drop Attachment Is Extended By Acceptance Application Payment Gateway SAP Uses Login

Special Requirements: The actor will have to attach affidavit about positive site inspection report, issued by the license issuing authority at district level in Form O.

Assumptions: The actor is registered either on SAP and access the application/service through single sign on.



Dependency: None


3.2.3.2.9 REQUEST FOR DUPLICATE LICENSE

Use Case ID: UC_

Use Case Name: Request for Duplicate License

Actors: Primary Actor Dealer or the person who wishes to apply for a duplicate copy of dealership license.



Secondary Actor

Payment Gateway

Description: This use case facilitates the actor to apply online to obtain a duplicate copy of the existing dealership license.

Trigger: The actor clicks on the link available under transaction->Request Duplicate License.

Pre-conditions: 1. The applicant dealers should be registered on the CAP or SAP and should have permissions to access “Request for Duplicate License”.2. The validity of the existing license should not be expired.

Post conditions: a. As the actor clicks on the “Save”, The system will respond with the message,” Request Duplicate License details have been stored in database.”

b. The stored details will be available for modification/deletion. The actor clicks on the “Confirm”, a. The confirmed application details will be forwarded to the

application acceptance authority for verification of the application details.

b. An alert SMS will be thrown to the stakeholder’s registered mobile number through alert system use case.

c. The recorded details will not be available for modification/deletion.




Dealer logs on and clicks

the “Request duplicate

License”.

Actor enters the existing

unexpired License Number

and the reasons for getting

the duplicate copy (If the

license has been lost/tear).

Actor receives the ref. no of

the request submitted on

the registered mobile no.

If any fee to remitted, the

actor deposits online

payments using use case

“Payment Gateway” or

offline Cash/Cheque/DD

payments in Banks or

treasury.

After specifying all the mandatory

details, actor may choose one of

the following options:

Save: The specified details will be

stored in the database and the

actor could modify/delete the

stored information.

Confirm: The actor may confirm

the details entered and the

application would be submitted to

the application acceptance

authority for acceptance of

application.

System Responses If dealer’s license details are stored in license database of ISS application,

System shows the dealer's

License details stored in

database.

System captures the inputs

from the existing dealer’s

database, generates ref. no.

and triggers sent to the alert

system.



Alternative Flow If the dealer’s license details are not

available in the license database, the

system will prompt the actor to

specify all the details required to

submit Application Form for

dealership license.


None

UI: required/not

required

Required


Low



Rare

Business Rules: Seed Control Order 1983


Dealer must be a registered user; license should not be expired.

Assumptions: The actor is requesting for a duplicate copy of certificate, if either his/her

license has been lost/misplaced/tear or in any reason it is not available

with him/her.

Dependency: Extends ISS home page Is extended by None Uses Login

Notes and Issues: The interface will be designed separately for State level, District level and

Range level.

3.2.3.2.10 CANCELLATION/SUSPENSION OF THE LICENSE

Use Case ID: UC_

Use Case Name: Cancellation / Suspension of License

Actors: LIA at (State/District/Range level)

Description: The system will facilitate the actor to suspend or cancel the license of the



dealers in case of violation of rules and regulatory acts or the sample results forwarded by the Seed Testing Laboratories using use case “Sample Testing Details at Seed Laboratories”.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> “Cancellation / Suspension of License”

Pre-conditions: The applicant dealers should be signed up on SAP and should have permissions to access “Cancellation/Suspension of License”.

Post conditions: a. As the actor clicks on the “Save”, the system will respond with the message,” Suspension/Cancellation of License details has been stored in database.”

b. The stored details will be available for modification/deletion.

The actor clicks on the “Freeze”,

c. The System will respond with the message,” Suspension/Cancellation of license details have been frozen successfully.”

d. An alert SMS will be thrown to the stakeholder’s registered mobile number through alert system use case.

e. The recorded details will not be available for modification/deletion.

f. To modify freeze details, the actor will have to unfreeze the details.

Basic Flow: Actor Actions - Actor logins and click the

“Cancellation/Suspension of

License” link.

- Actor specifies the details.

System Responses a The System will prompt the

actor to specify following

details of the dealer whose

license is to be suspended or

cancelled:

Name of the dealer

License number

Reasons for

cancellation/suspension

Duration of suspension

Remarks (if any)

Upload file



OR

(if the dealer registered in old

system)

Under the instructions from DOA,

based on the negative test results

provided by testing laboratories AO

tears the original License in front

of notary public.

Actor may choose one of the

following options:

Save: Actor clicks on the save link

to store details in database which

are not confirmed and could be

modified.

Freeze: Actor clicks on the freeze

link, if the specified details are

confirmed and will not be required

to modify.

System captures the inputs and

updates the table.

The System will send trigger to the

alert system and an SMS alert will

be sent to the stakeholder giving

license suspension/cancellation

information.



None

UI: required/not

required

Required


High



Rare

Business Rules: As per Seed Control Order 1983

The authorized user would be allowed to unfreeze the freeze

details.


A legal document (test report of non - standard, report from AO of non-suitability premises, etc)

Assumptions: None



Dependency: Extends ISS Home Page Is Extended By Alert System Uses Login

Notes and Issues: The interface will be designed separately for State level, District level and

Range level.

3.2.3.3 Seed Certification

Process Diagram

Seed Grower

Inspection Officer

Seed Processing Centre

STO

Seed Certification Agency

Field Inspection

Report

Seed Grower

Registration

Test Results

Processing

Information for seed

SCO

Sampling

Information

Seed Producing Agency

Plant Officer

Document Verification

& Application Acceptance

Issue Registration

Certificate

Packaging & Tagging

Release Order


Seed Grower Registration (Form-I)

This use case will facilitate the actor to submit application for

Seed Grower/Seed Producing Centre



Seed Production under the Seed Certification Program

Document Verification and Application Acceptance

This use case will facilitate the actor to verify the documents submitted by the applicant and it’s acceptance for registration.

SCO

Issue Registration Acknowledgement

Once the documents get verified and found satisfactory by the SCO, a registration number will be issued to the applicant for registration confirmation for certification process.

SCO

Field Inspection Report This use case will facilitate the actor to specify field inspection details of the seed grower’s inspected field.

Inspection Officer/SCO

Processing Information for seeds This use case will facilitate the actor to specify seed processing details of the seed grower.

SCO/Processing Center Officer

Sampling Information This use case will facilitate the actor to specify sampling details of the processed seed. Refer Use Case Sample Collection w.r.t Certified Samples

SCO

Seed Test Results This use case will facilitate the actor to specify test results for the seed samples. Refer Use Case Generate Test Card from Seed Testing & QA.

STO

Release Order If the test results meet the standards of the certification, certification number will be given to the tested Lot number in Release Order.

SCO

Packaging and Tagging certificate number

This use case will facilitate the actor to specify packaging samples details and tagging certificate no on them.

Plant Officer/ SCO

3.2.3.3.1 SEED GROWER REGISTRATION

Use Case ID: UC_

Use Case Name: Seed Grower Registration

Actors: Seed Grower or the Producing Agency through which the seed grower is being registered for seed certification.

Description: The actor will have a provision to select nearest division of his/her belonging area where he/she can register for obtaining seed certification.



The system will facilitate the actor to specify the application details for the seed production mentioning Seed Grower details, Source Verification details, Seed details to be registered for certification etc and fee details deposited for certification process.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Seed Grower Registration.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access seed grower registration page. If the seed grower is being registered through Seed Producing Agency, then that agency will be responsible for source verification of the seed grower’s seed. If the seed grower is directly applying for Seed Production Registration & Certification, he will have to submit source verification certificate issued from the verification Agency.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Seed Grower

registration details have been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Seed Grower registration details have been frozen successfully.”

d. The System will generate the application reference number and it will be sent to the stakeholder’s registered mobile no through alert system use case.


f. Uploaded documents will not be allowed to drop/delete from the registration form.

g. The application will be forwarded to the SCA for verifying the attached documents and application acceptance for registration.

h. Seed Grower’s application status will be updated on the SAP as “Pending for Acceptance” in the available link and the actor can track status of his/her application using the Reference No sent on the mobile.


“Seed Grower Registration”

link.

System Responses b There will be a Help option

available on the top of the

form to provide guidance

about how to specify details

in the form.

c Seed Grower Registration

detail will comprise of four

sub sections:



Grower Details (Form-I)

Registered Seed Details

Payment Details

Attach Documents

Grower Details


specify following registration details

of the seed grower in the system:

Select Division

Name of the Seed

Producer

Address of the Seed

Producer

Name of the grower

Father’s Name

Valid Mobile Number

E-Mail id (Optional)

Village

Post Office

District

Category

Location of the Seed

Plot (along with

district land marks)

Village Name

Gram Panchayat

District/Taluka

Survey No

Crop Offered for

Certification

Variety Offered for

Certification

Class of Seed

(Foundation/Certifie

d/Breeder)

Area Offered for

Certification

(hectares)

Source of Seed Used

(Give details):



Source

Verification Date

Certificate No

Certificate Date

Validity Period

Seed distributed

(Qty in Kgs.)

- Male

- Female

- Variety

Bill No

Bill Date

Isolation distance

from other varieties

(in meters):

North

South

East

West

Actual Date of

sowing/transplanting

Details of service

charges paid for (Rs.):

Registration

Inspection

STL

GPT

Others

Total (auto computed-sum of above

5 fields)

Charges Paid

through: Cheque/DD

If Cheque, then

Cheque Number

Cheque Date

If DD, then

DD Number

DD Date







to store details in database and the

details could be modified later on.



confirmed and will not be available

for modification.

Attach Documents

The System will facilitate the

actor to upload the scan

copy of supporting

documents required for

registration through use

case “Attach File”.

The actor could attach

multiple files in the

registration form.

Trigger will be sent to the alert

System.



None

UI: required/not

required

Required


High



Medium



1. Verification list will be displayed to the actor before finally freezing the details.

2. Source Verification Certificate, Original documents related to Seed Plot and Fee Deposit Receipts would be required to attach.

Assumptions: Parent Producing Agency for the seed grower and Seed Certification

Agency should be stored in master database.





3.2.3.3.2 APPLICATION ACCEPTANCE

Overview: The applications with the confirmed documents submitted will be forwarded to the actor for verifying documents and confirming registration of seed for certification process.

Use Case Name: Application Acceptance

Actors: Primary Actor SCO

Stake Holder: Seed Grower/Producing Agency

Description: This use case will enable the actor to select the form of applications submitted by the seed grower/producing agency to register for certification process, whose documents have been physically verified and pending for acceptance/rejection. All the pending applications will be highlighted to the actor with a flag set as “Pending for Acceptance”.

Trigger: The actor selects the option available Transactions->Application Acceptance


should have permissions to access ISS and Acceptance Application page in it.

2) There must be at least one application available with the status “Pending for

Acceptance”.

3) The actor must have received deposited fee draft/challan along with the photo

copy of the application form and Source Verification Certificate.



Post conditions: Once the actor clicks on the link “Accept and Register”, a. The System will respond with an alert message, “The application has been

accepted successfully.” b. The System will generate Seed Grower’s “Registration Number” and An

SMS alert in a pre define format will be thrown to the Seed grower/producing agency mobile number which is registered in our database.

c. The status of the accepted application will get updated with the status “Registered” or “Rejected based on the selected link by the actor in the “View Status of the Application” page and on the SAP under the available link.

d. The accepted application will not be available to the actor for modification and deletion.

e. The accepted applications will be forwarded to the field inspector for site inspection.

Input: 1. Select one application from the list of pending applications for acceptance and registration.

2. Verify the entered details and Click on the “Accept & Register” link.

Output: The accepted application form will be forwarded to the site inspector for specifying site inspection details.


The actor clicks on the option “Application Acceptance”.

The actor selects one of the

application records to verify.



The System will provide a list of all the pending applications for acceptance with the following information: S. No, Reference No, Application Submission Date, and Application Status as Pending for field inspection.

The System will display all the information recorded in the application form through use case “Seed Grower’s Registration” in read only mode. The actor could either download/print/View the attached document by clicking on the respective links available for maintaining records and verification.

System captures the input, changes

the status to “Document

submission” as approved and



Once the actor verifies the entered information, the actor may choose one of the following links:

Accept and Register Reject Close The actor selects the “Accept

and Register” link to accept the application if all the details get verified.

The actor may select the “Reject” link, if the entered information doesn’t satisfy the acceptance criteria or the documents are incomplete.

The actor may click on the “Close” link to close the “Application Acceptance” page.

Register and sends triggers to alert

system.

The actor will specify the Remarks,

if any.





Required


High


medium/ less/ rare

Medium


.jpmg and scan copy formats. 3. Only one record at one time could be allowed to select for acceptance and

registration. 4. Seed Control Order 1983





ISS Menu Page

Is Extended By Alert System Field Inspection Uses Login





Dependency: None


3.2.3.3.3 REGISTRATION ACKNOWLEDGEMENT

Use Case ID: UC_

Use Case Name: Registration Acknowledgement

Actors: SCO

Stakeholder: Seed Grower

Description: Once the documents have been verified and accepted by SCO, he will issue Registration Acknowledgement mentioning system generated Application Registration Number in PDF format.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification -> Registration Acknowledgement.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to generate registration acknowledgement. Application Acceptance details must be frozen in the system.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Registration

Acknowledgement Details has been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Registration Acknowledgement details have been frozen successfully.” And the system will generate Registration Acknowledgement in PDF format



and it will be sent to the seed producing agency or the seed grower’s registered e-mail id (if specified) through mail.

d. The Receipt Acknowledgement will be dispatched to the SCA-Head Office, Divisional Officer, and Processing Center.


Basic Flow: Actor’s Action Actor clicks on the link “Registration Acknowledgement” After specifying all the mandatory details, the actor may choose one of the following options: Save: If the actor doesn’t actually want to generate acknowledgement and only wishes to save the details, he/she may choose this option. The save details will be available for modification or deletion. Confirm Details and Generate Acknowledgement: If the actor is confirmed about the mentioned details and desires to generate acknowledgement, he/she may choose this option. The acknowledgement will be generated in PDF format and the actor could print it using Print option.

System Responses



a. Date of Receipt of Form-I

b. Certification Charges collected

vide C.R. No-

Date

Amount (in Rs.)

c. Registration Acknowledgement

Date, Time, Place, Registration

No, Season, Designation and

name of the officer issuing

Registration Acknowledgement

will be auto displayed by the

System.



Print: Clicking this option, the actor may print the generated acknowledgement



None

UI: required/not

required

Required


High



Medium

Business Rules: By default, server date will be the Acknowledgement date and

server time will be the Acknowledgement Generation time.

Acknowledgement date and time will be editable and the actor

could manually specify the date in dd/month/yyyy format.

As per Seed Control Order 1983


None

Assumptions: Name of the Registration Officer will be stored in master database.



3.2.3.3.4 INSPECTION REPORT FORM

Use Case ID: UC_

Use Case Name: Inspection Report Form

Actors: Inspection officer/SCO

Stakeholder: Seed Grower

Description: The system will facilitate the actor to specify the field inspection details of the seed grower. The actor could specify the report details of first inspection, intermediate inspection, and Final inspection and re inspection.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Inspection Report Form.



Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access inspection report page.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Inspection Report

Details has been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Inspection Report details have been frozen successfully.” And the system will generate lot numbers for the inspected field in pre define format i.e. <<month-year-state code-processing plant centre number-stage given by SCA-auto generated grower registration no>>. The lot numbers will be sent to the seed grower’s registered mobile number.

d. The inspection report will be dispatched to the SCA-Head Office, Divisional Office and Processing Center.


f. The seed grower could search the inspection details of his/her field on the SAP/ISS home page using Lot no.


“Inspection Report Form”

link.

The actor selects name of the Seed

Grower.

As the actor submits the selected

details,

System Responses d. There will be a Help option

available on the top of the

form to provide guidance

about how to specify details

in the form.

e. The System will prompt the

actor to select-

Name of the Seed

Grower whose inspection

report is to be filled. The

seed growers registered

by the SCA will be listed

down for selection.

The System will prompt the

actor to select;

Seed: for which

inspection report is to be

made for the selected

grower. The system will

display all the seed’s

(seed name, variety,



Actor selects one of the inspection

type,

stage) specified for the

selected grower for

selection.

Depending on the

selected Seed/Variety, the

system will display the

details specified in the

Seed Grower’s

Registration use case in

read only mode like:

Registration No, Actual

Sowing Date, Foundation

Seed/Certified Seed

(Stage-I/II), Source of

Seed used, Name and

Address of the Seed

Grower, Location of Seed

Plot

All these details will be

editable by inspector, in

case variations are

recovered during

inspection.

Report No: The System will auto

generate the report no.

Report Date: By default, current

system date will be displayed as the

Report Date (on which date, report

is being specified)

Division: The system will auto

display the Division for which

he/she is authorized to log in (from

the user log in and accessibility use

case).

FIR No: The System will auto

generate the FIR No.

f. The System will prompt the

actor to select the Inspection

Type i.e.

First Inspection

Intermediate



Inspection

Final Inspection

Re-Inspection

Corresponding to which the

report details are being

specified in the system.


specify following inspection details:

Inspection Date: The System will

prompt the actor to select the date

from the displayed calendar, on

which inspection was done.

Crop Sown: Irrigated/Rain fed

Number of Mail Rows around seed

plot:

Total acreage offered for seed

production (Acres):

Acreage Inspected (Acres):

g. Observation Recorded during

field inspection: The actor

would specify following

observation details –

Field Counts

Number of Plants/Ear

heads per

count:100/500/1000

Total Contamination

Plants/Ear heads and

percentage factors

Variety/Rows (i.e.

Self

Pollinated/Hybrid

Female

Rows/Hybrid Rows)

Off type Plants (No.)

Off type Plants (%)

Receptive skills (No.)

Receptive skills (%)



Pollen Shedders (No.)

Pollen Shedders (%)

Designated Disease

Plant/Ear heads

(No.)

Designated Disease

Plant/Ear heads (%)

Objectionable Weed

Plants (No.)

Objectionable Weed

Plants (%)

Open Flowers (No.)

Open Flowers (%)

Total No.: (auto

computed)

Total %: auto

computed

Previous Crops

No of male rows

around seed plot

Crop condition

(Poor/Fair/Medium/

Good)

Seed Plot Condition:

Satisfactory/dissatis

factory.

Expected yield of

seed crop

(Quintals/acre)

Date of harvesting

h. Field Inspection Remarks and

Observations: The system

will display list of the

observation points and

remarks in read only mode.

The actor would select the

remarks suitable for the

inspected field.

i. Reason for Rejection: The

actor would specify the

reason for seed plot











confirmed and lot number is to be

issued.

Once the actor clicks on the freeze

rejection

j. Other special

remarks/observation if any:

k. Name of the

Producer/Grower/Represent

ative: The actor would

specify the name of the

grower’s representative

available during the field

inspection.

Inspection Officer: The actor will

select the name of the field

inspection officer who is specifying

the inspection details, from the list

enlisting names and designations of

the officers.

Dispatch Date: The System will

prompt the actor to select the date

from the displayed calendar, on

which the report has been

dispatched.

The System will auto generate the

lot numbers to the grower for the

inspected field in a pre define

format and a trigger will be sent to

the alert System.



option:



None

UI: required/not

required

Required


High



Medium

Business Rules: By default, server date will be the report date and server time will

be the report time.

Report date and time will be editable and the actor could manually

specify the date in dd/month/yyyy format.

Stages to the seed growers are given by the SCA at the time of

seed grower’s registration.

As per Seed Control Order 1983


None

Assumptions: Inspection Officer details should be stored in master database.



3.2.3.3.5 PROCESSING INFORMATION FOR SEEDS OF A GROWER

Use Case ID: UC_

Use Case Name: Processing Information for seeds

Actors: SCO

Description: The system will facilitate the actor to specify the seed processing details of the seed growers.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Processing Information for Seeds.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home



page and should have permissions to access Processing Information for Seeds page.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Seed Processing

details have been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Seed Processing details have been frozen successfully.”

d. The recorded details will not be available for modification/deletion.

e. After completion of seed processing, only freeze processing records will be available for recording sampling details.

f. To modify the freeze details, authorized actor would be required to unfreeze and modify/delete the details.


“Processing Information for

Seeds” link.


Grower.

System Responses There will be a Help option

available on the top of the form

to provide guidance about how

to specify details in the form.


actor to select-

Name of the Seed

Grower whose seed

processing information is

to be filled. The seed

growers registered by the

SCA will be listed down

for selection.


actor to select;

Seed: for which

processing information is

to be made for the

selected grower. The

system will display all the

seed’s (seed name,

variety, stage) specified

for the selected grower

for selection.

The system will



display list of all the

FIRs recorded for the

selected Seed

Grower and variety

for selection.

As the actor selects

one record, the

system will display

following details in

read only mode as

specified in

Inspection Form use

case:

FIR No

FIR Date

Expected yield

quantity as per Final

FIR (Quintals/per

Acre)

Lot number issued


specify following seed processing

details:

Raw Seed (in Quintals):

The actor would specify

the quantity of the raw

seeds brought to Seed

Processing Unit for

processing.

Raw Seed Processed

Quantity(in Quintals)

Processing Date

Area (in Ha) from which

seed received: The actor

would specify the area of

the field from which raw

seeds received for

processing.

Processing Center

Receiving Seed: The actor

would select the name of











confirmed and will not be available

for modification.

Unfreeze: Actor clicks on the

unfreeze link to modify/delete the

frozen details.

the processing center to

which raw seeds were

given for processing at

plant.

Date of Sampling



None

UI: required/not

required

Required


High



Medium

Business Rules: None


None

Assumptions: Seed Processing Centers are stored in master database.

Dependency: Extends ISS Home Page Is Extended By None Uses Login




3.2.3.3.6 SAMPLING INFORMATION

Use Case ID: UC_

Use Case Name: Sampling Information

Actors: Seed Processing Center/ SCO or the person authorized to perform this task.

Description: After completion of the seed processing activity, the system would facilitate the actor to specify seed sampling details.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Seed Sampling Information.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access sampling information page.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Sampling Information

has been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Sampling Information has been frozen successfully.” And a codified sample number will be generated by the System in a pre define format.

d. The sample number will be sent to the seed grower’s registered mobile number.

e. Sampling information will be sent to the head office of the SCA through registered email id.

f. Freeze details will not be available for modification/deletion.

Basic Flow: Refer Use Case Sample Collection

Details from Seed Quality Testing and

Assurance Process.



None

UI: required/not

required

Required


High



Medium



None



Assumptions: Seed Processing Centers, Names of the Sampling Officers and contact

details (mobile numbers and e-mail ids) of the head offices and divisional

offices of SCA are stored in master database.

Dependency: Extends ISS Home Page Is Extended By Alert/Email System Uses Login


3.2.3.3.7 SEED TEST RESULTS

Use Case ID: UC_

Use Case Name: Seed Test Results

Actors: SCO/STO at STL or the person authorized to perform this task.

Description: After performing codification of the samples, the samples are sent to the testing labs and the test results would be uploaded in the system by the authorized person in STL.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Seed Test Results.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access seed test results page.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Test Results have been

saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Test Results have been frozen successfully.”

d. Seed Test Results will be sent to the head office and divisional office of the SCA through registered email id.

e. Seed Test Results will be published on the SAP and ISS home page under the available link and the seed grower can view or search the results by using sample no received on his/her registered mobile number.

f. Freeze sample test results will be forwarded to the SCO at the plant for specifying packaging and tagging details.

g. Freeze details will not be available for modification/deletion.

Basic Flow: Refer use case Test Card Generate

from Seed Quality Testing and

Assurance Process.





None

UI: required/not

required

Required


High



Medium



None

Assumptions: Seed Testing Labs, Plant Names, addresses and SCO are stored in master

database.



3.2.3.3.8 GENERATE RELEASE ORDER

Use Case ID: UC_

Use Case Name: Generate Release Order

Actors: SCO-HO

Description: Once the same test results declare the test Pass, Certification number will be issued for the tested variety under belonging lot number through Release Order.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification -> Release Order.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access Release Order page. The actor must have received the test card results sent by Seed Testing Laboratory.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Release Order Details

have been saved successfully.” b. The stored details will be available for modification/deletion.



The actor clicks on the “Freeze and Generate Release Order”, c. The System will respond with the message,” Release Order Details

have been frozen successfully.” d. Certification number will be generated by the System and it will be

displayed on the actor’s screen. The certification number will be sent to the grower’s/producing agency’s registered mobile number.

e. Release Order will be generated in PDF format and the same will be sent to the Seed Processing Center, SCA-Divisional Office and the Seed Grower’s/Producing Agency’s registered e-mail id (if exists in database)

f. Seed grower can view/ search/down load the Release Order through SAP by using certification no received on his/her registered mobile number.


Basic Flow: Actor’s Action

The actor clicks on the link available “Generate Release Order”

System Response

There will be a Help option





actor to select-

Name of the Seed

Grower whose Release

Order details are to be

filled. The seed growers

registered by the SCA and

whose test card result is

having “Pass” status will

be listed down for

selection.


actor to select;

Seed: for which release

order is to be made for

the selected grower. The

system will display all the

seed’s (seed name,

variety, stage) specified

for the selected grower



for selection.

Lot No allotted to the

selected Seed: The

system will prompt the

actor to select the lot

number from the list

displaying all the lot

numbers issued to the

selected seed variety,

corresponding to which

release order details are

to be specified.

Depending on the selected Lot

number, following details will be

displayed on the screen as specified

in the corresponding Test Card:

Crop Name

Variety Name

Class of Seed

(Foundation/Certified/Hybrid-Stage-

I/II)

Quantity of Seed in the Lot (Kg)

Grower’s Name

Village

Taluka

District

Producer’s Name


specify following details related to

the selected Lot number, to be

displayed on Release Order:

Packing Size (Kg.)

Validity of Certificate (From Date,

To date)

Lab Report No

Genetic Purity test Report No.

Total No. of tags issued with Sl. No

Total No. of tags used with Sl. No

Total No. of tags unused with Sl. No



After specifying all the mandatory details, the actor may choose one of the following options: Save Freeze and Generate Release Order Unfreeze Edit Delete Save: The actor may choose the save link to save the specified details in the system. The saved details will be available for modification/deletion. Freeze and Generate Release Order: To finalize the certification details and generating the Release Order, the actor will choose this option. Once the release order get’s generated, the details will not be available for modification/deletion. If the actor freeze the unfreeze record or the certification number has already been generated by the system in that case, new certificate number along with the release order will be generated by the

Pure Seed (%)

Objectionable Weed Seed (No’s/Kg.)

Inert matter (%)

Total Weed Seed (%)

Germination (%)

Genetic Purity (%)

Moisture (%)

ODV (No’s/kg)

Other crop seeds (No’s/Kg)



system and previously release order will be treated as cancelled. In this case history of the previously recorded data will be maintained in the database. Unfreeze: To modify the freeze release order details, the actor will have to unfreeze the record. Only the authorized actor could access this link. Edit: The actor could modify the recorded saved/unfreeze release order details. Delete: The actor could delete the saved details. Only the authorized actor could be allowed to delete the unfreeze record.



None

UI: required/not

required

Required


High



Medium



None

Assumptions: None





3.2.3.3.9 PACKAGING AND TAGGING

Use Case ID: UC_

Use Case Name: Packaging and Tagging

Actors: Officer at the Plant who is authorized to perform this task.

Description: After performing sample testing, based on the results generated samples packaging, tagging and certification takes place. The system will facilitate the actor to specify the details required for packaging and tagging and the system will automatically generate the tag number for each package.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> Seed Certification and Quality Assurance-> Packaging and Tagging.

Pre-conditions: The actor must be registered on CAP/SAP and signed up on SAP/ISS home page and should have permissions to access packaging and tagging page.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Packaging and Tagging

details have been saved successfully.” b. The stored details will be available for modification/deletion.


c. The System will respond with the message,” Packaging and Tagging details have been frozen successfully.”

d. The System will generate a Certificate Number, to be specified on the tags of the packet. The auto generated Seed Certification Number would be sent to the selected seed grower on their registered mobile numbers and a copy will also be sent to the SSCA’s Head Office.

e. System will generate the Certificate in PDF format and it’ll be forwarded to the seed grower’s register email id.

f. Status of the selected seed variety will be changed as “Certified Seed” on the SAP and ISS home page under the available link and the seed grower can view or search the results by using sample no received on his/her registered mobile number.



“Processing Information for

Seeds” link.

System Responses There will be a Help option





actor to select-

Name of the Seed

Grower whose packaging

and tagging details are to

be filled. The seed

growers registered by the




Grower.

The actor submits the selected

parameters.

SCA will be listed down

for selection.


actor to select;

Seed: for which packaging

and tagging details are to

be made for the selected

grower. The system will

display all the seed’s

(seed name, variety,

stage) specified for the

selected grower for

selection.

Lot No allotted to the

selected Seed: The

system will prompt the

actor to select the lot

number from the list

displaying all the lot

numbers issued to the

selected seed variety,

corresponding to which

packaging and tagging

details are to be specified.


specify following details against the

selected Lot no:

Parental Information: The System

will display the parentage

information of the seed as

specified in the notified seed

varieties.

Quantity of the certified seeds (in

Quintals): The actor would specify

the quantities of the seeds to be

certified in a package.

Packing Size: The actor would

specify the size of the package.

Packing Loss: The actor would




details, actor clicks on one of the

following options:






confirmed and Certificate number

is to be generated.

Add: To add more packaging and

tagging details and to generate

certificate number to them, actor

will select add option available on

the form

specify loss in the packing.

Tags issued from: The actor would

specify starting number of the tags

issued.

Tags issued up to: The actor would

specify last number up to which tags

are issued.

Agency Name (if samples are

packed in the agency other than

processing center): The actor would

select the name of the agency who

is packing samples. The system will

list down all the agencies registered

for the seed processing.

A certificate number will be generated by the system and trigger will be sent to the alert system.



None

UI: required/not

required

Required


High





Medium



None

Assumptions: Seed Processing Agencies are stored in master database.



3.2.3.4 Seed Quality Testing and Assurance Process Process diagram: Sample Collection and Lab Processing

Seed Certification Officer

Seed Inspector

STO

STL-Head Officials

Seed Testing Lab

Sample Acceptance

Generate Test Card

Generate Sample

and MIS Reports

Testing Results

Sample Collection

Details




Sample Collection details This use case will facilitate the actors to specify collected sample details during field inspection.

Field Inspectors/SCO/STO (Authorized Officers of DOA)

Sample Acceptance This use case will facilitate the actors to accept the seed samples received through the use case “Sample Collection Details”.

STO

Sample testing details at seed laboratories

This use case will facilitate the actors to specify test details of the seed samples tested in the laboratories.

STO

Generate Test Card This use case will facilitate the actor to generate Test Card based on the recorded test details for the samples.

STO

Generate Reports This use case will facilitate the actor to generate test reports/MIS reports for the samples tested in a specified duration.

Testing Labs-Head Officials

3.2.3.4.1 SAMPLE COLLECTION DETAILS

Use Case ID: UC_

Use Case Name: Sample Collection Details

Actors: Field Inspectors/authorized official of DOA/SCO/STL

Description: The system will facilitate the actor to specify field inspection details.

Trigger: Actor clicks on the link available under ISS home page->Transaction-> “Sample Collection Details”

Pre-conditions: The actor should be signed up on SAP and should have permissions to access “Sample Collection Details” interface.

Post conditions: As the actor clicks on the “Save”, a. The system will respond with the message,” Sample

Collection details have been stored in database.” b. The stored details will be available for

modification/deletion. The actor clicks on the “Freeze”,

a. The System will respond with the message,” Sample Collection details have been frozen successfully.”

b. The recorded details will not be available for modification/deletion.



c. To modify freeze details or no action has been taken by STO at Laboratory for acceptance/rejection, the actor may unfreeze and modify details.

d. Sample Collection details will be available to the seed testing laboratory’s authorized person for sample acceptance for testing.

e. Once test results have been recorded for any sample, corresponding Sample Collection details should not be allowed to modify.


“Sample Collection Details”

link.

System Responses The System will prompt the actor to specify following details of the collected sample:

a Sample Number b Name of the Sample Sender c Address of Sample Sender - Address1 - District - City - Pin Code d Sample Collection Date e Sample Submission Date to

Laboratory f Test Laboratory Number g Test Laboratory Name h Name of Crop i Variety Name j Quantity k Lot No (If samples are

collected by Inspector/any official).

l Inspection Remarks m Amount Paid for Testing:

Default value would be 0. n Upload File o Sample Type : list option

(Certified Sample / Official Sample / Service Sample)

If selected sample type is “Certified Sample”, the actor would specify following details:

p Seed Grower/Producer

Name q Seed Grower/Producer

Address



- Actor may choose one of



to store details in database which

are not confirmed and could be

modified.



confirmed and will not be required

to modify. The specified sample

details will be forwarded to the

Seed Testing Laboratory officer for

acceptance.

r License Number s Memo Letter No t Memo Letter Date u Coupon Number

If selected sample type is “Official Sample”, the actor would specify following details:

v Seed Distribution Company Name

w Dealer Name x License Number y Dealer Address (District,

City, Pin Code) z Memo Letter No aa Memo Letter Date

If selected sample type is “Service Sample”, the actor would specify following details:

bb Farmer Name cc Farmer Address (District,

City, Pin Code) System captures the inputs and

updates the table.



None

UI: required/not

required

Required


High





Rare


The authorized user would be allowed to specify and freeze

details.


1- Certified Sample: Sample collected by Seed Certification Officer. At the time of Sample Collection Annexure 2: 4.2.12 will be in the packet with the sample and Annexure 2: 4.2.13 will be along with the sample.

2- Official Sample: Sample collected by notified Seed Inspector ie

District Agriculture Officer, Sub Division Agriculture Officer, Jt. Director Agriculture, Director of Agriculture. At the time of sample collection Seed Inspector will fill the form V (Refer Annexure 2: 4.2.3) Enclosure which is memorandum to Seed Analyst and Form VIII (Refer Annexure 2: 4.2.4) which is acknowledge of having taken sample.

3- Service Sample: Sample collected by other than Seed Certification Officer or Seed Inspector. Like Kissan, any other official. This sample is sent with the request letter.

Assumptions: None

Dependency: Extends ISS Home Page Is Extended By None Uses Login


3.2.3.4.2 SAMPLE ACCEPTANCE

Use Case Name: Sample Acceptance

Actors: Primary Actor STL Officer

Stake Holder: Seed Grower/Producing Agency/Dealer/Farmer



Description: This use case will enable the actor to select the sample details submitted by field inspectors/SCO through use case “Sample Collection Details” for acceptance/rejection depending on the condition of the received samples. All the pending sample records will be highlighted to the actor with a flag set as “Pending”.

Trigger: The actor selects the option available Transactions->Sample Acceptance


should have permissions to access ISS and Sample Application page in it.

5) There must be at least one application available with the status “Pending”.

Post conditions: Once the actor clicks on the link “Accepted”,

a. The System will respond with an alert message, “The sample has been accepted successfully.”

b. An SMS alert regarding status of the sample in a pre define format will be thrown to the person’s/agencies mobile number which is registered in our database.

c. The status of the accepted samples will get updated with the status “Accepted” or “Rejected based on the selected link by the actor in the “View Status of the Application” page and on the SAP under the available link.

d. The accepted samples will not be available to the actor for modification and deletion.

e. The actor could search the status of the submitted sample details on SAP using Sample Sr. No specified in the Sample Collection details use case.

f. The accepted sample records will be forwarded to the STO for testing samples and specifying sample results.

g. In case samples have been rejected, the reason of the sample rejection will also be displayed on SAP.

Input: 1. Select one sample record from the list of pending records for acceptance. 2. Verify the entered details and Click on the “Accept” link.

Output: The accepted sample details will be forwarded to the assigned STO for specifying sample test results.




The actor clicks on the option “Sample Acceptance”.

The actor selects one of the

sample records to specify results.

Once the actor verifies the entered information and received samples, the actor may choose one of the following links:

Accept Reject Close The actor selects the “Accept”

link to accept the samples for testing.

The actor may select the “Reject” link, if the entered information or received sample doesn’t satisfy the acceptance criteria.

The actor may click on the “Close” link to close the “Sample Acceptance” page.



The System will provide a list of all the pending sample records (Field inspection reports) for acceptance with the following information: Sample Sr. No, Sample Details Submission Date, Sample Type (Certified/Official/Service) and Sample Status as Pending for specifying test results.

The actor will specify Sample Receiving Date.

The System will display all the details specified in the field inspection details form through use case “Field Inspection Details” in read only mode. The actor could either download/print/View the attached document by clicking on the respective links available for maintaining records.







Required


High


medium/ less/ rare

Frequent


.jpmg formats. 3. Only one record at one time could be allowed to select for acceptance. 4. Seed Control Order 1983



ISS Menu Page

Is Extended By Sample testing details at seed laboratories Uses Login





Dependency: None


3.2.3.4.3 SAMPLE TESTING DETAILS AT SEED LABORATORIES

UC Sample testing details at seed laboratories

Version:

Context: This use case will facilitate the seed testing laboratory officer to specify samples testing details against the accepted samples.

Priority: Rare

Frequency: As and when get request for testing seed samples.

Primary Actor: Seed Testing Lab Officer



Preconditions: Actor should be logged on to CAP/SAP and must have privileges to access the specified page.

Basic Flow: 1 As the actor accesses the sample testing details at seed laboratories interface, the system will display all the accepted field inspection records to the actor with Sample Sr. No, Sample received Date, Sample Type and Crop Variety Name. The actor will select one record to specify sample test result details. The actor could specify following details:

a. Test Start Date b Test Report Release Date c Status of the sample testing (In process / Report

Generated ): If, Report Release Date has been specified by the actor, status will be displayed as “Report Generated” and if, only Test Start Date has been specified by the actor without specifying Report Release Date, the status will be displayed as “In Process”.

d Test Result (PASS/Fail)

If the selected record is having sample type as “Certified Sample” ,the actor would be required to specify following details:

e Germination (Standard, Non Standard) %

- Normal - Abnormal - Hard Seed - Dead Seed - Fresh Un germinated Seed

f Purity Percentage - ODV (%) - Inert Matter (%) - Weed Speed

g Moisture (%) h Infestation by pest

i Remarks

If the actor chooses, sample type as “Official Sample” ,the actor would be required to specify following details:

j Germination (Standard, Non Standard) %

- Normal - Abnormal - Hard Seed



- Dead Seed - Fresh Un germinated Seed

k Remarks

If the actor chooses, sample type as “Service Sample” ,the actor would be required to specify following details:

l Germination (Standard, Non Standard) %

- Normal - Abnormal - Hard Seed - Dead Seed - Fresh Un germinated Seed

m Remarks

2 After specifying all the mandatory details, the actor may

choose one of the following options: Save Freeze Add Edit Save: Actor clicks on the save link to store details in database and the


Freeze: Actor clicks on the freeze link, if the specified details are

confirmed; Test Result Card could be generated by the system.

Add: To add more sample test details, actor will select add option available on the form. Edit: Actor clicks on the edit option to modify the sample details. This use case ends.


Post Condition: As the actor clicks on the “Save”, a. The system will respond with the message,” sample test

details have been stored in database.” b. The stored details will be available for modification/deletion.




c. The System will respond with the message,” sample test details have been frozen successfully.”

d. An SMS alert will be sent to the stakeholder informing status of the test result against the submitted Sample Sr. No.


f. To modify freeze details, the actor will have to unfreeze the details.

g. Copy of sample test details will be forwarded to the DOA /SCO and the inspector who sent the sample.

h. The actor would be able to generate “Test Card” for the tested samples.

i. Test result of the samples could be searched on SAP using “Sample Sr. No.”.


None

Unresolved Issues: None

3.2.3.4.4 GENERATE TEST CARD

UC Generate Test Card

Version:

Context: This use case will facilitate the actor to generate test card report against the freeze sample test details.

Priority: Rare

Frequency: As and when sample testing process completed at laboratories.

Primary Actor: Seed Testing Lab Officer

Preconditions: 1. Actor should be logged on to the CAP/SAP and should be authorized to access Generate Test Card option in ISS application.

2. Sample test details at laboratories should be frozen.

Basic Flow: 1 The actor clicks on the “Generate Test Card” interface. 2 The system will display “Test Card” in a pre define format

(enclosed in Annexure 2: 4.2.5 Enclosure (Test Card)) comprising of the pre defined sample test details in the required fields.

3 The actor may choose one of the following options: Save Print

4 The actor may choose ‘Save’ option to save the generated test card in PDF format.

5 The actor may choose ‘Print’ option to print Test Card.

This use case ends.




Post Condition: The System will send a copy of the generated test card to the DOA/SCO and field inspection officer by triggering email.


Email address of the DOA/SCO and field inspector should be stored in database.


3.2.3.4.5 GENERATING TEST REPORTS

UC Generating Reports

Version: 00

Context: This use case will facilitate the actor to generate reports by using the test results updated in the use cases “Sample testing details at seed laboratories” and “Generate Test Card”. The actor could generate test reports for various samples tested in the lab and the MIS reports.

Priority:

Frequency: As and when Head of Laboratory desires to generate the reports.

Primary Actor: Seed Testing Lab

Preconditions: Actor should be logged on the CAP/SAP and must have privileges to generate test reports in the ISS application.

Basic Flow: 1. The system will prompt the actor to select one of the report types i.e. Sample Report or MIS Report, which he/she desires to generate:

>> When actor chooses report types as Sample Report, the system will prompt the actor to select reports for one of the following sample types i.e. Certified Sample Report / Official Sample Report / Service Sample Report >> When actor chooses report type as MIS Report, the system will prompt the actor could generate reports: City Wise Monthly report Crop Wise Monthly report Sample Wise Monthly report 2. From Date and To Date: The system will prompt the actor to

select from date and to date, pertaining to which the test records are to be displayed in the report.

3. Actor will choose option ‘Generate Repots’ 4. The system will generate reports in the pre define formats as

mentioned in, For Sample Reports:



Annexure 2: 4.2.6 Enclosure: Certified Sample Report Annexure 2: 4.2.7 Enclosure: Official Sample Report Annexure 2: 4.2.8 Enclosure: Service Sample Report For MIS Reports: Annexure 2: 4.2.9 Enclosure: City Wise Monthly report Annexure 2: 4.2.10 Enclosure: Crop Wise Monthly Report Annexure 2: 4.2.11 Enclosure: Sample Wise Monthly Report 5. Actor may choose the ‘Print’ option to print the reports in PDF

format. 6. The actor may click on the ‘Send Mail’ option to send mail to the

respective actors. 7. This use case ends.


Post Condition: None


Generating Reports, details save in database with fallowing info:

- Generated by - Time of reports generate - Reports Type - Mail sent to

Printed reports can be post to the respective office or person.


3.3 Performance Requirements

3.3.1 Scalability Requirements

Scalability refers to the maximum user load on the system. In the current scenario, there will be 2,50,000 application users of the system at central, state and village level. At any point of time, no more than 25,000 simultaneous application users would be expected in the system. At any point of time, the software should support a peak load of 2500 concurrent users.

3.3.2 Response Time

The response time should be as follows:

90% of the responses should be within 2 sec.

5-10 second: For user operation on data (for e.g. sorting of data in a column) or (5 to 50 records per page

upto max of 100,000 records).

10-20 second: For user awaiting response from the system upon executing a transaction (for e.g. a

query/update).

1 minute – Unacceptable response time



3.4 Software System Attributes

3.4.1 Usability

The Screens should be designed for ease of use by non technical users who do not have any computer knowledge. The GUI design shall be intuitive and task-based without any superfluous design. The design should adopt the following principles:

Use relative font size so that a user can easily change overall font size from the browser

interface.

Text equivalents should be given for all graphics.

Application should function even if Javascript, CSS and Frames are turned off.

Navigability –The user should be able to perform operations without having to navigate

through multiple pages/links – No operation should require more than 2 to 3 clicks.

Familiarity – The system’s interfaces and navigations should be based on other systems that

the users are familiar with.

Administration – The system should not require any administration tasks at the user level.

Interfaces should be available for administration/setup operations.

Help - The system should come equipped with Computer based tutorial in English and ten

other languages for users to “self-solve” any navigability or operational doubts.

Standards Adherence – The system should adhere to commonly accepted standards of web-

design (such as acceptable size of web pages, minimal images, small style sheets etc)

3.4.2 Reliability

Individual ISS application may be unavailable for not more than 120 hours in each year. It is expected that there shall not be any bug and the system shall be tested on end cases to offer user a quality and reliable package.

3.4.3 Availability

ISS application shall be up and running and must be available 24x7 and any one should be able to connect to it from anywhere. It should trap all errors and prevent users from accessing unauthorized areas of the application. In case of application or a hardware failure, the system should re-initiate immediately. In case of a possible hardware failure or corruption of database the system administrator should immediately restore the backup.

3.4.4 Security

The system should have protection against

Unauthorized creation/modification of data - through user name and password

authentication as defined for relevant user groups.



Unauthorized viewing of data - through user name and password authentication as

defined for relevant user groups.

The software should adhere to security guidelines, standards and policies prescribed by

NIC’s Security Division and should be audited & certified for compliance to these

standards by Security Division before it is hosted in Production Environment.

The software should be protected against any unauthorized access to the software.

3.4.5 Maintainability

In order to ensure maintainability of the application, the following should be insured

The application will be designed and developed using Open Source Tools and

Technologies. Software Code must be modular and well documented

All the artifacts related to the software such as code, SRS, User Manual etc. should be

well documented and self-explanatory for any programmer to understand. Detailed

documentation shall be available at each stage for easy comprehensions of the

application system.

All documents shall be prepared as per the defined documentation standards.

The system administrator shall take regular back up of the database.

3.4.6 Portability

The software will be hosted/installed in Linux RHEL 5 and above O/S based server and will be accessed through Windows (XP) based machines using I.E 6.0 or above OR Mozilla 3.5.11 or above browsers.

3.4.7 Language Support

• The system will support the entry and display of:

Non-Latin scripts such as Hindi, Tamil and other Indian vernacular languages

The application will store data using Unicode representation.

• Nowadays there are many plug-in based applications are available in market, through which the phrase written in one language can be translated in different languages. By using this plug-ins, a portal that supports vernacular languages can be developed.

• The database can develop in a base language for e.g. in English. This plug-in is then placed between the database and the application. The language of the data is first selected in the application and then data is entered through the form available in the application. This information of the language and the data reaches the plug-in first. The plug-in understands the language and then translates the data in to base (English) language and then stores the data in the database. Similarly, when the information is retrieved from the database, it reaches the plug-in first, meanwhile; the plug-in also has the information



of the language in which the data in base (English) language needs to be translated into, from the form available in the application. The plug-in then translates this data in the language of the user’s choice and displays the same on the form available in the application.

• Examples of the above mentioned plug-ins are as below:

An Application related to Land Use and Acquisition has been developed by NIC which makes use of the plug-in developed by C-DAC, Pune.

Details of another such Plug-in software developed by C-DAC, Pune is available at the mentioned link:

http://pune.cdac.in/html/aai/mantra.aspx

Software by the name of “MANTRA – Rajbhasha” has been developed by C-DAC, Pune. The details of the same are available at the below mentioned link:

http://pune.cdac.in/html/aai/mantra_rajbhasha_en.aspx

3.4.8 Interoperability

The software will interoperate with other software applications which are being developed under National e-Governance Program, Mission Mode Project, in particular Central Agriculture Portal and State Agriculture Portal. The following are the likely points of information exchange/reconciliation:

State Codes/Names

Panchayat Codes/Names

Scheme Code/Names

Scheme component Code/Names

Prices of Notified Seed Varieties to show the dealer’s stock availability of the seed,

fertilizer and pesticides nearest to the farmer’s area.

3.5 Logical Database Requirements

3.5.1 Data entities

3.5.1.1 Entity Name: Season Entity Description: This entity will store all the attributes associated with the crop season.

S. No. Attribute Type Mandatory /

Optional /

Conditional

Remarks

1. Season_id Number M PK



2. #Season Text M Value in (Summer, Kharif,

Rabi) and code for season

is 1, 2,3 respectively.

3.5.1.2 Entity Name: Variety_Prices


Optional /

Conditional

Remarks

1. Crop Name Char M Value Rabi and Kharif

2. Notified Seed Variety Char M

3. Variety Prices Varchar M Prices up to 2 decimal points

3.5.1.3 Entity Name: Area Codes Entity Description: This entity will store all the attributes associated with the Location.


Optional /

Conditional

Remarks

1. Entity_code Int M

2. Code Integer M

3. Entityname VarChar M

4. Entity_type Char

5. Parent_code Integer M

6. Old_parent_code Integer

7. Classification_type Char

3.5.1.4 Entity Name: FAQ Category Entity Description: This entity will store all the attributes associated with FAQ Category.




Optional /

Conditional

Remarks

1. Category_code Integer M

2. FAQ_category Varchar M

3.5.1.5 Entity Name: Add New Query Entity Description: This entity will store all the attributes associated with a new query.


Optional /

Conditional

Remarks

1. Entity_code Integer M From where the query is being raised

2. User_mobileno Number M User’s mobile no. on which the query’s

reference number is to be sent.

3. New_query Varchar M

3.5.1.6 Entity Name: Add FAQ Entity Description: This entity will store all the attributes associated with FAQ.


Optional /

Conditional

Remarks

1. FAQ_code Integer M

2. FAQ_Category Varchar M Category under which query is being specified

3. FAQ_query Varchar M Specify the question

4. FAQ_answer Varchar Specify the answer against the question.

5. FAQ_status Number M Save/published

3.5.1.7 Entity Name: QueryAdvice_Status



Entity Description: This entity will store the status of the query raised by any citizen for seeking expert advice .


Optional /

Conditional

Remarks

1. entity_code Integer Location of the citizen from where query is

being raised.

2. query_code Integer

3. query_category Varchar

4. query_reference_no Number

5. First_expert_code Number Code of the expert who is forwarding the query to the next level expert.

6. Expert_code Number C Code of the expert to who query is forwarded

by the system.

7. Status_flag Integer M Values 0, 1 or 2. 0 for rejection, 1 for

acceptance, 2 for forwarding it to another

expert.

8. Remarks Varchar Description of query

3.5.1.8 Entity Name: Expert_Advice Entity Description: This entity will store all the attributes associated with expert advisory.


Optional /

Conditional

Remarks

1. query_reference_no Number M

2. Status_flag Number M It will be always accepted to be replied

by the expert.

3. query_category Varchar M

4. Expert_code Number M

5. Expert_advice Varchar C



6. Advice_status_code Number M Replied, delayed, auto forwarded

7. Response_ status Number M Query saved/published

6. Response_date Time span M Recorded Date of response published

7. Response_time Time span M Recorded Time of response published

3.5.1.9 Entity Name: Complaint Form Details Entity Description: This entity will store all the attributes associated with the application form of complaint register.


Optional /

Conditional

Remarks

1. User_id Number M

2. User_registrationno Number M

3. Complaint_category Varchar M

4. Complaint_dept Varchar M

4. Complaint_remarks Varchar M

5. Complaint_referenceno Number M

3.5.1.10 Entity Name: Grievance View Entity Description: This entity will store all the attributes associated with the stored grievances in database to the actor.


Optional /

Conditional

Remarks

1. Complaint_dept Varchar M Values seed varieties, prices, PoP, technical

issues etc

2. Complaint_receivername Varchar M Name of the concerned authority receiving the

complaints

3. Complaint_receivercode Number M code of the complaint receiver



4. Complaint_detail Varchar M Posted complaint details

5. Grievance_sender Varchar M Name of the person who has posted

grievance.

6. Entity_grievance Varchar M Area code of the person posting grievance.

3.5.1.11 Entity Name: Complaint Status Entity Description: This entity will store all the attributes associated with the complaint status.


Optional /

Conditional

Remarks

1. Complaint_referenceno Number M

1. Complaint_dept Varchar M

2. Approver_code Number M The code of the actor who is accepting or rejecting complaints

3. Complaint_status Boolean M Values 0, 1 or 2. 0 for rejection, 1 for

acceptance, 2 for forwarding it to another

expert.

4. Progress_status Integer M Replied/awaited/forwarded

5. First_expert_code Number Code of the expert who is forwarding the query to the next level expert.

6. Expert_code Number C Code of the expert to who query is forwarded

by the system.

3.5.1.12 Entity Name: Grievance Response Entity Description: This entity will store all the attributes associated with the grievance responses.


Optional /

Conditional

Remarks



1. query_reference_no Number M

2. Status_flag Number M It is always accepted to be addressed by the

expert.

3. query_category Varchar M

4. Expert_code Number M

5. Expert_response Varchar C

6. Advice_status_code Number M Replied, delayed, auto forwarded

7. Response_ status Number M Query saved/published

7. Response_date Time span M Date of response published

8. Response_time Time span M Time of response published

3.5.1.13 Entity Name: Form A Details Entity Description: This entity will store all the attributes associated with the application form for marketing license in seed.


Optional /

Conditional

Remarks

1. Applicant_name Varchar M

2. Postal_address1 Varchar M

3. Postal_address2 Varchar

4. Address_district Varchar M

5. Address_block Varchar M

6. Postal_ Pin_code Number

7. Mobile_no Number M

8. Sale_address1 Varchar M

9. Sale_address2 Varchar

10. Sale_district Varchar M

11. Sale_Pin_code Number M

12. Storage_address1 Varchar Specify storage address if, it is different from the

postal address.

13. Storage_address2 Varchar

14. Storage_district Varchar

15. Storage_pin_code Number



16. Type_dealership Varchar M Values: Proprietary/Partnership

/ Limited Company/ Hindu undivided Family

concern

17. Name_pr_p_man_k Varchar M Name of the proprietor/ partner/ manager/ karta

18. Address1_pr_p_man_k

Varchar M

19. Address2_pr_p_man_k Varchar

20. District_pr_p_man_k Varchar M

21. Block_pr_p_man_k Varchar M

22. Pincode_pr_p_man_k Number M

23. Capacity_application Varchar M Values are Proprietor/Partner/Man

ager/Karta

24. Applicant_conviction Boolean M Values 1 for yes and 0 for No

25. Seed_name Varchar M Name of the seed/varieties handled. Values: seed varieties.

26. Seed_remarks Varchar

27. Applicant_code Varchar M

28. Status_flag Number M For application save/submit. Values, 0

for save and 1 for submit

29. Application_type Varchar M Values, 0 for new and 1 for renewal application

30. Renewal_no Varchar C

3.5.1.14 Entity Name: Payment Details Entity Description: This entity will store all the attributes associated with the fee payment details.


Optional /

Conditional

Remarks




2. Mode_payment Varchar M Values cash/cheque/dd/interne

t banking/ debit card/ credit card

3. Challan_no Number M

4. Challan_date Time span M Date in dd/month/yyyy

5. Depositin Varchar M Values bank/treasury/post

office

6. Deposit_bankname Varchar C Values, all central/state banks specified in

database.

7. Deposit_treasuryname Varchar C Values, district treasury, sub treasury, special

treasury names

8. Deposit_poname Varchar C Values, post office names

9. Amount Number M

10. Applicationrefno Number M

3.5.1.15 Entity Name: Payment Gateway Entity Description: This entity will store all the attributes associated with the payment gateway for online payments.


Optional /

Conditional

Remarks

1. Epay_mode Varchar M

2. Ibankname Varchar M

3. Transaction_charges Number C

4. Amount Number M

5. Payment_status Boolean M Values, 0 for transaction failure, 1 for transaction

successful.


3.5.1.16 Entity Name: Application Status Entity Description: This entity will store all the attributes associated with the application status against Form A.




Optional /

Conditional

Remarks


2. App_status Integer M Values 0 for rejected, 1 for accepted, 2 for

pending

3. Date_status Time span M

4. Time_status Time span M

5. Reviewercode Number M

6. Application_refernceno Number M

7. Application_type Varchar M Values, new/renew

3.5.1.17 Entity Name: License Details Entity Description: This entity will store all the attributes associated with the License Details.


Optional /

Conditional

Remarks

1. Applicationrefno Number M

2. Application_type Varchar M

3. Application_status Integer M The status of the accepted applications 1

will be stored here.

4. License_date Time span M

5. Validity_date Time span M

6. License_status Boolean M Values, 1 for license issue and 0 for license

rejected

7. License_no Varchar M

8. License_renewalno Varchar C

3.5.1.18 Entity Name: Dealers Register Entity Description: This entity will store the dealer’s address details.




Optional /

Conditional

Remarks

1. Dealershipcode Varchar M

2. Dealer_name Varchar M

3. Dealer_Address1 Varchar M

4. Dealer_entitycode Varchar M

6. Dealer_cropcode Integer M

3.5.1.19 Entity Name: Dealers Stock Availability Entity Description: This entity will store all the attributes associated with Stock Opening Balance.


Optional /

Conditional

Remarks

1. Crop_code Integer M

2. Entity_code Integer M

3. Dealership_code Integer M

4. Openingbalance Numeric M

6. Asondate Date M

7. Openingvalue Numeric M Quantity in quintal

8. Totalimport_Qty Numeric Quantity in quintal

9. Totalreceived_Qty Numeric Quantity in quintal

10. Total_stock Numeric M Quantity in quintal

11. Totalexport_Qty Numeric Quantity in quintal

12. TotalSold_Qty Numeric Quantity in quintal

9. Closingbalance Numeric M Quantity in quintal

10. Date_of_entry Timestamp M It has default value

now().



3.5.1.20 Entity Name: Grower


Optional /

Conditional

Remarks

1. Grower_id Number M

2. #Sg_name Text M

3. #F_Sg_name Text M

4. Vill_id Text

5. Distt_id Number FK references District

6. Post Text

7. Category Text Value in (General, OBC,SC,ST)

8. Status_flag Number Status 1 for new record,

2 for edited record

3.5.1.21 Entity Name: Seed


Optional /

Conditional

Remarks

1. Seed_id Number M PK

2. #Crop Text M

3. #Variety Text M

4. #Stage Text M

5. Harvest_month Text Value in (Jan, Feb,….,Dec)

6. Type Text Value in (Self Pollinated, Cross Pollinated,, Paddy, Wheat, Vegetables, Hybrid Cotton)


2 for edited record



3.5.1.22 Entity Name: Offices


Optional /

Conditional

Remarks

1. Office_id Number M PK

2. #Type Text M Value in (Head Office, Divisional, Center)

3. #Place Text M Value in ( Distt of M.P)

4. Address Text

5. Fax Text

6. E-mail Text

7. Tel1 Text

8. Tel2 Text


2 for edited record

3.5.1.23 Entity Name: Employees


Optional /

Conditional

Remarks

1. Employee_id Number M PK

2. #emp_name Text M

3. #F_emp_name Text M

4. Designation Text

5. Dob Date

6. Doj Date

7. E-mail Text

7. Tel Text



8. Mobile Text


2 for edited record

3.5.1.24 Entity Name: Processing_Center


Optional /

Conditional

Remarks

1. Pc_id Number M PK

2. #Pc_Name Text M

3. #Pc_Distt_id Number M

4. Addr Text

5. Tel Text

6. Bulding_no Text

7. Post Text

8. Block Text

9. Fax Text

10. E-mail Text

11. Capacity Text

12. Storage_satisfactory Boolean Value, 0 for No and 1 for

Yes

13. Proper_light Boolean Value, 0 for No and 1 for

Yes

14. Wall_crack_free Boolean Value, 0 for No and 1 for

Yes

15. Tarpoline Number

16. Wodden_pallets Number

17. Fumigation_cover Number



18. Sitting_facility_satisfactory Boolean Value, 0 for No and 1 for

Yes

19. First_aid_box Boolean Value, 0 for No and 1 for

Yes

20. Record_keeping_satisfacto

ry

Boolean Value, 0 for No and 1 for

Yes

21. Incharge_name Text

22. Incharge_qualification Text


2 for edited record

3.5.1.25 Entity Name: Producing_Agency


Optional /

Conditional

Remarks

1. Pa_id Number M PK

2. #Pa_name Text M

3. Addr Text

4. Pa_distt_id Number FK references District

5. Vill Text

6. Post Text

7. Type Text Value in (Ownership, Partnership, Ltd Company)

8. Sales_tax_regno Text

9. Off_tel1 Text

10. Off_tel2 Text

11. Fax Text

12. E-mail Text

13. Applicant_name Text



14. Applicant_address Text


2 for edited record

3.5.1.26 Entity Name: Registering_Organization


Optional /

Conditional

Remarks

1. Ro_id Number M PK

2. #Ro_Name Text M

3. #Distt_id Number FK references District

4. Addr Text


2 for edited record

3.5.1.27 Entity Name: Lots


Optional /

Conditional

Remarks

1. Lots_id Number M PK

2. #Month_harvest Text M Value in (Jan, Feb,…., Dec)

3. #Year_Sow Number

4. #State Number Value is 12 for M.P

5. #Pc_regno Number

6. #Sg_regno Number

7. #Crop_S.no Number

8. #Stage Text

9. #Same_crop_no Text



10. Certificate_Seed Number In Kg

11. Pack_loss Number In kg

12. Pack_size Number

13. Packed_in_Pc Boolean

14. Packed_for_other Boolean

15. From_tag Number

16. To_tag Number


2 for edited record

3.5.1.28 Entity Name: Sample


Optional /

Conditional

Remarks

1. Sample_id Number M PK

2. Sampled_qty Number

3. Sampling_date date

4. Passed Boolean

5. Lots_id Number FK references Lots

6. Regrading Boolean

7. Ungraded_Seed Number

8. Graded_Seed Number

9. Employee_id Number FK references Employee

10. Laboratory_id Number FK references Laboratory

11. Test_date date


2 for edited record



3.5.1.29 Entity Name: Sample_Result


Optional /

Conditional

Remarks

1. Sample_id Number M PK, FK references Sample

2. #Standard_name Text M PK, Value in ( seed standards )

3. Result Number FK references District


2 for edited record

3.5.1.30 Entity Name: Laboratory


Optional /

Conditional

Remarks

1. Laboratory_id Number M PK

2. #Lab_Name Text M

3. #Place Text M Value in ( Distt of M.P)

4. Address Text

5. Fax Text

6. E-mail Text

7. Tel1 Text

8. Tel2 Text


2 for edited record

3.5.1.31 Entity Name: Sg_Registration


Optional /

Conditional

Remarks



1. Period_id Number M PK, FK references Producing Agency

2. Grower_id Number M PK, FK references Period

3. Office_id Number M PK, FK references Period

4. Pa_id Number M PK, FK references Pa_Registration

5. Period_id_pa Number M PK, FK references Pa_Registration

6. Reg_fees Number M

7. Status_flag Number Status 1 for new record, 2 for edited record

3.5.1.32 Entity Name: Grower_Seed


Optional /

Conditional

Remarks

1. Period_id Number M PK, FK references Sg_Registration

2. Grower_id Number M PK, FK references Sg_Registration

3. Office_id Number M PK, FK references Sg_Registration

4. Pa_id Number M PK, FK reference Sg_Registration

5. Seed_id Number M PK, FK references Seed

6. Appl_Date Date

7. Appl_Letter_No Number

8. Sowing_date Date

9. Appl_Accepted Boolean

10. Reason_Appl_Rejection Text

11. Appl_Pc Text

12. Sowing_inspection Date Obtained in Ist inspection

13. Inspected_Area_M Number In Hectare

14. Inspected_Area_F Number In Hectare

15. Inspected_Area_Total Number In Hectare, Inspected_Area_M + Inspected_Area_F

16. Est_yield Number In Kg



17. Center Number FK references Offices (Office_id)

18. Land_location Text

19. Land_Record Text

20. Reg_Area_M Number In Hectare

21. Reg_Area_F Number In Hectare

22. Reg_area_Total Number

23. Rejected_Area_M Number In Hectare

24. Rejected_Area_F Number In Hectare

25. Rejected_Area_Total Number In Hectare, Inspected_Area_M + Inspected_Area_F

26. Net_Area_Certified Number

27. Insp_fees Number

28. Seed_Test_Fees Number

29. Health_Test_Fees Number

30. Grow_Test_Fees Number

31. Others Number

32. Receipt_No Number

33. Pc_id Number FK references Pc_Registration

34. Period_id_pc Number FK references Pc_Registration

35. Raw_Seed Number In Kg

36. Seed_From_Area Number In Hectare


3.5.1.33 Entity Name: Inspection_Report


Optional /

Conditional

Remarks

1. Period_id Number M PK, FK references Grower_Seed

2. Grower_id Number M PK, FK references Grower_Seed

3. Office_id Number M PK, FK references Grower_Seed

4. Pa_id Number M PK, FK references Grower_Seed



5. Seed_id Number M PK, FK references Grower_Seed

6. ##Report_No Number PK

7. Report_Date Date

8. Time Time

9. Area_Rejected_Isolation Number

10. Area_Rejected_Contamination

Number

11. Unit_No Number

12. Dispatch_Date Date

13. Remarks Text

14. Reinspection Boolean

15. Employee_id Number FK references Employee

16. Dispatch_Date Date


3.5.1.34 Entity Name: Reg_Officers


Optional /

Conditional

Remarks

1. Employee_id Number M PK, FK references Grower_Seed


3. Grower_id Number M PK, FK references Grower_Seed

4. Office_id Number M PK, FK references Grower_Seed

5. Pa_id Number M PK, FK references Grower_Seed

6. Seed_id Number M PK, FK references Grower_Seed


3.5.1.35 Entity Name: Parent_Seed




Optional /

Conditional

Remarks


2. 3.

Grower_id Number M PK, FK references Grower_Seed

3. 4.

Office_id Number M PK, FK references Grower_Seed

4. 5.

Pa_id Number M PK, FK references Grower_Seed

5. 6.

Seed_id Number M PK, FK references Grower_Seed

6. P_Seed Number M PK, FK references Seed (Seed_id)

7. Lot_No Text

8. Qty_M Number

9. Qty_F Number

10. Qty_Total Number Qty_Total = Qty_M + Qty_F

11. Challan_No Number

12. Challan_Date Date

13. Producing_Agency Text

14. Seed_Certifying_Agency Text

15. 7. Status_flag Number Status 1 for new

record, 2 for edited record

3.5.1.36 Entity Name: Grower_Seed_Lot


Optional /

Conditional

Remarks

1. Lots_id Number M PK, FK references Lots

2. Period_id Number M FK references Grower_Seed

3. 3.

Grower_id Number M FK references Grower_Seed

4. 4.

Office_id Number M FK references Grower_Seed



5. 5.

Pa_id Number M FK references Grower_Seed

6. 6.

Seed_id Number M FK references Grower_Seed


3.6 Other Requirements

This section lists the other non-functional requirement related to installation/un-installation /upgrades of ISS application. A non-technical person shall be able to setup and run the ISS application.

3.6.1 Backup

An automated and scheduled data backup mechanism shall be provided which will write a backup of the data to one of the system’s disks. From there, the backup date can be manually written to CD or tape if required.

The data backup should cover data held in a database and any data held outside of the database such as files uploaded through the software.

3.6.2 Recovery

A simple manual data recovery procedure will be provided to recover the data from a data backup when required by the system administrator. The data backup will be used to recover the data in the event of a disk corruption or database corruption.

3.6.3 Data Retention

The latest data on the Server will be kept for the seasons of the two calendar years. The data for more than a five year is to be backed up on to a CD/DVD and remove from the Server.

3.6.4 Customer/User Training

It is proposed that NIC will conduct a training program for 5 days at NIC, HQ to fully train selected ISS Administrator on the installation, use, backup, recovery, plan creation/updation and problem diagnosis. These Administrators will become “ISS Master Trainers (also known as Trainers of Trainers) who will then train ISS users in the use of the software. (Consultation with NIC require on this point)

3.6.5 Audit Trail

The Software shall offer a comprehensive report on the user actions (changes made with time stamp) through audit trail.



4. ANNEXURES

4.1 Annexure-1

4.1.1 System-Use Case Diagram

Annexure-1

Dealer/Menufacturer/farmer

Content Creator/Content Manager

A.D.A/S.A.D.O

J.D.A/D.D.A

SME

Login

Registration,

Licensing & renewal

Application

Acceptance

Testing

Status Tracking

Reference No

Alert System

Grievances

Expert Advice

E Payment

Content SearchFAQ/Compalint

Acceptance

«extends»

«extends»



4.2 Annexure-2

4.2.1 Enclosure Form-A





4.2.2 Enclosure Form-B



4.2.3 Enclosure Form V



4.2.4 Enclosure Form VIII



4.2.5 Enclosure Test Card



4.2.6 Enclosure Certified Sample Reports



4.2.7 Enclosure Official Sample Report



4.2.8 Enclosure Service Sample Report



4.2.9 Enclosure City Wise Monthly Report



4.2.10 Enclosure Crop Wise Monthly Report



4.2.11 Enclosure Sample Wise Monthly Report



4.2.12 Enclosure Certified Seed Sample Collection Form-1



4.2.13 Enclosure Certified Seed Sample Collection Form-2