Chapter 5: System Design
26
Chapter 5: System Design
5.1Functions of the system 5.1.1 Use Case Diagram 5.2Data Modeling 5.2.1Class /E-R Diagram 5.2.2System Activity Diagram 5.2.3Data Dictionary 5.2.4 Sequence Diagram 5.3Functional Modeling 5.3.1Context Diagram 5.3.2Data Flow Diagram 5.4 Flow Chart
Chapter 5: System Design
27
5.1 SYSTEM INTRODUCTION:
Our application starts with the Login function with requirement of User Id and
Password. Mainly contains two parts of the system.
1) Batch Data import: Import external data to the system for the information
regarding management data.
2) Video displaying.
1) Batch data import:
Batch data import is the first section of the project. In this section we are
storing data into database as normal function of the system. First section is the
interaction section with database that interacts with external data and user interface
for the system user. Batch import is the one primary level user interface that can
implement the more detail about the user and work to support the user to use second
section of the system. Registration of Farmer, Merchant and Area Admin ,addition of
crop, crop price, whether, seminar, news update,7/12,8/A certificate ,advance query
and its response system are remain in database system.
2) Send SMS and E-mail:
Master Admin send SMS to any farmer and merchant for any event about
farming so farmer easily know what is new happening in farmer field around them
and merchant also get confirmation for to buy crop from admin side.sms will be send
by connecting mobile to pc than select device for send SMS .This functionality also
at Area admin side remaining except SMS system
.
3) Get Certificate:
Farmer get certificate of 7/12 and 8/A from their account that certificate on
land that is useful for many place at bank, Toluca panchayat and more. Using this
system farmer does not have to go far for that.
4) Advance help system:
Farmer ask any question about land, crop agro, piyat ,irrigation problem,
subsidy, loan in farming and he get complete satisfactory solution for that without
any complexity and money.
Chapter 5: System Design
28
5) Video streaming:
Following is the brief details of the changes /addition in Dspace to implement
the Video Streaming functionality. The Details provides list of java files , jar files
that were modified , class paths used to compile the sources and the details of the
flash plug-in used.
The video Streaming module for Dspace helps the user to view and even
download video software at the client machine.
We are using Quick time Full screen Video Player as our flv plug-in because it
is open source and freeware.
The plug-in also helps the user to view the video in full screen Mode.
The videos available were in analog format (Digicam,Betacam) Which were
converted to flv using super (an open Source software).
The Videos are as from their own desk without installing any converted into
Flash Video (flv) format because of the following Reason:
More than 80% Videos related websites are using flv as their format
already.
Commonly already available as plug-in in client so no new installation.
Supports advanced video codes like H264, Hence can deliver better
quality even at lower bitrates.
In the Existing system of Dspace , the user needs to download the
video but cannot see the video on the same pages.
The Video streaming modules for Dspace helps the user to view and
even download software at the client machine.
We are using Flv Flash player Full Screen Video Player as our flv
plug-in because it is open source and freeware.
The plug-in also helps the user to view the video in full screen mode.
In initial stage the video from VCD/DVDs are converted to flv using
FFMPEG library (open sources).
Chapter 5: System Design
29
5.1.1 USE CASE DIAGRAM:
Actor: The following actors interact and participate in this use case.
Master Admin
Area Admin
Farmers
Merchant
Pre-Condition:
Farmer, Master Admin. Area Admin must have to login into system.-user
name & Password.
Post Condition:
Final certificate is generated, send SMS or E-mail to farmer or merchant.
Scenario:
Framer register himself or through Area Admin for 7/12 and 8/A certificates
and advance help system. Area admin make registration for 7/12 and 8/A and send E-
mail to farmer for farming master. Master Admin make all addition of crop, crop
price, whether, seminar, news update information. He also send SMS and E-mail to
farmer and merchant.
Chapter 5: System Design
30
Use Case Diagram for Master Admin:
System
Login
Add information
Send Email/SMS
Answare the
question
Master Admin
«uses»
«uses»
«uses»
«uses»
«extends»
Area Admin
Registration
crop,city price
addition
Seminar and News
Update
Add district and
whether info
«extends»
«extends»
«extends»
Fig 5.1 Use case for Master Admin
Master Admin handles the events for the login, Add information, send SMS, Answer
the query, and another operation for the admin which extends the registration information for
the special purpose.
Chapter 5: System Design
31
Use Case Diagram for Sub Admin and User:
System
Area Admin
User
Login
Farmer and
Cerificate Registration
get whether info
Get crope price
and notification
Update/Delete info
Send email
«uses»
«uses»
«uses»
«uses»
Get certificate
«uses»
«uses»
«uses»
«uses»
Ask Question/Get
Reply
«uses»
Fig 5.2 Use case Diagram for Area Admin and User
Chapter 5: System Design
32
5.2 DATA MODELING:
5.2.1 ER Diagram:
1+ * 1+ *
1
1
1 * 1
* 1 *
1 * *
1
tblUserLogin
Election_no: string Password:string Name:string Login()
tblMaster Admin
Register Areaadmin()
Add Districtinfo()
Add whetherinfo()
Update allinfo()
Delete allinfo()
Send sms()
Send Email()
Add cropinfo()
Add cropprice()
tblAreaAdmin
Address:string
Age:string
Farmer Registration ()
Certificate Registartion()
Send mail()
Update allinfo()
Delete allinfo()
tblFarmerregister
Gneder:string
Address:string
Email:string
Contact:integer
Age:integer
Get Certificate()
Ask question()
Get Cropprice()
Get whetherinfo()
Get allstaticinfo()
Feedback()
tblMerchant
Address:string
Email:string
Contact:integer
Age:integer
Turnover:integer
Factor:string
Org_name:string
Feedback()
Get Cropprice()
Get whetherinfo()
Send requirement()
Get allstaticinfo()
Tblfor8a
Account no:string
Area:integer
No_Trees:integer
LocalTax:integer
PropertyTax:integ
er
EducationTax:int
Other:string
Tblfor7/12
Land name:string
Land address:string
Land area:string
Land source:string
Irrigation:string
Method:string
Account no:string
Tblquery
Sender_name:string
Sender_address:string
Sender_topic:string
Role:string
Question:string
Answare:string
Tblquery
Sender_name:string
Sender_address:string
Sender_topic:string
Role:string
Question:string
Answare:string
Whether
Humidity:integer
Temprature:integer
Note:string
Photo:string
Tblcrop
Crop_name:string
Crop_group:string Tblcity
City_name:string
Crop_name:string
Crop_price:integer
Districtinfo
District:string
Taluka:string
Crop:string
Piyat:string
Area:string
tblWhether
Humidity:integer
Temprature:integer
Note:string
Photo:string
Tblcrop
Crop_name:string
Crop_group:string
Tblcity
City_name:string
Crop_name:string
Crop_price:integer
tblDistrictinfo
District:string
Taluka:string
Crop:string
Piyat:string
Area:string
Chapter 5: System Design
33
5.2.2 SYSTEM ACTIVITY DIAGRAM:
Registration Login
Change DetailEnter Detail
Send Email Generate Report
Log out
[Reject]Checked [Accept]Checked
[Success]Register
[Done] [Done]
[Fail]Register
Fig 5.3 Activity Diagram
Chapter 5: System Design
34
5.2.3DATA DICTIONARY:
Table 5.1 Weather information
Table 5.2 Sub Admin information
Table 5.3 Login Details
Chapter 5: System Design
35
Table 5.4 Query Table
Table 5.5 News Details
Table 5.6 Merchant Information
Chapter 5: System Design
36
Table 5.7 Table for 8A Certificate
Table 5.8 Table for 7/12 certificate
Chapter 5: System Design
37
Table 5.9 Table for farmer registration detail
Table 5.10 Table for Toluca information of City
Table 5.11 Table for crop information
Chapter 5: System Design
38
Table 5.12 Table declaring information for crop price for area wise
Table 5.13 Seminar Details
Table 5.14 Merchant Requirement Table
Chapter 5: System Design
39
Table 5.15 Table for feedback from user
Table 5.16 Table for district information
Chapter 5: System Design
40
View 1:
View 2:
Chapter 5: System Design
41
View 3:
View 4:
Chapter 5: System Design
42
View 5:
View 6:
Chapter 5: System Design
43
5.2.4 SEQUENCE DIAGRAM:
USer Client application Database Server
Check For entry
confirmation
Allow
Login User Name/Password
Check into DBValid
Invalid UserInvalid user
Registration
Add information Added intoDB
Send Mail/SMS
Check
ReplySMS/email confirmation
Requiest for certificate request added into db Check user account
Message2Generate cerificate
Certificate{Print Document
}
Log out
end session
ConfirmSuccessfully Logout
Fig 5.4 Sequence Diagram
Chapter 5: System Design
44
5.3 FUNCTIONAL MODELING
5.3.1 Context Diagram: Level 0
E-Kheti
(The Natural activity)
0.0
Master Admin
MerchantUser
Area Admin
New Register and
allocate area adminRetrieve
Information
Registration
Give Access
Send Mail
Edit/ Update
operationRetrieve information
Edit/Update
operation
Apply for certificate
Create Certificate
Request for Crop
Get confirmation
Fig 5.5 Context Diagram
Chapter 5: System Design
45
5.3.2 Data Flow Diagram:
LEVEL 1 :( Master Admin)
Master Admin E-Pharm
login
E-Pharm
2.0
Add information
3.0
Edit/Update info
Delete info
Changes back to
database
Invalid
Username
Or Password
Check into
DBBack to
page
Valid ID
Fetch data
Make
changes
4.0
Log Out
Added Back to page
1.0
Log in
Cancel
Fig 5.6 LEVEL 1 :( Master Admin)
Chapter 5: System Design
46
LEVEL-2(Master Admin): Add information
Send Email/
SMS
2.3
Weather Info
2.5
Add new
information
2.0
Add Area
Admin
2.2
Add
AddAdd
Change
Information
2.4
Edit
Operation
2.6
Added
Added
Added
Add
Add seminar/
News info
2.1
Send Reply
2.6
E-Pharm
Added
Fig 5.7 LEVEL-2(Master Admin): Add information
Chapter 5: System Design
47
LEVEL-1 (Area Admin):
Area Admin
Log In
1.0
E-Pharm
Add
Information
2.0
Edit
Information
3.0
Delete/Update
Information
4.0
Log Out
5.0
E-Pharm
Invalid UserId
Or Password
Verify
DataBack to
page
Valid User
Log In
Added
Add into DB
Changes
Confirmed
Apply to DB
Cancel
Chnages
Cancel
Chnages
Fig 5.8 LEVEL-1 (Area Admin)
Chapter 5: System Design
48
LEVEL-2(Area Admin): Add information
Send Mail
2.2
Create
Certificate
2.3
Add new
information
2.0
Farmer
Registration
2.1
Add
Add
Add
Add
Change
Information
2.4
Edit
Operation
2.5
Added
Added
Added
Edit
E-Pharm
Added
Fig 5.9 LEVEL-2(Area Admin): Add information
Chapter 5: System Design
49
LEVEL-3(Area Admin): Generate Certificate
Generate
report
2.3.0
E-Pharm
Process Data
2.3.1
PDF/DOC
Format
Certificate
Cert
ific
ate
PDF/DOC
Format
Certificate
Certifi
cate
Log Out
2.5For Report
Check for
request
Check into DB
Fetch Data from
DB
Check for another
request
Work done
7/12 8A
Fig 5.10 LEVEL-3(Area Admin): Generate Certificate
Chapter 5: System Design
50
LEVEL-1:(Merchant)
Merchant
Registration
1.0
E-Pharm
Request for
crope
2.0
Check into
DB
Back to
page
User name already Exist
Valid
UserRegister
Feed Back
3.0
Fig 5.11 LEVEL-1(Merchant)
Chapter 5: System Design
51
LEVEL-1(User):
User
Data Retrieve
process
1.0
Request for
Certificate
Process
7/12
5.0
Request for
certificate
8a
Process
6.0
Ask for Help
Process
4.0
Log In
Process
3.0
Smart SchoolDB
Check into
DBBack to
page
Valid User
Retrieve
Info
Back to
page
Log Out
7.0
User Home
Work done
Work done
Work done
Contains Multiple process
where user can perform
more then one task and
complete their work with
log out process
Registration
Process
2.0
Registered?
No
YES
Fig 5.12 level 1 User
Chapter 5: System Design
52
5.4 FLOW CHART:
Login
Valid?
Role?
Yes
No
Master
Admin
Start
Area
AdminUser
Edit/
Update/
Delete
DataTa
ble
Send Mail/
SMS
Add Seminar
Detail/Reply of
Quetion
E-Pharm
Update/
Delete
Operatio
n
Send email Registration
Select Area
Crop
price/
other
Details
Certificate
Ask
Questio
n
Log Out
Stop
Fig 5.13 System Flow Diagram