Fair Document

WEB TRAFFIC ANALYZER SKASC
CHAPTER I
INTRODUCTION
This project is entitled as “Web Traffic Analyzer” is developed using

ASP.NET as front end, C# as coding language and SQL Server as back end. ASP is Server side
scripting language, loosely typed to write, understand easily also user friendly to both
Programmer and user compare to all other web technologies. SQL Server is basically a relational
database management system. It is based on the structure query language. So that executions of
queries will be much simple.
The main objective of this project is to develop to analysis the traffic of a web
site, this details can be viewed by admin. Admin can able to control all the details of the website.
Here a special backend page will be provided for admin, So that he can access that page with his
user name and password. By entering in to their login he can able to view the entire website page
details as well the IP accessed pages, number of visitors of the page, date and time of visit etc.
This information will help the admin to analysis the traffic of their website as well frequently
visiting pages, in case of visiting their website from other countries process will helps the admin
to change their product trend according to their country. Time of visiting process will helps the
admin to maintain the website at less visitor’s time.
A web traffic analyzer is a web analytics tool that helps you track your web site traffic. A
web traffic analyzer is a tool that you can use to monitor your web site traffic. Find out how
many people are visiting your web site with the help of a web traffic analyzer. A web traffic
analyzer will help you to find out who is coming to your web site, when they are coming, if they
are return visitors or if they are new visitors.
A web traffic analyzer is almost a necessity in this day an age when web based
companies is getting more and more popular. If you are an online company and you participate
in online marketing then you need to look into a possible web traffic analyzer. The web traffic
analyzer is an important tool that enables you to optimize your web pages. You can use the web
Page 1
traffic analyzer to find out which of your advertisements are converting and those that don't.
Once you find out which advertisements are converting you can put your budget into those
advertisements with the help of a web traffic analyzer.
1.1 ABOUT THE ORGANIZATION
JAI FURN is a remarkable one stop wholesale shop offering quality furniture’s for all
homes, office and industrial needs. It is a reputed furniture store in Coimbatore, Tamil Nadu. We
started our operations in Saravanampatti at Sathyamangalam Main Road. Their philosophy is to
provide quality at a reasonable price and to do the same to this day. This showroom started in the
year of 2012. In 2006, they started a factory named MAX WORTH. They have variety of
designs. The furniture’s are fully made of pure teak wood, rose wood, sandal wood etc. Jai Furn
World expertise lies in manufacturing and marketing extremely innovative and cost effective
customised office furniture such as Dining tables, Study desks, Crockery stands, Coffee
tables, Telephone stands, Computer tables, Book shelves, Office tables, Chairs and
Cabinets.
JAI FURN has demonstrated Execution of mega and multi location projects without
compromising on requirements of the customers. There are more than 80 peoples working this
company. They import the furniture’s from Malaysia, Indonesia, Taiwan and china. This
company deals with the foreign dealership. They export the furniture’s to Sri Lanka, Singapore,
Nepal and Bhutan. It is proud of having skilled and motivated team members who are highly
committed to producing quality products and implementing positive change. Their “do it right
the first time” attitude is matched with the company’s modern equipment to produce WoodMark
Quality certified products with innovative designs. WoodMark is a quality system designed for
the wood products industry, with the emphasis on ensuring consistent product quality and
continuous improvement. This innovative approach enables Dynamic to significantly increase its
efficiency and remain competitive in today’s ever-changing marketplace. Customer delight is our
prime motto and we strive to achieve this by understanding the views of our every customer
needs. Our clients actively participate in the ongoing decisions affecting their projects and are
Page 2
encouraged to visit the shop during the construction phases. Most find this experience interesting
and rewarding.
1.2 PROBLEM DEFINITION
Web analytics is the measurement, collection, analysis and reporting of internet data for
purposes of understanding and optimizing web usage. Web analytics is not just a tool for
measuring web traffic but can be used as a tool for business and market research, and to assess
and improve the effectiveness of a web site. Web analytics applications can also help companies
measure the results of traditional print or broadcast advertising campaigns. It helps one to
estimate how changes traffic to a website after the launch of a new advertising campaign. Web
analytics provides information about the number of visitors to a website and the number of page
views. It helps gauge traffic and popularity trends which is useful for market research.
There are two categories of web analytics; off-site and on-site web analytics. Off-site web
analytics refers to web measurement and analysis regardless of whether you own or maintain a
website. It includes the measurement of a website's potential audience (opportunity), share of
voice (visibility), and buzz (comments) that is happening on the Internet as a whole.
On-site web analytics measure a visitor's behaviour once on your website. This includes
its drivers and conversions; for example, the degree to which different landing pages is
associated with online purchases. On-site web analytics measures the performance of your
website in a commercial context. This data is typically compared against key performance
indicators for performance, and used to improve a web site or marketing campaign's audience
response. Google Analytics is the most widely-used on-site web analytics service; although new
tools are emerging that provide additional layers of information, including heat maps and session
replay. Historically, web analytics has referred to on-site visitor measurement. However in recent
years this has blurred, mainly because vendors are producing tools that span both categories.
Many different vendors provide on-site web analytics software and services. There are
two main technical ways of collecting the data. The first and older method, server log file
Page 3
analysis, reads the log files in which the web server records file requests by browsers. The
second method, page tagging, uses JavaScript embedded in the site page code to make image
requests to a third-party analytics-dedicated server, whenever a page is rendered by a web
browser or, if desired, when a mouse click occurs. Both collect data that can be processed to
produce web traffic reports.
1.3 HARDWARE SPECIFICATION
PROCESSOR : Intel Pentium i3 1.8 GHz
MOTHERBOARD : Intel 915GVSR chipset board
RAM : 4 GB DDR 3 RAM
HARD DISK DRIVE : 500 GB
FLOPPY DRIVE : 1.44 MB
DVD/CD DRIVE : Sony 52 x Dual layer drive
MONITOR : 17” Color TFT Monitor
KEYBOARD : Multimedia Keyboard 108 Keys
MOUSE : Logitech Optical Mouse
CABINET : ATX iball.
HUB : Compex 16 lines.
BANDWIDTH : 100 mbps.
Page 4
1.4 SOFTWARE SPECIFICATION
FRONTEND : ASP.NET 2010
BACKEND : SQL Server 2008
CODING LANGUAGE : C#
OPERATING SYSTEMS : Microsoft windows 7
DOCUMENTATION : Microsoft word 2007.
SCRIPTING LANGUAGE : Java Script
CLIENT SERVER TOOL : AJAX 2.0
Page 5
CHAPTER II
SYSTEM STUDY
2.1 PROBLEM DESCRIPTION
The modules used in these project are listed below and explained:
1. Web admin
2. Analysis portal
3. Traffic analyzer using bandwidth
4. Admin web view
5. Admin report
6. Logs and Reports
1. Web admin
This is the initial module of this project; here a product based website will be developed
for analysing the website. This website may be a product based website or any kind of service
based websites. But it should not be less than eight pages for the basic web analysis. This kind of
website may be static or dynamic. This is a content based management system for the entire
work group so that it will work accordingly to the coding.
2. Analysis Portal
In this module an analysis report will be generated for the admin, it will capture all the
basic traffic based information from the web server. All the basic details will be saved in the
admin table. This analysis portal will display the details of data of visiting, time of visiting, No
of user visited, visited ip address and bandwidth used for the website. All the details will be
displayed in the grid for admin manage purpose.
Page 6
3. Traffic analyzer
In this process bandwidth will be used for calculating the speed and resource of the
website. In website hosting, the term bandwidth is often used to describe the amount of data
transferred to or from the website or server within a prescribed period of time, for
example bandwidth consumption accumulated over a month measured in gigabytes per month.
The more accurate phrase used for this meaning of a maximum amount of data transfer each
month or given period is monthly data transfer.
4. Admin web view
A detailed grid will be displayed here for displaying all the gathered details from the
web server as well as there will be some options available for deleting and sorting the details.
These details can be view only through the login username and password of the admin only. Buy
displaying the details in the grid admin can go through the content easily. The details will be
displayed as default sorted dates, so admin no need for sorting the retrieved details. There is a
password updating option also available in the admin side.
5. Admin report
This is the final module of this project. Admin report process will be done automatically
by the tab inside their admin login. These can be downloaded by the admin for future reference.
The download can be done through daily backups or monthly backups. The data will be
downloaded in the format of excel. The total bandwidth usage also viewed in the admin report so
that the available bandwidth of the website can be calculated easily.
6. Data Logs
This is the final module of this project for the user interaction. Here data filters are used
for clustering the data. Data filers are enabled in three modes like IP filtering, Date filtering and
Time Filtering. IP Filters will furnish the relevant IPs, Frequent visited IPs and User filtered IPs.
Date can be selected manually the user. User can select the date for viewing the visitors IP data
Page 7
wise. Similarly time filters will be used. All the data will be published in the data grid and in
report format.
2.2 STUDY ON EXISTING SYSTEM
Existing low-latency anonymity networks are vulnerable to traffic analysis, so location

diversity of nodes is essential to defend against attacks. Previous work has shown that simply
ensuring geographical diversity of nodes does not resist, and in some cases exacerbates, the risk
of traffic analysis by ISPs. Ensuring high autonomous-system (AS) diversity can resist this
weakness. However, ISPs commonly connect to many other ISPs in a single location, known as
an Internet exchange (IX). This project shows that Ices are a single point where traffic analysis
can be performed. User examine to what extent this is true, through a case study of Tor nodes in
the UK. Also, some Ices sample packets flowing through them for performance analysis reasons,
and this data could be exploited to denonymize traffic. User then develops and evaluates
Bayesian traffic analysis techniques capable of processing this sampled data.
On low-bandwidth small office or business networks, full packet analysis tools such as
tcp dump are adequate to monitor traffic for debugging or to measure load. However, on links
found on high-speed networks, the capacity required to store all packets rapidly becomes
infeasible. For example, at time of writing, both LINX and AMS-IX carry approximately 150
Gb/s, which exceeds the theoretical maximum capacity of the high-speed PCIe bus, 64 Gb/s (32
lanes at 2 Gb/s each). Despite these difficulties, there is high demand for monitoring of such
high-speed links, to detect problems such as routing loops, balance load across network
infrastructure and anticipate future demands on capacity.
There are two basic types of traffic analysis. The first treats the anonymity network as a
“black-box” and only inspects traffic entering and leaving the network. The second approach
additionally examines flows within the network, and so improves the accuracy of the attack. In
this project, we will concentrate on the former category. As this does not make any assumptions
about the structure of the network, it is the more general approach. However, the techniques user
Page 8
present here could also be applied to the latter category of attacks, as intra-network Tor traffic
will also often cross a small number of Internet exchanges.
User assumes that the attacked flow passes through an attacker controlled IX on both its
path into and out of the anonymity network. This would be the case if, for example, both the
customer and site are hosted on ISPs whose backbone connection was through an IX under
surveillance. Also, user assumes that packet sampling is independently and identically
distributed over the flow. Although some models of network hardware implement periodic
sampling, rather than random, this assumption will remain true because Tor traffic makes up an
in significant proportion of overall traffic.
2.3 STUDY ON PROPOSED SYSTEM
All the drawbacks overcome in the proposed system. Concerns about the accuracy of log
file analysis in the presence of caching, and the desire to be able to perform web analytics as an
outsourced service, led to the second data collection method, page tagging or 'Web bugs'.
The web analytics service also manages the process of assigning a cookie to the user,
which can uniquely identify them during their visit and in subsequent visits. Cookie acceptance
rates vary significantly between web sites and may affect the quality of data collected and
reported.
Collecting web site data using a third-party data collection server (or even an in-house
data collection server) requires an additional DNS look-up by the user's computer to determine
the IP address of the collection server. On occasion, delays in completing successful or failed
DNS look-ups may result in data not being collected.
With the increasing popularity of Ajax-based solutions, an alternative to the use of an

invisible image is to implement a call back to the server from the rendered page. In this case,
when the page is rendered on the web browser, a piece of Ajax code would call back to the
server and pass information about the client that can then be aggregated by a web analytics
company. This is in some ways flawed by browser restrictions on the servers which can be
Page 9
contacted with Xml Http Request objects. Also, this method can lead to slightly lower reported
traffic levels, since the visitor may stop the page from loading in mid-response before the Ajax
call is made. Both log file analysis programs and page tagging solutions are readily available to
companies that wish to perform web analytics. In some cases, the same web analytics company
will offer both approaches. The question then arises of which method a company should choose.
There are advantages and disadvantages to each approach.
The main advantages in technical are follows:
 The web server normally already produces log files, so the raw data is already available. No
changes to the website are required.
 The data is on the company's own servers, and is in a standard, rather than a proprietary,
format. This makes it easy for a company to switch programs later, use several different
programs, and analyze historical data with a new program.
 Log files contain information on visits from search engine spiders, which generally do not
execute JavaScript on a page and are therefore not recorded by page tagging. Although these
should not be reported as part of the human activity, it is useful information for search
engine optimization.
 Log files require no additional DNS lookups or TCP slow starts. Thus there are no external
server calls which can slow page load speeds, or result in uncounted page views.
 The web server reliably records every transaction it makes, e.g. serving PDF documents and
content generated by scripts, and does not rely on the visitors' browsers cooperating.
Commonly, click analytics focuses on on-site analytics. An editor of a web site
uses click analytics to determine the performance of his or her particular site, with regards to
where the users of the site are clicking. Also, click analytics may happen real-time or "unreal"-
time, depending on the type of information sought. Typically, front-page editors on high-traffic
news media sites will want to monitor their pages in real-time, to optimize the content. Editors,
designers or other types of stakeholders may analyze clicks on a wider time frame to aid them
assess performance of writers, design elements or advertisements etc.
Page 10
Advantage of proposed system
 Admin can know their available bandwidth day by day.
 Can know the number of visitors per day and per page, so that admin can able to change
their product details according to the viewers.
 IP of the visitor will be displayed in the grid, So that visited user country can be viewed
by the admin.
 A prior login will be allocated for the admin.
Page 11
CHAPTER III
SYSTEM DESIGN AND DEVELOPMENT
3.1 DATA FLOW DIAGRAM
A data flow diagram (DFD) illustrates how data is processed by a system in terms of
inputs and outputs. As its name indicates its focus is on the flow of information, where data
comes from, where it goes and how it gets stored.
DATA FLOW DIAGRAMS NOTATIONS
The data flow diagram is used to describe the flow of diagram in the project. The symbol
used in the diagram explains the type data present in it. The data flow diagram is very useful
form of representations for the end user. Some of the symbols used in DFD are:
Process
Flow
Data storage
Page 12
Process
A process shows a transformation or manipulation of data flows within the system. The
symbol used is a rectangular box, which contains 2 descriptive elements: Firstly an identification
number appears in the upper left hand corner. This is allocated arbitrarily at the top level and
serves as a unique reference. Secondly, a location appears to the right of the identifier and
describes where in the system the process takes place.
Data Flow
A data flow shows the flow of information from its source to its destination. A data flow
is represented by a line, with arrowheads showing the direction of flow. Information always
flows to or from a process and may be written, verbal or electronic. Each data flow may be
referenced by the processes or data stores at its head and tail, or by a description of its contents.
Data Store
A data store is a holding place for information within the system: It is represented by an open
ended narrow rectangle. Data stores may be long-term files such as sales ledgers, or may be short-
term accumulations: for example batches of documents that are waiting to be processed. Each data
store should be given a reference followed by an arbitrary number.
LEVEL 0:
LOGIN:
Username&
password View/Update
page details
Web traffic
Admin Database
Analyzer
FIG 3.1 DATA FLOW DIAGRAM LEVEL 0
Page 13
LEVEL 1:
Username & password Admin table

Login
Username1
password Create Static/Dynamic page

Page Name
Content1 Page
Updated page Page creation

Manage
Edit/delete
page
Total count No of visitors

Check total
Members Total view
Admin viewed
Total IP
Total IP
View total System
IP address IP
Page count
No of users/page
Page view
View
individual
Page IP Viewed
Page view Downloaded
date page
View Download
individual time
Page view
Page 14
FIG 3.2 DATA FLOW DIAGRAM LEVEL 1
3.2 ER DIAGRAM
An E-R Diagram stand for Entity Relationship Model is a tool that is commonly used to
translate different views of data among user and programmers to fit into a common framework,
define data processing and constraints requirement to help us meet the different views and helps
to implement the database.
Link
Relationship
Entity
Attributes
ENTITIES
An entity is represented by a rectangle containing the entity occurrence. An entity is

represented by a rectangle containing the entities name. It is denoted by rectangle by specifying
the table name in it.
ATTRIBUTES
Attributes are represented by ovals and are connected to the entity with a line. Each oval
contain the name of the attribute it represents. For example travelling system attributes such as
passenger name, address, phone number etc.
RELATIONSHIP
Page 15
A relationship is an association between entities. Each relation is identified so that is

name is descriptive of the relation.
Page 16
contents nooflink Page

s name
Page_id
Content
id id content Page Id
s
1 1 n
Page contents has Page
create
Id
password
username
admin manage
1
individualcount
date
1
page name
page Id
IP
address time
Id
Id Individual
view view
Page view
Total n 1
date IP address
date count count
n Total 1
page name
time count date
Id
1 page Id
Total page time
Total page time
has
View count Id
IP view Individual
1
IP view
Page 17
3.3 INPUT DESIGN
The input design of this project is planned according to the web application based
website. The input design of this project deals with various architecture. The input design is
based on some networking concepts like architecture designs. This multi information was
established to the admin in various formats. The basic input design of this application is a user
interaction web page.
Major input pages:
 Home page
 Product pages
 All supporting pages
In order to retrieve the traffic from the web server, various details are gathered.
Basically IP based input has been used. This IP gathering can analyze the user activities and web
application usage on the users.
Input taken on web application:
 IP address
 Visited page details
 Visited product details
 Duration of the visit
 Date and time of visit
The input pages fetch all these details during web site visit and store the details
in the SQL server database. User sign up forms are available in case the user getting sign in
means, various details of the user should be provided in the input design. The input supports on
validation control like, numerical based fields accepts only numerical values and characters
based fields accepts only character.
Page 18
In the input design contains a calendar control with data and time picker. The
calendar control will automatically get enabled during the time of user login and user visit.
3.4 DATABASE DESIGN
Table name: pageanalyse
Field Data Type Size Constrains Description
Totalcount Int 50 Not Null Total website viewed count
Home Int 50 Not null Home page count
About us Int 50 Not null About us page count
Dining table Int 50 Not null Dining table page count
Chairs Int 50 Not null Chairs page count
wardrobe Int 50 Not null Wardrobe page count
offtable Int 50 Not null Office table page count
cot Int 50 Not null Cot page count
scase Int 50 Not null Show case page count
Customer Int 50 Not null Customer support page count
Contact Int 50 Not null Contact page count
Page 19
Table name: ipadd
Primary Key: Ip address
Ipaddress Int 50 Primary Key System ip address
Coun Int 50 Not null Individual page count
Page varchar 20 Not null Page name
Mintime Int 50 Not null Time taken
Table name: pagecreation
Pageid int 10 Not null Page identification number
Pagename int 50 Not null Page name
Contents int 50 Not null Page contents
Page 20
Table name: data and time
Foreign Key: Ip address
Ipaddress Int 50 Foreign Key System ipaddress
Date Int 50 Not null Date of visit
time Int 20 Not null Time of visit
Mintime Int 50 Not null Time taken
Table name: bandwidth
Availband Int 50 Not null Available bandwidth details
Pageband Int 50 Not null Individual page bandwidth
Totband Int 20 Not null Total bandwidth
Topup Int 50 Not null Total bandwidth needed
3.5 OUTPUT DESIGN
The output design is based on the interactive graphical user interface. The output page of
this project is a web page design. These web pages contain various organization information and
product details. The signed up details of the users are available in the admin login. A data grid is
available is the admin login page. The grid contains all the user information.
Page 21
Major output forms
 Admin IP view
 Admin product details view
 User details grid
 Traffic page
 Bandwidth usage
Most of the information is shown in data grid and text enabled label boxes. All the output
is only for admin usage. Admin can analyze all the information in a single interactive page. This
makes the output design more efficient than the input design. The data grid contains sorting
options, so that admin can customize the information date wise, time wise, IP wise and etc
In case of bandwidth, the available bandwidth is shown in the admin login page. Even
ever the user visits the webpage a minimum amount of bandwidth will be reduced for the total
bandwidth. Admin can check the available bandwidth at anytime. Also admin will have the
option to top up the bandwidth of the web application.
Admin have the option to analyze the bandwidth per page. The makes the web page to
load faster. The important components used in the output design are:
 Data grid
 Text enabled label box
 Image box
 Label box
 Text box
Page 22
CHAPTER IV
SYSTEM TESTING
System testing is the process of exercising software with the intent of finding and
ultimately correcting errors. This fundamental philosophy does not change for web applications,
because Web-based systems and application reside on a network and interoperate with many
different operating system, browsers, hardware platforms, and communication protocols; the
search for errors represents a significant challenge for web application.
The distributed nature of client/server environments, the performance issues associated with
transaction processing, the potential presence of a number of different hardware platforms, the
complexities of network communication, the need to serve multiple clients from a centralized
database and the requirements imposed on the server all combine to make testing of client\server
architectures.
TESTING ISSUES
 Client GUI considerations
 Target environment and platform diversity considerations
 Distributed database considerations
 Distributed processing considerations
TESTING METHODOLOGIES:
System testing is the state of implementation, which is aimed at ensuring that the
system works accurately and efficiently as expect before live operation commences. It certifies
that the whole set of programs hang together. System testing requires a test plan that consists of
several key activities and steps for run program, string, system and user acceptance testing. The
implementation of newly designed package is important in adopting a successful new system.
Page 23
Testing is an important stage in software development. The system test in

implementation stage in software development. The system test in implementation should be
confirmation that all is correct and an opportunity to show the users that the system works as
expected. It accounts the largest percentage of technical effort in the software development
process.
Testing phase in the development cycle validates the code against the functional
specification. Testing is vital to the achievement of the system goals. The objective of testing is
to discover errors. To fulfill this objective a series of test step unit, integration, validations and
system tests were planned and executed.
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 on as yet undiscovered error.
A successful test is one that uncovers on as yet undiscovered error.
The above objectives imply a change in view. They move counter to the commonly held
view that a successful list is one in which no errors are found. Any engineered product can be
listed in one of two ways
1. Knowing the specified function that a product has been designed to perform tests can
be conducted to demonstrate each function is fully operational.
2. Knowing the internal workings of a product, tests can be conducted to ensure that “all
gear mesh” that is, the internal operation of the product performs according to specification and
all internal components have been adequately exercised.
Page 24
Types of testing
1. Unit Testing
2. Integration Testing
3. Validation Testing
4. Output Testing
5. User acceptance Testing
6. System Testing
4.1 Unit Testing :-

All modules were tested and individually as soon as they were completed were
checked for their correct functionality. Unit testing is carried out by verify and recover errors
within the boundary of the smallest unit or a module. In this testing step, each module was found
to be working satisfactory per the expected output of the module. In the package development,
each module is tested separately after it has been completed and checked with valid data. Unit
testing exercise specific paths in the modules control structure to maximum error detection.
4.2 Integration Testing :-

The entire project was split into small programs; each of these single programs
gives a frame as an output. These programs were tested individually; at last all these programs
where combined together by creating another program where all these constructions were used. It
give a lot of problem by not functioning in an integrated manner. The user interface testing is
important since the user has to declare that the arrangements made in the frames are convenient
and it is satisfied. When the frames are the test, the end user gave suggestion. Since they were
much exposed to do the work manually.
4.2.1 Validation Testing: -

At the culmination of the black box testing software is completely assembled as a
package. Interfacing errors have been uncovered and corrected and a final series of test i.e.,
Page 25
validation succeeds when the software functions in a manner that can be reasonably accepted
by the customer.
4.2.2 Output Testing:-
After performing the validation testing the next step is output testing of the
proposed system. Since the system cannot be useful if it does not produce the required output.
Asking the users about the format in which the system is required tests the output displayed or
generated by the system under consideration. Here the output format is considered in two ways.
One is on screen and another one is printed format. The output format on the screen is found to
be corrected as the format was designed in the system phase according to the user needs. And for
the hardcopy the output comes according to the specifications requested by the user. Here the
output testing does not result in any correction in the system.
4.3 User Acceptance Testing:-
User acceptance testing of the system is the key factor the success of any
system. The system under consideration is tested for user acceptance by constantly keeping in
touch with prospective system at the time of development and making change whenever
required. This is done with regard to the input screen design and output screen design.
4.3.1 System Testing:-
This is to verify that all the system elements have been properly integrated and
perform allocated functions. Testing is executing a program to test the logic changes made in it
and with intention of finding errors. Tests are also conducted to find discrepancies between
system and its original objective, current specification and documents.
Page 26
CHAPTER V
SYSTEM IMPLEMENTATION AND MAINTENANCE
5.1 SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a
working system. The most crucial stage is achieving a successful new system & giving the user
confidence in that the new system will work efficiently & effectively in the implementation state.
The stage consists of
 Testing the developed program with simple data.

 Detection’s and correction of error.
 Creating whether the system meets user requirements.
 Testing whether the system.
 Making necessary changes as desired by the user.
 Training user personnel.
5.1.1 Implementation Procedures
The implementation phase is less creative than system design. A system project may be
dropped at any time prior to implementation, although it becomes more difficult when it goes to
the design phase.
The final report to the implementation phase includes procedural flowcharts, record
layouts, report layouts, and a workable plan for implementing the candidate system design into
an operational one. Conversion is one aspect of implementation.
Several procedures of documents are unique to the conversion phase. They include the
following,
 The conversion portion of the implementation plan is finalized and approved.

 Files are converted.
Page 27
 Parallel processing between the existing and the new system are logged on a
special form.
 Assuming no problems, parallel processing is discontinued. Implementation
results are documented for reference.
 Conversion is completed. Plans for the post-implementation review are prepared.
Following the review, the new system is officially operational.
5.1.2 User Training
User Training is designed to prepare the user for testing & converting the
system. There are several ways to train the user. They are
1) User Manual.
2) Help Screens.
3) Training Demonstration.
1) User Manual:
The summary of important functions about the system and software can be
provided as a document to the user.
2) Help Screens:
This features now available in every software package, especially when it

is used with a menu. The user selects the “Help” option from the menu. The system accesses the
necessary description or information for user reference.
3) Training Demonstration:
Another User Training element is a Training Demonstration. Live

demonstrations with personal contact are extremely effective for Training Users.
Page 28
5.1.3 Operational Documentation
Documentation means of communication; it establishes design and performance criteria

for phases of the project. Documentation is descriptive information that portrays the use and / or
operation of the system.
(i) Documentation Tools

Document production and desktop publishing tool support nearly ever aspect of
software developers. Most software development organizations spend a substantial amount of
time developing documents, and in many cases the documentation process itself is quite
inefficient. It is not use unusual for a software development effort on documentation. For this
reason, documentation tools provide an important opportunity to improve productivity.
(ii) Document Restructuring
Creating document is far too timed consuming. If the system work’s, we’ll live with
what we have. In some cases, this is the correct approach. It is not possible to recreate document
for hundreds of computer programs.
Documentation must be updated, but we have limited resources. It may not be
necessary to fully redocument an application. Rather, those portions of the system that are
currently undergoing change are fully documented.
The system is business critical and must be fully redocumented. Even in this case, an
intelligent approach is to pare documentation to an essential minimum.
5.2 SYSTEM MAINTENANCE

Maintenance is actually the implementation of the review plan. As important as it is,
many programmers and analysts are to perform or identify themselves with the maintenance
effort. There are psychological, personality and professional reasons for this. Analysts and
programmers spend far more time maintaining programs than they do writing them.
Maintenance accounts for 50-80 percent of total system development.
Page 29
Maintenance is expensive. One way to reduce the maintenance costs are through
maintenance management and software modification audits.
 Maintenance is not as rewarding as exciting as developing systems. It is

perceived as requiring neither skill not experience.
 Users are not fully cognizant of the maintenance problem or its high cost.
 Few tools and techniques are available for maintenance.
 A good test plan is lacking.
 Standards, procedures, and guidelines are poorly defined and enforced.
 Programs are often maintained without care for structure and documentation.
 There are minimal standards for maintenance.
 Programmers expect that they will not be in their current commitment by time
their programs go into the maintenance cycle.
Page 30
CHAPTER VI
CONCLUSION
This project is done according to the committed concepts. And followed all the valid
implementation methods and testing methods. Our mission in this project is to develop a highly
deliverable output. This is an ideal implementation of the Single Responsibility Principle (SRP).
Furthermore, by careful application of abstractions can reduce dependency on concrete classes
and increase the expansibility and reliability of our web applications. There will be no losing of
any data by using this type of software. Various reports are generated based on the requirement
of the concern reports will present the management with the current position of the management.
Thus this project was successfully completed and satisfied all the needs from the requirement.
And output had shown in the efficient manner.
Page 31
CHAPTER VII
FUTURE ENHANCEMENT
In future the logging of information about visitors to Websites began as a simple

extension of the information kept by server administrators long before the Web came into being.
In those days the information about files served, peak times for traffic etc were collected in order
to provide detail about the level of service. This could be used by the system administrator to
anticipate necessary upgrades to the service, to spot bottlenecks in processing, identify
unauthorised use of the facilities, etc. Analysis of this data could be presented in simple
graphical form to the managers of the service in hourly, daily, or weekly breakdowns, illustrating
aspects of usage.
The arrival of large-scale commercial interest in the Web was changed everything. The
Web was no longer an exclusive playground for IT people and academics, and the newcomers
needed statistics for their own purposes. Marketing departments needed stats to show that the
investment in a Web presence was generating some kind of interest, if not direct evidence of
business done, and to establish relative success compared to competing businesses.
For commercial companies, the principal data to be mapped by augmented Web logs is
customer transactions. This information is already collected, one way or another, however it is
not always recorded in a way which can be easily analysed. The information is not represented in
the conventional Web log, and cannot therefore be processed by standard analytical tools. As
things stand, the e-commerce information may well be split up among several aspects of the
service.
Details should be stored in a standardised format compatible with the existing Web logs.
Every aspect of the customer’s journey towards a successful transaction should be available for
scrutiny, since analysing the behaviour of the customer is the best way of understanding the
strengths and weaknesses of the Website as a vehicle for commercial transactions.
Page 32
CHAPTER VIII
BIBILOGRAPHY
8.1 BOOKS REFERRED:
1. Programming with Web Services
Authour : Masumi Nakamura
Publisher: O'Reilly Media
Released: December 2010
2. Professional Programming with ASP.NET
Authour : Nathan Blevins, John J. Croft IV, Jonathan Dick, Chris Hardy
Publisher: Wiley / Wrox
Released: December 2011
8.2 WEBSITE REFERRED:
1. https://developers.google.com/webservices.com
2. www.openhandsetalliance.com/aspoverview.html
3. www.sourceproject.com
4. www.valuecoders.com/hire-developers/hire- -developers
5. www.devlease.com/hire -developers-from-india.html
Page 33
CHAPTER IX
APPENDIX
9.1 INPUT DESIGN
FIG 9.1.1 HOME PAGE
Page 34
FIG 9.1.2 PRODUCT-SOFA PAGE
FIG 9.1.3 ADMIN LOGIN

Page 35
FIG 9.1.4 BANDWIDTH
Page 36
9.2 OUTPUT DESIGN
FIG 9.2.1 HOME PAGE VIEWED DETAILS
Page 37
FIG 9.2.2 PRODUCT-SOFA PAGE DETAILS
FIG 9.2.3 BANDWIDTH
Page 38
9.3 REPORT
FIG 9.3.1 HOME PAGE REPORT
Page 39
FIG 9.3.2 PRODUCT-SOFA PAGE REPORT
Page 40
9.4 SAMPLE CODING
using System;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Linq;
using System.Web.Configuration;
using System.Data.SqlClient;
public partial class _Default : System.Web.UI.Page
SqlConnection con;
SqlCommand cmd;
string query,date,time;
int h,count;
int bandwidth, finalbandwidth;
protected void Page_Load(object sender, EventArgs e)
Page 41
date = System.DateTime.Today.ToShortDateString();
time = System.DateTime.Now.ToShortTimeString();
//bandwidth code
data();
query = "select bwidth from bandw";
cmd = new SqlCommand(query, con);
SqlDataReader rd = cmd.ExecuteReader();
if (rd.Read())
bandwidth = Convert.ToInt32(rd[0].ToString());
rd.Close();
con.Close();
if (bandwidth == 0)
Response.Redirect("errpage.aspx");
else
finalbandwidth = bandwidth - 3;
if (finalbandwidth < 0)
finalbandwidth = 0;
Page 42
data();
query = "update bandw set bwidth=" +

finalbandwidth + "";
cmd.ExecuteNonQuery();
con.Close();
data();
query = "select home from pageanalyse";
h =
Convert.ToInt32(cmd.ExecuteScalar().ToString());
h = h + 1;
query = "update pageanalyse set home=" + h +

"";
con.Close();
string ip;
ip =
(Request.ServerVariables["REMOTE_ADDR"].ToString());
data();
query = "select coun from ipadd where

ipaddress='" + ip.ToString() + "' and page='Home' and
cdate='" + date.ToString() + "'";
Page 43
SqlDataReader red = cmd.ExecuteReader();
if (red.Read())
count = Convert.ToInt32(red[0].ToString());
count = count + 1;
data();
query = "update ipadd set coun =" + count +

",cdate='" + date.ToString() + "',ctime='" +
time.ToString() + "' where ipaddress='" + ip.ToString() +
"' and page='Home' and cdate='" + date.ToString() + "'";
con.Close();
else
data();
query = "insert into

ipadd(ipaddress,coun,page,cdate,ctime)values('" +
ip.ToString() + "',1,'Home','" + date.ToString() + "','" +
time.ToString() + "')";
con.Close();
red.Close();
Page 44
con.Close();
public void data()
string connstring =
WebConfigurationManager.ConnectionStrings["connect"].Connec
tionString;
con = new SqlConnection(connstring);
con.Open();
Page 45

Fair Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fair Document

Uploaded by

Copyright:

Available Formats

WEB TRAFFIC ANALYZER SKASC

This project is entitled as “Web Traffic Analyzer” is developed using

1.1 ABOUT THE ORGANIZATION

1.2 PROBLEM DEFINITION

1.3 HARDWARE SPECIFICATION

PROCESSOR : Intel Pentium i3 1.8 GHz

MOTHERBOARD : Intel 915GVSR chipset board

RAM : 4 GB DDR 3 RAM

HARD DISK DRIVE : 500 GB

FLOPPY DRIVE : 1.44 MB

DVD/CD DRIVE : Sony 52 x Dual layer drive

MONITOR : 17” Color TFT Monitor

KEYBOARD : Multimedia Keyboard 108 Keys

MOUSE : Logitech Optical Mouse

CABINET : ATX iball.

HUB : Compex 16 lines.

BANDWIDTH : 100 mbps.

1.4 SOFTWARE SPECIFICATION

FRONTEND : ASP.NET 2010

BACKEND : SQL Server 2008

OPERATING SYSTEMS : Microsoft windows 7

DOCUMENTATION : Microsoft word 2007.

SCRIPTING LANGUAGE : Java Script

CLIENT SERVER TOOL : AJAX 2.0

2.1 PROBLEM DESCRIPTION

3. Traffic analyzer using bandwidth

4. Admin web view

6. Logs and Reports

4. Admin web view

2.2 STUDY ON EXISTING SYSTEM

Existing low-latency anonymity networks are vulnerable to traffic analysis, so location

2.3 STUDY ON PROPOSED SYSTEM

With the increasing popularity of Ajax-based solutions, an alternative to the use of an

The main advantages in technical are follows:

Advantage of proposed system

 Admin can know their available bandwidth day by day.

 A prior login will be allocated for the admin.

SYSTEM DESIGN AND DEVELOPMENT

3.1 DATA FLOW DIAGRAM

DATA FLOW DIAGRAMS NOTATIONS

FIG 3.1 DATA FLOW DIAGRAM LEVEL 0

Username & password Admin table

password Create Static/Dynamic page

Updated page Page creation

Total count No of visitors

FIG 3.2 DATA FLOW DIAGRAM LEVEL 1

An entity is represented by a rectangle containing the entity occurrence. An entity is

A relationship is an association between entities. Each relation is identified so that is

contents nooflink Page

3.3 INPUT DESIGN

Major input pages:

Input taken on web application:

3.4 DATABASE DESIGN

Table name: pageanalyse

Field Data Type Size Constrains Description

Totalcount Int 50 Not Null Total website viewed count

Home Int 50 Not null Home page count

About us Int 50 Not null About us page count

Dining table Int 50 Not null Dining table page count

Chairs Int 50 Not null Chairs page count

wardrobe Int 50 Not null Wardrobe page count

offtable Int 50 Not null Office table page count

cot Int 50 Not null Cot page count