Mini Project

CERTIFICATE

This is to certify that the project entitled

“LOAD MAIL MANAGEMENT TOOLS”

IS SUCCESSFULLY COMPLETED

BY

SHAIKH MOHAMMAD ALI

OF

MCA-III (B)

ROLLNO -109

Under the Guidance of

Mrs. Yogita .

Date:

Prof. in charge Head of dept

Load Mail Management Tools

Index

Sr.No.

Topic Page No.

1 Introduction 2

2.1 Existing System 3

2.2 Need for System 3

2.3 Scope of System 4

3 Feature of System 4

4 Hardware and Software Specification

5

5 System methodologies 5

6 Detail Introduction 6

7 Objective of the System 6

8 User Requirement 7

9 Problem definition 8

10 Inter Module Interaction 8

11 Development Method 8

12 Feature set 9

13 Need for D DBMS 9

14.1 Use Case Diagrams(server side) 10

14.2 Use Case Diagrams(client side) 11

14.3 Class Diagram 12

14.4 Activity Diagram 13

14.5 Component Diagram 15

14.6 Deployment Diagram 16

14.7 Sequence Diagram 17

14.8 Data Dictionary 18

Allana Institute of Management Sciences 1

1


15 Table Designing 19

16 Overall Description 22

17 Distributed Database Management System

23

Sr.No.

Topic Page No.

18 Feasibility study 23

19.1 Economical Feasibility 24

19.2 Technical Feasibility 24

19.3 Business Feasibility 24

19.4 Operational Feasibility 24

19.5 Motivational Feasibility 25

19.6 Legal Feasibility 25

19.7 Architectural Details 24

20 Input Screen and Output Screen 26

21 Limitations & Enhancements 29

22 Bibliography 29

i) Title of Project : “ LoadMail Management Tools”

ii) Introduction:

The main objective of my project is to provide users with a comprehensive mail management tools that fulfill their need for mail network and load management. The aim of project is to provide the user with a full package which includes mail, load


2


balance service, service analyzer and data management.

iii) Existing System:

Previously there was no such type of the system that supported the automatic mail management tool in the client Computer.

All the incoming mails are managed by client manually on their pc.

Supported to the GUI. File attachment facility was available. Mail sorting facility was available. The decision of what data will be stored on which

machine can’t be dynamically made.

iv) Need for System:

Computer system handles various stages Automatically & Efficiently as it has got Artificial Intelligences.

The Advantages are as follows: 1) Data Storage capacity is large.2) Storage of information is high as compared to

time..3) Retrieving of data is easily done.4) Data can be randomly access able..


3


5) Information access is rapidly done and timely reports can be generated are useful.

6) Management decision is easily made so was decided to computerized system overall over for limitation.

Working hours limitations. Time wastage as well as un utilized

memory. Documents and report storage for

future decision makings for the management.

Server side:

There exists an interactive GUI for the system administrators to add and configure any number of servers to store data (both user-related information and the mail data.)

The decision of what data will be stored on which machine can be dynamically made and also altered as per the system requirements, by the administrator on the server side.

Client Side:

A welcome page that’ll have the options wherein users can either create a new account by filling the registration form or login to an existing account.

An Inbox for each user that’ll have all the previously received messages, and the new ones. The unread messages will be highlighted.

A compose mail page on which mails can be composed and sent along with an attachment of unlimited capacity.

A check mail page on which mails can be viewed along with an attachment browser.


4


v) Scope of project:

Side Administrator enters login id and password checks authenticity access granted if authentic else retries enters password checks authenticity access granted if authentic else Requests the Mail Service and provides

Mail Info establishes connection and sends reprocesses the request displays the requested data on the user screen request for Clustering Service request for checks permission for validates info establishes connection if successful else fails requests for particular checks for permission for particular validate.

If successful , processes request sends back the result displays the processed result on the user

vi) Feature of project:

The Feature of Mail Management Tool is categorized two parts:LoadMail's Business E-Mail solution is designed to address the unique messaging needs of businesses of every size and scope, from small start-ups to Fortune 1000 companies.

Server side:

There exists an interactive GUI for the system administrators to add and configure any number of servers to store data (both user-related information and the mail data.)



5


Client Side:





vii) Hardware and software specification: Software requirements:

WINDOWS NT 4 | 2000 | 9.X | ME

Java,Jsp

WINDOWS 2003 AND ABOVE. MS Access

Hardware requirements:

PIII 500MHZ or above

256 MB RAM

4GB Free Hard disk space

STD Color Monitor

Network interface card or Modem (For Remote Access)

LAN Network (For Remote Sources)

viii) Project Category : Web Based project

ix) Project Methodologies : OOAD


6


Class Diagram E-R Diagram Use Case Diagram (server) Use Case Diagram (Client) Deployment Diagram Activity Diagram Sequence Diagram Component Diagram

x) Detail Introduction:

The main objective of my project is to provide users with a comprehensive mail management tools that fulfill their need for mail network and load management. The aim of project is to provide the user with a full package which includes mail, load balance service, service analyzer and data management.

The client side module provides the end user a client mail application through which a user can mail massages, upload and upload attached files.On the Server side, an Analysis module is provided which can be viewed by the administrator so as to monitor the flow of traffic within the network. This module also provides administrative functions such as monitoring/management of the space (memory) used by the clients

viii) Objective of system: The main objective of this solution is to make easy way

of mail management of any organization.


7


This system is designed by keeping in mind both parties like Administrator & User.

System allows Administrator to register their details like name & address etc. with the system.

On the other hand even it allows Administrator providers to post their requirement with the system to user.

The System also provides full package of Mails, Load Balances, Service Analyzer and Data management.

xi) User Requirement:There are two different kinds of users, which are as follows:

Administrator Client

Administrator:

Side Administrator enters login id and password checks authenticity access granted if authentic else retries enters password checks authenticity access granted if authentic else Requests the Mail Service and provides

Mail Info establishes connection and sends reprocesses the request displays the requested data on the user screen request for Clustering Service request for checks permission for validates info establishes connection if successful else fails requests for particular checks for permission for particular validate.

If successful , processes request sends back the result displays the processed result on the user

Client:


8






: In login form there are following fields: Login ID Password

Once the Login process is completed, job seeker can perform the following functions on next form:

Can Change Password. Can submit File. Can update File. Can Change the personal information. Can give the Feedback Apply to System

xii) Problem definition:

This project involved a lot of research as: We spent a lot of time in deciding upon a

backbone server for our project, and finally came to a conclusion that Web Logic 6.1 would prove to be the best.

Initially we started the development in Java Swing but due many complications, we decided to switch over to JSP i.e. Java Server Pages.

We started with fragmentation of user registration form, but we extended it to mail fragmentation too.

xiii) Inter ModuleInteraction:


9


xiv) Development Method:

The Linear Sequential Model is designed for straight-line development. It is assumed that a complete system will be developed after the linear sequence is completed.

The Linear Sequential Model

xv)Feature Set:Server side: There exists an interactive GUI for the system

administrators to add and configure any number of servers to store data (both user-related information and the mail data.)


Client:

Allana Institute of Management Sciences

Client Server

DataBasebackend

10

10






xvi) Need for DDBMS: Local autonomy: It provides local control on the

database. No reliance on a central site: In case of a failure, when

your data is stored on a centralized system the complete information is lost. Whereas in case of distributed database systems if a particular machine fails only the data stored on that particular machine is lost rather than losing the complete information.

Location independence: Distributed systems are location independent i.e. there is no need to operate on the same machine where the data is stored; you can access it from any of the machines within the scope of the system.

DATA FRAGMENTATION Data fragmentation means the break up of an entity

into smaller logical units of distribution. There are three types of data fragmentation: Horizontal fragmentation: which divides a relation

(table) “”horizontally” by grouping rows to create subsets of tuples, where each subset has a certain logical meaning.

Vertical fragmentation: of a relation, that keeps only certain attributes (columns) of a relation.

Mixed fragmentation: that means both horizontal and vertical partitioning of data.


11


xviii)Use Case Diagram(Server side):

administrator


12

Login

Backup

Start server

Account block

Security

Column dstri

Add cluster node

Delete from cluster

Add to cluster

Delete mail

Add mail

Db conectivity

Validation


xix)Use Case Diagram(Client side):

User


13

updation

Start commnction

Deletion

Compose

Read inbox

Registration

Reply

Forward

Read msg

Save records

Login validation


xx) Class Diagram:


14

Mail server Name:stringAddress:stringSize:int

Adding cluster()Blocking accnt()

Mail server::inbox

UsernameFrmMail dateMsgMsg len

Read inbox()Get colvalue()Delete msg()Set connection()

Mail server::login

Login namepassword

get dsn colum()set dbcnnectn()executequery()

Mail server::registration

Login namePasswordBirthdateCitycountry

get totaldsn()get columdetail()set dbcnnectn()executequery()

Mail server::distribution

Table nameDsnCol name

con()get total dsn()get dsn for col()get dsn id()get col details()

Mail server::compose

Mail idToFrmCcBcc

Count mail()Compose mail()Set conn()

Db con

Db url1

Set conn()


xxi) Activity Diagram:


15

User

Enter username & password

Verify Valid or not

Homepage

Authorized

Registration for New user

New user

No

Yes

Display Main page



16

A

A

Action type

Select

Check mail

Delete

Compose

Logout

Reply Forward


xxii) Component Diagram:

Request to

Request to

Request to

Request to


17

Database

Client

Web Server

ApplicationProgram

Web Browser


xxiii) Deployment Diagram:

Upload

Request


18

Database

Web Server

Client


xxiv) Sequence Diagram:

Request for URL

Display homepage

Registration form

Provide form

Form fill

acknowledgement

Login

verify Display main page

Perform operationi.e.check,delete,compose

store informant in database


19

User Web Server Database


store

Request for logout

Ack. logout

xxv) Data Dictionary:

1.) Table Name: Login form Purpose : For storing login details.

Field Name

Datatype Size Constraint

Description

UserName Text 15 Not NullPrimary Key

User id

Password Text 15 Not Null Password

2.)Table Name: Registration form Purpose: For storing client details.

Field Name Datatype Size

Constraint

Description

Login name Text 15 Not Null Primary Key

Identifier of the User

Password Text 15 Not Null Password of the UserRetype Password

Text 15 Not Null Rentered password

Birthdate Number 10 Not Null Birth date of the customer

Country Text 50 Not null Nationality of the


20


customerCity Text 20 Not null Address city of the

customerName Text 20 Not null Full name of the UserGender Text 20 Not null Gender of the UserState Text 20 Not null State of the Addressed

UserPincode number 10 Not null Pin code of the userEducation Text 10 Not null Education done by

clientOccupation Text 10 Not null Profession of the User

3.) Table Name: Load_bal Purpose: For proper sign out done by user details.

Field Name

Datatype Size Constraint

Description

Sing in Text 15 Primary Key

The identifier of the User

4.) Table Name: Balanced Purpose: Messages send by the customer details.

Field Name Datatype Size

Constraint

Description

To Text 15 Primary Key

Message to be sent by client

Ccc Text 15 Not null Carbon copy of the user name

Bcc Text 15 Not null Black Carbon copy of the user name

Subject Text 20 Not null Request of the customer to be sent


21


xxvi) Table Designing:

1) Mail Server Table Table Name: - Mail Server

Field Name Data type(size)

Constraint Description

Name Text(25) Primary key Administrator First Name

Address Text(100) Not Null Administrator residential address

Size Integer (10) Not null Code size

2) Login Table Table Name: - Login

Field Name Data type(size)


Login name String (25) Primary Key Valid user name

Pass word String(10) Not Null Valid pass word

3) Login Error Table Table Name: - error

Field Name Data Type(size)


Login name String (25) Primary Key Valid user


22


namePass word String(10) Not Null Valid pass

wordError String(10) Not Null Invalid user

name and password

4) Registration Table for Table Name: - registration



Login name String (25) Primary Key Valid user name

Pass word String(10) Not Null Valid pass word

Birth date integer(10) Not Null Birth date of the user

Country Text(10) Not null Nationality of the user

City Text (10) - Address of the client

5) Inbox Table Table Name: - inbox



User name Text(20) Primary Key Name of the user

from Text(50) Not Null Message sending

Mail date Integer(10) Not Null Sending dateMessage String(200) Not Null Message to

be writtenMessage length

String(200) Not Null Status of the messageS – shortL – long


23


6) Check mail Table Table Name: - Checkmail



Mail id Text(40) Primary Key User name Code

From Text(20) Not Null Message receiver

Date Integer (10) Not Null Sent date of the message

Time Integer (10) Not Null Sent time of the message

Subject Text(20) - Message results

7) Compose Table Table Name: - compose



Mail id Text(40) Primary Key User name Code

To Text (20) Not Null Message sender

From Text(20) Not Null Message receiver

Cc Text(20) Not Null Carbon copy of the user name

Bcc Text(1) Not Null Black carbon


24


copy of the uset name

8) Distribution table Table Name: - distribution



Table name Text(5) Primary Key should not be Null

Validation of the Field

Dsn Text(4) Not Null Conncetion between database and server

Column name Text (5) Not Null Headings for the proper fileds

10) Connection Table Table Name: - connection



dburl Text(5) Not Null Connection between data base and server


25


xxvii)Overall Description:

Server Side Interfaces Configuration Page

Client Side Interfaces The main page of the website. The Login page The Login Error Page The Registration Form Page The Inbox The Check Mail page The Compose Mail Page The Attachment Browser Page

xxviii)Distributed Database Management System: Distributed database is a logically interrelated

collection of shared data (and a description of this database) physically distributed over a computer network.

A Distributed DBMS consists of a single logical database that is split into a number of fragments. Each fragment is stored on one or more computers under the control of a separate DBMS, with the computers connected by a communication network.

Users access the distributed database via applications. Applications are classified as those that do not require data from other sites (local applications) and those

that do not require data from other sites (global applications). We require a DDBMS to have at least one

global application


26


xxix) Feasibility Study:

All projects are feasible, provided unlimited resources and infinite time is available. Unfortunately in most of the cases this does not hold true. Thus, it is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time. If project risk is high, then feasibility of producing good software reduces.

Types of Feasibility study:

Economic Feasibility: As far as the economics of the project goes, it is well in reach since almost most of the development tools used are Open source, and the rest are already being used by our sponsoring company.. Moreover, there is no external interfacing with any special hardware; hence there is even no hardware cost.

Technical Feasibility: The project is technically

feasible, as everything has been done starting from the root level and then proceeding to the apex. At no point have we used the concepts that are out of the scope of Bachelor’s Engineering course.

Business Feasibility: The project will be used by BSNL, Pune, and if they want, they can extend it for a nation-wide network. Operational Feasibility: TheProposed system is

beneficial only if it can be turned into information system that will meet the Port requirements.

The proposed system is operationally feasible due to the following reasons:

The system is easy to use as it is very simple.


27


After the system implementation, the user will need no changes as the system is developed by keeping in view the user’s requirements.

The proposed system will prevent unwanted data to be entered into the system.

The new system will attract user attention as it is presentable

Motivational Feasibility: The users of our system need no additional training. Visitors do not require entering password and are shown the appropriate information.

Legal Feasibility: The licensed copy of the required software is quite cheap and easy to get. So from legal point of view the proposed system is legally feasible.

xxx) Architectural Detalis:

This system will be using 3-tier architecture as architectural building block. The third tier (middle tier server) is between the user interface (client) and the database management (server) components. This middle tier provides process management by providing functions such as queuing, application execution and database staging. The three tier architecture is used when an effective distributed client/server design is needed that provides increased performance, flexibility, maintainability, reusability and scalability, while hiding the complexity of distributed processing from the user.

An application requester (client side program) supports the application end of a connection. It transforms a database request from the application into communication protocols suitable for use in the distributed database network. These requests are received and processed by an application server (server side program) at the other end of the connection. Working together, the application requester and application server handle the communication and location considerations so that the


28


application is isolated from these considerations and can operate as if it were accessing a local database.


29


xxxi) Architectural Diagram:


30


xxxii) Input and Output Screen:

Input Screen

Registration formRegistration form


31


Login formLogin form

File AttachmentFile Attachment


32


Output Screen

NotificationNotification

InboxInbox


33


xxxiii) Limitation And Enhancemnet:

Limitation

The limitation of the project is that reports are generated as per the user’s requirement and not for the administrator. Also it doesn’t keep track of the entire detailed information issued to the Client and it doesn’t keep track of the finer detail of the User and its family background.

Enhancement In future, we would like to include a sub system that would

generate individual reports for individual user/administrator.

xxxiv) Bibliography:

We referred the following book to give functionality to our project.

Java Server pages Analysis & Design of Information Systems-James

Senn Mastering Visual Basic 6.0-Unleased Web Logic 6.1


34



35

Mini Project

Documents

data management

mail data

load management

management decision

load mail management

mail service

automatic mail management

mail info