1. W3ANALYZER
BY
K.Vamshi Krishna
P.Shankar Murthy

2. EXISTING SYSTEM
The normal website do not include any tracking system facilities and
there are no controlling techniques to overcome the page uploads when
there are more number of visitors online.The Frequent customers who visit
the web site may feel some difficulties. We cannot know the user system
details and the difficulties he is facing while surfing web site.

3. PROPOSED SYSTEM
In proposed system we can estimate the user system configuration details ,
browser details and we can track his traversal and we can conclude the
difficulties facing regarding traversal , background effects , themes etc.
Thus we can include those features desired by the user and make him feel
better.
The other aspect we are stressing is on that the user can upload his images
and can change his wished color theme dynamically.

4. INTRODUCTION
The W3Analyser includes three components namely web tracker, hit
counter and real-time detailed web statistics.
When someone visits the website, the code is executed and the visitor's
public details (ip address, browser, operating system, referrer, page
title and url etc) are analysed and stored for reporting to the website
owner later.
The website owner has control on which pages he/she wants to track
just by placing the code in required pages.

5. COMPONENTS..
HIT COUNTER
The hit counter display's a counter on the web page. The webmaster
has the option to choose between displaying unique visitors.
WEBTRACKER
The web tracking system allows the admin to track the user path
traversed throughout the web site.
WEBSTATISTICS
Web statistics offers a breakdown of current unique, returning and
repeat visitors over the lifetime of the website. Also it will offer browser,
resolution, operating system, country, search engine, keyword, referring link,
and visitor analysis and reporting.

6. SCOPE OF THE PROJECT:
The Scope Of the Project revolves round the Three components
1. Web Tracker
2. Hit Counter
3. Web Statistics
The features that can be implemented are:
• Magnify User
• Popular Pages
• Entry Pages
• Exit Pages
• Visitor Paths
• Recent Page load Activity
• Recent Visitor Activity

7. Functional Requirements
 Functional requirements define all the operations that take place in the
system. The following are the list of functional requirements of the system.
User
Administrator
Mail Reports

8. NON-FUNCTIONAL REQUIREMENTS
Performance Requirements:A performance requirement is a statement that describes
how well a function is to be executed or achieved, or how well it is to be accomplished.
Performance requirements are categorized and mentioned as follows:
Response Times: 90% of interactive tasks such as loading of web page, validating user id
and password etc would take less than 10seconds of time.
Throughput and concurrency: Throughput and concurrency is expected to be as high as
possible.
Efficiency: Specifies how well the software utilizes scarce resources: CPU cycles, disk
space, and bandwidth.
Usability: The measurement of how often, how efficiently, and/or correctly people use the
System.

9. Safety requirements
Safety requirements specify those requirements that are concerned with possible
loss, damage, or harm that could result from the use of the product.
Every user must be verified thoroughly before allowing him to use the system.
Requirements:
Each user must have unique login details.
Database of each user should be kept safely.

10. Modules
 User: It contains the detail information about the user such as Uid ,
Uname , Pwd , Gender , EmailId.
 Administrator: It encloses the Information like Bid, Browsing Data,Os,
System Details, Image settings, Theme settings etc.
 Mail Reports: The report consists of all the above details in neat format.

11. SCREEN SHOTS

12. Home page

13. About us

14. Change themes

15. After Change

16. Reports

17. User login

18. Add images

19. Admin pages:
Updates User Accounts

20. Updates Theme Details

21. UML DIAGRAMS

22. CLASS DIAGRAM

23. Sequence diagram for login
u:user ul:userlogin db:database
1: request for login
2: submit username password
3: verifying user details
4: user verified(loged or unloged)

24. Sequence diagram for profile update
u:user ud:userdetails db:database
1: request for profile update
2: load existing details
3: enter new details
4: update the database
5: database updated
6: load new profile

25. Sequence diagram for image gallery
u:user uig:userimage db:database
gallery
1: request for image upload
2: load existing images
3: loading new image
4: update the database
5: database updated
6: load all images

26. Activity diagram for user login

27. Activity diagram for profile
update
Start
upload existing
details
update the
profile
invalid details
valid details
submit new
details
stop

28. Activity diagram for image gallery

29. Use Case For user login
submit login info
verification of user database
user
user verified and logged in

30. Use case diagram for profile update
load existing profile
user update details database
update the profile

31. Use case diagram for image gallery
load existing images
user upload new image database
update image gallery

32. CONCLUSION
The project we developed allows user to sign up if he is the
new user else allows existing user to login .The logged in user
can select his choice of theme from the list of themes provided
by the Admin. The user can upload his images $ the website
can be viewed as an Art Gallery.
The Admin has control over all the users can include or
exclude from the website. He tracks all the user information
such as Os used, user system Configuration, number of users
online etc and generates reports based on them.

33. REFERENCES
NET COMPLETE REFERENCE : by
PETERICKNAUGHTON
PROGRAMMING WITH .NET : by
BALAGURUSWAMY
SQLSERVER DATABASE ACCESS WITH .NET : by
GRAHAMAMELTON
RICH CATTELL
MATADENE FISHER
 SOFTWARE ENGINEERING : by
ROGER S.PRESSMAN