MAJOR PROJECT REPORT

(TECHTUTUS4U)

Submitted in the partial fulfillment of B.Tech in Computer Science & Engg. under
Punjab Technical University , Jalandhar

Submitted by

ANURADHA (81002107007)

Under the Guidance of

Ms.Swati Goyal,
Project Head

Department Of Computer Science Engineering

RBCEBTW, SAHAURAN, KHARAR

August to November, 2011

 DECLARATION

I hereby declare that the project work entitled (“Online employee payroll system”) in
partial fulfillment of the requirement for the award of the degree of
B.E. (Computer Science Engineering), RBCEBTW, Mohali, is an authentic work done by
me during a period from August 2011 –November2011, under the Guidance of (Ms.Swati
Goyal).

(Signature of student)
Anuradha
81002107007

Date: ___________________

Certified that the above statement made by the student is correct to the best of our
knowledge and belief.

(Name &
Designation)

Coordinator
 ACKNOWLEDGEMENT

Inspiration and hard work plays a key role in the success of any venture. At the level of
practice, it is often difficult to get knowledge without guidance, “project is like a bridge
between theoretical and practical.” With this willing we joined his project.

I am really grateful to Ms. Swati Goyal who have given me their valuable time for
giving information about the subject and their experience. Their guidance helped me in
completion of this work.
I am deeply inbeted to honorable Director Dr. S.C.Layoria .I wish to extend my sincere
gratitude to “HOD, CSE & IT and faculty of CSE/IT Department ” for their guidance,
encouragement and valuable suggestions which proved extremely useful and helpful in
completion of this industrial training.

My heartfelt gratitude and indebtness goes to all teachers and guidance group who with
their encouraging, caring words, constructive criticism and segmentation have
contributed directly or indirectly in a significant way towards completion of this training.
My special thanks go to my friends whose support and encouragement have been a
constant source of assurance, guidance, strength, and inspection to me.

This report conveys my heartiest thanks to Ms. Swati Goyal for his active support, whole
hearted guidance, sincere cooperation and pains-taking involvement during the study and
in completing the assignment of preparing the said project within the time stipulated.

At last but not least we made our grateful acknowledgement to all our friends and batch
mates for their cooperation.
Date: Anuradha

81002107007
 LIST OF FIGURES

S.No. Name of the Figure Page Number

1. Data Flow Diagram(Level- 30
0)
2. Data Flow Diagram(Level- 31
1)
3. Working of the Site 32
4. Data Flow Diagram of Blog 33
Site

LIST OF TABLES
S.No. Name of Table Page No.
1. Admin table 34
2. User Table 34
3. Discussion Zone Table 34
4. Overall Discussion Zone 35
Table
5. Placemnt Paper Table 35
6. Comments Table 36
7. Demand Detail Table 36
8. Feedback Table 37
9. Movie News Table 37
10. Movie Review Table 37
11. Box Office Report Table 38
12. Box Office Review Table 38
13. Company Table 39
14. Exam Table 39
15. User Form Details 40
16. Exam Type 40
17. Experienced 41
18. Job Details 41
19. Login 42
20. Question Table
21. Result Table

LIST OF ABBREVIATIONS

S.No. Abbreviation Meaning

1. HTTP Hyper Text Transfer Protocol

2. XML Extensible Markup Language
 3. SRS Software Requirement Specification
4. Admin Administrator
5. DFD Data Flow Diagram
6. HTML Hyper Text Markup Language
7. SQL Structured Query Language
8. J2EE Java 2 Enterprise Edition
9. API Application Programming Interface
10. JSP Java Server Pages
11. ASP Active Server Pages
12. JDBC Java Data Base Connectivity
13. DESC Describe
14. OOP Object Oriented Programming
15 AJAX Asynchronous JavaScript And XML

INDEX

1) Introduction to Project 3-4

3) Objectives of the Project 5-6
4) Study of Existing System 7
5) System Requirements 8-24
5.1) Product Definition
5.1.1) Problem Recognition
5.1.2) Function to be provided
5.1.3) User Requirements
5.1.4) Functional Requirements
5.1.5) Performance Requirements
5.2) Methodology Adopted
 5.3) Feasibility Analysis
5.4) Introduction o J2EE Framework
6) Software Requirement Specification 25-27
7) System Design 28-42
7.1) Characteristic of Well Defined System
7.2) Data Flow Diagram
7.3) Tables Used in the Project
8) Testing 43-50
8.1) Unit Testing
8.2) System Testing
8.3) Objectives of Testing
8.4) Testing Principles
8.5) Test Information Flow
8.6) Test Case Design
8.6) Basic Testing Methods
9) System Implementation 51-75
9.1) Introduction
9.2) Types of Implementation
9.3) Implementation Tools
9.4) Conversion Methods
9.-5) Post Implementation Review
9-6) Snap Shots
10) Maintenance and Security Aspects 76-79
10.1) Types Of Maintenance
10.2) Security Aspects
11) Conclusion 80
12) Future Plans 81
13) Bibliography 82
 INTRODUCTION TO PROJECT

The term 'payroll' encompasses every employee of a company who receives a regular
wage or other compensation. Some employees may be paid a steady salary while others
are paid for hours worked or the number of items produced. All of these different
payment methods are calculated by a payroll specialist and the appropriate paychecks are
issued. Companies often use objective measuring tools such as timecards or timesheets
completed by supervisors to determine the total amount of payroll due each pay period.

For small business owners, keeping enough cash in a payroll account is often one of their
highest priorities. Even if the business itself hasn't become profitable, employees must
still be compensated for their services. This is why many smaller companies prefer to
keep their payroll obligations as low as possible until they've reached a certain level of
profitability. It's not unusual for small business owners to forego their own salaries in
order to meet their payroll obligations.
Setting up an effective payroll system is not especially difficult for trained accountants,
but it can be very time consuming. Some smaller businesses rely on user-friendly
computer software to set up a simple payroll system complete with check printers and file
storage. Larger companies may assign trained accountants to handle payroll issues as part
of their overall duties. But many businesses without the means to maintain their own
payroll systems choose to farm out this task to outside specialists.

Since payroll records are based on objective criteria such as timecards and federal tax
forms, outside accountants can perform all of the calculations, store all of the year-to-date
data and issue paychecks in a timely fashion. Employers simply need to update these
payroll companies with changes in employee pay rates or deductions.

This project titled "Employee Management and Payroll System" is a classic example of
how to maintain the records of employees On an electronic storage. The entries of new
employees , the upkeep of already working employees etc. has been facilitated in a quite
simplified manner.

When the main program is executed following menu appears on the screen -

1) Master
2) Daily

When the user clicks on Master option following sub menu appears -

1) Employee Master
2) Exit

On clicking the employee master sub option user is provided with the following
choices :-
1) Personnel information
2) Salary Related information
3) Previous Company
4) Other information

In personnel information option details of all the new employees can be fed . Also
The details of already joined employees can be viewed.

In Salary related option, the basic salary, deductions, Pf etc. are fed into the details
& processed.

Previous company information show as the details of working statistics’ of the employee
that he had been working with previously.

In the daily option of the main menu, user can check the electronic attendance register &
also can feed the attendance for the employees into it.

In Totality, we can say this project is very helpful for the companies & firms who are
required to regularly put records related with their employees’ details into the computer
system. They can also keep a tab on the attendance history of their respective employees.

OBJECTIVES OF PROJECT

There are some Objectives, which are Envisaged under the Project:-

Practicality: The system should be stable and can be operated with average
intelligence.
Efficiency: There should be balance amongst various factors like accuracy,
comprehensiveness on one hand and response timeliness of the system on the other hand.

Cost: It is desirable to aim for the system with a minimum cost subject to the condition
that it must satisfy the entire requirement.

Flexibility: The system should be modifiable depending on the changing needs of the
employee or department. Such modifications should entail extensive reconstructing. It
should also be portable to different computer systems.

Security: This is very important aspect requiring rigorous designing of database

including hardware reliability, fallback procedures and physical security of data.

The development of the proposed system is done keeping in view the problems in the
existing system. The proposed system will not only overcome the limitations of the
present system but will also provide the following characteristics.

The objective of the system would be:

1.To reduce the paper work involved in managing the information.

2.To reduce the time constraint involved.

3.To centralize all the data needed.

4.To maintain the information about the latest technology for students.

5.To generate various reports as required

6.To maintain the user rights.

System Outline view

After firming the requirements of the system, the summary chart or data flow diagram
(DFD) of the proposed system is prepared. This gives the brief of the system with respect
to the inputs being considered, the outputs reports, the data being transformed and the
main processed involved in the system.

Member Users
s

Register & Add Acquire Data

Knowledge Base Website from Knowledge
Base

DFD VIEW OF SYSTEM

SYSTEM TESTING
The purpose of system testing is to identify and correct errors in the candidate system.
Testing is and important element of software quality assurance ad represents the ultimate
review of specification, design and coding. The increasing visibility of the software as a
system element and the cost associated with a software failure are motivated forces for
well planned, through testing.System testing was conducted in order to detect errors and
for comparing then the final system with the requirement specification reports, i.e.
whether the system meets requirements. During testing the software was executed with
the set of test cases and the output of programs for the test cases was evaluated to
determine if the program is performing as it was expected to. Testing presents an
interesting challenge for the software engineers attempt to build software from an abstract
concept to an acceptable implementation. In testing engineer create a series of test cases
that occurs when errors are uncovered. Testing is the process of executing a program for
finding errors. A good test is one that has the high probability of finding an uncovered
error. A successful error is one that uncovers undiscovered errors. The term error is used
to refer the difference between actual output of the software and the current output. Fault
is a condition that causes the software to fail to perform its required function. Software
reliability is defined as a required function. Software reliability is defined as the
probability that the software will not undergoes failures for a specified times under
specified condition. Failure is the inability of a system or a component to perform a
required function according to its specification. Different levels of testing were employed
for software to make it error free, fault free and reliable.

Unit Testing:

Unit testing was conducted first. Different modules of the software were tested against
the specifications produced during design of the modules. Verification of the code
produced during the coding phase was done. Each module was tested separately.

Unit testing focuses verification effort on the smallest unit of software design module.
This uncovers errors within the boundary of a module. Unit testing is actually White box
testing both the external things as well as the internal codes are tested. In testing, the
interfaces are tested in order to ensure the proper flow of data in and out of the module.
The boundary testing is done to ensure that the module keeps the limit of it. All
independent paths are tested to ensure that all statements are tested at least once. At last
the error path is also tested.

Unit testing comprises the set of tests performed by an individual programmer prior to
integration of the unit into a larger system. There are four categories of test that can be
performed on a program unit

1) Functional Unit

2) Performance Unit

3) Stress Unit

4) Structure Unit

System Testing:

Then system testing was conducted. Here the entire software system was tested.

The reference document used for this process was requirement document and the goal
was to see if the software meets its requirements.

System testing includes the thorough testing of the product. System testing is actually a
series of different tests whose primary purpose is to fully exercise the computer based
system. The tests are recovery testing: this checks the recovery of the system when failure
occurs. This is to ensure that there are recovery procedures for error occurrences.

System testing involves unit testing, integration testing, acceptance testing. Careful
planning and scheduling are required to ensure that modules will be available for
integration into the evolving software product when needed. A test plan has the following
steps:

1) Prepare test plan

2) Specify conditions for user acceptance testing

3) Prepare test data for program testing

4) Prepare test data for transaction path testing

5) Plan user testing

6) Compile/Assemble program

7) Prepare job performance aids

8) Prepare operational documents

Objectives of Testing.

First of all objectives should be clear.

1) Testing as a process of executing a program with the intent of finding errors.

2) To perform testing, test cases are designed. A test case is a particular made up of
artificial situation upon which a program is exposed so as to find errors. So a good test
case is one that finds undiscovered errors.

3) If testing is done properly, it uncovers errors and after fixing those errors we have
software that is being developed according to specifications.

The above objective implies a dramatic change in viewpoint .The move counter to the
commonly held view than a successful test is one in which no errors are found. In fact,
our objective is to design tests that a systematically uncover different classes of errors
and do so with a minimum amount of time and effort.

Testing principles

Before applying methods to design effective test cases, software engineer must
understand the basic principles that guide the software testing process. Some of the most
commonly followed principles are:

All test should be traceable to customer requirements as the objective of testing is to

uncover errors, it follows that the most severe defects (from the customers point of view)
are those that causes the program to fail to meet its requirements.

Tests should be planned long before the testing begins. Test planning can begin as soon as
the requirement model is complete. Detailed definition of test cases can begin as soon as
the design model has been solidated. Therefore, all tests can be planned and designed
before any code can be generated.
The Pareto principle applies to software testing stated simply the Pareto principle implies
that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent
of all program modules. The problem of course, is to isolate these suspects’ modules and
to thoroughly test them.

Testing should begin “in the small “and progress towards testing “in large”. The first tests
planned and executed generally focus on individual modules. As testing progresses,
testing shifts focus in an attempt to find errors in integrated clusters of modules and
ultimately in the entire system.

Exhaustive testing is not possible. The number of paths permutations for impossible to
execute every combination of paths during testing. It is possible however to adequately

cover program logic and to ensure that all conditions in the procedural design have been
exercised.

To be most effective, an independent third party should conduct testing. By “most

effective”, we mean testing that has the highest probability of finding errors (the primary
objective of testing).

Software project management is an umbrella activity within software engineering. It

begins before any technical activity is intimated and continues throughout the definition,
development, and maintenance of computer software.

Three p’s 1 have a substantial influence on software project management –people,

problem, and process. People must be organized into effective teams, motivated to do
high quality software work, and coordinated to achieve effective communication. The
problem communicated from customer to developer, partitioned (decomposed) into its

Constitute parts, and positioned for work by the software team. The process must be
adapted to the people and the problem. A common process framework is selected, an
appropriate software engineering paradigm is applied, and a set of work is chosen to get
the job done.

The pivotal element in all software projects is people. Software engineers can be
organized in a number of different team structures that range from traditional control
hierarchies to “Open paradigm” team. A variety of coordination and communication
techniques can be applied to support the work of the team. In general, formal reviews and
informal person-to-person communication have the most value for the practitioners.The
project management activity encompasses measurement and metrics, estimation, risk
analysis, schedules, tracking and control, and control. Each of these steps was followed
during project also.

Test information flow

Testing is a complete process. For testing we need two types of inputs:

Software configuration –It includes software requirement specification, design

specification and source code of program. Software configuration is required so that
testers know what is to be expected and tested.

Test configuration – it is basically test plan and procedure. Test configuration is testing
plan that is, the way how the testing will be conducted on the system. It specifies the test
cases and their expected value. It also specifies if any tools for testing are to be used.

Test cases are required to know what specific situations need to be tested. When tests are
evaluated, test results are compared with actual results and if there is some error, then
debugging is done to correct the error. Testing is a way to know about quality and
reliability. Error rate that is the occurrence of errors is evaluated. This data can be used to
predict the occurrence of errors in future.

Test case design

We know, test cases are integral part of testing. So we need to know more about test cases
and how these test cases are designed. The most desired or obvious expectation from the
test cases is that it should be able to find most errors with the least amount of time and
effort.

A software product can be tested in two ways. In first approach, only overall functioning
of the product is tested. Inputs are given and outputs ate checked. This approach is called
black box testing. It does not care about the internal functioning of the product.

The other approach is called white box testing. Here the internal functioning of the
product is tested. Each procedure is tested for its accuracy. It is more intensive than black
box testing. But for the overall product both these techniques are crucial. There should be
sufficient number of tests in both categories to test the overall product.

Basic Testing Methods

White box testing

White box testing is performed to reveal problems with the internal structure of a
program. This requires the tester to have detailed knowledge of the internal structure. A
common goal of white box testing is to ensure a test case exercises every path through a
program. A fundamental strength that all white box strategies share is that the entire
software implementation is taken into account during testing, which facilitates error
detection even when software specification is vague or incomplete. The effectiveness or
thoroughness of white box testing is commonly expressed in terms of test or code
coverage metrics, which measure the fraction of code exercised by test cases.

Basic Path Testing

It is a white box technique. It was proposed by Tom McCabe. These tests guarantee to
execute every statement in the program at least one time during testing. Basic set is the
set of all execution paths of a procedure.

Black Box Testing

Black box tests are performed to access how well a program meets its requirements,
looking for incorrect or missing functionality. Functional tests typically exercise code
with valid or nearly valid input for which the expected output is known. This includes
concepts such as ‘boundary values’.

Performance tests evaluate response time, memory usage, throughput, device utilization
and execution time. Stress tests push the system to or beyond its specified limits to
evaluate its robustness and error handling capabilities. Reliability tests monitor system
response to representative user input, counting failures over time to measure or certify
reliability.

Black box testing uncovers the following types of errors

1) Incorrect or missing functions

2) Interface errors

3) External database access

4) Performance errors

5) Initialization and termination errors

The following techniques are employed during black box testing

Integration Testing

One of the most difficult aspects of software development is the integration and testing of
large untested subsystems. The integrated system frequently fails in significant and
mysterious ways and it’s difficult to fix it.

Integration testing exercises several units that have been combined to form a module,
subsystem or system. Integration testing focuses on the interfaces between units, to make
sure the units work together. The nature of this phase is certainly ‘white box’, as we must
have knowledge of the units to recognize if we have been successful in focusing them
together in the module.
 SYSTEM IMPLEMENTATION

INTRODUCTION

Software testing is used in association with verification and validation (V&V).

Verification is the checking of or testing of items, including software, for conformance
and consistency with an associated specification. Software testing is just one kind of
verification, which also uses techniques such as reviews, inspections, and walkthroughs.
Validation is the process of checking what has been specified is what the user actually
wanted. Verification: Have we built the software right? (i.e. does it match the
specification). Validation: Have we built the right software? (i.e. Is this what the customer
wants?)

Implementation is the stage in the project where the theoretical design is turned into the
working system and is giving confidence to the new system for the users i.e. will work
efficiently and effectively. It involves careful planning, investigation of the current
system and its constraints on implementation, design of method to achieve the change
over, an evaluation, of change over methods. A part from planning major task of
preparing the implementation is education of users. The more complex system is
implemented, the more involved will be the system analysis and design effort required
just for implementation. An implementation coordinating committee based on policies of
individual organization has been appointed. The implementation process begins with
preparing a plan for the implementation for the system. According to this plan, the
activities are to be carried out, discussions may regarding the equipment has to be
acquired to implement the new system.

Implementation is the final and important phase. The most critical stage is in achieving a
successful new system and in giving the users confidence that the new system will work
and be effective. The system can be implemented only after thorough testing is done and
if it found to working according to the specification. This method also offers the greatest
security since the old system can take over if the errors are found or inability to handle
certain types of transaction while using the new system.

At the beginning of the development phase a preliminary implementation plan is created

to schedule and manage the many different activities that must be integrated into plan.
The implementation plan is updated throughout the development phase, culminating in a
change over plan for the operation phase. The major elements of implementation plan are
test plan, training plan, equipment installation plan, and a conversion plan.

Types Of Implementation

There are three types of implementation:

1. Implementation of a computer system to replace a manual system.

2. Implementation of a new computer system to replace an existing system.

3. Implementation of a modified application to replace an existing one, using the same

computer.
Successful implementation may not guarantee improvement in the organization using the
new system, but improper installation will prevent it. It has been observed that even the
best system cannot show good result if the analysts managing the implementation do not
attend to every important detail. This is an area where the systems analysts need to work
with utmost care.

IMPLEMENTATION TOOLS:

1. Training personnel

2. Conversion Procedures

3. Post-implementation review

Training of Personnel involved with system

Even well designed system can succeed or fail because of the way they are operated and
used. Therefore, the quality of training received by the personal involved with the system
in various capacities helps or hinders and may even prevent the successful
implementation of management information system.

Those who are directly or indirectly related with the system development work must
know in detail what must know in detail what their roles will be, how they can make
efficient use of the system and what the system will or will not do for them. Both system
operators and users need training.

System Operators Training

Running of the system successfully depend on the personnel working in the Computer
Centre. They are Responsible for providing the necessary support. Their training must
ensure that they are able to handle all possible operations, both routine and extra-ordinary
in nature.
If the system calls for the installation of new equipment, such as new computer system,
special terminals or different data entry machines, the operators training should include
such fundamentals as how to turn the equipment on and use it, how to power off and a
knowledge of what constitutes normal operations. The operators should also be trained on
different type of malfunctioning, how to recognize them and what steps should also be
taken whenever they arise.

User Training

User may be trained on use equipment, particularly in the case where, e.g. a micro
computer is in use and individual involved is both operator and user. In such cases, user
must be given training on how to operate and user. In such cases, user must be given
training on how to operator the system also. Questions that may be trivial to the analyst,
such as how to turn on a terminal, how to insert a diskette into a micro-computer or when
it is safe to turn off equipment with out danger of data loss are significant problems to
new users who are not familiar.

Inmost of the cases user training deals with the operation of the system itself, with proper
attention given to data handling techniques. It is imperative that users be properly trained
in methods of entering transaction, editing data, formulating inquiries, deleting and
inserting of records. No training is complete without familiarizing users with simple
systems maintenance activities. Weakness in any aspect of training may lead of awkward
situation that creates user frustration and error.

Conversion Methods

A conversion is the process of changing from the old system to the new one. It must be
properly planned and executed. Four methods are common in use. They are Parallel
Systems, Direct Conversion, Pilot System and Phase In method. Each method should be
considered in the light of the opportunities that it offers and problems that it may create.
In general, system conversion should be accomplished in shortest possible time. Long
conversion periods create problems for all persons involved including both analysts and
users.
Parallel systems:

The most secure method of converting from an old to new system is to run both systems
in parallel. This method is safest one because it ensures that in case of any problem in
using new system, the organization can still fall back to the old system without the loss of
time and money.

The disadvantages of parallel systems approach are:

It doubles operating costs.

The new system may not get fair trial.

Direct conversion:

This method converts from the old system to new system abruptly, sometimes over a
weekend or even overnight. The old system is used until a planned conversion day, when
it is replaced by the new system.

Pilot system:

Pilot approach is often preferred in the case of the new system which involves new
techniques or some drastic changes in organization performance. In this method, a
working version of the system is implemented in one part of the organization, such as a
single work area or department.

Phase –IN- method:

This method is used when it is not possible to install a new system throughout an
organization all at once. The conversion of files, training of personnel or arrival of
equipment may force the staging of the implementation over a period of time, ranging
from weeks to months.
 POST IMPLEMENTATION REVIEW

After the system is implemented and conversion is complete, a review should be

conducted to determine whether the system is meeting expectations and where
improvements are needed. A post implementation review measures the systems
performance against predefined requirement. It determines how well the system
continues to meet the performance specifications.

SNAP SHOTS

Home Page
About us
Contact us
Admin Home Page
New Employee Details
Employee Salary Details
Employee Maintenance
Edit Employee Details
View Employee Details
Generate Pay Slips
Generate Pay slips
Search Employee
Leaves Details
Pay slip with deductions
Change Password
Employee Section
View Personal Details
Leave Requests
Loan Request
Bill Payment
View Leave Request
Accept / Reject request
View request
Accept Loans
 CONCLUSION
The system has been developed for the given condition and is found working effectively.
The developed system is flexible and changes whenever can be made easy. Using the
facilities and functionalities of Java, the software has been developed in a neat and simple
manner, thereby reducing the operators work.

The speed and accuracy are maintained in proper way. The user friendly nature of this
software developed in Java framework is very easy to work with both for the higher
management as well as other employees with little knowledge of computer. The results
obtained were fully satisfactory from the user point of view.

The system was verified with valid as well as invalid data in each manner. The system is
run with an insight into the necessary modifications that may require in the future. Hence
the system can be maintained successfully without much network.
 FUTURE PLANS:

In future we will do some major advances in the project and it may be extended for the
major one. This may include many features like replying can be user specific and we can
see the replies according to selecting the user. We may make to look it attractive by
adding some flash animation to the pages.

Going further to access this project on Wifi we can buy the desired web space and after
that it can be made to run on the Wifi and can be accessed from any region. Thus it will
be available on net every moment.

Link in the documents are more important than simple text. Number and types of links
and other web structures can be given higher weights to improve the overall classification
of the document.

Web structures can also be given importance for classification. The higher font size labels
can be given more importance while classifying a document than other text. These can be
done by giving the different weights to keywords depending upon the font size.

In this project the features like remote login can also be made possible. The features like
online chatting on the blogs and giving the comments can also be made possible.
 BIBLIOGRAPHY

1) www.google.com

2) www.wikipedia.org

3) Jewei Han and Micheline Kamber(2005) “Elementary implementation of Tomcat”.

4) The complete reference for Java by Helbert Schildt

5) The complete reference for Java Server Pages by Helbert Schildt

6) John M. Pierre(2000) “Practical issues for automated generation of blogs”

7) Google News www.googlenews.com

8) Microsoft Network www.msn.com

9) CDNOW www.cdnow.com

10) Lycos www.lycos.com

11) 95506am.blogspot.com

12) Eblog.com

13) Bloggers.com

14) Programming in Java by Balaguruswamy.