Documente Academic
Documente Profesional
Documente Cultură
On
Developed by
Student Name
(B.Tech IIIrd Year)
Mody Institute of Technology & Science
Guided By
Mr. Devesh Kumar Gupta
(Director)
K.P.I. Pvt. Ltd., Jaipur
Abstract
POJECT TITLE
OBJECTIVE:
The aim of this project is to develop a Chat application using client server
architecture which relies on Socket programming provided by java .
CONTEXT:
there are many client (Geographically spread), at any time, these client can established
their connection to a centralized server and can share their ideas through this chat
application. One to one chat by using private chat is also provided in the developed chat
application.
COMPLEXITY INVOLVED:
Concept of broad cast and private chat.
Concept of enable user and disable user .
Concept view ,edit and delete user record.
Transferring the text
Designing UI by using AWT/SWING.
5. Private Chat Module: : This module is used for private chatting and
display his inbox and outbox.
Constraints:
• Time Constraint: The project should be completed in all aspect
within 30 days.
Functional Requirement:
The main function of project is to develop a chat applet and server application in a
client-server architecture, where a user can choose and chat room. Other than text
user should also be able to send some images for expressing emotions like smile etc.
During a chat session a user should be able to change his room. A user can use public
chat, in which the message sent by one of the user will be send to all the online users
of the same room. A user should be able to select another user for private chat just by
double-clicking on the user name in the list of online users.
Interface Requirement:
It includes two types of interfacing as mentioned.
o Human interface: It includes interfacing with the users i.e. the users who
will be using this software. For human interfacing the front end
development should be user friendly.
It is achieved when all the buttons provided on client side shown tool tips
and having self-explanatory icons remain consistence throughout the
system.
Appropriate help should be provided for the input of information to reduce
input errors.
o Non-human interface: It includes the client server structure. In a client
server model the client requests services and server provides them.
Performance Requirements:
The response time between client and server should be minimum (a few
nano-seconds).
Exception condition/Handling:
This includes the action to be taken for undesired conditions. Proper messages
should be displayed wherever needs for any unauthorized activity. No
duplicate person should be allowed to play with its databases. A message
displays for every event whether it was successful or not.
System Requirements:
Hardware Requirements:
Software Requirements:
AWT/Swing.
JDBC, Database (Oracle/MySQL/MS Access), Print API.
Tool:
About Organization:
The company was established in 2004 with the objective of software development,
consultancy and training. The company has developed Software for various private and
government organizations. The company also provides corporate training.
Applications Developed:
Core Team
Context Diagram
User Authentication Info
and broadcasting
and Private message
Chatting
New Registration
Administrator Request
View list of registered
user.
Can enable disable and
view , edit and delete
records
And also search user.
Chat Client
and Server
Application
Examination
New Registration
System New Registration
Request
Request
Response
User Authentication Info User Authentication Info
and broadcasting and broadcasting
and Private message and Private message
Chatting, Chatting,
Register User
Filling
Loginid , Password
And other Info Databas
e Server
If not Registered
us hat
t
re er
C
es
qu
A
lis dm
Authenticate re t o in c
User an gis f an
an d v tere se
us d r iew d u e
Se er em , e se
User User can Admi ar and ov di r
ch e t
be
Chat n
Request
User Admi Private Chatting for
or
User4
Admin n
User
Broadcasting
Admi
n
Broadcasting
Private
C
For Us hatting Pr
er1 Ch ivat
Us at f e
er or
4
1. Registration Table
S.No Column Name DataType Constraints Description
1. loginid varchar(50) primary key
2. username varchar(50)
3. password varchar(50)
4. phone varchar2(15)
5. emailid varchar2(50)
6. registrationdate varchar2(50)
7. enable_status varchar(20)
8. usertype varchar(20)
9. address varchar(500)