Professional Documents
Culture Documents
Abstract
System shall accept the mails from authorized users providing security. Submitted
messages will be delivered to appropriate person only. Provides the facility to review messages
from the respective folders. Effective Communication has become an integral part of
organizations today. The rapid development of intranets may provide construction and design
teams with an innovative tool for meeting these growing communication challenges.
A project specific intranet uses a database server to store mails information and the
organizational information such as users details including the personal information and
information requests. Teams members can be then access this information using the Ezee Mail
System. As information changes, the server content can be easily updated with new or revised
data. This flexible approach allows geographically remote project teams to access timely,
consistent and accurate information without expensive typesetting, printing, distribution and
mailing charges.
The user can access this mailing system for sending the information to other users of the
same organization. He is also provided with login and logout services, service of checking into
the mails through the inbox, sending the mails using compose service, checking the sent mails
list, creating and deleting the folders in association to the user involved in the communication.
User is also provided with the flexibility of maintaining the address book in the mailing system
through which he can store the details of his contacts. Users of the Ezee Mail System are also
provided with the chance to change the password of his account through the options service
designed.
This system is to be designed with user flexible screens through which user can navigate
through the mailing system and access the above services for the basic purpose of
communication.
Existing System
In the Existing system of communication the data transfer between the different
individuals of the organization in conducting the works for the company is a cost effective and
not a reliable architecture where even the security standards are very low. In the traditional 2-tier
architecture there existed only the server and the client. In most cases the server was only a data
base server that can only offer data. Therefore majority of the business logic i.e., validations etc.
had to be placed on the clients system. This makes maintenance expensive. Such clients are
called as fat clients. This also means that every client has to be trained as to how to use the
application.
The proposed system should have the following features. The Webserver Interface should
be as simple as possible so that the server can be configured easily. The transactions should take
place transparently. The validation code should be placed on the server and not on the client.
This leads to a thin client, which is more desirable. The server should identify the type of request
(GET/POST) and perform appropriate action. It should also identify the file requested
(HTML/CGI) and run the required process at the server if necessary. When responding to the
client, the server should send necessary information such as Content Length, MIME types etc.
Software requirements
Web-Server : Tomcat Server.
Front-end : HTML, JavaScript.
Communication Architecture : Servlets.
Database maintenance : Oracle 8i.
Hardware Requirements:
Hardware Configuration
Pentium III Processor with 700 MHz Clock Speed