You are on page 1of 35

Review Report on e-Farming

ABSTRACT

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 of computer 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.

Users of the system:


Director Admin Users Farmers, wholesaler who wants to buy product directly from Farmers

Computer professionals any other users

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 his products. 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.

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 transactions which 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.

The data should be stored inside database such that when queried with different parameters the query should retrieve the results quickly , for example 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.

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

Presentation Layer Access Layer

Business Layer

Data

UserRegistrationUI

UserRegistrationBL
LoginDB

LoginUI

LoginBL

ViewStockUI

ViewStockBL

ViewUsersUI

ViewUsersBL

DBC

SearchUI

SearchBL

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

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.

Notation:

An entity may be a physical object 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.

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.

UML Diagrams:
Class Diagram Use case Diagram Sequence Diagram Activity 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 objectoriented code, for those "code-then-design" maintenance projects.

login usename password registration() login()

home page

farmer username : string password : varchar viewstock() sellproduct()

admin username password viewprofilelog()

computer proffessionals pid pname advicetofarmers()

logout

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.

Use case Diagram for Admin:


login view profile update profile <<extend>>

<<include>> authenticate users verify user id & password

view request

<<extend>>

reply request

admin

view stock

view users

delete users

search users search

search products

logout

Use case Diagram for Farmer:


user nam e < in d > < clu e > < in lu e> < c d > register < in d > < clu e> address passw ord

login

change pass w ord < in d > < clu e> < in d > < clu e > enter comm odity details

nam e

variety

< in lu e > < c d> price

F armer

com odity id m < in d > < clu e> view stock < in lu e > < c d> < in lu e > < c d> < in d > < clu e > com moditynam e

com odity variety m

available stock

log out

sell product

Use case Diagram for wholesaler:


re gis t e r

lo gin

cha nge pa s s wor d

<<include>> whole s a le r pur cha s e co m m odit y <<include>> <<include>> lo go ut

m e nt io n co m m o dit y na m e

com m o dit y v a r ie t y

pr ice

Use case Diagram for supplier:


r e g is t e r

lo g in

change password s e ll s e e d s

s e ll c r o p in f r a s t r u c t u r e e q u ip m e n t s u p p lie r

s e ll c r o p e q u ip m e n t s

f a r m e q u ip m e n t s

lo g o u t

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.

Sequence Diagram for Admin:


am di n lg oi n hm oe dt bs aa a e 1:u e n m( s r a e) 2:p s wr ( a s od) 3:l g ( oi ) n

4: v ld te) ai a (

5:s c e s l l g ( u c s fu o i ) n

6:u s c e s l l g ( n u c s fu o i ) n

7:ve po l ( i w r fie)

8:ve s o k) i w t c(

9:ve u es ) i w s r(

1 : d l t u es ) 0 eee s r (

1 : uesd l te ( 1 s r ee d)

1 : s ac u es r d c ( 2 e r h s r ,po u ts )

1 : s o s ac r s l ) 3 h w e r h eu t(

1 : l g u( 4 oot)

1 :r d e t t l g ( 5 e i c oo i ) r n

Sequence Diagram for Farmer:


fa mr r e 1: u e n m( s r a e) lo in g hm oe d tab s a ae 2: p s w r ( a s od) 3: l g ( o in)

4: v l a ( aid te )

5: s c e s l l gn) u c s fu o i (

6: u s c e s l lo i ( n u c s fu gn)

7: e te c m o i d ta s ) n r o mdty e il (

8: d talse te e ( e i n r d)

9: ve s c ( i w to k)

1 : s l po u ts ) 0 el r d c (

1 : v lu su a a d) 1 a e p d te (

1 : lo o t( 2 gu )

1 : r d e tstolo i ( 3 e ir c gn)

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()

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.

Activity Diagram For User Registration:

Activity Diagram:
e te u e n m &p s w rd n r s r a e as o

ve a no u e n m &p s w rd rific tio f s r a e a s o

in a u e n m v lid s r a e

v lid a

hmpg o e ae

am d in

fa e rmr

w o s le h le a r

e u mn s p lie q ip e t u p r

vie p file w ro

e te p d c d ta n r ro u t e ils s ll fa e u mn e rm q ip e ts

a th n a u e u e tic te s rs

v ws c ie to k

p rc a ec m o ity u h s o md

vie s c w to k

s ll p d c e ro u ts

End

You might also like