Web Mail Processor

WEB MAIL PROCESSOR
MAIL TRACKER
INTRODUCTION
 An email address so that your incoming

messages stores at the right place
 A private mail storage area that will hold
incoming messages until they get read
 Secure access to that area with username
and password
 It also provides an area for you to store
messages once they are read.
KEY GOALS OF THIS PROJECT:
 Fully compatible with Internet messaging standards.
 Allow message access and management from more
than one computer.
 Client needs no knowledge about the server's file
store format.
 The protocol checking for new permanently removing
messages, setting and clearing flags, selective
fetching of message attributes, texts and portions for
efficiency.
Introduction to Modules
ADMIN
User
Inbox.
Outbox.
Checking mails.
Composing
Deleting the unnecessary mails.

Admin
Admin is the one who is going to monitor all the users and
grant or deny permissions to any user.
Admin can have the information related to the

user like what the entire transactions user is doing.
User may do many transactions like sending and receiving mails

as the information accessed is related to the company.
As the information related to the company

should be kept confidential and should be accessed only to the prescribed
persons so the admin has to monitor all the user transactions.
User
 He can get into system with the authentication
and can access all the information related to

his id that is nothing but mailing services.
 He can do all the functionalities of the system
and at the same time he can utilize all the

services of the mailing server.
 He can send the mail or receive the mail and
read what ever features mailing server

provides the user can utilize all those services.
 SYSTEM ANALYSIS
 Definition and reason for Condition Analysis
 System analysis will be performed to determine if it is
feasible to design an information based on policies and
plans of the organization and on user requirements and to
eliminate the weaknesses of the present system.
 General requirements
 The new system should be cost effective.
 To augment management, improve productivity and
services.
 To enhance User/System interface.
 To improve information qualify and usability.
 To upgrade system’s reliability, availability, flexibility and
growth potential.
 Identification of Need
 Existing System (problems)
• Now days there are many mail servers which are
providing the mailing the systems to the users. By using
these servers we can send, receive or do all the mailing
services. But the problem with that we can’t view the
information of the user’s transactions because it is very
much important for an organizations like Call Centre.
Unfortunately no mail server is providing such option.
 Proposed System
• As the TRACKER project is developed using JAVA Html,
Servlets and JSP it provides a user friendly graphical user
interface which navigates user through out the program by
providing various task related to internet mail messaging
facilities when connected to a mail server.
 Key Goals of This Project (Advantages)
• Fully compatible with Internet messaging standards.
• Admin can keep track of all the user transactions
irrespective of their usage and designation.
• This TRACKER is going keep track of all the users’
transactions from the time of login to the time of logout.
• Allow message access and management from more than
one computer.
• Client needs no knowledge about the server's file store
format.
• The protocol checking for new messages, permanently
removing messages, setting and clearing flags, selective
fetching of message attributes, texts, and portions thereof
for efficiency.
 Feasibility Study
 Technical Feasibility
 Evaluating the technical feasibility is the trickiest
part of a feasibility study. This is because, at this
point in time, not too many detailed design of the
system, making it difficult to access issues like
performance, costs on (on account of the kind of
technology to be deployed) etc. A number of
issues have to be considered while doing a
technical analysis.
 Before commencing the project, we have to be
very clear about what are the technologies those
are required for the development of new system.
 OPERATIONAL FEASIBILITY
 Proposed projects are beneficial only if they can be
turned into information systems that will meet the
organizations operating requirements. Simply stated,
this test of feasibility asks if the system will work
when it is developed and installed.
 Have the user been involved in the planning and
development of the project?
 Early involvement reduces the chances of resistance
to the system and in
 General and increases the likelihood of successful
project.
 Since the proposed system was to help reduce the
hardships encountered
 ECONOMIC FEASIBILITY
 Economic feasibility attempts 2 weigh the costs of developing

and implementing a new system, against the benefits that
would accrue from having the new system in place. This
feasibility study gives the top management the economic
justification for the new system.
 A simple economic analysis which gives the actual comparison

of costs and benefits are much more meaningful in this case.
In addition, this proves to be a useful point of reference to
compare actual costs as the project progresses. These could
include increased customer satisfaction, improvement in
product quality better decision making timeliness of
information, expediting activities, improved accuracy of
operations, better documentation and record keeping, faster
retrieval of information, better employee morale.
 Functional Requirements
 Inputs
 The major inputs for this application can be categorized
module -wise. Basically all the information is managed by the
software and in order to access the information one has to
produce their identity by entering the user-id and password.
 Every user has their own domain of access beyond which the
access is dynamically refrained rather denied.
 Output
 The major outputs of this system are user details and services
of different departments. Links are created dynamically to
meet the requirements on demand. Reports, as it is obvious,
carry the gist of the whole information that flows across all
the services.
 This application must be able to produce output at different
modules for different inputs.
 Performance Requirements
 Performance is measured in terms of reports generated
according to the requirements.
 Hardware Requirements
 Processor : Intel Pentium III or more
 Ram : 256 MB or more
 Cache : 512 KB
 Hard disk : 16 GB hard disk recommended for
primary partition
 Software Requirements
 Operating system : Windows 2000 /XP or later
 Front End Software : jdk1.5.0
 Back End Software : oracle 10g
 Technologies : Servlets, jsp, html, css, js, xml
 Servers : tomcat 5.6.0
 Design Document
• The entire system is projected with a physical diagram
which specifics the actual storage parameters that are
physically necessary for any database to be stored on to
the disk. The overall systems existential idea is derived
from this diagram.
• The relation upon the system is structure through a
conceptual ER-Diagram, which not only specifics the
existential entities but also the standard relations through
which the system exists and the cardinalities that are
necessary for the system state to continue.
• The content level DFD is provided to have an idea of the
functional inputs and outputs that are achieved through
the system. The system depicts the input and out put
standards at the high level of the systems existence.
DIAGRAMS
• Use case Diagrams
• A use case is a set of scenarios that
describing an interaction between a user
and a system. A use case diagram
displays the relationship among actors
and use cases. The two main
components of a use case diagram are
use cases and actors.
 A use case is an external view of the
system that represents some action the
user might perform in order to complete a
task
 Classes are composed of three things: a
name, attributes, and operations. Below
is an example of a class.Classes are
composed of three things: a name,
attributes, and operations. Below is an
example of a class.
ER-Diagrams
Receiver
subject Sender
msg
Compose
Loginid Pwd
Admin Server Inbox
subi name
msg date
User
pwd Name
emaild Addre
 Conclusion
 Unique Features of the Project
 The System automatically Track all the user transactions.
 It gives the complete online mailing standards to the user and
organization
 The system includes various modules, which will help us to maintain
the Information about the Client’s Transaction . Hence, the Client
need not maintain any other system for maintaining their records.
 Scope for Expansion
 The project Tracker can be expanded to full pledged Mail Server
which can be implemented at any organization or on any server. We
can also implement the Messaging services with use of Mobile
Technology & Web Technology in this application. Tracker can
maintain all the transactions of the user so we can also take the
complete transactions done by the user from log in to log out.

Web Mail Processor

Uploaded by

Copyright:

Available Formats

Web Mail Processor

Uploaded by

Document Information

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

Web Mail Processor

Uploaded by

Copyright:

Available Formats

WEB MAIL PROCESSOR

 An email address so that your incoming

Deleting the unnecessary mails.

Admin can have the information related to the

User may do many transactions like sending and receiving mails

As the information related to the company

and can access all the information related to

and at the same time he can utilize all the

read what ever features mailing server

 Economic feasibility attempts 2 weigh the costs of developing

 A simple economic analysis which gives the actual comparison

Admin Server Inbox

You might also like