S. No Name of documents Document used by Purpose
III. User Profile Details IV. Assigning Privileges
3.2.3 Transactions and Work Flow
3.2.3.1 Seed Availability Process Diagram 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
Use Case Name Purpose of the Use Case Actor
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.
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.
Alternative Flow: None
Exceptional Flow: Actor Actions
Clicks link but the Service 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 High Frequency of Use:
Continuous/ frequent/
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 Special Requirements: None
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 Notes and Issues: 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.
Alternative Flow: None
Exceptional Flow: Actor Actions
Clicks link but the Service 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 High Frequency of Use:
Continuous/ frequent/
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 Special Requirements: None
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 Notes and Issues: 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/K arta
- 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.
Alternative Flow: None
Exceptional Flow: Actor Actions
Clicks link but the Service 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 High Frequency of Use:
Continuous/ frequent/
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
Notes and Issues: None .
3.2.3.1.4 DEVELOPMENT OF SMS APPLICATION BASED ON NICSMS 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.
Special Requirements:
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.