Client Server Design Sharing System Project

CLIENT SERVER DESIGN SHARING SYSTEM
Prepared By:
INTRODUCTION
Objective of Project
The aim of this project Client Server Design Sharing System is to provide a communication system within an organization.
This application will be capable of facilitating members of the organization to communicate through text as well as graphical designs. Application has client and server based architecture which allows multiple user to interact with each other individually and in groups at the same time remotely.
Firstly, server listens to all the registered client systems on network and helps each client system to interact with each other. Server Application receives the connection request from the client and will send the intimation to all other the client systems (friend) available on network. It will also manage client sessions. Client Application sends the connection request to the server for session management. Client system sends and receives messages (text/design information) from each other with help of server.
Need of the System

As many of the chat applications are available in the market today but still may wonder how it has been developed. Thus, this is a simple chat application developed in java using a web service. The application targets mainly the beginners of the organization who sometimes fear of using the web service. The members will get a taste of how web service can be easily developed and can be used in a chatting application.
DESCRIPTION
The project I have worked on is the development of a Client Server Design Sharing System. Today java client server application is the primary need of the working personnel specially and other people. We have tried to provide a user-friendly interface for providing a complete solution to the Client Server Design Sharing System.
Characteristics of a client:
Initiates requests. Waits for replies. Receives replies. Supports design sharing. Typically interacts directly with end-users using a graphical user interface.
Characteristics of a server:
Never initiates requests or activities. Listens to network and responds only to requests from connected,authorized clients.
Waits for and replies to requests from connected clients.
Basic Functionality of the system:

Whenever any user logs into the application, a notification window will get popup in all the online user machines from the right corner of the screen to show the name of the new online user.
Whenever the user minimizes the chat window, the new messages will start coming to that user in a popup window from the right corner of the screen. If the user wishes not to get the messages in a popup window he can select a suitable checkbox.
DESIGN
Design Description
Design of the project basically includes two applications namely
Client Application:
Main goal while designing the client is to make it multi-threaded. One thread runs the user interface. A separate thread handles the I/O with the server.
Server Application:
Here also the goal is to make the server multi-threaded. It handles the user interface with one thread. A second thread listens on a well-known port for client connections. A third thread is started when a client connection is made to handle that client's requests. After launching the thread to handle a client's connection, the server continues listening for additional client connections. If another connection comes in while an earlier client is being served, a fourth thread is started to handle the new client's requests, etc. Thus, the server includes at least three threads but may start additional threads for multiple simultaneous connections.
USE CASE DIAGRAM OF LOGIN TO SYSTEM
Server User1
Authentication Process
User2
USE CASE DIAGRAM OF USER PROFILING INFORMATION SHARING

Registration Process
User-Network Profiling Initialization User Server
User-Network Profiling Update
USE CASE DIAGRAM FOR TEXT/DESIGN SHARING
Send Message Parsing Process User1
Server
Forward Send Message
Received Message Parser
User2
SEQUENCE DIAGRAM
USER LOGIN
CLIENT SERVER
Connection Request
Accept Connection
User Credentials and profiling information
Validate Client
Network and Peer profile information
UPDATE CLIENT
CLIENT SERVER
Subscribe User Update Events
Subscribe Network Update Events
Client Update Information
Network Update Information
LOGOFF
CLIENT1 Connection Close Request SERVER NETWORK
Connection Closed
Client Update Event
SYSTEM DEVELOPMENT
TOOL/PLATFORM
A program used for software development or system maintenance. Virtually any program or utility that helps programmers or users develop applications or maintain their computers can be called a tool. Here in our application we are using Textpad (Java).
SOFTWARE REQUIREMENTS
Java (JDK 1.3) Some of the advantages of Java framework are: Consistent programming model Multi-platform applications Multi-language integration Automatic resource management
Ease of deployment
SYSTEM IMPLEMENTATION
HARDWARE PLATFORM
The Client Server Design Sharing System will be available to the Users who are the members of the organization. Therefore the system has two aspects, namely the client and the server.
The Client: The hardware requirements of the client are as follows:
A Local Area Network Connection Color Monitor or any other Visual Display Unit Mouse and Keyboard for User Inputs
The Server: The hardware requirements for the server are as follows:
A minimum of 512 MB of Random Access Memory Connection to LAN
SOFTWARE PLATFORM
The Client: The software requirements of the
client are as follows: Operating System Web Browser
The Server: The software requirements of the

server are as follows: The Java Framework
Glossary
An IP address is a 32-bit number that uniquely identifies each computer physically attached to the Internet. A protocol is a set of rules and standards defining a certain type of Internet communication. A port is a 16-bit number that identifies each service offered by a network server.
A socket is a software abstraction for an input or output medium of communication. A datagram is an independent, self-contained piece of information sent over a network whose arrival, arrival time, and content are not guaranteed.
Thank you

Client Server Design Sharing System Project

Uploaded by

Copyright:

Available Formats

Client Server Design Sharing System Project

Uploaded by

Document Information

Original Description:

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

Client Server Design Sharing System Project

Uploaded by

Copyright:

Available Formats

CLIENT SERVER DESIGN SHARING SYSTEM

Need of the System

Waits for and replies to requests from connected clients.

Basic Functionality of the system:

USE CASE DIAGRAM OF LOGIN TO SYSTEM

USE CASE DIAGRAM OF USER PROFILING INFORMATION SHARING

User-Network Profiling Initialization User Server

User-Network Profiling Update

USE CASE DIAGRAM FOR TEXT/DESIGN SHARING

Send Message Parsing Process User1

Forward Send Message

Received Message Parser

User Credentials and profiling information

Network and Peer profile information

Subscribe User Update Events

Subscribe Network Update Events

Client Update Information

Network Update Information

Client Update Event

A minimum of 512 MB of Random Access Memory Connection to LAN

The Server: The software requirements of the

You might also like