RAPID MAIL SERVICE

PROJECT PROFILE

Project Summary:
• Title:
Rapid Mail and Message Service

• Organization:
Atmiya Institute of Technology and Science.

• Project Guide:
Mr. Jayesh Rathod

• Platform: Frontend: JSP

Backend: MYSQL

Operating System: Windows XP.

• Type of Application:
Web Based Application

• Project Duration:
July-2008 to Oct-2008.

• Submitted By: Joshi Niraj H.

Limbadia Ankit D.

• Submitted To: Mr. Jayesh Rathod

CE DEPARTMENT 1
RAPID MAIL SERVICE

LIMITATION OF OLD SYSTEM

Before 5-6 decades, people have to write a letter and the receiver will get that letter
after 3-4 days. So that was very slow process. In the previous years, there is no security
of the message.

REQUIREMENTS OF NEW SYSTEM

1. To provide mail and message facility to the user.

2. To display the proper information about all users.
3. To provide security for login and password proper.
4. To give good user friendly environment.

CE DEPARTMENT 2
RAPID MAIL SERVICE

 Project Aim

 To provide the Security to the user.

 Very fast service of mailing.

 User can send mails to number of users.

 Project Definition:

Project is on Mail & Message service website made in JSP and the database is
MYSQL.

In this project we made one module of Registration. It also maintain the records of the
person who logs in.

 Project Scope:

This project may be extended up to a level of adding the facility of updating the profile
and dynamically change the image by browsing the file from the system.

This would add up to a 50 percent well developed project as it can be done using one
of the functionalities of your respective back end.

CE DEPARTMENT 3
RAPID MAIL SERVICE

PROJECT ANALYSIS

Analysis is an important part of any project; if analysis is not done properly then whole
project move in the wrong direction. It also provides a schedule for proper project
work.

Analysis task divided into 3 areas:

• Problem Recognition
• Feasibility Study
• Requirement Analysis.

o Problem Recognition:
It is the phase in which the current need for the system is to be defined. This project of
computer peripheral & consumables has all the up to date information. Regarding to all
peripherals and consumables.

o Feasibility Study:
There are 3 types of Feasibility study:

• Technical
• Operational
• Economical
Technical feasibility considers whether the project can be completed within the
available technology. As my project was windows based I get advanced tools that are
available.
Operational feasibility was done to assure that the product would be developed that is
used or not. A computer peripherals & consumables to have a project of its own. So,
that’s not problem for it. Economical feasibility was done to assure that the product
would be developed that is financial feasible for users and developers or not.

CE DEPARTMENT 4
RAPID MAIL SERVICE

o Requirement Analysis:

“These is the basic facilities that the good computer consumable project must require
and all other information that I require with the enhance of usage.”

A complete understanding of software requirement is essential to the success of a

software development effort. No matter how well designed or well coded, a poorly
analyzed and specific program will disappoint user and bring grief to the developers.

The requirement analysis task is process of discovery, refinement, modified and

specification. The software scope, initially established by the system engineer and
refined during software project planning, is refined in detail. Models of the required
data, information and control flow, and operational behavior are created. Alternative
solution are analyzed and various software element.

Both the developer and consumer take an active role in requirement analysis and
specification. The customer attempts to requirement a sometimes nebulous concept of
software function and performance into concrete detail. The developer acts as
interrogator, consultant, and problem solver.

Requirement analysis and specification may appear to be relatively simple task, but
appearances are deceiving. Communication content is very high, chances for
misinterpretations or misinformation abound. Ambiguity is probable. The dilemma that
confronts a software engineer may best be understood by repeating the statement of an
anonymous customer: “I know you believe you’re understood what you think I said,
but I am not sure you realize that what you heard is not what I meant”.

CE DEPARTMENT 5
RAPID MAIL SERVICE

o What does requirement analysis?

Requirement analysis is a software engineering task that bridges the gap between
system levels.
Software allocation and software design. Requirement analysis enables the system
engineer to specify software function and performance, indicate software’s interface
with other system element, and establish constrains that software must meet.
Requirements analysis allows the software engineer (often called analyst in this role) to
refine the software allocation and models of the data, functional, and behavioral,
domains that will be treated by software. Requirement analysis provides the developer
and finally, the requirement specification provides the developer and the customer with
the means to access quality once software is built.

CE DEPARTMENT 6
RAPID MAIL SERVICE

The description of the service and the constraints are the requirement of the system and
processes involved in the requirement engineering are:
• Finding out
• Analyzing
• Documenting
• Checking these services and constrains

CE DEPARTMENT 7
RAPID MAIL SERVICE

SYSTEM ENVIRONMENT

Macromedia Dreamweaver 8 is the professional choice for building web sites and
applications. It provides a powerful combination of visual layout tools, application
development features, and code editing support, enabling developers and designers at
every skill level to create visually appealing, standards-based sites and applications
quickly. From leading support for CSS-based design to hand-coding features,
Dreamweaver provides the tools professionals need in an integrated, streamlined
environment. Developers can use Dreamweaver with the server technology of their
choice to build powerful Internet applications that connect users to databases, web
services, and legacy systems.

MYSQL:

Taking SQL as my database has some reason and they are…

• MYSQL is Data Base Management System.
• MYSQL is relation Data Base Management System.
• MYSQL Software is Open Source.
• It is very fast for implement, reliable and easy to use.
• It is Client/Server means Embedded System.

• Security
All password traffic is encrypted connecting to a server.
A privilege and password system that is very flexible and allows host-based
verification.

CE DEPARTMENT 8
RAPID MAIL SERVICE

SYSTEM ANALYSIS

o Software Specification
Platform: Windows-XP
Front End: JSP
Back End: MYSQL
Designing Tool: Macromedia Dreamweaver 8
Reporting Tool: Macromedia Dreamweaver 8

o Hardware Specification

Server Side:
Pentium 4 or Higher
128 MB RAM
40 GB HDD

Client Side:
Pentium 4 or Higher
128 MB RAM
20 GB HDD

CE DEPARTMENT 9
RAPID MAIL SERVICE

PROJECT SECHEDULING

“Software project scheduling is an activity that distributes estimated efforts to specific

software engineering tasks”.

o Proper Scheduling required:

• All tasks appear in project.
• Efforts and timing are intelligently allocated to each task.
• Interdependencies between tasks are properly indicated.
• Resources are allocated for the work to be done.

 Compartmentalization:
In these we divided the project into following tasks:
• User Interface.
• Data Entry & Retrieval.
• Get an appropriate output.

 Interdependency:
Interdependency of each compartmentalized activities were found out. Some task must
occur in sequence whereas some can occur on parallel.

 Time Allocation:
Each task to be schedule must be allocated some number of work units. In our system,
we start date and completion date is noted in activity charts as file as well as note the
working days in my file.

 Task set
A task set was defined for the project; task set is a collection or work task, milestones
and outcomes that must be accomplished to complete a particular project.

CE DEPARTMENT 10
RAPID MAIL SERVICE

 Defining Adaptation criteria

Adaptation criteria were used to determine the recommended degree of rigor with
which the software should be applied on a project.

 Criteria for the project

• Size
• Mission critical
• Application longevity
• Application requirement
• Stable requirement
• Maturity if technology used
• Re-engineering efforts
• Performance constrains

CE DEPARTMENT 11
RAPID MAIL SERVICE

PROJECT LIFE CYCLE

We choose a linear sequential model, the purpose of this model is that it work parallels
within modules.
This model also called the waterfall models that follow the steps:
 DESIGN
 CODING
 TESTING

 DESIGNING
Designing of system is come after the completion of complete analysis.
The design must be understandable to the system implementer.
The design must be modular to accommodate changes easily.
The analyst must know the latest design tools to assist him in his task.

Cover all this point we try to make designing of project in latest tools Dreamweaver
for easy to design as well as to do changes is also very easy.

 CODING
The coding for any phase needed as the design phase of the project. Coding was the
second major task. Coding was done parallel as with design of the project.
This project cover some difficult coding which is needed to implement in this project
for creating it more user friendly.

Sample code :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<%@page language="java" %>

<%@page import="java.sql.*" %>
<%@page import="java.util.*" %>

CE DEPARTMENT 12
RAPID MAIL SERVICE

<%@page session="true"%>
<%
int i=0;
String mid="";
String ar[]=new String[10];
%>

<%request.setCharacterEncoding("utf-8"); %>
<%--
String arrow=(String)request.getParameter("email");
--%>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>E-Mail.jsp</title>
<meta name="keywords" content="" />
<meta name="description" content="" />
<link href="..//project-JSP/metamorph_ashfire/styles.css" rel="stylesheet"
type="text/css" />
<style type="text/css">
<!--
body,td,th {
font-size: 16px;
}
.style4 {font-size: xx-small}
.style7 {
font-size: 14px;
font-weight: bold;
}
.style10 {font-size: x-large; font-weight: bold; }
.style14 {font-size: large; font-weight: bold; }
.style8 {font-size: large}
.style15 {font-size: 16px}
.style16 {font-size: large; font-weight: bold; font-style: italic; }
-->

CE DEPARTMENT 13
RAPID MAIL SERVICE
</style>
</head>
<body>
<div id="main">
<p>
<!-- header begins -->
</p>
<p>&nbsp;</p>
<div id="menu">
<ul>
<li></li>
<li></li>
<li><a href="index.jsp" title="">Home</a></li>
<li><a href="Services.jsp" title="">Services</a></li>
<li><a href="AboutUs.jsp" title="">AboutUs</a></li>
<li><a href="ContactUs.jsp" title="">ContactUs</a></li>
<li>
<%
String uname=(String)session.getAttribute("Session_name");

if(uname!=null)
{%>
<a href="signout.jsp" title="">Log out :
<%out.print(uname);%>@rapidmail.com</a>
<%
}
%>
</li></ul>
</div>
<p>
<!-- header ends -->
<!-- content begins -->
</p>
<div id="content">
<table width="996" border="0">

CE DEPARTMENT 14
RAPID MAIL SERVICE
<tr>
<td width="109" rowspan="2" align="center" valign="top" bgcolor ="#993300"> <p>
<img src= "NIRAJ_FLASH_Creations/email5.gif" alt="" width="116" height =
"62" /> </p>
</td>
<td height="38" colspan="5" align="center" valign="middle" bgcolor ="#000000"
class="style10 style4"><span class="style14">Welcome to Email Service
</span><span class="style8 style8">... <em><a href="#" title=""><
%=session.getAttribute("Session_name")%></a></em></span></td>
<td width="241" rowspan="4"><div id="right"><div id="login" class="boxed">
<h2 align="left" class="title"><a href="compose.jsp">Compose Mail</a> </h2>
<p align="left" class="title"><strong><a href="email.jsp" class="style15">Inbox
</a><a href="email.jsp"><img src="NIRAJ_FLASH_Creations/arrow_1.gif" alt=""
width="73" height="28" /></a></strong></p>
<p align="left" class="title"><a href="sent.jsp">Sent Mail</a></strong></p>
<p align="left" class="title"><a href="draft.jsp"><strong>Drafts</strong></a></p>
<p align="left" class="title"><a href="Profileview.jsp"> <strong> Profile </strong>
</a></p>
<p align="left" class="title"><a href ="contacts.jsp"> <strong> Contacts</strong>
</a><font size="5"><em>
<label for="uname"></label>
<br />
</em></font> </p>
<div class="content2"></div>
</div>
</div></td>
</tr>
<tr>
<td width="155" align="center" valign="middle" bgcolor="#993300"><span
class="style8">Inbox</span></td>
<td width="202" align="center" valign="middle" bgcolor="#993300"><a
href="email.jsp" class="style7">Refresh</a></td>
<td width="52" align="center" valign="middle" bgcolor="#993300"><input
type="submit" name="nvp_a_tr" value="Delete" /></td>

CE DEPARTMENT 15
RAPID MAIL SERVICE
<td width="146" align="center" valign="middle"
bgcolor="#993300">&nbsp;</td>
<td width="53" height="37" align="center" valign="middle"
bgcolor="#993300">&nbsp;</td>
</tr>
<tr>
<td height="33" colspan="6" bgcolor="#000000"><img
src="NIRAJ_FLASH_Creations/animfrog.gif" alt="" width="703" height="33"
/></td>
</tr>
<tr>
<td height="140" colspan="6" align="left" valign="top">

<form id="form1" method="post" action="">

<table width="677" height="108" border="2" bordercolor="#FFFFFF">

<%
String connectionURL = "jdbc:mysql://localhost:3306/mail";
Connection connection = null;
Statement statement = null;
ResultSet rs = null;
Class.forName("com.mysql.jdbc.Driver").newInstance();
connection = DriverManager.getConnection(connectionURL, "root", "root");
statement = connection.createStatement();
rs = statement.executeQuery("SELECT * FROM inbox_table");
%>
<tr>
<td height="62" class="style8"><em><strong>id</strong></em></td>
<td align="center" valign="middle" class="style16">From </td>
<td align="center" valign="middle" class="style16"> Message </td>
<td align="center" valign="middle" class="style16">Sender Image </td>
<td align="center" valign="middle" class="style16">Time &amp; Date </td>
</tr>

CE DEPARTMENT 16
RAPID MAIL SERVICE

<%

i=0;
while (rs.next())
{
String f1 = rs.getString(1);
String f2 = rs.getString(2);
String f3 = rs.getString(3);
String f4 = rs.getString(4);
String f5 = rs.getString(5);
//try
//{mid=rs.getString(6);
ar[i]=mid;
//}
//catch(Exception ex)
//{
out.println("Exception : "+ex);
//}
if(f2.equals(uname))
{
%>
<tr>
<td width="22"><span class="style7">
</span></td>
<td width="77" align="center" valign="middle" class="style7"><%=f1%></td>
<td width="141" align="center" valign="middle" class="style7">
<form id="form2" method="post" action="read_msg.jsp">
<%=f4%>
<input name="tf1" type="hidden" id="tf1" value="<%=ar[i]%>" size="3" />
<input type="submit" name="Submit" value="open" /></form></td>
<td width="171" align="center" valign="middle">
<img src="image/<%=f1%>.jpg" alt="" width="83" height="56" /></td>
<td width="202" align="center" valign="middle" class= "style7"><label> <
%=f5%></label>&nbsp;</td>

CE DEPARTMENT 17
RAPID MAIL SERVICE
</tr>
<%
}//if
i=i+1;
}//while
rs.close();
%>
</table>
<span class="style7"></a></span>
</td>
<form>
</div>
</div>
<div><div><span class="style7"></a></span>
</td>
</tr>
<tr>
<td height="70" colspan="6">&nbsp;</td>
<td align="center" valign="middle">&nbsp;</td>
</tr>
</table>
</form>
</div>
</div>
<div id="footer">
<p>&nbsp;</p>
</div>
<div style="font-size: 0.8em; text-align: center; margin-top: 1.0em; margin-bottom:
1.0em;">
</div>
</body>
</html>

CE DEPARTMENT 18
RAPID MAIL SERVICE

 TESTING

Testing was done on the regular base during the coding phase itself. Some error that
remains uncovered that is done properly at the time of testing. And we get the required
output that we want. A large amount of situations create while entering the data during
input processing. So, testing is done to get the desired output.

Increment Model of Software Process

Since our project is completely dependent on modules we use the increment model.
Increment development model involves developing the requirements and delivering the
system in the increments.
Incremental development avoids constant changes. Entire system architecture is
established early to act a framework. Systems components are incrementally
developed.

CE DEPARTMENT 19
RAPID MAIL SERVICE

The incremental model combines elements of the linear sequential model (applied
repetitively) with the iterative philosophy of prototyping. As shown in figure, the
incremental model applies linear sequences in a staggered fashion as calendar time
progress. Each linear sequence produces a deliverable “increment” of the software. For
example, word-processing software developed using the incremental paradigm might
deliver basic file management, editing, and document production capabilities in the
second increment; spelling and grammar checking in the third increment; and
advanced page layout capability in the fourth increment. It should be noted that the
process flow for any increment could incorporate the prototyping paradigm.

The incremental process model, like prototyping and other evolution approaches, is
nature. But unlike prototyping, the incremental model focuses on the delivery of an
operational product with increment. Early increments are “stripped down” version of
the final product, but they do provide capability that user and so provides a platform
for evaluation buy the user.

Incremental development particularly useful when staffing is unavailable for a

complete implementation by the business deadline that has been established for the
project. Early increments can be implemented with fewer people. If the core products
can be added the additional staff (if required) can be added to implementation.

CE DEPARTMENT 20
RAPID MAIL SERVICE

PLANNING AND SCHEDULING

“The reality of a technical project is that hundreds of small tasks must occur to
accomplish larger goals”

As we choose this project first of all we refer some website through Internet for getting
information regarding messenger or mailing site. Then secondly we took visit of some
templates of some official website for designing. We collect different form of different
website for clear our idea for Messenger site. Then we make schedule in which in first
one month analysis of this project is being done.

For that we took help of different sites like gmail.com, mailyahoo.com, orkut.com etc.
After completion of analysis we gave my time for designing of this project. It took
around 10 Days.

Then we made code for this project. It took around 1 and ½ month. And for this we
took help of Mr. Jayesh Rathod, HOD assistant of our college as well as I referred
Complete References of Java and Swing and also JSP.

Then after that time we took verification as well as testing of this project. And
complete this much part we complete our project. This whole process took around 4
and ½ month for complete implementation. So it project take around 4 and ½ month
and last some days required for testing as well as modify our project.

CE DEPARTMENT 21
RAPID MAIL SERVICE

SYSTEM DESIGN

User interface:

CE DEPARTMENT 22
RAPID MAIL SERVICE
FLOW CHART

CE DEPARTMENT 23
RAPID MAIL SERVICE
DATA FLOW DIAGRAM

In the course of handling transaction and completing tasks, data are input, processed,
stored, retrieved, used, changed and output. Data flow analysis provides an overview
of what data a system would process, what transformation of data are done, what data
are stored and which stored data are used, and where the result flow. The graphical
representation of the system makes it a good communication tool between a user and a
system analyst on the one hand and system analyst and a system designer on the other.

Data flow design is concerned with designing a sequence of functional transformation

that converts system inputs into the required output. The design is represented as data
flow diagrams. These diagrams illustrate how data flow through a system and how the
output is derived from the input through sequences of functional transformations.

Data flow diagrams are a useful and intuitive way of describing a system. They are
normally understandable without special training, especially if control information is
excluded. They show end-to-end processing; that is, the flow of processing form when
enters the system to where leaves the system can be traced.

• Notation

CE DEPARTMENT 24
RAPID MAIL SERVICE
Logical data flow diagrams can be completed using only five simple notations. They
are,

1) DATA FLOW:
A line with an arrow represents data flows. The arrows show the direction of flow of
data. The name of the data appears next to the line. Data move in a specific direction
from an origin to a destination. The data flow is a “packet” of data.

2) PROCESS:
A circle is used to depict a process. Processes are numbered and given a name.

3) DATA STORE:
A data store stores data. Two parallel lines with square depict a data store. Process may
store or retrieve data from a data store. It indicates operation of writing in the store. If
it points away from the store, it indicates operation of reading form the stores. If both
arrows are there, it indicates that one may write in or read form the store.

4) EXTERNAL ENTITY:
External entities are represented by the rectangle, and are outside the system, such as
vendors or customers with whom the system interacts. The designers have no control
over them. They either supply or consume data. Entities supplying data are known as
sources and those that consume data are called sinks.

5) FILE:

CE DEPARTMENT 25
RAPID MAIL SERVICE

A file stores data. Following symbols depict a file. Processes may stores or retrieve
data from a file. If an arrow points to the file, it indicates operation of writing in the
file. If it points away form the file, it indicates operation of reading the file. If both
arrows are there, it indicates that one may write in or read from the file.

CONTEXT LEVEL-0 DIAGRAM:-

Mail
and Authentication Signed
Message User
New User Create account system

Authentication Enter valid ID and password

CE DEPARTMENT 26
RAPID MAIL SERVICE

CONTEXT LEVEL-1 DIAGRAM:-

User who Request for SMS User who wants

wants to SMS to Mail

Response to Send request

user to server
Mail &
Response to user Message
Request to add/delete msgs. system
Add/Remove
contacts
Update in
Database
Response to user User’s
User’s Inbox
Contacts

CE DEPARTMENT 27
RAPID MAIL SERVICE

USE CASE DIAGRAM:-

R a p id M a il S e r v ic e

c re a te/ m o d ify
m em b er d etail

«ex tends »

s e n d / R e c e iv e m a ils «ex tends »

« e x ten d s »
«ex tends »
« e x te nd s »
u p d a t e p r o f ile
« e x ten d s »
« e x ten d s »
a d m in
«ex tends »
a d d / d e le t e
c o n ta c ts
user

CE DEPARTMENT 28
RAPID MAIL SERVICE

E-R DIAGRAM:-

First Name

Log_id Last Name

End user
Birth Date

Address
Password

Login /
Signup Send Mail

Send Mail
Add /Remove
Receive contacts
Mail

CE DEPARTMENT 29
RAPID MAIL SERVICE

DATA DICTIONARY

A data dictionary, as defined in the IBM dictionary of computing is a “centralized

responsibility to other data, origin, usage, and format this typically includes the names
and description of various tables and fields in each database, plus additional details,
like the names and length of each data element this typically includes the names and
description of various tables and fields in each database, plus additional details, like
the type and length of data element.

User_Info:
This user_info table shows the basic information of the user. This information is being
filled by user when new user wants to register in the mail messenger or want to update
the profile or create a new account.

Variable Name Data type Primary key Not Null

fname VARCHAR(30) No Yes
lname VARCHAR(30) No Yes
gender VARCHAR(10) No Yes
birth_dd INTEGER No Yes
birth_mm INTEGER No Yes
birth_yy INTEGER No Yes
login_name VARCHAR(30) Yes Yes
password VARCHAR(30) No Yes
seq_que VARCHAR(100) No Yes
answer VARCHAR(45) No Yes
sec_email VARCHAR(100) No Yes
location VARCHAR(45) No Yes

CE DEPARTMENT 30
RAPID MAIL SERVICE
Contacts:

Variable Name Data type Primary key Not Null

ses_name VARCHAR(50) No Yes
fname VARCHAR(50) No Yes
Lname VARCHAR(50) No Yes
Login_id VARCHAR(100) No Yes

Inbox_table:

Variable Name Data type Primary key Not Null

Fr VARCHAR(50) No Yes
To VARCHAR(50) No Yes
Msg VARCHAR(1000) No Yes
Sub VARCHAR(1000) No Yes
Time1 VARCHAR(1000) No Yes
Msg_id VARCHAR(1000) Yes Yes

Drafts_table:

Variable Name Data type Primary key Not Null

Fr VARCHAR(50) No Yes
To VARCHAR(50) No Yes
Msg VARCHAR(1000) No Yes
Sub VARCHAR(1000) No Yes
Time1 VARCHAR(1000) No Yes
Msg_id VARCHAR(1000) Yes Yes

LAYOUTS

1.) Welcome Page (Home Page)

CE DEPARTMENT 31
RAPID MAIL SERVICE

 This page is the home page of our project.

 Here signed user can sign in by just entering ID and Password.
 New user can sign up.
 If registered user had forgotten the password then the user can get password back
by just remembering the security question and its appropriate answer.

2.) New User Signup Page

CE DEPARTMENT 32
RAPID MAIL SERVICE

 New user can create an account to register for the mail service.
 Here all the fields are compulsory and the validations are required according to the
specification given on the page.

3.) User’s Account has been created successfully

CE DEPARTMENT 33
RAPID MAIL SERVICE

 If all the validations are correct then user will get this page which shows the
successful registration of the user.
 From here user can continue with his account.

4.) User is successfully logged in

CE DEPARTMENT 34
RAPID MAIL SERVICE

 Here user can use the facility of sending mail to the one or more persons.
 User can also check his/her inbox as well the contacts, profile etc.

5.) User’s Inbox Page

CE DEPARTMENT 35
RAPID MAIL SERVICE

 This page shows the inbox which describes the messages that are received by the
user.
 Here user can get the feature of deletion of the one or more message(s).
 User will get the user photo ID & Received message’s date and time.

6.) User’s Sent Mails

CE DEPARTMENT 36
RAPID MAIL SERVICE

 This page shows the details of the mails that are sent by the user.
 It also shows the image of the receiver.
 This list of messages can also be deleted by the user.

7.) Compose Mail Page

CE DEPARTMENT 37
RAPID MAIL SERVICE

 This page is the compose mail page through which user can compose the mail and
also define to whom he/she wants to mail.
 This page also describes the subject of the message and save it in the sent mail
page.

8.) User’s Profile

CE DEPARTMENT 38
RAPID MAIL SERVICE

 This Page shows the profile of the user.

 This page cannot be edited.

9.) Update in User’s Profile

CE DEPARTMENT 39
RAPID MAIL SERVICE

 Here user can edit his/her profile.

 He or she can change the photo of him/her.
 Also can change the password.

10.) Upload user’s image from the file folder

CE DEPARTMENT 40
RAPID MAIL SERVICE

 In Profile edit page user can upload his/her image from the file/folder.

11.) Draft box for the saved messages

CE DEPARTMENT 41
RAPID MAIL SERVICE

 This page shows the draft box of the user.

 This draft box contains the messages which are saved but not sent.

12.) Read draft messages from READDRAFT page

CE DEPARTMENT 42
RAPID MAIL SERVICE

 This page is used to read the drafts of the particular user who has signed in.
 These drafts can be sent to one or more users.

13.) User’s Contacts page

CE DEPARTMENT 43
RAPID MAIL SERVICE

 This page is the contact page which describes the user’s contacts.
 This page also includes the facility of deleting one or more contacts

14.) Add Contacts page

CE DEPARTMENT 44
RAPID MAIL SERVICE

 This page is opened when user want to add new contacts to his/her address
book.

15.) Services provided by the software product

CE DEPARTMENT 45
RAPID MAIL SERVICE

 This page shows the services provided by the software product.

16.) About us page describes the software product

CE DEPARTMENT 46
RAPID MAIL SERVICE

 This page is providing the information of the product and its all facilities.

17.) Contact us page informs about the designer

CE DEPARTMENT 47
RAPID MAIL SERVICE

 This page shows the contacts of the designer of the software.

TESTING
Testing represents an interesting anomaly for the software engineering activities, the
engineer attempts to build software from an abstract concepts to a tangible product.

CE DEPARTMENT 48
 RAPID MAIL SERVICE
Now comes testing. The engineer creates a series of test case that are intended to
“demolish” the software process that could be viewed (Psychologically, at least) as
destructive rather than constructive.

• Testing objectives:
1) Testing is a process of executing a program with the intent of finding an error.
2) A good test case is one that has probability of finding an as-yet-undiscovered error.
3) A successful test is one that uncovers an as-yet-undiscovered error.

These objectives imply dramatic change in viewpoint. They move counter to the
commonly held view that a successful test is one in which no errors are found.

• Integration testing:
After our individual classes were out we go to the integrated to create a complete
system. This integration process involves building the system and testing the resultant
system for problems that arise from component interactions. We have applied top-
down strategy to validate high-level components of a system before design and
implementation have been completed. Because, our development process started with
high-level component and we worked down the component hierarchy.

TIME LINE CHART:-

Date/ 27th 4th 11th 18th 26th 1st 9th 16th 23rd 30th 6th 13th
Activities july Aug Aug Aug Aug Sep Sep Sep Sep Sep Oct Oct-
-3rd -10th -17th - - - 8th - - - - 5th - 20th

CE DEPARTMENT 49
 RAPID MAIL SERVICE
Aug Aug Aug 25th 31st Sep 15th 22nd 29th Oct 12th Oct
Aug Aug Sep Sep Sep Oct
Feasibility
Study
System
Analysis
System
Specification
Requirement
Analysis
Design
Coding
Testing
Implementin
g
Maintenance

FUTURE ENHANCEMENT

I would like to introduce this topic in future as:

CE DEPARTMENT 50
RAPID MAIL SERVICE
- Only by one click we can do send a SMS and also Mail from one user to the
other and also that message or mail will be received on the user’s ID as well as on the
user’s given mobile numbers. User can also send mail or message through the mobile
phones to the mail server by just activating the GPRS settings.

BIBLIOGRAOHY

CE DEPARTMENT 51
RAPID MAIL SERVICE
Adaptation by trial and error is sometimes treated as if it were merely one way of
adaptation, and inferior way at that. The argument given above shows that the method
of trial and error holds a much more fundamental place in the methods of adaptation.
The argument how, in fact, that when the organisms has to adapt (to get its essential
variables within physiological limits) by working through an environment that is of
the nature of a Black Box, then the process of trial and error is necessary, for only such
a process can elicit the required information.

The number of trial necessary to arrive at a new construction is commonly so great,

that, without something of an affection, or fascination, for the subject, one grows
weary of the task. The patient thought of the naturalist desirous of rising to new
classification, grows out of his liking for the subject, which makes it to him a sweet
morsel rolled under the tongue, and gives an enjoyment even to fruitless endeavors.

Creative through must always contains a random component. The exploratory process
the endless trial and error of mental progress can achieve the new only by embarking
upon pathways randomly presented, some of which when are somehow selected for
something like survival.

Evolution requires variation and selection. So does ontogenetic development. Both are
essential for learning to occur.

REFERENCES

CE DEPARTMENT 52
RAPID MAIL SERVICE
• http://javadoc.com
• www.daniweb.com
• www.sourcecode.com

For Layout
• www.layoutcodez.com

References books utilized

• Complete references of java
• SQL (oracle)

CE DEPARTMENT 53