Review Report on E-Farming

8/2/2019 Review Report on E-Farming

1/35

Review ReportReview Report

onon

e-Farminge-Farming


2/35

ABSTRACTABSTRACT


3/35

Objective/Vision:Objective/Vision:

The main objective of this project is build a website which will help farmers from

Indian villages too sell their products to different cities. Here if suppose some

village farmers want to use this facility and want to learn how is it possible and

how they can use e-farming to sell their products, If they have knowledge ofcomputer then they can directly register in the site and sell their product otherwise

they can contact company's computer professional who will schedule classes to

teach them basics of computers and internet like how they can open this site and

register with it and sell their products online etc. On the other side, wholesaler

from town can also register and buy products as per their needs.


4/35

Users of the system:Users of the system:

Director Admin

Users Farmers, wholesaler who wants to buy productdirectly from Farmers

Computer professionals

any other users


5/35

Functional Requirements:Functional Requirements: People can register in the site for some basic e learning like if some user

wants to learn how to operate computer, they can go and learn it from the

site. (It will be just HTML page with all basic courses on how to operate

computer).

While registering there should be option of selecting whether one who is

registering is farmer or wholesaler

If user select as farmer then there should be option to select

whether he wants to take lesson or if he is already familiar with

online buying and selling then he can directly go to sell hisproducts.

If user select as wholesaler then he needs to fill all details as per

requirement place, shop address, which product he wants to

buy, quantity etc.


6/35

Site should also be available in Hindi and local languages as per States.

Admin should be able to see all record from any users.

The records shown for selling should be available in a format of Quantity

name , Quantity available, price.

The database should be robust enough to handle all the online transactionswhich will be happening parallely.

There should be facility of scheduling classes for farmers who enrolled for

basic courses.

Automatic transfer of mails to company's computer professional(teachers) if

some user(farmer) enrolled for basic course.


7/35

The data should be stored inside database such that when queried with

different parameters the query should retrieve the results quickly , forexample there should be in build query for farmers to view what all

products they are selling and how many have been sold + the quantity left.

Another query must be there for wholesaler to query for products and also

drill down the results in the result page to view how much quantity of that

product is available with single farmer in case they are interested in single

lot.


8/35

Architecture Diagram:Architecture Diagram:

Architecture diagram is an architectural model (in software) is a rich and

rigorous diagram, created using available standards, in which the primary

concern is to illustrate a specific set of tradeoffs inherent in the structure and

design of a system or ecosystem. Software architects use architectural

models to communicate with others and seek peer feedback.

An architectural model is an expression of a viewpoint in software

architecture. There are many definitions of software architecture


9/35

UserRegistrationUI

LoginUI

ViewStockUI

UserRegistrationBL

LoginBL

ViewStockBL

ViewUsersUI

ViewUsersBL

SearchUI SearchBL

LoginDB

DBC

Presentation Layer Business Layer DataAccess Layer


10/35

Schema Diagram:Schema Diagram:

The word schema comes from the Greek word

(skhma), which means shape, or more generally, plan.

Schema may refer to:

Model (abstract)

Diagram

Schematic, a diagram that represents the elements of a system

using abstract, graphic symbols


11/35

ER Diagram:ER Diagram:

An entity-relationship model (ER model for short) is an

abstract and conceptual representation of data.

Entity-relationship modeling is a database modeling method,

used to produce a type of conceptual schema or semantic data

model of a system, often a relational database, and its

requirements in a top-down fashion.

Diagrams created by this process are called entity-relationship

diagrams or ER diagrams.


12/35

Notation:Notation: An entity may be a physicalobject such as a house or a car, an

event such as a house sale or a car

service, or a concept such as a

customer transaction or order.

A relationship captures how

entities are related to one another.

Relationships can be thought of as

verbs, linking two or more nouns.

Attributes are the properties

which describes an entity or a

relation ship.


13/35


14/35

UML Diagrams:UML Diagrams:

Class Diagram

Use case Diagram

Sequence Diagram

Activity Diagram


15/35

Class Diagram:Class Diagram:

Class diagrams identify the class structure of a system, including the

properties and methods of each class. Also depicted are the various

relationships that can exist between classes, such as an inheritance

relationship. The Class diagram is one of the most widely used

diagrams from the UML specification. Part of the popularity of Class

diagrams stems from the fact that many CASE tools, such as Rational XDE,

will auto-generate code in a variety of languages, including Java, C++, and

C#, from these models. These tools can synchronize models and code,

reducing your workload, and can also generate Class diagrams from object-

oriented code, for those "code-then-design" maintenance projects.


16/35


17/35


18/35

login

usename

password

registration()

login()

home page

farmer

username : string

password : varchar

viewstock()

sellproduct()

admin

username

password

viewprofilelog()

computer proffessionals

pid

pname

advicetofarmers()

logout


19/35

Use case Diagram:Use case Diagram:

Use Case diagrams identify the functionality provided by the system

(use cases), the users who interact with the system (actors), and the

association between the users and the functionality. Use Cases are

used in the Analysis phase of software development to articulate the

high-level requirements of the system

The primary goals of Use Case Diagrams include:

Providing a high-level view of what the system does

Identifying the users ("actors") of the system

Determining areas needing human-computer interfaces.

Use Cases extend beyond pictorial diagrams. In fact, text-based

use case descriptions are often used to supplement diagrams, and

explore use case functionality in more detail.


20/35


21/35

Use case Diagram for Admin:Use case Diagram for Admin:

admin

login

view profile

authenticate users

view request

view stock

view users

delete users

update profile

reply request

searchsearch users

search products

logout

verify user id & password


22/35

Use case Diagram for FarmerUse case Diagram for Farmer::

Farmer

register

user name

password

address

login

enter commodity details

name

variety

price

view stock

commodity id

commodityname

commodity variety

available stock

sell productog out

change pass word


23/35

Use case Diagram for wholesaler:Use case Diagram for wholesaler:

w h o l e s a l e r

r e g i s t e r

l og in

p u r ch a s e c o m m o d it y

m e n t io n co m m o d it y n a m e

c o m m o d it y v a r i e t y

p r i c e

l o g ou t

c h a n g e p a s s w o r d


24/35

Use case Diagram for supplier:Use case Diagram for supplier:

e q u ip m e n t s u p p lie r

r e g i s t e r

l o g i n

c h a n g e p a s s w o r d

s e l l c r o p in f r a s t r u c t u r e s e l l c r o p e q u i p m e n t s

s e l l s e e d s

fa r m e q u ip m e n t s

l o g o u t


25/35

Sequence Diagram:Sequence Diagram:

Sequence diagrams document the interactions between

classes to achieve a result, such as a use case. Because

UML is designed for object-oriented programming, these

communications between classes are known as messages.

The Sequence diagram lists objects horizontally, and time

vertically, and models these messages over time.


26/35


27/35

Sequence Diagram for Admin:Sequence Diagram for Admin:admin login home database

1: user name()

2: password()

3: login()

4: validate()

5: successful login()

6: unsuccessful login()

7: viewprofile()

8: viewstock()

9: viewusers()

10: delete users()

11: users deleted()

12: searchusers,products()

13: showsearchresult()

14: logout()

15: redirect tologin()


28/35

Sequence Diagram for Farmer:Sequence Diagram for Farmer:farmer login home data base

1: user name()

2: password()

3: login()

4: validate()

5 : successful login()

6: unsuccessful login()

7: enter commodity details()

8: details entered()

9 : viewstock()

10 : sell products()

11: values upadated()

12 : logout()

13 : redirects tologin()


29/35

Sequence Diagram for Wholesaler:Sequence Diagram for Wholesaler:

whole saler login home database

1 : user name()

2 : pass word()

3 : login()

4 : purchase commodities()

5 : update commmodity list()

6 : logout()

7 : redirect to login()


30/35

Activity diagram:Activity diagram:

Activity diagrams are used to document workflows in a

system, from the business level down to the operational level.

When looking at an Activity diagram, you'll notice elements

from State diagrams. In fact, the Activity diagram is a variation

of the state diagram where the "states" represent operations,

and the transitions represent the activities that happen when the

operation is complete. The general purpose of Activity

diagrams is to focus on flows driven by internal processing vs.

external events.


31/35


32/35

Activity Diagram For Userct v ty agram For User


33/35

Activity Diagram For Userct v ty agram For UserRegistration:Registration:

i i iA ti it Di


34/35

Activity Diagram:Activity Diagram:

enter user name &password

verification of user name &password invalid user name

home page

valid

admin farmer whole saler equipment supplier

viewprofile

authenticate users

viewstock

enter product details

viewstock

sell products

purchase commodity

sell farmequipments


35/35

EndEnd

Documents

Review Report on E-Farming