AGRICULTURAL PRODUCTS E-MARKETING

GUJARAT KRISHI VAHINI

20-Oct-11 OM SHANTI ENGINEERING COLLEGE-RAJKOT Ashish Pokiya and Virendra Vekariya

A PROJECT REPORT ON

Agricultural Products E-Marketing (Gujarat Krishi Vahini)

DEVELOPED BY: Ashish Pokiya (080360116036) Vekariya Virendra (080360116036)

INTERNAL GUIDE Mr. Mahesh K. Kaluti Dept. of Information and technology Om Shanti Engineering College, Rajkot

A project submitted in the partial fulfillment of the requirement for the degree of

BACHELOR OF ENGINEERING In Information and technology

Department of Computer Science & Engineering & Information Technology Om Shanti Engineering College, Rajkot October 2011

OM SHANTI ENGINEERING COLLEGE Department of Computer Science & Engineering & Information Technology
CANDIDATE DECLARATION
I declare that final Year report entitled Agricultural Products e- Marketing is my own work conducted under the supervision of the guide Prof Mahesh K. Kaluti.

I further declare that to the best of my knowledge the report for B.E. final semester does not contain part of the work which has been submitted for the award of B.E. Degree either in this or any other university without proper citation. Candidates Signature:

Guide: Department of Computer Science & Engineering and Information Technology, Om Shanti Engineering College-Rajkot, State: Gujarat

OM SHANTI ENGINEERING COLLEGE Department of Computer Science & Engineering & Information Technology
CERTIFICATE

This is to certify that the project entitled Agricultural Products e-Marketing is a bonafied report of the work carried out by Mr. Ashish R. Pokiya (080360116036) under the guidance and supervision of Mr. Mahesh K. Kaluti for the award of the Degree of Bachelor of Information Technology at Om Shanti Engineering college, Rajkot , Gujarat

To the best of my knowledge and belief, this work embodies the work of candidate himself, has duly been completed, fulfills the requirement of the ordinance relating to the Bachelor degree of the university and is up to the standard in respect of content, presentation and language for being referred to the examiner.

Date of Submission:

Project Co-ordinates Mr. Mahesh K. Kaluti

Head of Department Prof. Harshal Shah

ACKNOWLEDGEMENT
I would like to express a deep sense of gratitude and thanks profusely to my project guide Mahesh K. Kaluti for his proper guidance and valuable suggestions. Without the wise counsel and able guidance, it would have been impossible to complete the report in this manner. It is moment of great pleasure to acknowledge their help and encouragement. Their interest and constant encouragement helped me in making the report a success.

The constant guidance received from Mr. Harshal Shah Professor and H.O.D department of Computer Science & Engineering and Information Technology has been of great help in carrying out the present work.

I am thankful to all the faculty members who have directly or indirectly helped me in completion the seminar.

ASHISH R. POKIYA 7TH SEM

Abstract
At present, in field of agriculture in Gujarat buying and selling is done with the involvement of intermediaries. This gives undue profit to intermediaries who do not even own a single land for cultivation. The aim of the project is to empower the farming community with the market information, to get particular produces updated price. In the first Phase, the project has connected with 25 agricultural product markets. This project provides an ease of access market related information to the farmers. The price rates could be accessed on a cell phone with a one-time registration. Along with the aforesaid features, the website will also be developed in Gujarati.

College profile

The institution SANJAYRAJ EDUCATION ZONE, OM SHANTI ENGINEERING COLLEGE is located in the outskirts of Rajkot city is the capital of Saurashtra. The city is ?young? in comparison with other Indian city. It is the nerve centre for dance, music, and arts. The SANJAYRAJ EDUCATION ZONE, OM SHANTI ENGINEERING COLLEGE campus is 2nd nearest campus to the Rajkot city. Within an easy driving of just 11km from the Rajkot City, Race course. Entire campus premises spread in 106 acres of landscape. Unlike from the other campus this is probably the 1st campus right from their beginning of its 1st college offers sports complex, Hostel, Staff Quarter, Landscape, etc. From getting bored out of studies, we have facilities of exclusive Horse Riding and swimming. The campus is well equipped with high security and staff. The arena of campus is situated under the natural roof, attire of greenery and little knoll which gives bird view of Rajkot city.

Tables
List of Figures Fig 1 Fig 2 Fig 3 Fig 4 Fig 5 Fig 6 Fig 7 Fig 8 Fig 9 Fig 10 Fig 11 Incremental Model Diagram Expected Day Chart: Risk Statements Class Diagram Activity Diagram for user Activity Diagram for admin Sequence Diagram for user Sequence Diagram for admin Data flow Diagram Use case Diagram Testing Process

List of Tables

Table-1 Table-2 Table-3 Table-4 Table-5 Table-6

Project scheduling. Effort estimation using cocomo model Database Design for Login Database Design for market Database Design for commodity Database Design registration

Abbreviations:

SMS SRS IEEE http APEM ASP KLOC OOP

Short Message Service Software Requirement Specification Institute of electrical and electronic engineers. Hyper text transfer protocol Agricultural Products E-Marketing Active server page Kilo lines of code Object oriented program

Notation 1. Class diagram:

2. Activity Diagram:

3. DATA FLOW DIAGRAM

4. E-R DIAGRAM:

5. OBJECT DIAGRAM:

*.1 **

6. USECASE DIAGRAM:

include

extend

7. SEQUENCE DIAGRAM:

TABLE OF CONTENT

ABSTRACT COMPANY PROFILE. TABLES. 1. LIST OF FIGURES. 2. LIST OF TABLES ABBREVIATIONS NOTATIONS 1. INTRODUCTION 1.1. PROJECT SUMMARY. 1.2. PURPOSE. 1.3. SCOPE.. 1.4. OBJECTIVE. 1.5. TECHNOLOGY AND LITERATURE REVIEW.. 2. PROJECT MANAGEMENT. 2.1. PROJECT PLANNING 2.1.1. PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION 2.1.2. PROJECT PLAN.. 2.1.3. MILESTONES AND DELIVERABLES 2.1.4. ROLES AND RESPONSIBILITIES. 2.1.5. GROUP DEPENDENCIES..

2.2. PROJECT SCHEDULING 2.3. RISK MANAGEMENT.. 2.3.1. RISK IDENTIFICATION. 2.3.2. RISK ANALYSIS. 2.3.3. RISK PLANNING 2.4. COST ANALYSIS 3. SYSTEM REQUIREMENTS STUDY. 3.1. USER CHARACTERISTICS. 3.2. HARDWARE AND SOFTWARE REQUIREMENTS.. 3.3. CONSTRAINTS 3.4. ASSUMPTIONS AND DEPENDENCIES 4. SYSTEM ANALYSIS.. 4.1. STUDY, PROBLEMS AND WEAKNESS OF CURRENT SYSTEM.. 4.2. REQUIREMENTS OF NEW SYSTEM 4.3. FEASIBILITY STUDY. 4.4. FEATURES OF NEW SYSTEM 4.5. PROCESS MODEL 4.6. OO APPROACH.. 4.6.1. CLASS DIAGRAM.. 4.6.2. USE CASE DESCRIPTION 4.6.3. FUNCTIONS OF SYSTEM.. 4.6.4. DATA FLOW DIAGRAM. 4.6.5. DATA MODELING.. 4.6.5.1. 4.6.5.2. DATA DICTIONARY.. ER DIAGRAM

5. TESTING.. 5.1. TESTING OBJECTIVES 5.2. TESTING TECHNIQUES 6. FUTURE OUTCOME AND CONCLUSION. 7. APPENDICES

8. REFERENCES EXPERIENCE

Chapter 1: Introduction
1.1Project Summary
This project is useful for the Agriculture Market and Farmer Community. Project contains all the market Information about the rate of commodity in Gujarat.

1.2Purpose
Purpose of project is to empowering farmer community with the market information. The farmer community which dents has information about market rate to provide them up to date market price.

1.3Scope
The scope this project is it can be used in any farmer that can be non-technical or technical, and any intermediate work office which they want to know current Mandi Rate. Agriculture product e-marketing project will maintain the current rate of market. This project also provides other related information about market like what is current whether of market area so, they can protect his product against natural Disaster. The system is mainly web based system and it contain of a SMS server. Project focus on provide efficiency information to make decisions easily.

1.4 Objectives
The advantages of Agriculture product e-marketing accrue to the farmers, as they have choices to sell their produce in the nearest market at remunerative prices. In addition to this, the Country witnesses: State wide market information for wholesale produce Access mainly through the Internet Information dissemination progressively through local languages

Computer facilities at the markets Information collected by nodes in the various markets Information on loans, policies and regulations Bypass middlemen.

1.5 Technology and Literature review

This project will be a web application to be developed in .Net Technology using Ms Server 2010 as back end.

Database Design (Ms Server 2010) Form Design (Asp.net) Coding (Asp.net) Reporting (Crystal Report)

Chapter 2: Project Management

2.1Project Planning 2.1.1 Project Development Approach and Justification
The project development approach to be used is the incremental model: In the incremental model, there are many phases, like analysis, designing, coding and testing.

Fig 1

Why incremental modal: As product is to be delivered in parts, total cost of project is distributed. Limited number of persons can be put on project because work is to be delivered in parts. As development activities for next release and use of early version of product is done simultaneously, if found errors can be corrected. Customers or end users get the chance to see the useful functionality early in the software development life cycle. As a result of end users feedback requirements for successive releases

become more clear. As functionality is incremented in steps, testing also becomes easy. Risk of failure of a product is decreased as users start using the product early.

When we developed this software first of all we will prepare a roughly project as per the requirement of the project. In first level of the project contain information about only 25 market and next level contain other market information. This level contain also commodity price rate and SMS functionality.

2.1.2 Project Plan

Project was well planned. Project began with gathering user requirements, than diagrammatic representation of the functionalities was designed. Required database was designed and normalized as required. Code written in such a way that maximum functionality was coded with minimum possible lines of code.

2.1.3 Milestone and Deliverables

Milestone means the, during the project planning, at the particular time these much work must be completed and all the work information in a fixed format. For example: at the end of the every week how much work should be completed by the developer, if the company want to know then it is a fixed mile stone. In our project at the end of the every week we have to submit the report to the collage, how much analysis we have at the end of the every week. First Milestone: analysis of the software and the technology which we are used. Industry definition problem will be submitted to the college and to the university. Second Milestone: in this milestone we have done the technology analysis and we will fixed the software designing approach and which model will be used and what are the basic functionality will be required for the development and analysis. Third Milestone: in this milestone till decided the project approach and designing (comparatively) and modules will be there. Which module will be handle by whom

can decided here. And finally the database designing will be done here in this milestone Fourth Milestone: in this milestone the database designing is ready so now the coding and before that how much time is required for the developing the modules means the time estimation will be done here, before the coding. Fifth Milestone: in this milestone the coding will be done. Sixth Milestone: the testing of the software will done here.

2.1.4 Role and Responsibilities

The different roles like database designer, modules designer and coder or developer like many things will be here during the software development. Analysis: Ashish Pokiya and Vekariya Virendra Database Designer: Ashish Pokiya Module Designer: Vekariya Virendra Developer: Ashish Pokiya and Vekariya Virendra Testing: Mahesh Kaluti

As shown here the many responsibilities will be there while developing the project. The responsibilities of the database will be taken by the Ashish Pokiya and the modules will be designed by the Vekariya Virendra. During this stage the guidance will be provided by Mahesh Kaluti.

2.1.5 Group Dependencies

There will be not any kind of the group dependencies in our project All the developers can work as they want to, Means in the sequential but not dependant will be there between the users.

2.2Project Scheduling.
Project scheduling means the which process will be done by whom and at which particular time.

Analysis Design Coding Testing

Expected Day 7 32 45 12 Table: 1

Expected Day Chart:

Actual Day 12 40

45 40 35 30 25 20 15 10 5 0 ANALYSIS DESIGN CODING TESTING

Days

Fig. 2

2.3Risk Management
Risk are future uncertain events with a probability of occurrence and a potential for loss".

2.3.1 Risk Identification In this face, during the development of the project, which kind of the risk will arise
and how to solve that risk will be done here.

Now here during the development, risk like, if user want to add any functionality to
the project when the project is at the last stage of the development then at that time what to do?

Now at that time, if the designing of the developer is sufficient, and can be done in
the proper way, then it is ok to add the functionality, but if it is not in the proper way, then all these development the developer has to do again.

So the database designing and modules should be design in that way that any kind of
the future changes can be apply.

The software is developed in the C#.Net so in the market right it is workable

language, so if it is developed in the VB.Net than problem may arise if user want to apply changes in the future.

2.3.2 Risk Analysis In the risk analysis phase, which kind of the risk will arise in the softwares will be
known here.

Like cost risk, benefit risk, time risk, project completion risk, employee risk etc. Risk of the cost, if the software is decided to complete in the 4 months, if it will
complete in the 6 months, then at that time the cost of this delaying software, the company has to the employees as well as to the market also.

Because the company had or fixed the money as per the requirement of the 4 months
but now they becomes 6 months, so extra money user may give or may not.

 After that timing risk will be there. During the development of the software we
doesnt phase any risks.

2.3.3 Risk Planning

In this phase, if any risk arise, then how to solve that risk, will be identified here.

Fig: 3

2.4 Estimation 2.4.1 Effort Estimation

After gathering all the requirement of the software and complete the analysis of the software, the effort estimation will be done. Effort estimation means how much time will required for the complete the project, and how much amount will required for the development of the project. Effort estimation as per the cocomo model can be find out from the following equations E= ab (KLOC)bb. D = Cb(E)db. P= E/D. Where E= effort applied in person-months. D= development time in chronological months. KLOC= kilo line of the code for the project. Software Projects Organic Semi-detached Embedded
Table: 2

Ab 2.4 3.0 3.6

Bb 1.05 1.12 1.20

Cb 2.5 2.5 2.5

Db 0.38 0.35 0.32

2.4.2 Cost Estimation

In the cost estimation, the cost of the project will be defined. In this stage, for example, for any project there 5 developers are working and company have to pay 10,000 to each developer and the project must complete to in three months. So that money plus the maintenance and the profit of that project will be added to the cost. In our example 50,000 at each month and the 10,000 maintenance money at each month then the total cost of 60,000 rs per month.

Project will work for 3 months, so total cost estimation will be 1,80,000 rs. In our project the cost estimation will be like 1,50,000.

3.

System Requirements Study

3.1 User Characteristics

Registered user: To achieve all the services these users, must log on into system or communicate with system by using SMS. If user communicates with system via SMS, user must have use mobile number that used during registration procedure. According to the services request be user operation will vary.

None registered users: Does not require registering. Can view maps, price alert ranks procedure stores. Price alert can request and also received via SMS.

Administrator:

They should be able to login according to privileges assigned. Add. Edit, Delete user accounts and also manage it. Every market has specific code, on basis of that admin can login on their related market account, and does modify that price alert.

3.2Hardware and Software Requirement Hardware Requirements:

Computer

Minimum required, Pentium IV processor (2 GHZ or higher is recommended), Ram with minimum 512 Mb, Disk space: 1 GB, Mouse and keyboard are needed as input and a monitor. Mobile phone

Software Requirements:
Operating system: Windows platform. Data base: Sql sever 2010. Java script enable web browser.

Communication interfaces
Internet

The APEM used MS server and hence required HTTP for transmission of data. More over this allow easy interact with between the user and server. Mobile phone

3.3 Constrains 3.3.1 Regulatory Policies

All the access rights to access the project is provided to all the users depending on their user type that is given by the administrator. 3.3.2 Hardware Limitations

Computer

Minimum required, Pentium IV processor (2 GHZ or higher is recommended), Ram with minimum 512 Mb, Disk space: 1 GB, Mouse and keyboard are needed as input and a monitor. Mobile phone

3.3.3 Interfaces to Other Applications

The system is also provide link to agmarknet.nic.in to view all India price list of commodity System will provide whether information using the weather departments system.

3.3.4 Parallel Operations

The site can be used by administrator as well as user at the same time. Administrator provides different category for applications. And user can also access the application at the same time. As same time user can see the price list and also get SMS of commodity rate.

3.3.5

Higher Order Language Requirements

In this software development higher order language is required. We are using .NET and in that C#.NET because of that is easy to use, third party controls also can use thats functionality is easy and provide best look. Plus we are using the third party controls of the DEV Express, because of that the look and feel becomes more attractive and the validation of will becomes more stronger.

3.3.6 Reliability Requirements

Reliability, of the system can be expressed as continuity of service.[2] The reliability of the system should be high quality and deliver the service as expected by users. The reliability of the system is highly increased because system depends on both internet and SMS. There would always be a backup storage of the database maintained, thus if system crashed then easily recovery can be possible. But the Change of system crashing is very law. To avoid the network fault, login problem, virus attracts. User friendly system, registered user can directly log on to website or access through the SMS. The systems automate report with less error

3.3.7 Criticality of the Application 3.3.8 Safety and Security Consideration

There will be proper security regarding to the accessing of application. The external security of updating daily rate can be provided by given the login authentication. The whole software is secure from the outside accessing. The mobile number from resisted user should be authenticated. The database may get crashed at any certain time due to virus or operating system failure, Therefore; it is required to take the database backup.

3.4Assumption and Dependencies

Developer assumes that a modern web server with server side scripting capabilities is available on the host system. Software developer assumed that there will be a system Administrator that will maintain this system. Assume user who achieves the services via mobile phone user predefined format of SMS. Assume each registered user have a mobile number. Assume each market have one admin person. Proper browser should be installed Internet connection is a must.

4.0 System Analysis

4.1 Study of Current System
At present, in field of agriculture in India Buying and Selling is done with involvement of intermediates. This gives undue profit to intermediate who do not even owned a single land for cultivation. The result of the involvement of intermediate in the process make buyers consumer to buy agricultural product at higher prices and seller/farmer do not get fair price to their product.
Currently, Gujarat has a system that focused on providing information about different event, news and commodity profile for agriculture goods that handle by Gujarat State Agriculture Marketing Board and Designed by: Silvertouch Technology Ltd. That system contain following features.

Price alert facility for agriculture goods, but that can link on agmarknet.nic.in. Proved information about current Latest news and events and provide commodity profiles And Related Act e.g. whether information.

Limitation of this system is, it not direct providing price alert of commodity goods, it provide link to agmarknet.nic.in which is providing price alert in all India but not specific languages.

4.2 Problem and Weaknesses of Current System

Limitation of this system is, it not direct providing price alert of commodity goods, it provide link to agmarknet.nic.in which is providing price alert in all India but not specific languages. In the current system there are many problems indicate below: In the current system not available the up to date commodity prices of the market. In some website only the information about the market is present not the market product prices. Also not provide the good user interface. This system not implemented on the rural area. In website language option not available on some site, so Lack of market information

4.3 Requirements of New System In mention above system problem and add some more feature s related to farmer requirement of new system is arise. User requirement Retrieval of Local Agri product information. Show the different market price for take the decision to sell their commodity product. Also show the some other information related to the farming community. e.g., if farmer wants to show the information about the pet animals, about their food or medical information. And other requirement is general information about the chemical medicine use in the crop for better fertilizing purpose or to get the more production. For plantation the crop seeds requirement are arise someone do not get the good seeds so information about the better seeds also they want to know. Also to know the new technology used in the cultivation and new tools for the farming community to works in the land that gives flexibility to farmer. System Requirement To develop the real time application system requires the all information mentioned above in the user requirement. System analyzes the user requirement and develops the system.

4.3.1 User Requirements

All the system provides help to assist the user. The product will include user manual which include product overview, complete configuration of the used software, technical details, backup procedure and contact information which will include mobile number. This Project will also available in Gujarati also
thus why its help is also available in Gujarati also

4.3.2 System Requirements System requirement are more detailed specification of system functions, services and
constraints than user requirements. System required SMS gateway. All other hardware and software requirement as per given above section.

4.4 Feasibility Study

Feasibility study is carried out whenever there is a complex problem or opportunity, it is a fact a preliminary investigation which emphasizes the Lock undertaken to determine the possibility or probability of either improving the existing system or developing a completely new system. It helps to obtain an overview of the problem and to get rough assessment of whether feasible solutions exist. There is essential to avoid committing large resources to a project and the repent on it later. The feasibility study is needed to Answer the question whether a new system is to be installed or not? Determine the potential of the existing system. Improve the existing system. Know what should be embedded in the new system. Define the problems and objectives involved in a projects Avoid costly repairs at a later larger stage when the system is implemented. Avoid the hardware approach.

4.4.1 OPERATIONAL FEASIBILITY: PERFORMANCE: Does the system provide adequate throughput and response time? Yes, our system is quite capable of good utilization. It will also have good response time as if any user wants to save , update , delete and view records will obtain it faster.

INFORMATION: Does the system provide end-users and managers with timely, pertinent, accurate and usefully formatted information? Yes, the users will generate automatic rate by only select particular commodity from list box . They can also get information about all items and their prices.

EFFICIENCY: Does the system make maximum use of available resources including People, time, and flow of forms? Yes, the system will make the maximum utilization of the available resources. Any forms of data if provided will be efficiently worked out. Our system will be quick enough to carry out his task in time. SERVICES: Does the system provide desirable and reliable service to those who Need it? Yes, I have provided the services according to the categories of users. So, the users of one category if require some service which is not applicable to them then our system will not be desirable to them. But security being considered it was a must. How do the end-users and managers feel about the problem? My system will be enough satisfactory to the end users as well as managers such that they will not be able to face any kind of problem and any kind of complexity in the system.

Can The System Be Integrated With Other System Which Already In Place? Yes , the system is integrated with other system which are already in a place. 4.4.2 ECONOMIC FEASIBILITY: The cost required for the creation of our system will be less compared to the benefits provided by our system. Our system will provide both the types of benefits. Here requirements for the system are very low so it is very economical to use this system. 4.4.3 SCHEDULE FEASIBILITY: I will try my best to complete the system within the time limits provided to me. But according to my view, quality rather than speed is very important

4.5 Requirements Validation (Is Concerned With Showing That The Requirements Actually Define The System Which The Customer Wants)
Requirement validation is a process in which it is checked that weather the gathered requirements represent the same system that customer really wants. System provides the functionality actually user wants that describe below: First of all main functionality user wants is easy interface with the system. Another one is user get always up to date market information for to take the better decision for their product. And also know about the current status of the different market product prices for their comparison of the prices of crops. Also user required the future rate of the commodity from that they take the benefit, so benefit and awareness toward the system these both are the system as well as user main requirement when interfacing with the any system. Also user wants that this system use is freely available or minor charges only. Also require the msg. facility to know the commodity price without opening the system thats user wants the mobility from the system. Also user wants to know the new technology of farming that decrease the hard work and increase production.

Requirement of farmer is also provide the other related information or related link for details of the new technology and get the other information they wants.

Requirement checking can be done in following manner: 1. VALIDITY: Does the system provide the functions which best support the customers need? 2. CONSISTENCY: Are there any requirements conflicts? 3. COMPLETENESS: Are all functions required by the customer included? 4. RELISM: Can the requirements be implemented according to budget and technology? 5. VERIFIABILITY: Can the requirements be checked?

Requirements Validation Techniques: 1. Requirements Reviews: Requirements review is a systematic manual analysis of the requirements. The requirement review should be taken only after formulation of requirement definition. And both the customer and contractor staff should be involved in review. 2. Prototyping: The requirements can be checked using executable model of system. 3. Test-Case Generation: In this technique, the various tests are developed for requirements. The requirement check can be carried out withVerifiability: Is the requirement realistically testable? Comprehensibility: Is the requirement properly understood? Traceability: Is the origin of the requirements clearly stated?

4.6 Activity/Process In New System(Use Event Table) 4.7 Features of New System: Do not need to registration
APEM project is provide the user who wants to only check the price related information and compare with other market price.

SMS Facility
The user who wants to see price daily they can registered at one time only and received massage every day on his demand.

In Localize Language
The project is also developed in Gujarati also so locally farmer may access information in Gujarati also.

State Wide Information.

This project will provide information about all market in Gujarat and all price rate also.

Commodity wise and Marketwise information.

APEM is providing to the weekly information so that user can compare the price about previous days also.

Other facility
Other facility such as whether information any fertilization related information.

For OO Approach:
Object-oriented programming (OOP) is a programming paradigm using objects data structures consisting of data fields and methods together with their interactions to design applications and computer programs. Programming techniques may include features such as data abstraction, encapsulation, messaging, modularity, polymorphism, and inheritance. Simple, non-OOP programs may be one long list of statements (or commands). More complex programs will often group smaller sections of these statements

into functions or subroutines each of which might perform a particular task. With designs of this sort, it is common for some of the programs data to be global, i.e. accessible from any part of the program.

4.8 Class Diagram for APEM:

Market
-Marketing_id : string -Market_name : char -City : char +setvalue() +getvalue() +updatevalue()
* *

Login
-Login_id : string -Password : string +getvalue() +setvalu()

Contact_info -Market_id : string -Admin_id : string -Password : string -Phone_no : int +setvalue() +getvalue()

Commodity -Market_id : string -Commodity_name : char -Date : Date -Minimum_price : int -Maximumum_price : int -Arrivals : int -variety : int +commodity_details() +update_commodity() +setcommodity() +viewcommodity()

Fig 4

4.9 System Activity

For user

Registered user

Open User

Chech Price Alert Fill Resistration

Compare price

Successful regisrstion message

Prompt to re enter

Select service

Select market

Select Comodity

Select Variety

Fig :5

For Admin

Login

Check for availability

Set market info

View Rates

Update Rate

Send failure notice

join

Logout

Finish

4.10

Sequence Diagram

For user:

User/Farmer

System

price list

Select Language

Request for commodity rate

Check For Updated rate

Send Acknowledgment

Display Price rate

Request for sms service

Send service Command

Returns results

Receved message

Fig 7

For Admin:

For Admin

User/Admin
Login

System

Db

Check availability
Execute query

Give responce

Login Successfully

Request to update rate and market info

Update info
Exicute command

Give responce

Update Successcfully

4.11 Level 0:

Data Flow Diagram:

User

Request for price

APEM System

Price Detail

Ariculture Market

Price Details

Level 1:
List of price rate Rate User Request for price View Price rate Commodity rate List of Commodity

Price Details

Market info

List of market

Agriculture market Request as needed Search as per need

Price Details as needed

Level 2:

User

Request for price

Get price rate

Rate

Price rate

Price Details

Market name List of Market

Find market

Market

Commodity rate And Details

Find market and Commodity

Commodity info Variety info

List of Commodity

List of variety

Agriculture Matrket

Fig 9

4.12

Use case Diagram

Use Case diagram

Language Selection view commodity price list Admin login

* *

View Report

User Related Link

Login * * * {<<include>>} * Validate user * Register update commodity price {} Admin * *

Registed user

* AddComment

Conform registation

Update Market information

Data base Management

Fig 10

For OO Approach
5.1

System Application Design

5.2 Table Design

5.2.1 Table and Relationship: 1. Login Table for admin

Field Name
Username
User_id Password Market_id

Data Type
Text
String String String Table :3

Description
Not Null Not Null Not Null

2. Market Table

Field Name
Market_id Market name City

Data Type
String Text Text Table: 4

Description
Not Null

3. Commodity Table:
Field Name
Commodity name Commodity_id Market_id Date Minimum price Maximum price Arrivals

Data Type
Text String String Date Number Number Number

Description
Not Null Not Null

Variety

Number Table:5

4. Registration Table
Field Name
Name Address Mobile no Profession Text Text Number Text

Data Type

Description

Not Null

Table: 6 5.2.2 Logical Description of Data: Here in this phase, the description about the every table and its attributes. Table: 6 contain the Registration table for the user who want to be SMS functionality. That include name, address of user that is not mandatory, Mobile number. Table: 5 contains the commodity list which include commodity id, commodity name, market name, as a primary key, minimum price, maximum price and date. Table:4 contains market information which include market id, market name, and city fields. Table:3 contains admin login information who wants to update commodity rate which include username user id password

6.0 IMPLEMENTATION PLANNING:

6.1 Implementation Environment (Single vs. Multiuser, GUI vs. Non GUI)
"Single user" defined for a product designed for cheapness and short-term convenience rather than medium to long-term durability.

Multi-user is a term that defines an operating system or application software that

allows concurrent access by multiple users of a computer. Implementation environment in that mainly multi users.

6.2 Program/Modules Specification: 6.3 Security Features: We have basically two users with different accessibility rights.
There will be proper security regarding to the accessing of application. The external security of updating daily rate can be provided by given the login authentication. The whole software is secure from the outside accessing. The mobile number from resisted user should be authenticated.

6.4 Coding Standards An good software development approach suggests to adhere to some well-defined
standards or rules for coding. These rules are called coding standards.

Following are some commonly used naming conventions in the coding. Package name and variable names should be in lower case. Variable names must not being with numbers.

 The type name should be noun and it should start with capital letter. Constants must be in upper case.(Example PI,SIZE) Method name must be given in lower case. The variable with large scope must be given in lower case. The variables with large scope must have long name. for example count_total, sum
variables with short scope must have short name. For example I,j.

The prefix is must be used for Boolean type of variables. For example isEmpty or
isFull.

1. Classes:
Class name should be and , again, should be meaningful. Avoid verbs. Class Search { }

2. Methods:
Always use a verb-noun pair, unless the method operates on its containing public void GetPath().

3. Methods with return values: The name should reflect the return value. Public init GetImage Width (Bitmap
image ).

4. Variables: Do not abbreviate variable names. Variable name should be descriptive and
meaningful. int quantity Count=0; int index=0; string temp=; 5. Pascal Casing: Public class search {

Public void BookName(); }

6. Commenting/Layout: Comments are non executable part of the code. But it is very important because it
enhances the readability of the code. The purpose of the code is to explain the logic of the program.

Single line comments must be given by// For the names of the variables comments must be given. A black of comment must be enclosed within /* and +/. 7. Statements: There are guidances about the declaration and executable statements. Declare variable never be declared public. Make use of only loop control within the for loop. Avoid make use of break and continue statements in the loop. Avoid complex conditional expressions. Make use of temporary variables instead. Avoid the use of dowhile statement.

CHAPTER 6: TESTING
Testing is process of executing a program with the intent of finding an error.

This is very useful and important tool after the software is design. It tests the software is design. It tests the software for quality, result and accuracy. There are many strategies that can be used to test software.

At one extreme team could wait until the system is fully constructed and the then conduct tests on the overall system in hopes of finding errors. At the other extreme, a software engineer could conduct tests on a daily basis, whenever any part of the system is constructed.

The testing strategy that is chosen by our software team falls in between the individual program units, moving to tests designed to facilitate the integration of the units and culminating with test that exercise the constructed system.

Fig 11

Testing Objectives:

Testing is a process of executing a program with the intent of finding an error.

A good test case is one that has a high probability of finding as yet undiscovered error A successful test is one that uncovers yet undiscovered error.

Testing Techniques:
White Box Testing: White box testing is a test case design method that uses the control structure of the procedural design to derive cases. It derives test cases that guarantee that all independent paths within a module have been exercised at least once.

Black Box Testing: Black box testing methods focus on the functional requirements of the project. That is this testing enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a program.

Unit Testing: Here we tested each and every module of the system. Integration Testing: It is a systematic technique for constructing the program structure while conducting test to uncover errors with interfacing. The objective is to take the tested module and build the program structure that has been dictated by design. After testing all individuals modules all modules were integrated and tested.

LIMITATION AND FUTURE ENHANCEMENT:

Limitation:
Connectivity in rural area. Data updating in real time is not easy. Training to the stakeholders.

Future Enhancement:
The system will display the information in English as well as Gujarati .In later version it will implemented to used Hindi also. In later version also proved particular markets all details.

CONCLUSION AND DISCUSSION:

Self Analysis of Project Viabilities Every project work, does not matter software project or any other project, could not
be the result of sole effort; even though, developer team consists two members.

We think success of any project doesnt depend only on better software

development skills.

Only user interaction at development phase can give you idea to fulfill their
requirements.

Problem Encountered and Possible Solutions:

Currently, Gujarat has a system that focused on providing information about different event, news and commodity profile for agriculture goods that handle by Gujarat State Agriculture Marketing Board and Designed by: Silvertouch Technology Ltd. That system contain following features. Price alert facility for agriculture goods, but that can link on agmarknet.nic.in. Proved information about current Latest news and events and provide commodity profiles And Related Act e.g. whether information.

Summary Of Project Work: We have complete our project work based on using software engineering and system
analysis and design approach. Work that we have done with preplanning and scheduling related with time constraints and result oriented progress in project development.

 Our project start in first week of june and will complete this project at starting of
September.

Initially , there were some problem regarding Some phases but we have planned to
resolve those problems.

We have devided our work in different phases and solve problems and difficulties