INTRA MAILING SYSTEM

CONTENTS

1. ABSTRACT

2. INTRODUCTION

3. DESIGN PRINCIPLES & EXPLANATION

3.1. MODULES

3.2. MODULE DESCRIPTIOIN

4. PROJECT DICTIONARY

4.1. UML DIAGRAMS

4.2. DATA DICTIONARY

5. FORMS & REPORTS

5.1. I/O SAMPLES

6. BIBILIOGRAPHY
1. ABSTRACT

This project INTRAMAILING SYSTEM aims of providing a good

communication interface for the organization. It can cut down the time of
employees spend on routine communication tasks. Its successful
implementation makes easy the job of employees in the organization.
The basic problem is that the employees in the organization
communicate or make correspondence only through post, as their units are
located in remote areas. This method of communication is very slow in
nature and it is not reliable.
Therefore the solution for this problem is to develop a
communication channel that meets the need of the organization. Basically,
the computerized solution is for improving the services as well as self-
efficiency of the computer.
The objective of the system is for meeting the needs of the
employees in the organization for communicating with each other within
their units. This application provides basic requirements such as Mail
management, File transfer and instant messaging. It also has enhanced
features like web browsing and utilities.
The Intra-mailing System is very user-friendly application.
Only certain applications like system monitoring instant messaging,
chatting between two users needs a little training.
2. INTRODUCTION

This company has different departments situated in different

locations. It has four offices and three sites (factory). These are situated at
different places and have a minimum distance of 15 Km.

The basic problem is that they communicate or make

correspondence only through post as their units are located in remote
areas. This method of communication is very slow in nature and it is not
reliable.
Therefore the solution for this problem is to develop a communication
channel that meets the need of the organization. Basically, the
computerized solution is for improving the services as well as self-efficiency
of the computer.

This project INTRA MAILING SYSTEM aims at providing a good

communication interface for the organization. It can cut down the time of
employees spend on routine communication tasks. Its successful
implementation makes easy the job of employees in the organization.

This application provides facilities like mails, instant messages and

allows employees to communicate more effectively, and access the
resources they need to maximize their day-to-day productivity. It provides
fast and better access to up-to-date information.
MAIL:
Intra mailing facility allows organizations with simple intranet to
exchange emails internally without the need of an Internet connection, in
which
(a) Usually text is transmitted,
(b) Operations include sending, storing, processing, and receiving
information,
(c) Users are allowed to communicate under specified conditions, and
(d) Messages are held in storage until called for by the addressee.
Intra Mailing System is the system which is used to establish
online communication among the employees of an organization at different
branches and within the organization between the departments. The
employees of the organization can send mails to each other in the working
in different departments at different locations.
The purpose of “Intra Mailing System” is, an employee of a
company can send and receive mails only in that organization’s Local Area
Network or Wide Area Network. It will work like Internet mailing system for
this intranet.

PURPOSE:
The purpose of this document is to describe all the external
Requirements of the Intra Mailing System. It also describes interfaces for
the system it is:

1. To serve as a basis for the users to confirm that the results of the study
phase are acceptable to them.
2. To serve as a basis for the design phase of the project.
3. To serve as a basis for monitoring the progress of the entire project with
reference to the Intra Mailing System.
4. To serve as the basis for the acceptance testing of the application
system with reference to the functional requirements.
5. To document the functions, the proposed system is to perform without
actually going into the implementation details.
SCOPE:
This document describes the requirements of the system. It is meant
for use by the developers, and will also be the basis for validating the
final system. Any
Changes made to the requirements in the future will have to go through
a formal change approval process. The developer is responsible for
asking for clarifications where necessary and will not make any
alterations without the permission of the client.
3. DESIGN PRINCIPLES & EXPLANATION

3.1. MODULES

This project consists of two modules.

1. Administration Module.
2. Mailing Module.
3.2. MODULE DESCRIPTIOIN

Administrator:

• In administrator module we have five options.

1. Generate User.
2. Delete User.
3. Check Mail.
4. Send Mail.
5. Show Users

When the administrator select the option generate user, he will

creates a new user id and password for the new user. When the
administrator selects the option Delete User, he will delete an existing user
if not necessary.
When the administrator selects the send mail option, then the form
will be opened for sending mail. Then the admin send mail to any other
user who has a user id in the organization. In check mail option, the admin
check for the mails. If the user has any mails, then the mails are displayed.
He will check the mails and delete the unnecessary mails. If the user has
no mails then the message No Mails is displayed. . When the admin selects
the show user’s option, then the number of users who are currently logged
on is displayed. This page automatically refreshes after every 5 seconds to
give the current users list.
Normal User:

• In user module we have two options.

1. Send Mail.
2. Check Mail.

When the user selects the send mail option, then the form will be
opened for sending mail. Then the user can send mail to any other user
who has a user id in the organization. In check mail option, the user can
check for the mails. If the user has any mails, then the mails are displayed.
He will check the mails and can delete the unnecessary mails. If the user
has no mails then the message No Mails is displayed.
4. PROJECT DICTIONARY

4.1. UML DIAGRAMS

USE CASE DIAGRAM

Login Process

Branch User Check

Process Organization

Mail Check
Process

Other Options

User Admin

CLASS DIAGRAM
 Enter
User Login

has
Accessing

User Details Mails

Normal Admini
User strator

STATE DIAGRAM
 Check UID User ID
Check ID Ok Initiate:
Do: User id/
Do: Mails,
Admin
Compare Check
id
ID

Administrator
ID not ok

Unacceptable
ID
Do: Repeat Create:
New User
 SEQUENTIAL DIAGRAM

Musers Mails

(User id, password)

User

User Request

Mails Access Report

 Muser
New User
(User id,
Password)

Admin
user
User Request

New User Details

4.3. DATA DICTIONARY

Table name: Musers

Description: contains all existing users in the organization.

Field Name DataType and Size

Userid Varchar2(10)
Password Varchar2(10)
Catid Varchar2(3)

Table Name: Minbox

Description: contains all mails send by the users.

Field Name DataType and Size

Userid Varchar2(10)
Sender Varchar2(10)
Mail Varchar2(200)
Mdate Date
Mailid Number(6)

Table Name: Clogin

Description: Contains all the user currently logged on.

Field Name Data Type and Size

Userid Varchar2(10)

Table Name: Cat.

Description: Contains the categories of the employees.

Field Name Data Type and Size

Catid Varchar2(3)
Catname Varchar2(10)

5. FORMS & REPORTS

5.1. I/O SAMPLES
6. BIBLIOGRAPHY

1. C.J.Date-
An Introduction to Database System---Narosa
Publications- 1998
2. David Cockmen-
Oracle Database Development
- Tech Media - 1997
3. Joseph Schmuller-
Teach Yourself UML in 24 Hours
- Techmedia
Publications-1999
4. Pankaj Jalote-
Integrated Approach to
Software Engineering
-Narosa
Publication- 1998
5. Orielly-

Java Servler Pages

6. Patrick Naughton, Herbert schildt-

The Complete Reference Java2

TATA Mc
-GRAW HILL Edition, 1998