MCSP-060 [ MCA New Syllabus Synopsis ]

Title of the Project :

Online Enterprise Marketing and Analysis

System in J2EE

INTRODUCTION
This

project

is

web-based

enterprise

software,

which

provides

management of marketing data. This software is being developed for companies

which have work in marketing or dealer. The sample data collected to design and
test in Net Co Ltd. which is a marketing company. The company has branches at
almost all state-capitals in India. The company wants to manage marketing
information like sell, wear out, performance by an easy, fast and cheaper way.
The software is being designed keeping in mind the problems which the
observers have find out in the company. The software will work on-line. This is
made to provide accessibility to everywhere. It works centrally and data entry is
done from all the branch offices. This software takes marketing information from
all branches and keep it at one central location. At the central location (The Head
Office) the data is analyzed on the basis of various parameters like total sell
(branch wise/overall), total sell return (branch wise/area wise/overall) etc.

The software project is very big and includes almost all aspects of
Enterprise application. The project mentioned is based on one unit of this. This
unit is concerned with getting data from branches and maintenance of data at
the central location. In this unit web-based forms are designed which facilitate
entry of data and there is facility to store it in the database which is centrally
installed at the head office. As the complete architecture is distributed and online so the maintenance and management of data is done on-line. To manage
data like update, delete, etc. is to be developed. The data which is collected
branch wise and area wise are stored at the central database. At this location the
data is collected and analyzed by passing various parameters. Here strong
authentication mechanism is used to ensure security of data. The software is
designed

in

such

scalable

manner

that

enhancements.

Page 1 of Synopsis

it

can

incorporate

further

OBJECTIVES
1. The web-site is to be accessed from anywhere anytime.
2. As the project is web-based so the software should be platform independent.
3. The data is very important asset for corporation so strong authentication
method is to be used to ensure security of information from malicious user.
4. As the valuable data is being transferred through internet so the security of
data is to be maintained at any cost.
5. Easy to be customized in future. As the client demand some other additional
feature. The complexity of customers company may be different or if mode
of business changes then the system has capability to make appropriate
modification to suite that change. Customization is key factor of designing
this software.
6. The web-site manipulates data in an accurate way.
7. Accuracy of all type of calculations are important and to be achieved at any
cost.
8. This should always be observed during the development of the software that
the user is not from technical background, so the software should be user
friendly and can be handled easily.
9. Storage of data should be easily accessible.
10. The data retrieval and other manipulation related task which is done at the
database level should be fast enough. The database should support multiple
users at a time.
11. The product should fulfill users requirement.

Page 2 of Synopsis

CATEGORY OF THE PROJECT

This

is

Web-Based

project.

It

uses

some

aspect

of

distributed

programming to implement scalable management software. Number of levels is

identified so far in this project are four. A brief description of these layers is given
below:-

I.

The Users Layer :

Tools And Languages Used JSP, HTML, DHTML, And Java Script
Editors -> Microsoft Front Page, Edit Plus, Microsoft Word.
There is a front end which is web-pages which are displayed before the
user and user directly interact with the software. Web pages are developed
by using various design tools like Flash, Photo Shop etc and documentation
languages like HTML and DHTML.

II.

The Presentation Layer :

Tools And Languages Used JSP, SERVLET

Editor -> Edit Plus
At this layer all the services related with presentations like format check,
mailing interface, parsing, deployment descriptor etc. this layer is
developed in java using servlet , JSP.

III. The Integration Level :

Tool/Technology Used JDBC 3.0, JDBC Type 4 Driver Is Used.
This

tier

is

dedicated

for

database

connectivity

and

connection

management with the database. This is tier is developed in java and the
components to be used JDBC 2.0.

IV. The Data Resources Level:

Tool/Technology Used Micro Soft SQL 2000
At the back end, there is a data base which maintains data. This is to be
developed in MS SQL. In this server tables are created and all primary key

Page 3 of Synopsis

 Foreign Key constraints are implemented. The data base follows all the
Integrity Constraints.

SOFTWARE REQUIREMENT
SPECIFICATION

Platform Used :

Microsoft Windows 2000 Advanced Server

Features Of Windows 2000 Advanced Server Which May

Contribute To This Project :
This is server edition and contains all the features of server.
Easy to use and configure different components of the system.
Provide good base to develop enterprise software.
Provide multi-user facilities to distribute and reintegrate different
components of the project easily.

Architecture implemented :

Java 2 SDK Enterprise Edition

1.3

Justification Behind The Recommendation Of J2EE :

Page 4 of Synopsis

 Enterprise Nature : The project is web-based and Enterprise applications

can provide services to end-users via the internet or private networks.
Diversity Of Information Needs :

In an enterprise, information is

created and consumed by various users in a number of different forms,

depending of specific needs. It is vary common to find that each business
activity may process the same information in a different form.

Complexity Of Business Processes : Processes involved in this project

need complex information capture, processing , and sharing. Very often,
we encounter complex logic to capture and process information. This leads
to complex technical and architectural requirements for building enterprise
applications.
Diversity Of Applications : Due to the complex nature of enterprise
business processes, it is common to find that an enterprise consists of a
large number of applications each built at various times to fulfill different
needs of various business processes. This commonly leads to the presence
of applications built using different architectures and technologies. One of
the challenging need of our project is to make such applications that can
talk to each other so that business processes can be implemented
seamlessly.

Technical Requirements :
Programming Productivity : The technology we adopt to develop this
web-site will have potential and appropriately integrated with other
relevant technologies. Thus, the ability to develop and then deploy
applications as effectively and as quickly as possible is important.
Reliability And Availability : E-com. transactions must be complete
and accurate.

Page 5 of Synopsis

 Security :

Security of information is a prime concern for e-commerce

type applications.
Scalability : The architecture adopted to develop this project must have
technical flexibility to adopt changes in the future. To scale effectively
requires not only the ability to handle a large increase in the number of
clients but also effective use of system resources.
Integration : All components must be properly integrated so that
performance of the system must be good.

Page 6 of Synopsis

REQUIREMENTS SPECIFICATION
Architecture Provided By J2EE :
Java 2 SDK, Enterprise Edition (J2EE SDK) is a platform for developing and
deploying the enterprise and multi-tier application in a distributed environment.
The J2EE SDK architecture consist of
J2EE server,
EJB Container and
Web Container

The following figure illustrates the J2EE Application components

The Front End Specifications :

To meet the requirements to build the web-application, the following
specifications are to be used:-

Language For Front End Programming :

Programming Language : Java

Script Language : Java Script

Documentation Language :
DHTML(Dynamic Hyper Text Mark-up Language)
HTML (Hyper Text Mark-up Language)

Page 7 of Synopsis

 XML
WebComponent: Java Servlet and Java Server Pages

The Middle Layer Specifications :

Language: Java
The Business Layer Component: In this layer business

logic is implemented. This project is at its evolving stage. Here, all

business logic is implemented in JSP files which are running on
servlet container. In near future it will be converted into EJB
(Enterprise Java Beans).
Managed objects: J2EE Applications are container centric both
these notations are very critical to building server-side applications.
By being managed J2EE component utilize the infrastructure
provided by J2EE Servers without the programmer being aware of it.
J2EE application are also declarative, a mechanism using which one
can modify and control the behavior of applications without
changing code.
Reusability: Segregating an application, business requirements
into component parts is one way to achieve reuse. Using object
orientation to encapsulate shared functionality is another. JAVA uses
both.

Java is an object oriented language and as provides

mechanism for reuse.

Modularity: Breaking our applications into different tiers and
individual tasks is easy in java.

The Back End Specifications :

Language: T-SQL
The Data Base Server: SQL Server2000.
Driver Used To Connect With Database: JDBC Type 1 Driver

Page 8 of Synopsis

PROJECT PLANNING & SCHEDULING

PERT CHART (Program Evaluation And Review
Technique)

START 8 Days

Problem
Problem

10 Days

Analysis
Analysis

Analysis
Analysis of
of
the
the existing
existing
System
System
Like
Like the
the
proposed
proposed
one
one

7 Days
Selection
&
Learning
the s/w to
be used

Days

10 Days
Under
-standin
g
Databas
e
13 Days
12 Days

Codin
g

Page
Designing
7 Days
Testing

3 Days
Implementatio
n

Page 9 of Synopsis

 GANTT CHART :
Activity
1

TASKS

Activity 2

Activity

Activity

Activity

Activity

Activity

Activity

Activity

Problem
Analysis
Analysis of
Existing
Systems

Selection &
Learning the S/W
To be used

Understanding
Database
Coding

Page Designing
Testing
Evaluation

Implementation

Analysis :
Analysis is done using two different strategies:

Structure Modeling and Object Oriented Modeling

Here structured approach is used.

Analysis Modeling
It uses a combination of text and the diagrammatic forms to depict
requirements for data, functions and behaviors in a way that is
relatively easy to understand, and more important, straightforward
to review for correctness, completeness and consistency.

Objective Of The Analysis we have done: To describe what the customer requires.
To establish a basis for the creation of a software design.

Page 10 of Synopsis

 To define a set of requirements that can be validated once the software

is built.
Dynamic Web Application : Dynamic Web Application represent a
new era in ASP based communications and business system development.
They integrate a wide range of web server and browser technology into
powerful applications like business that are easily deployed on Internet
and Intranet. A Dynamic web JSP application can use a relational database
of consolidated JSP files for reporting, time tracking and status updating,
as well as manages data and user access.
Dynamic Web Applications Share Several Common Features :
A server based application architectures in which most of the
application logic and functionality is stored on the server.

The integration of open Internet standards and protocols for

communication.
The use of the browser as a universal client and browser technologies
such as HTML and Java. This creates rich and flexible user interfaces that
can be delivered across multiple platforms.

WEB BROWSER

WEB SERVER
Internet or Intranet

Server

Client
Dynamic Web Application Processing :

When a user clicks on SEND button on a form or hypertext link on a

page, the users web browser sends an http request to the web server.

Page 11 of Synopsis

 The web server passes the data submitted by the user and process the
script used in the template. Based on the script, the Application Server
interacts with Database Servers, the file system and other applications
as necessary.
A web page is dynamically generated and return to the Web Server.
The Web Server returns the HTML page to the users browser.

Validation :
In the login module a user or a company has to enter the login id and
Password. But there is a check on the Password and login id. Password
must be at least five(5) character long and it must not exceed ten(10)
characters. The two user have never got the same login id and is at least
five(5) character long and it must not exceed twenty(20) character.
There is no any field in the user detail form empty. If any of them is
empty then the details of that particular user is not accepted.

Page 12 of Synopsis

ACCESS MODELS
A Java Server Pages file may be accessed in at least two different ways:
1. A Client Request Comes Directly Into A Java Server Page.

In this

scenario, suppose

components

that

perform

the

page

particular

accesses

reusable

well-defined

Java Bean

computations

like

accessing a database. The result of the Bean's computations, called result

sets are stored with in the Bean as properties. The page uses such Beans
to generate dynamic content and present it back to the client.
2. A Request Comes Through A Servlet.

Technical
Page compilation is the process of generating HTML pages from hybrid
HTML/Java source files using the PageCompileServlet. The
PageCompileServlet is loaded and inititialized like any other servlet.

Page 13 of Synopsis

The PageCompileServlet is a part of the package com.sun.server.http. The

Page Compilation Tutorial provides both an introduction to the process of page
compilation and a guide to using the PageCompileServlet.
The PageCompileServlet performs the following tasks the first time a hybrid
HTML/Java file is requested:
Translates the HTML/Java file into a Java source file
Compiles and instantiates the source file as a servlet
Runs the compiled file as a servlet

Page 14 of Synopsis

SOFTWARE REQUIREMENT
ANALYSIS
Requirement analysis provides the software designer with a representation of
information, function and behavior that can be translated to data, architectural
interface and component level designs.
Software requirements are studied under five headings

1.

Problem Recognition :

There is software which manages the data

they are working but the problem with existing software solution is that
they dont have any facility to take opinion of the common reader. This is a
new feature in the existing news website. This will work as a public notice
board where any one can write his/her opinion.

2.

Evaluation and Synthesis :

There are other document and

opinion gathering systems but they are not working as proper notice
board. They have their own limitations. The basic problem is that the
feature is not available as a component and cannot be integrated with the
existing web-site. So there is only option to develop their own. This
software may be used in much organization where there is a use of
common notice board. The appropriate market of the product is still to be
explored. This software is developed to keep it affordable for Indian
market and with least functionality which is required by Indian market.

3.

Modeling:

The model serves as a foundation for software design as

the basis for creation of specification for the software the model used to
develop the software is waterfall model as the development requirement of
the software suits this model.

4.

Specification: This phase is explained in detail.

Quality Function Deployment : This is a quality
management technique to translate the needs of customer

Page 15 of Synopsis

into technical requirements for the software. The detail QFD

is given under separate headings.
5.

Review :

In this phase all the specifications which is suggested by the

development team is reviewed. The revision is done under various

parameters like cost, quality, requirements, alternatives etc.

In this

project all the specifications is reviewed and found ok.

Requirement Of Web-Based ProgrammingWeb application can be those that cater to enduser via the Internet or
private networks, various business units within the enterprise via various kinds of
user interfaces. Interfaces.
Diversity of information needs
Complexity of business processes
Diversity of application
Maintenance of a huge amount of data
Multi user environment

Technical Requirements Programming Productivity - The technology we adopt this Web-site

will

have

potential

&

appropriately

integrated

with

other

relevant

technologies. Thus , the ability to develop & then deploy applications as

effectively & as quickly as possible is important.
Reliability & Availability - E-commerce transactions must be complete
& accurate.
Security - Security of information is a prime concern for e-commerce
type applications.
Scalability - The architecture adopted to develop this project must have
technical flexibility to adopt the changes in the future. To scale effectively
requires not only the ability to handle a large increase in the number of
clients but also effective use of the system resources.
Integration - All components must be properly integrated with each
other so that performance of the system must be good.

Page 16 of Synopsis

Hardware & Software Requirement Specification

Platform used - Microsoft Windows 2000 Advanced Server

Specification
ServerHardware Requirements Minimum

Processor Memory Disk Space -

Dual Pentium III 650 MHz Or higher

1024 MB
2 GB
Software Requirements Minimum

Operating System -

Microsoft Windows 2000

Advanced Server or higher

Database Server -

SQL server 2000

ClientHardware Requirements Minimum

Processor Memory Disk Space -

Pentium III 500 MHz Or higher

128 MB
1 GB
Software Requirements Minimum

Operating System -

Microsoft Windows 98/NT/2000

Internet Explorer -

IE5.5 /Netscape Navigator/ any

Features Of Windows 2000 Advanced Server Which May

Contribute To This Project

This is server edition & contains all features of server.

Easy to use & configure different components of the system.

Provide good base to develop enterprise software.

Provide multi-user facilities to distribute & reintegrate different

components of the project easily.

Architecture Implemented: JSP-Servlet Architecture (part of

J2EE)

Page 17 of Synopsis

Justification behind the recommendation of this architecture Enterprise Nature : The project is Web-based & Enterprise
applications can provide services to end-user via the internet or
private networks.
Diversity Of Information Needs : In an enterprise, information is
created & consumed by the various users in a number of different
forms, depending upon the specific needs. It is vary common to find
that each business activity may process the same information in a
different form.
Complexity Of Nature Of The Processes : Processes involved in
this project need complex information capture, processing, &
sharing. Very often, we encounter complex logic to capture &
process information .This leads to complex technical & architectural
requirements for building enterprise applications.

Diversity Of Applications: Due to the complex nature of the

enterprise nature of the processes, it is common to find that an
enterprise consists of a large
Number of the applications each built at various times to fulfill
different needs of the various business processes .This commonly
leads

to

the

presence

of

applications

built

using

different

architecture & technologies . One of the challenging needs of our

project is to make such applications that can talk to each other so
that business processes can be implemented seamlessly.

Page 18 of Synopsis

Container Architecture :

Web Container

The Front End Specifications:

To meet the requirements to build the web applications , the

following specifications are to be used:-

Language for Front End programming: Programming language: Java

Script language : Java Script
Language : DHTML (Dynamic Hyper Text Mark Up
Language), HTML (Hyper Text Mark Up Language) , XML

Web-component: Java Servlet & Java Server Pages, Java

Justification behind the selection of Java :

Platform Independence: Difficulties encountered from integrating

many of the different technologies that grow up specific to certain
platforms & applications.
Managed Objects: J2EE Applications are container centric both
these notations are very critical to building server-side applications.

Page 19 of Synopsis

By being managed J2EE component utilize the infrastructure

provided by J2EE Servers without the programmer being aware of it.
J2EE applications are also declarative; a mechanism using which
One can modify & control the behavior of applications without
changing code.
Reusability: Segregating applications, business requirements into
component parts is one way to achieve reuse. Using object
orientation to encapsulate shared functionality is another. JAVA uses
both. Java is an object oriented language & as provides mechanism
for reuse.
Modularity:

Breaking

our

applications

individual task is easy in java.

The Back End Specification:

The Data Base Server: SQL 7.0.

Data base Design (Data Structures) :

Target

Branch

Product_Sale

Product

Page 20 of Synopsis

into

different

tiers

&

 Inventory

Page 21 of Synopsis

ENTITY RELATIONSHIP DIAGRAM

B_Email
B_Name

P_Stock

B_Address

P_Id

B_Id
B_Phone

Branch

B_Performance

B_Fax

Inventory

ha
s

Product_Sale

relate
d

P_Id

P_Sale

P_Id

B_Id

P_Retu
rn

P_Nam
e

P_Damage

Product
B_Id

P_Id

P_Price

Target

P_descriptio
n

ha
s
Page 22 of Synopsis

Target

Target_Da
te

MODULARIZATION
A Modularization consists of well-defined manageable units with
well defined interfaces among the units.

Desirable Property Of Modular System Include

Each module is a well defined sub-system.

Single, well defined purpose of each module.

Modules can be separately compiled and stored in a library.

Modules can use other module.

Modules should be easier to use than to build.

Modules should be simpler from outside then from inside.

Design Constraints To Be Observed During

Modularization

Coupling:

Coupling is a measure of the degree of

interdependence between software modules.

Two modules with high coupling are strongly inter connected and thus
dependent on each other.
Two modules with low coupling are not dependent on one another.

Cohesion:

Cohesion is a measure of the degree to which the

elements of a module are functionally related.

A strongly cohesive module implements functions, which is related to one
feature of the solution and requires little interaction with other modules.

Details Of The Modules And Process Logic :

Total number of Modules is 8(Eight) which are as follows
1. MAKING NEW ENTRY FOR PRODUCT (Dynamic insertion of

new product) -

Page 23 of Synopsis

In this module new product is to be entered by the user. The user must
have administrative privilege. The Process Logic to be followed in this
module is as follows: User login by passing userid and password.
If he/she has admin privilege Admin page is opened with enter
new

product option.

To insert new product user clicks the new Product option. A new
form for inserting new product is opened.
User enter p_code , p_id for inserting new product.
Then request for format checking that anything is missing or not.
If missing then display error msg.
If format checking is correct then check information in product
table in database.
If information match in product table then display same
information exists.
If information not match in product table then inserting process
will go on.

DATA FLOW DIAGRAM (DFD)

User

P_code

Getting
Information

Request

Format
Checking

No
P_id

Yes

Error

Yes

Same
Info
Exists
Page 24 of Synopsis

Info
Match
in D.B.
No
o

Insert
Info in
Table

Product

FLOW CHART
User

p_code p_id

Yes

Format
checkin
g

Matc
h in
D.B.

No

No

Insert
information
in table

Yes

Display
Error
End
2. MAKING NEW USER : In this module new user is created. There are
two category of users. One is Admin group users and the second is General
user. General user has only privilege to insert data and Admin group has
privilege to make any modification.
New user can added by the Administrator. The Process Logic to be
followed in this module is as follows:[LOG-IN]
//User log in by passing user id and password.
Id [User id]
Pass [Password]
[CHECK PRIVILEGE]
if (id == Admin) then
//check in Admin table

Page 25 of Synopsis

//db= table at database

if (id = db.id and pass = db.pass)
//Open Admin page
Else
//Check in User page
//db= table at database
if (id = db.id and pass = db.pass)
//Open User page
else
Print Error
[ADMIN:?]
//Admin chooses Insert User option
[NEW USER FORM ]
// New user form is opened
[SUBMIT]
// Format check is done
if (format not correct)
Print Error
Else
//Value is inserted.

DATA FLOW DIAGRAM (DFD)

USER

Id, pass

Request

Getting
Information

Branch

Format
Checking

No
Yes

Error
Yes

Same
Info
Exists
Page 26 of Synopsis

Info
Matc
h
in No
D.B.
Insert
Info in
Table

Login

FLOW CHART
User

Id , Pass & Branch

Yes

Format
Checkin
g

Matc
h in
D.B.

No

No

Insert
Information
in Table

Yes

Display
error
End
3. UPDATE BRANCH : The Process Logic to be followed in this module is
as follows:[LOG-IN]
//User log in by passing user id and password.
Id [User id]
Pass [Password]
[CHECK PRIVILEGE]
if (id == Admin) then
//check in Admin table
//db= table at database
if (id = db.id and pass = db.pass)
//Open Admin page

Page 27 of Synopsis

Else
//Check in User page
//db= table at database
if (id = db.id and pass = db.pass)
//Open User page
else
Print Error
[ADMIN:?]
//Admin chooses Update Branch option
[BRANCH FORM]
// Branch form is opened
//take branch name
//retrieve branch info and open new form
[BRANCH INFO FORM IN EDIT MODE]
//Make appropriate changes
[SUBMIT]
// Format check is done
if (format not correct)
Print Error
Else
//Value is updated

DATA FLOW DIAGRAM (DFD)

Page 28 of Synopsis

B_code

Request

Getting
Informatio
n

Admin

Format
Checking

No

B_id

Yes

Error
Search
in Table

No

Branch

Yes
o

Info
doesnt
Exists

Update
Info in
Table

FLOW CHART
Admin

B_code, B_id

Format
Checkin
g

Yes

No

Check
in
D.B.
No

Display
Error
End

Page 29 of Synopsis

Yes

Update
Information
in Table

4. REMOVING BRANCH: In this module the system provide facility to the

administrator to remove branch which is not required. The Process Logic to be
followed in this module is as follows:[LOG-IN]
//User log in by passing user id and password.
Id [User id]
Pass [Password]

[CHECK PRIVILEGE]
if (id == Admin) then
//check in Admin table
//db= table at database
if (id = db.id and pass = db.pass)
//Open Admin page
Else
//Check in User page
//db= table at database
if (id = db.id and pass = db.pass)
//Open User page
else
Print Error
[ADMIN:?]
//Admin chooses Delete Branch option
[DELTE BRANCH FORM]

B_Code

Getting
// Delete Branch form is opened
Admin
Informatio
B_Id name
//take branch
n

Request
No

//retrieve branch info and open new form

[ASK FOR DELETING THIS BRANCH]
//If user select yes then

Format
Checkin
g
Yes

Error

[SUBMIT]
//Value is deleted at the database level

No

Info
Match
In
D.B.

Branch

InfoDIAGRAM (DFD)
DATA FLOW
Yes
doesnt
Exists

Page 30 of Synopsis

Delete
Info from
Table

FLOW CHART
Admin

B_Code, B_Id

Format
Checkin
g

Yes

Matc
h in
D.B.

No

No

Display
Error
End

Page 31 of Synopsis

Yes

Delete
Information
In Table

5.REMOVING PRODUCT INFO:

The Process Logic to be followed in this module is as follows:[LOG-IN]
//User log in by passing user id and password.
Id [User id]
Pass [Password]

[CHECK PRIVILEGE]
if (id == Admin) then
//check in Admin table
//db= table at database
if (id = db.id and pass = db.pass)
//Open Admin page
Else
//Check in User page
//db= table at database
if (id = db.id and pass = db.pass)
//Open User page
else
Print Error
[ADMIN:?]
//Admin chooses Delete Product info option
[DELTE PRODUCT FORM]

P_Code
Request
// Delete Product form is opened

User

Getting

Format
Checkin
//retrieve product info and No
open new form g
//take product
name
Information

P_Id

[ASK FOR DELETING THIS PRODUCT]

//If user select yes then
[SUBMIT]

Yes

Error

//Value is deleted at the database level

Info
No
Match
In (DFD)
DATA FLOW DIAGRAM
D.B.
Info
Yes
Doesn
t
o
Delete
Exists
Page 32 of Synopsis
Info From
Table

Product

FLOW CHART
User

P_Code, P_Id

Format
Checkin
g

Yes

Match
In D.B.

No

No

Display
Error
End
Page 33 of Synopsis

Yes

Delete
Information
From Table

6. DELETE USER INFORMATIONThe Process Logic to be followed in this module is as follows:-

1. Enter user id, password &branch.

2. Then request for format checking that anything is missing or
not

3. If missing then display error msg.

4. If format checking is correct then check information in login
table in database.

5. If information not matches in login table then display there is no

such type of user.

6. If information matches in login table then deletion process will

go on.

DATA FLOW DIAGRAM (DFD)

USER

Id, Pass

Getting
Information

Request

Format
Checking

No

Branch
Yes

Error

No

There
Is No
Such
Info.

Page 34 of Synopsis

Info
Match
In
D.B. Yes

Delete
Info
From
Table

Login

FLOW CHART
User

Id, Pass & Branch

Format
Checkin
g

Yes

Yes

Match
In
D.B.

No

Delete
Information
In Table

No

Display
Error
End
7.

INSERT BRANCH
The Process Logic to be followed in this module is as follows:1. Admin enter b_code , b_id for insertion new branch.
2. Then request for format checking that anything is missing or
not.
3. If missing then display error msg.
4. If format checking is correct then Request
check information in branch

B_Code

Admin

Getting
Information

Format
Checking

table in database.

5. If information matches in branch table then display information

No

all readyB_Id
exits.

Yesinsertion
6. If information not matches in branch table then
process will go on.

Error

Info

DATA FLOW DIAGRAM

(DFD)
Match
Yes

Info
Already
Exists
Page 35 of Synopsis

In D.B.
No

Insert
Info In
Table

Branch

FLOW CHART
Admin

B_Code, B_Id

Format
Checkin
g

Yes

Matc
h In
D.B.

No

Yes

Display
Error
End
Page 36 of Synopsis

No

Insert
Information
In Table

8.

UPDATE PRODUCT
The Process Logic to be followed in this module is as follows:1. User enter p_code , p_id for updating product.
2. Then request for format checking that anything is missing or
not.
3. If missing then display error msg.
4. If format checking is correct then check information in product
table in database.
5. If information not match in product table then display
information doesnt exists.
6. If information matches in product table then updating process
will go on.

DATA FLOW DIAGRAM (DFD)

User

P_Cod
e

Request

Getting
Information

P_Id

Format
Checkin
g

No

Yes

Error

No

Info
Doesn
t
Exists

Page 37 of Synopsis

Info
Check
In D.B.
Yes
o

Update
Info In
Table

Product

FLOW CHART
User

P_Code, P_Id

Format
Checkin
g

Yes

No

Match
In
D.B.

Yes

Update
Information
In Table

No

Display
Error
End

FURTHER ENHANCEMENT AND

SCOPE
1. This software is to be developed as full fledged Enterprise Marketing
system.
2. The software lacks enterprise nature and it is basically a web based
system. This should be designed to suite distributed environment.
3. The system should be developed in such a way that it can incorporate
flexibility at the level that can be customized to any organization.
4. It should include analysis features also. It has capability to analyze the
data better to say OLAP (On Line Analytical Processing) at one or two
level.
5. The graphical representation of the report should be included.

Page 38 of Synopsis

6. The user can generate reports. The reporting tool should be included with
the existing software.

Page 39 of Synopsis

BIBLIOGRAPHY
1. JavaTM Servlet & JSP Cookbook (SPD O`REILLY) Bruce W.
Perry
2. Java Server Pages (SPD O`REILLY)
3. Java 2 TMH Herbert Shield
4. NIIT techref ( SQL SERVER)
5. JSP by Wrox Press Ltd
6. www.sun.com

Page 40 of Synopsis