java chat app

1. Tilak Education Society
Tilak College of
Arts, Commerce, Science College
Vashi
PROJECT REPORT ON
LIVE CHAT
By
Mr. DNYANRAJ SUBHASH PATIL
Under the Guidance Of
Prof. Mrs.Triveni Kaul
Submitted to
University of Mumbai
2011-2012
DEPARTMENT OF COMPUTER SCIENCE
Tilak Education Society
TILAK COLLEGE OF SCIENCE & COMMERCE
Plot no. 231 Sector-28,Vashi, Navi Mumbai-400 705

2. This is to certify that the project of
Live Chat Application
Undertaken at
TILAK COLLEGE OF SCIENCE & COMMERCE
By
MR.DNYANRAJ SUBHASH PATIL (Seat o._____________).
In partial fulfillment of B.Sc. (computer science) degree Examination
had not been submitted for any other courses undergone by the
candidate. It is further certified that they are completed all required
phases of the project.
Internal Examiner Head of Department
External Examiner

3. ACKNOWLEDGEMENT
Making of project Live Chat Application is been unique experience for
us.
We would like to thanks the entire staff of the Computer
Science department of Tilak College of Science and Commerce, who
kept helping continuously through out our project.
A special thanks to Mr. Rao Ghuge and Mrs. Bhagyashree
Kulkarni and Mrs.Triveni Koul for their valuable guidance,
cooperation and encouragement and time spend for this project
work. Without her help and guidance this project would be
unsuccessful.
Last but not least we would like to thank to my family and
friends for their constant moral support.
Thanking You,
DNYANRAJ SUBHASH PATIL

4. SIGNED SHEET
Class : T.Y.B.Sc Subject : project
Signed sheet details are as follows (As per Practical)
PHASE COMPLITION SIGN
PHASE
DATE (guide)
NO.
1 Project Finalization
2 Investigation of
system
requirements/Synopsis
3 Data & Process
collection
4 System Design
5 Program Design
6 Program Coding
First phase
Second phase
Third phase
Last phase
7 Unit testing checked
by Guide
8 Integration testing
9 Complete Project
10 Documentation
printout Checking
11 Final Submission

5. INDEX
Sr.No. Title Page
No.
1 Introduction
2 Gantt Chart
3 Organizational overview
a. Purpose
b. Scope
c. Organization chart
d. Present system
e. Limitations of present system
4 Proposed system
Benefits of proposed system
5 System study
a. System analysis
b. Requirement specification
c. Feasibility study
6 System analysis
a. Prototyping model
b. Event table
c. ER-Diagram
d. Use case diagram & use case description
e. Activity diagram

6. f. Sequence diagram
g. Collaboration diagram
h. State chart diagram
i. Context Level diagram
j. Data Flow Diagram.
k. Class Diagram
7 System Design
a. Component Diagram
b. System Flow Chart
8 System coding
a. List of tables with attributes and
constraints
b. Testing & Validation
c. Test cases
9 System Implementation
10 Future Enhancement
11 Reference and Bibliography

7. 1
CHAPTER
INTRODUCTION

8. INTRODUCTION TO PROJECT
1.1 Introduction
Live Chat is an easy-to-use, server based LAN messaging application
for effective communication. It correctly identifies and works under
all operating systems with unlimited user accounts and is the only
secure, messenger .The simple interface makes special training
needless.
1.2 Goals of the Project
 Communication: To develop an instant messaging solution
to enable users to seamlessly communicate with each other.
 User friendliness: The project should be very easy to use
enabling even a novice person to use it.
1.3 Innovative Ideas of the Project
 GUI: Easy to use GUI (Graphical User Interface), hence any
user with minimal knowledge of operating a system can use
the software.
 Platform independence: The messenger operates on
any system irrelevant of the underlying operating system.
 Unlimited clients: ‘n’ number of users can be
connected without any performance degradation of the
server.

9. 2
CHAPTER
GANTT CHART

10. Gantt Chart:-

11. 3
CHAPTER
ORGANIZATIONAL
OVERVIEW

12. Organizational overview
Purpose of the Project:-
This project is to create a chat application with a server and
clients to enable the clients to chat with many other clients in the
same common chat group. This project is to simulate the multicast
chatting. In the case of multicasting when a message is sent to a
group of clients, then only a single message is sent to the router.
Which means that the client will send the message only once and
based on the location of the clients, the router will either pass the
message to another router or if the clients are in the same local
network the router will send a copy of the message to each client in
that network. So this way we are reducing the number of messages
being passed in the whole network.

13. Scope of the Project:-
Mail Server with Live Chat is going to be a text communication
software, it will be able to communicate between two computers
using point to point communication. .
The limitation of Live Chat is it does not support audio conversations.
To overcome this limitation we are concurrently working on
developing better technologies.
Data communication over LAN networks is going to be a most
important mode of communication for the corporates in the very
near future. Companies have to rely on external networks which not
only are unreliable but also cost inefficient.
Companies would like to have a communication software wherein
they can communicate instantly within their organization.
The fact that the software uses an internal network setup within the
organization makes it very secure from outside attacks.

14. Organization chart:-
Detailed Idea about the Project:-

15. Communication:-
The different ways of communication are telephone lines, postal
services, satellites communication etc.
But the communication on computer is broadly divided into two
types i.e. communication over internet and communication over
intranet. For communicating over the internet you need to have an
internet connection which is not cost effective.
But communication over the intranet is very efficient and cost
effective. For that purpose you just need to have a LAN connection
within your organization and a continuously running server.

16. LAN:-
A local area network (LAN) is a computer network covering a local
area, like a home, office, or group of buildings.
The defining characteristics of LANs in contrast to WANs (wide area
networks) are: their much higher data rates; smaller geographic
range; and those they do not require leased telecommunication lines
Therefore, to enhance the communication features of the current
communication system, we are designing a product called Live Chat.
It is an instant messaging software.
Basically, any organization that requires continuous communication
between their employees can use this software.

17. The basic interaction between the client and the
server would be:-
Server
get Groups
Send Message

18. Client:-
The client would first authenticate itself as a valid user to the
server. Once the server validates the user, the user will try to
get the groups that are available in the server currently where
the client can chat. if a user wants to send a message to the
group then it will have to invoke the Send Message object of the
server. At any time the client can leave the group by sending
the Leave Group message to the server and the server will
delete this user from that group.
The above specified interactions is being implemented using
RMI and the particular instance where the Server sends the
message to all other users of that group will be implemented
using UDP socket. So the client will be listening for any
messages pertaining to that group at a particular port.The
initial aim of this project will be to create an application that
will try to work as a multicast server.
Since there is only 1 server being used here, so the actual
effect of multicasting will not be directly seen. But the main
aim here is to reduce the traffic in the network by having a
server which will actually propagate the messages in the
network instead of the client trying to send the message to

19. each of the user on its own. I will be first trying to implement
the client application with the interactions on the command line
rather than trying to make it fancy using an applet or Java
Swing. If time permits I will implement the fancy user interface.
Present system:-
When the existing system was studied, it was found having
some problems, existing system was very time consuming and
was not very efficient. The drawback of the existing system has
resulted in to the development of new system, which is very
user friendly and effective. Existing system was also very low in
performance.
While developing the new system all requirements of the end
user was taken into consideration. These have been maximum
efforts towards overcoming the drawbacks of the existing
system, while the new system was designed & developed.

20. Limitations of present system
 There is no private chatting option had been available.
 Client can connect with the server with the only IP
Address.
 The Performance of existing system s very low.
 The system does not maintain the list of active user.

21. 4
CHAPTER
PROPOSED
SYSTEM

22. PROPOSED SYSTEM
 The system to be developed here is an Chat facility.
 It is a centralized system.
 It is Client-Server system with centralized database server.
 All local clients are connected to the centralized server via
LAN.
 There is a two way communication between different clients
and server.
 This chat application can be used for group discussion.
 It allows users to find other logged in users.

23. Tradeoff between Existing and Proposed System:-
1. No need of Internet connection:
Existing system requires Internet connection; whereas in the
proposed system only Intranet connection i.e. only a LAN connection
is required. This system is useful for those who can not afford to
have an Internet connection. For example: schools, colleges, small
companies, etc.
2. Conference possible on LAN:
Usually on LANs connections conferencing is not possible. The
proposed system allows the LAN users to create and participate in
conference. This makes communications possible among number of
LAN users simultaneously.

24. 5
CHAPTER
SYSTEM STUDY

25. SYSTEM STUDY:-
Existing System Study:-
Currently there is no such system available. The users earlier need to
login into official website. Therefore the need for a chat system
facility was necessary. There is LAN network spread across various
offices, so we can develop software which can work on LAN.

26. SYSTEM ANALYSIS :-
System analysis is the way of studying a system with an eye on
solving its problem using computer. It is the most essential part of
the development of a project of a system analysis. System analysis
consists of system element, process and technology. To analyze a
system, has to study the systems in details.
The analyst has to understand the functioning and
concept of the system in detail, before design the appropriate
computer based system that will meet all the requirements of the
existing system. The system analyst has to carry out a customary
approach to use the computer for problem solving.
The above steps constitute the logical framework for the system
analysis.

27. After the preliminary investigation and feasibility study, the
scope of the defined and comparable items are set forth and hence
detailed investigation is executed. This allows the system analyst to
comprehend the full scope of the project. Soon after the
implementation of the newly developed system, followed by the
training of the users, the system analysis is included.

28. PRELIMINARY INVESTIGATION:-
A request to receive assistance from information system can be
made for many reasons, but in case a manager, employee or system
specialist initiates the request. When that request is made, the first
system activity preliminary investigation begins. The activity has
three parts .
Request clarification: -
the request from employee may not be well stated. Sometimes the
request may not be well defined. Therefore before any system
investigation can be considered, the project request must be
examined to determine precisely the actual requirements of the
organization.

29. Feasibility study:-
the basic idea of feasibility study is to determine whether the
requested project is feasible.
Request approval:
all projects that are requested are not desirable or feasible .some
organization receive so many projects requests from employee that
only a few of them can be pursued. However those projects that are
feasible and desirable should put into a schedule. The management
decides request that are most important. After a project request is
approved the cost priority, the completion time and the personal
required are estimated. Once the request is approved, the collection
of data and determination of requirements can be started.

30. REQUIREMENT SPECIFICATION
The primary goal of the system analyst is to improve the efficiency of
the existing system. For that the study of specification of the
requirements is very essential. For the development of the new
system, a preliminary survey of the existing system will be
conducted. Investigation done whether the up gradation of the
system into an application program could solve the problems and
eradicate the inefficiency of the Existing system.
HARDWARE REQUIREMENTS
Server:-
 128 MB RAM
 PIII and above processors
 2.1 GB Free Space
 Router

31.  NIC Card
 10BaseT Ethernet Card
Client:-
 128 MB RAM
 PIII or above
 1 GB Free Space
 NIC Card
 10BaseT Ethernet Card

32. Software Requirements:
 Operating system-Windows 98 or above.
 JDK 1.6
Network Requirements:
 LAN connection

33. Software Specification
Why java?
 Write once, run anywhere(WORA)
JAVA technology promises you that you only have to write your
application once –for the java platform & then you will able to run it
anywhere (any operating system)
 Security:-
The capacity of java platform allows users to download entrusted
code over a network & run it in secure environment in which can not
do any harm. Because the security guarantee, nearly as strong as
java makes.

34. Network-Centric Programming:-
SUN’s corporatism’s motto has always been ‚The network is the
computer, ‚The designer of the java platform believes in the
importance of Networking & designing the java platform to be
network-center to create network-based application using client-
server or multitier architecture.
 Performance
Java is portable interpreted language java programs runs almost as
fast as native non-portable C & C++.

35.  Programmer efficiency & Time-to-market
Java is an elegant language combined with a powerful & well
designed set of API. Java increases programmer’s efficiency
Why MS-Access?
MSACCESS for windows is a database management system,
that helps us to manage the data stored in the database. Database
Management System is a collection of interrelated data and a set of
program to access data. This collection of data is called the
database. The column heading are called as fields. The rows of data
are called as records.
MSACCESS, a relational database management system enables us
to manipulate data in more sophisticated ways. Relational database

36. management system avoids redundancy in data and defines the
relationship between sets of data.
The data stored in each table can be retrieved and updated based on
other tables. MSACCESS is a relational database management
system designed for the graphical environment .With
Dccess we can perform following tasks:
 Organize data into manageable data related units.
 Enter, locate and modify data.
 Extracts subset of data based on specific criteria.
 Automate command database task.

37. In Access, the term database returns to a single file that contains a
collection of information. A database consists of following objects:
Tables:
In Tables Data are stored in the format of rows and columns. Every
table in a database focuses on one subject. Each row or record in a
table is a unique instance of the subject of the table.
Queries:
Queries extract data from the table on a user defined criteria. They
enable us to view fields from more than one table.

38. Feasibility study
A feasibility study is undertaken to determine the possibility or
probability of improving the existing system or developing a totally
new system. Feasibility study is systematic and thorough study of
the existing system and an attempt to trace out the disadvantages
of the existing system.
Once management accepts the study proposals, it will lead to an
investigation of the existing system or problem area. This
investigation is conducted in close collaboration with user
management and in sufficient depth to establish in broad terms the
technical, operational and economical feasibility of the proposal.

39. The purpose of the LIVE CHAT is to communicate efficiently
between the different users in a local area network and exchange
data between them. The feasibility of this project depends upon a
number of factors such as cost, time, technology etc.

40. NEEDS FOR FEASIBILITY STUDY:
The feasibility study is needed for following things:-
 Answer the questions whether a new system is to be installed
or not?
 Determine the potential of the existing system.
 Improve the existing system.
 Know what should be embedded in the new system.
 Define the problems and objectives involved.
 Avoid costly repairs at later stage when system is
implemented.
 Avoid crash implementation of the new system.
 Avoid the ‘Hardware approach’ i.e. getting a computer first
and then deciding how to use it.

41. The Feasibility study is divided in to three parts:-
 TECHNICAL FEASIBILITY
 ECONOMIC FEASIBILITY
 OPERATIONAL FEASIBILITY
ECONOMIC FEASIBILITY:-
Economic analysis is most frequently used for evaluation of the
effectiveness of the system. More commonly knows as cost/benefit
analysis. the procedure is to determine the benefit and saving that
are expected from a system and compare them with costs, decisions
is made to design and implement the system.

42. This part of feasibility study gives the top management the economic
Justification for the new system. This is an important input to the
management the management, because very often the top
management does not like to get confounded by the various
technicalities that bound to be associated with a project of this kind.
A simple economic analysis that gives the actual comparison of costs
and benefits is much more meaningful in such cases.
In the system, the organization is most satisfied by economic
feasibility.
Because, if the organization implements this system, it need not
require any additional hardware resources as well as it will be saving
lot of time.

43. TECHNICAL FEASIBILITY:-
Technical feasibility centers on the existing manual system of the
test management process and to what extent it can support the
system.
According to feasibility analysis procedure the technical feasibility of
the system is analyzed and the technical requirements such as
software facilities, procedure, inputs are identified. It is also one of
the important phases of the system development activities.
The system offers greater levels of user friendliness combined with
greater processing speed. Therefore, the cost of maintenance can
be reduced. Since, processing speed is very high and the work is
reduced in the maintenance point of view management convince
that the project is operationally feasible.

44. BEHAVIOURAL FEASIBILITY:-
People are inherently resistant to change and computer has been
known to facilitate changes. An estimate should be made of how
strong the user is likely to move towards the development of
computerized system. These are various levels of users in order to
ensure proper authentication and authorization and security of
sensitive data of the organization.

45. 6
CHAPTER
SYSTEM
ANALYSIS

46. The prototyping model:
The mode is used for developing the ‚Exam Tool‛ as the prototyping
model. Prototyping Model is based on the idea of developing an initial
implementation, exposing this to user comment and defining this
through many until an adequate system has been developed.
Benefits of prototyping model:-
The prototyping paradigm begins with requirement gathering.
Developers and customers meet and define the overall objective for
the software, identify the requirements and outline the areas where
further definitions are necessary. The prototype design is often,
quite different from that of the final system.

47. The benefits of developing a prototype early in the software process
are:
 Misunderstanding between software developers and users may
be identified, as the functions are demonstrated.
 Missing user services may be detected.
 Difficult to use or confusing user services may be indentified
and refined.
 Software development staff may find incompleteness and
inconsistency in requirement as the prototype is developed.
 A working albeit limited systems is available quickly to
demonstrate the feasibility and usefulness of the application to
the management.
 The prototype serves as a basis for writing the specification for
a production quality system. Though the principle purpose of

48. prototyping is to validate software requirements, software
prototype also has other uses.
 A prototype system can be used for training users before the
formal system has been delivered.
Prototype can run back-to-back tests. This reduces the need for
tedious manual checking of test run. The same test is given to both
the prototype and the system under test to look for differences in
the final results and thereby making necessary changes. Thus
prototype serves as a technique of risk reduction.

49. Selecting the prototype approach:-
The prototype paradigm can be either close-ended (throwaway
prototyping) or open-ended (evolutionary prototyping). Before
selecting closed or open-ended approach, it is necessary to
determine whether the system to be built is suitable for prototyping
or not. This is decided depending on application area, complexity,
customer characteristics and projects characteristics.
The throwaway is developed to understand the system requirements
while the evolutionary prototype evolves through a number of
versions to the final system.

50. Event table:-
Event Trigger Source Activity Response Destinati
on
User Ask for User User User User
form record selected
Login
User Ask for User Create User User
registra form new user registere
tion record d
User Ask for User Add the Nick User
Nick nick nick name name
name name in the chat saved
list
Ask for Enquire Server Look up IP User
IP for IP for IP address
Address address address checked
User Enquiry User Look up User User
selects for other for other selected
other users users
users
for chat

51. Entity Relationship diagram:-
SERVER
Message passes Server resends the message to
on to the server the respective client or
INTRANETWORK broadcasts it on every
clients screen
The message comes to the
Client sends the message respective client(s) again
to the server via the LAN through the LAN
CLIENT 1
CLIENT N
Preliminary System Design

52. USE Case Diagram:-

53. USE CASE Scripts:-
 Logging as Server-user inserts his personal data (login,
password)
 verification is taking place after submitting data
 verification error is signalized by error message
 if verification doesn’t return error, user is allowed to
system
 Broadcasting Messages called by Server
 Server recived the message from one client and
broadcast it to other client

54.  Logging as a Client- inserts his personal data (login, password)
 verification is taking place after submitting data
 verification error is signalized by error message
 if verification doesn’t return error, user is allowed to
system
 Chatting with multiple client
 Client can chat with multiple client.
 Registration
 Client can add update delete the data from database

55. Activity diagram for Login:-
Enter Username and Password
Submit Username and Password
Verify Username and Password
Invali Login
Valid Login
Redirect to Chat Client Page

56. Activity diagram:-
Enter Username and Password
Submit Username and Password
Verify Username and Password
Invali Login
Valid Login
Redirect to chat Client Page
Login
Select Client or Group
chat

57. Sequence Diagram:-
aSendMessag
eWindow
client
Client
Message()
* write() Server
* recieve()
mssgType :=
getMssgType()
[validMssg]
new aBroadcastMssg
new
LogEntry
| |
| | |
|
| | |
X |
| | |
|
| | |
|
| | |
|
| | |
|
|
|

58. Collaboration Diagram :-
:SendMesseWindow
1 :client Message()
:Client
1.1.1 * receive()
1.1 * write()
:Server
1.1.2:
new
:BroadcastMssg

59. State chart diagram:-

60. Context Level diagram:-

61. Dataflow diagram:-

62. Class Diagram:-
Chat Server Class Diagram:-
ChatServer
ChatLogThread 1
1
ChatServerThread 1
1 1
1 1 ChatSocket
ChatLogBuffer 1 SocketNumber
1 1 ServerConnetionPool Hostname
close()
1 1
getConnection(), broadcast()
1
0..* 1..*
ChatHistoryItem ServerConnection
1
broadcast()
1 1
1 1
ServerSendThread ServerReceiveThread
broadcast()

63. Chat Client Class Diagram:-
ChatClient
MainWindow 1 1
exit() 1
1 1
1
ClientConnectionThread ChatSocket
1 1 1 SocketNumber
Hostname
DisplayTextArea close()
1 1
displayMsg()
1
ClientReceiveThread
1 1
ClientSendThread
SendTextArea
broadcast()

64. 7
CHAPTER
SYSTEM DESIGN

65. Component diagram :-
Main Application
Server GUI
ChatServerInterface
DB Magement
Client GUI
ChatClientInterface
Database

66. System flow chart:-
Live Chat
Server
Client
Maintain
Chatting active user

67. 8
CHAPTER
SYSTEM
CODING

68. List of tables with attributes and constraint:-
Table name : - login
Description : -It contains information of username and assword.
Field Data type Size Constraint Description
username Text 50 Foreign key Keeps the
username of
User
password Text 50 Keeps the
password of
User

69. Table name : - registration
Description :- It contains registration information of User.
Field Data type Size Constraint Description
firstname Text 30 User’s First Name
lastname Text 30 User’s Last Name
gender Text 10 User’s Gender
email Text 30 User’s Email Address
contact Text 10 User’s Contact
number
username Text 30 Primary Key User’s Username
password Text 30 User’s Password

70. Testing & Validations:-
System testing is a critical aspect of Software Quality Assurance and
represents the ultimate review of specification, design and coding.
Testing is a process of executing a program with the intent of
finding an error.
A good test is one that has a probability of finding an yet
undiscovered error. The purpose of testing is to identify and correct
bugs in the developed system. Nothing is complete without testing.
Testing is vital in the success of the system.
In the code testing the logic of the developed system is tested. For
this every module of the program is executed to find an error. To
perform specification test, the examination of the specifications
stating what the program should do and how it should perform
under various conditions.

71. Unit testing focuses first on the modules in the proposed system to
locate errors. This enables to detect errors in the coding and logic
that are contained within that module alone. Those resulting from
the interaction between modules are initially avoided. In unit testing
step each module has to be checked separately.
System testing does not test the software as a whole, but rather
the integration of each module in the system. The primary concern is
the compatibility of individual modules. One has to find areas where
modules have been designed with different specifications of data
lengths, type and data element name.
Testing and validation are the most important steps of the
developed system. The system testing is performed to ensure that
there are no errors in the implemented system. The software must
be executed several times in order to find out the errors in the
different modules of the system.

72. Validation refers to the process of using the new software for the
developed system in a live environment i.e., new software inside the
organization, in order to find out the errors.
The validation phase reveals the failures and the bugs in the
developed system. We will come to know about the practical
difficulties the system faces when operated in the true environment.
By testing the code of the implemented software, the logic of the
program can be examined. A specification test is conducted to check
whether the specifications stating the program are performing
under various conditions.

73. Apart from these tests, there are some special tests conducted
which are given below:
Peak Load Tests:
This determines whether the new system will handle the volume of
activities when the system is at the peak of its processing demand.
The test has revealed that the new software for the agency is
capable of handling the demands at the peak time.
Storage Testing:
This determines the capacity of the new system to store transaction
data on a disk or on other files. The proposed software has the
required storage space available, because of the use of a number of
hard disks.

74. Performance Time Testing:
This test determines the amount of the time used by the system to
process transaction data.
In this phase the software developed Testing is exercising the
software to uncover errors and ensure the system meets defined
requirements. Testing may be done at 4 levels
 Unit Level
 Module Level
 Integration & System
 Regression
 UNIT TESTING

75. A Unit corresponds to a screen /form in the package. Unit testing
focuses on verification of the corresponding class or Screen. This
testing includes testing of control paths, interfaces, local data
structures, logical decisions, boundary conditions, and error
handling. Unit testing may use Test Drivers, which are control
programs to co-ordinate test case inputs and outputs, and Test
stubs, which replace low-level modules. A stub is a 40 dummy
subprogram.

76. MODULE LEVEL :
Module Testing is done using the test cases prepared earlier.
Module is defined during the time of design.
INTEGRATION & SYSTEM TESTING:-
Integration testing is used to verify the combining of the software
modules. Integration testing addresses the issues associated with
the dual problems of verification and program construction. System
testing is used to verify, whether the developed system meets the
requirements.

77. REGRESSION TESTING:-
Each modification in software impacts unmodified areas, which
results serious injuries to that software. So the process of re-testing
for rectification of errors due to modification is known as regression
testing.
Testing Methods:
The box approach Software testing methods are traditionally divided
into white- and black-box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing
test cases.

78. White box testing:-
White box testing is when the tester has access to the internal data
structures and algorithms including the code that implement these.
Types of white box testing
The following types of white box testing exist:
 API testing (application programming interface) - testing of
the application using public and private APIs
 Code coverage - creating tests to satisfy some criteria of code
coverage (e.g., the test designer can create tests to cause all
statements in the program to be executed at least once)
 Fault injection methods - improving the coverage of a test by
introducing faults to test code paths
 Mutation testing methods
 Static testing - White box testing includes all static testing

79. Black Box Testing:-
Black-box test design treats the system as a "black-box", so it doesn't
explicitly use knowledge of the internal structure.
Black-box test design is usually described as focusing on testing
functional requirements. Synonyms for black box include: Behavioral,
functional, opaque-box and closed-box.
A Simple Black box Specification:
Black Box Testing is testing technique having no knowledge of the
internal functionality/structure of the system. This testing technique
treats the system as black box or closed box. Tester will only know
the formal inputs and projected results. Tester does not know how
the program actually arrives at those results.

80. Hence tester tests the system based on the functional specifications
given to him. That is the reason black box testing is also considered
as functional testing.
This testing technique is also called as behavioral testing or opaque
box testing or simply closed box testing. Although black box testing
is a behavioral testing, Behavioral test design is slightly different
from black-box test design because the use of internal knowledge is
not illegal in behavioral testing

81. Test case:
For Login Page
 Cursor position in username field
 Validations for wrong entry of username
 Case sensitivity can be tested
 Cursor back to username field after being shown validation
message
 Cursor position to Password field on pressing Tab key.
 Validations for wrong entry of password.
 Case sensitivity should be tested
 Cursor back to password field after being shown validation
message.
 Focus to Login button on pressing Tab key.

82. 9
CHAPTER
SYSTEM
IMPLEMENTATION

83. System implementation:-
Implementation is the stage of the project where the theoretical
design is turned in to a working system. The implementation state is
a system project in its own right.
It involves careful planning, investigation of the current system and
its constraints on implementation, design of methods to achieve the
changeover, training of staff in the change over procedure and
evaluation of change over methods.
Once the planning has been completed, the major efforts are to
ensure that the program in the system is working properly.
At the same time concentrate on training user staff. When the staff
has been trained a full system can carry out.

84. The various activities involved while implementing a project:-
 End user education and training.
 Training on application software
 System testing
 Parallel run and change over to new system
 Post implementation review

85. 10
CHAPTER
FUTURE
ENHACEMENT

86. FUTURE ENHANCEMENTS:-
The primary application of a messenger is to communicate with
people.
A messenger is useful in the following ways for communication:
 The user can communicate with many people simultaneously.
 The user can transfer files to others.
 Files can also be shared between two or more users.
Communication plays a pivotal role in any organization, whether it is
a business organization, an educational institution or industry.
Besides telephone, emails etc a messenger can be used as an
effective and faster means of communication.
The people in the organization can have a meeting session using the
conferencing facility in the messenger.
Besides this it can also be used as a medium for entertainment.
For e.g. for chatting with friends, conferencing etc.

87. FUTURE ASPECTS:-
 Login session information: We can include a feature in this
application that will keep a record of the user’s login session.
 Profile Database: The profile information of every user can be
stored at the server.
 Login Timeout: This feature allows the user to be logged in only
for a specific time. After this time span ends, the user is
automatically logged out.
 File transferring and sharing: User can transfer one or more
files to other users. A file can also be shared between two or
more users

88. 11
CHAPTER
BIBOLIGRAPHY

89. BIBLIOGRAPHY:-
Books referred
Java: The Complete Reference
- by Herbert Schildt
Introduction to Java Programming
- by Y. Daniel Liang
Internet References:-
www.books.google.co.in
www.howstuffworks.com
www.wikipedia.org
www.javaworld.com
www.sun.com