Presentation on project

E-BUSINESSREPORT
 INTRODUCTION

• Ebusinessreports.co.in is
designed keeping in mind
different levels of operations, of
a marketing chain in an
organization. The kind of
operational differences, work
responsibility varies from level
to level.
ARCHIETECTURAL
DESIGN
TOP LEVEL MANAGEMENT

MIDDLE LEVEL MANAGEMENT

LOWER LEVEL MANAGEMENT

 TOP LEVEL
MANGEMENT
This is the first phase of any
organization where the decision
making is done i.e.. Here the top
level decides the company
policies ,rules and regulations
and the strategies which
consists of Directors, CEO .
 MIDDLE LEVEL
MANAGEMENT
This is the second level of any
organization which consists of
managers which implements
the decisions of upper level
management i.e. they are
responsible for the target to be
completed .
 LOWER LEVEL
MANAGEMENT
This consists of the workers
,supervisors which are
responsible for achieving the
target under the guidance of
middle level management.
DIFFERENT MODULES
OF PROJECT
 LEVEL I

• At Level I ---- Supposedly,

CEO will be deciding on
Pricing of Products and also
allocate Sales Targets to
various Regions on Specific
Product categories.
 LEVEL II
• At Level II --- Regional Managers are
able to fetch these allocated targets
for a specific product and time period.
They further allocate these targets to
Field Engineers. The specific data
about pricing i.e. Sales Tax in different
states is input by concerned Regional
Managers and hence the final price of
all products is being decided
 LEVEL III
• At Level III --- Sales Executive fetch
the prices of products and billing to
Dealer Partners is done accordingly.
The allocated target to a field
Engineer is further allocated to
concerned Dealers in various Cities.
As Sales Executive are having most
information about ever changing
market scenario, the feedback is
being taken on performance of
various Competitors
 OBJECTIVE
• The objective of this software is to completely automate
the process of:
• Allocating Targets to lower hierarchical level Team
Members.
• Fetching Targets allocated by higher hierarchical level
Team Members.
• Allocating Pricing of Products.
• Fetching Product Pricing and further billing Products to
Dealers.
• Graphical Analysis of companies performance at various
levels on basis of a specific Region, Product, State either
Inter-Region or Intra-region.
• Graphical Analysis of companies performance, compared
to performance of competitors on basis of a specific
Region, Product, State either Inter-Region or Intra-region.
• It also tracks down region wise contribution achieved.
• Maintaining feedback about dynamic Market Scenario and
on basis of that various POLICY DECISIONS can be taken
by different Departments in the Organization.
• This application manages all the data giving at most
priority to DATA SECURITY at each Hierarchical Level.
 PROJECT
CATEGORY
 INPUT

• INPUT: The input being given to

the application varies at various
levels. The input is given inform of
various values i.e. Employee code,
region, city,quantity, target value,
product code ,product
price,month,year state, Dealer code
etc. Based on these input values
database is updated each time.
 OUTPUT
The output that is displayed is based
on the input values; it is displayed in
tabular form. All the comparative data
about comparison on basis of Region,
Product, State (Various Combinations)
about Company’s Performance are
being displayed in Graphical Form.
Also comparative performance,
Company’s Vs Competitors on basis of
Region, Product, State (Various
Combinations) are being displayed in
Graphical Form.
PROPOSED SYSTEM
 BENIFITS

• Fully works as a online

• Reducing the time
• Don’t Thinking
• Centralized maintain all
information.
• Easy to Searching the information.
• Easy to managing whole response,
Mail
Modules & Process
Logic
 ALLOCATING SALES
TARGET
• Input: Quantity, Target Value,
Year, Month, City, state,
Employee code, Region, Dealer
code
• Output: Further allocated targets
(Qty, value)
 ALLOCATING PRICING OF
PRODUCTS
• Input: Transfer Price,
Sales Margin, Cash
Discount, Sales Tax,
Dealer price, MRP
• Output: Billing products
to Dealers
 Allocating Dealer
Schemes:
• Input: Dealer name, Dealer
code, Quantity, Additional
Sales Margin, Year, Month,
City, State.
• Output: Passing additional
margin if qualifies in the
scheme.
 ORDER FORM
• Input: Dealer name, Dealer
code, City, State, Quantity,
Value, Payment Terms, Region,
Product code
• Phone no, Fax, Contact Person
• Output: Courier Company
intimated for delivery
 Company Performance
Tracking
• Input: Region, Product
code, State
• Output: Graphical
Comparisons
MY MODULE
 RESPONSIBILTIES OF
REGIONAL MANAGER
1. View targets allotted by CEO
to him.
2. Allocates the sales targets to
various region’s of Sales
Executives
on specific product categories.
REGIONAL MANAGER
LOGIN
When the CEO login’s .it has are
four options
1. Set target
2. View pricing
3. Performances
4. Competitor’s data.
 SALES TARGET

Sales target :-
This operation has been
provided for selling the target,
modifying the previous target
and also views the set targets
This target allotted to Sales
Executive .
 VIEW PRICING

View Pricing :-
This option is provide the view
of pricing which is set by the
CEO for the Regional Manager.
PERFORMANCES

Performances:-
This option gives the facility to
Regional Manager to check the
performances of the sub ordinate.
i.e. A particular Regional Manager
is able to view the performance
graphically or statically
COMPETETIOR’S DATA

Competitor’s data:-
In this option we have provided
to view to competitor’s detail.
Who is currently competitor of
our product’s and what is the
sale of that product compare to
our product is described in that
portion.
DFD’S OF REGIONAL
MANAGER
 REGIONAL is
CEO
MANAGER lys
a
An
Targets & e
tiv
price ra s &
pa et
m rg
Comp Co Ta ice
ar ative
Analys pr
is

eBusi Employee
eBusi
ness ADMINISTRATOR
ness Details
Repor
Repor
ts In
ts pu
tV
ce

al
or &

ue
an
rf sis

s
m

fo
P e ly

M rO
k
n na

at rd
ac

er
O eA

er
db

ia Fo
l
of m
w

ee

De rm
w he

liv
tF
ie c

e
V S

re
ke

d
ar
M

EMPLOYEE
DEALER
 I Level DFD for Any User
System Access

User User ID & Validation

Password
Process

Access Denied
 I Level DFD for a REGIONAL MANAGER

Set Targets and

Pricing Displayed Targeting
&
Pricing

Values to set
Targets and Pricing

REGIONAL
MANAGER
Values to review
Performance

Comparative
Comparisons Displayed Analysis
Graphically
 II Level DFD for a RM - Targets
REGIONAL 1.1.1
MANAGER
Setting of R
Year
ets Targets ,Mo M
Request arg nth,P
for Sales Set t Val
code
,R
t to ue egion
Target
eques s ,Qty
& Tota
option R l

Value
s Balance -
1.1 1.1.2
T
Request to Modify Targets Target Year,Month,Pcode,Region,Qty & Total
Sales Target Modifier A

Req G
ues
t to v
iew
Set
R
Set Tar
Tar get
E
g ets
Dis
p
s
1.1.3 ty &
T otal
la y n ,Q
ed
Regio T
d e ,
View Set t h, Pco
r, Mon
Targets Y ea
 Level DFD for a RM-PRICING
REGIONAL
MANAGER
Request for
P
Pricing
R
Request I
for view Response of request C
price PRODUCT
I
PRODUCT PRICE
N
PRICING VIEW
G
 II Level DFD for REGIONAL MANAGER
Company Performance

Request to
Analyse
Company
Performance
REGIONAL
Performance Comparative
MANAGER Analysis
le s Graphs Displayed

Ac
sa

tua
ed
lay

Sal
sp

le
Di

s
e d i ve
et at
rg ar
Ta omp
C

RM_Target Form
 ASPECTS OF
IMPLEMENTATION
DATA ACCESS OBJECTS
Data Access Objects (DAOs) :
• can be used in a large percentage of applications -
anywhere data storage is required.
• hide all details of data storage from the rest of the
application.
• act as an intermediary between your application
and the database. They move data back and forth
between Java objects and database records.
• allow ripple effects from possible changes to the
persistence mechanism to be confined to a specific
area.
 ADVANTAGES OF DAO
• Enables Transparency

• Enables Easier Migration

• Not Useful for Container-Managed

Persistence

• Adds Extra Layer

• Needs Class Hierarchy Design

 APPLICATION
ARCHIETECTURE

N-TIER
ARCHITECTURE
 WHAT IS N-TIER
ARCHIETECTURE
Firstly, what is n-Tier architecture?
N-Tier architecture refers to the
architecture of an application that
has at least 3 "logical" layers -- or
parts -- that are separate. Each layer
interacts with only the layer directly
below, and has specific function that
it is responsible for.
 Presentation Tier

Caching Service Tier

Application Server Tier

Integration Service Tier

Data Tier (Back-end Services)

 WHY N-TIER
ARCHIETECTURE
Because each layer can be located on
physically different servers with only
minor code changes, hence they
scale out and handle more server
load. Also, what each layer does
internally is completely hidden to
other layers and this makes it
possible to change or update one
layer without recompiling or
modifying other layers.
HARDWARE AND
SOFTWARE
 HARDWARE

• Processor Pentium 4th

• RAM 128MB
• Hard Disk 20GB/40GB.
 SOFTWARE

• Operating System Windows

98/2000/XP,UNIX
• Front End Html/JSP.
• Back End Oracle10g.
• Design Patterns MVC.
LIMITATIONS
 LIMITATIONS

• Presently the software is

handling only three hierarchical
levels.
• Only able to handle restricted
Product range.
• No direct access to Customers
• Dealers should be able to
access more information
FUTURE SCOPE
 FUTURE SCOPE

• It can be further enhanced to handle

much wider Product range.
• It can be further enhanced to take
online direct Customer Orders.
• Courier Service providers should
directly fetch pending delivery
details along with CVC form and
dispatch the material.