0% found this document useful (0 votes)
19 views49 pages

Mail Received Authentication System

Uploaded by

jashuj885
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views49 pages

Mail Received Authentication System

Uploaded by

jashuj885
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 49

A Mini Project Report on

MAIL RECEIVED AUTHENTICATION SYSTEM

submitted in partial fulfillment for award of the degree of Bachelor of Technology in

Computer Science and Engineering

by

Thigulla Shivani 18325A0516

Boddu Srilekha 18325A0520

Vemula Swetha 18325A0522

Under the esteemed Guidance of

Internal Guide

MS. AVS. RADHIKA

Assistant Professor (CSE)

Bhoj Reddy Engineering College for Women


Department of Computer Science and Engineering
(Sponsored by Sangam Laxmibai Vidyapeet, approved by AICTE & affiliated o JNTUH)
Vinaynagar, IS Sadan Crossroads, Hyderabad – 500 059
Ph: +91-40-2453 7282; Website: www.brecw.ac.in; Email: [email protected]

2020- 2021
Bhoj Reddy Engineering College for Women
(Sponsored by Sangam Laxmibai Vidyapeet, approved by AICTE & affiliated to JNTUH)
Vinaynagar, I S Sadan Crossroads, Hyderabad 500 059, Telangana
Telephone: 040-2453 7282, Website: www.brecw.ac.in, Email: [email protected]

Date: 6th February 2021

CERTIFICATE
This is to certify that the Mini Project Report entitled “MAIL RECEIVED
AUTHENTICATION SYSTEM” is a bonafide work carried out by

Thigulla Shivani 18325A0516

Boddu Srilekha 18325A0520

Vemula Swetha 18325A0522

in partial fulfillment for award of the degree of Bachelor of Technology in Computer


Science and Engineering department from Bhoj Reddy Engineering College for Women,
Hyderabad, affiliated to Jawaharlal Nehru Technological University Hyderabad
(JNTUH).

Internal Guide Head of the Department


MS. AVS. RADHIKA N Satyanandam

External Examiner

Sangam Laxmibai Vidyapeet is an educational society for promotion of education among girls and women.
It is established in 1952 and registered under the Telangana Societies Registration Act.
ACKNOWLEDGMENT

It is our pleasure to express our whole-hearted thanks to Mr N Satyanandam, Associate


Professor & Head of Computer Science and Engineering Department for providing the
necessary facilities to undergo this project.

We are thankful to our project coordinator Mrs M Vineela, Associate Professor, Computer
Science and Engineering Department, for giving us this opportunity to do this project.

We are also thankful to our internal guide Ms AVS Radhika, Assistant Professor, Computer
Science and Engineering Department for her extreme guidance and support in completing this
project successfully.

We express our deep sense of gratitude to our external project guide Conscience
Technologies, for having permitted us to carry out the project work in their institute and for
their valuable guidance and supervision at every stage.

We are also thankful to the staff members of Computer Science and Engineering department,
my friends and to our parents who helped us in completing this project successfully.

By

Thigulla Shivani (18325A0516)

Boddu Srilekha (18325A0520)

Vemula Swetha (18325A0522)


Contents
Page No
List of Figures i
List of Tables ii
Abstract iii
1. Introduction 1-2
1.1 Introduction of the project 1
1.2 Scope 1
1.3 Existing system 1
1.4 Problems in existing system 1
1.5 Proposed system 1
1.6 Advantages of proposed system 2
2. Requirements Analysis 3-6
2.1 Functional requirements 3
2.1.1 Admin 3
2.1.2 User 3
2.2 Non functional requirements 3
2.2.1 Performance 4
2.2.2 Reliability 4
2.2.3 Scalability 4
2.2.4 Portability 4
2.2.5 Usability 4
2.3 Computational resource requirements 5
2.3.1 Software requirements 5
2.3.2 Hardware requirements 5
2.4 Life cycle model 6
3. Design 7-15
3.1 Architectures 7
3.1.1 Software Architecture 7
3.1.2 Technical Architecture 8
3.2 UML Diagrams 9
3.2.1 Use case diagrams 10
3.2.2 Class diagram 11
3.2.3 Sequence diagrams 13
3.2.4 Activity diagrams 15
4. Implementation 16-20
4.1 Technologies 16
4.2 Pseudo code 18
4.2.1 Composing a mail 18
4.2.2 Status of Composed mail before receiver view 19
4.2.3 Status of composed mail after receiver view 20
5. Testing 21-23
5.1 Overview of Testing 21
5.2 Dimensions of Testing 21
5.3 Test cases 23

6. Screenshots 24-31
7. Conclusion and Future scope 32
8. References 33
List of Figures

S. No Figure Name Fig. No Page No


1 Waterfall model 2.1 6

2 Software Architecture 3.1 7

3 Technical Architecture 3.2 8

4 Use case diagrams 3.3-3.4 9-10

5 Class diagram 3.5 10-11

6 Sequence diagrams 3.6-3.7 11-13


7 Activity diagrams 3.8-3.9 14-15

8 Screenshots 6.1-6.15 24-31

i
List of Tables

S. No Table name Table. No Page. No


1 Registration 3.1 15

2 Sent Mail 3.2 15

3 Receive Mail 3.3 15

4 Test Cases 5.1 23

ii
Abstract
In this digital era,mail serves as successful to communicate with customers and colleagues.
An mail has brought about an innovative change in our communication system. In this, we
only require a personal computer or mobile phone as well as internet connection.It is also
very and cheap so the students can use it to communicate with their friends at home and
abroad. Because it is widely used all over the world, it is known as the most advanced
communication system. In Existing system we have only the facility of sending and view
mail, But we don’t know whether receiver has read it or not ,No information regarding time
at which user read the email and also we don’t have the facility to delete the mail that we
have sent to receiver by mistake .In this system we came up with the facility that allows
sender to know the date and time at which a particular mail has being read by receiver and it
also provide a facility to delete a mail if the receiver has not opened it.

iii
1. Introduction
MAIL RECEIVED AUNTHENTICATION SYSTEM INTRODUCTION

1. Introduction
1.1 Introduction of the project

At present generation e-mail plays a prominent role. It is most used application for
communication through which we can send text messages, documents, images and files. In
present e-mail system we have only the facility of file sent notification. We don’t know whether
receiver has seen it or not. To know whether mail send or not we proposed a system for message
receipt facility.

1.2 Scope

This web site allows users of any business or uncommerical users to communicate with each
other by sending mails remotely with support of acknowledgment about the mail being read by
receiver

1.3 Existing System

In present e-mail system we have only the facility of file sent notification. But we don’t know
whether receiver has seen it or not. Because of this some important mails may get ignored by the
receiver after seeing it also.

1.4 Problems in Existing System

 We have only the facility of file sent notification..


 The sender doesn’t know whether user received the email or not.
 No acknowledgement.

1.5 Proposed System

Our proposal system for message receipt facility when it is seen by the recipient, so that sender is
aware of the fact that his message has been read. This also displays the time and date when the
receiver opens the mail.

Department of CSE, BRECW Page No.1


MAIL RECEIVED AUNTHENTICATION SYSTEM INTRODUCTION

1.6 Advantages of Proposed System

 Sender is aware of the fact that his message has been read.
 This also displays the time and date when the receiver opens the mail.

Department of CSE, BRECW Page No.2


2. Requirement Analysis
MAIL RECEIVED AUTHENTICATION SYSTEM REQUIREMENT ANALYSIS

2. Requirement Analysis

2.1 Functional Requirements

2.1.1 Admin

• Login

• Delete user details

• View user details

2.1.2 User

• Register

• Login

• Sending mail

• Delete mail

• View mail

• Acknowledge mail

• Update time

2.2 Non Functional Requirements

2.2.1 Performance

In computing, computer performance is the amount of useful work accomplished by a computer


system. Outside of specific contexts, computer performance is estimated in terms of accuracy,
efficiency and speed of executing computer program instructions. Performance engineering
within systems engineering, encompasses the set of roles, skills, activities, practices, tools, and
deliverables applied at every phase of the systems development life cycle which ensures that a
solution will be designed, implemented, and operationally supported to meet the performance
requirements defined for the solution. Performance testing is in general testing performed to

Department of CSE, BRECW Page No.3


MAIL RECEIVED AUTHENTICATION SYSTEM REQUIREMENT ANALYSIS

determine how a system performs in terms of responsiveness and stability under a particular
workload.

2.2.2 Reliability

Reliability describes the ability of a system or component to function under stated conditions for
a specified period of time. Reliability is closely related to availability, which is typically
described as the ability of a component or system to function at a specified moment or interval of
time. Reliability is usually defined as the probability that a product will operate without failure
for a specified number of uses (transactions) or for a specified period of time. To be truly testable
a requirement for software reliability should be stated as a forecast and the test results should
indicate the confidence level associated with the forecast that the product will meet the
requirements.

2.2.3 Scalability:

The site should be easily implemented by other IT professionals for further uses no matter what
platform it is. The database of the site should be able to deal with an enormous and increasing
amount of data

2.2.4 Portability

Portability, in relation to software, is a measure of how easily an application can be transferred


from one computer environment to another. A computer software application is considered
portable to a new environment if the effort required to adapt it to the new environment is within
reasonable limits. Portability is also used to describe the flexibility of the use of data. Some file
formats are less portable than others.

2.2.5 Usability

Usability can be described as the capacity of a system to provide a condition for its users to
perform the tasks safely, effectively, and efficiently while enjoying the experience. In software
engineering, usability is the degree to which a software can be used by specified consumers to
achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified
context of use.

Department of CSE, BRECW Page No.4


MAIL RECEIVED AUTHENTICATION SYSTEM REQUIREMENT ANALYSIS

2.3 Computational Resource Requirements

2.3.1 Software Requirements

• Operating system : Windows 10

• Front end : HTML, CSS, Java Script

• Middle-ware : Java, JSP

• Server : Tomcat

• Database : MYSQL

2.3.2 Hardware Requirements

• Processor : Intel i3 and above

• Hard Disk : 120 GB

• Ram : 1GB

2.4 Life Cycle Model

We use waterfall model for software development process which has various phases in it.

The sequential phases in Waterfall model are −

 Requirement Gathering and analysis − All possible requirements of the system to be


developed are captured in this phase and documented in a requirement specification
document.

 System Design – The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system architecture.

 Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.

Department of CSE, BRECW Page No.5


MAIL RECEIVED AUTHENTICATION SYSTEM REQUIREMENT ANALYSIS

 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.

 Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model".
In this model, phases do not overlap.

Fig 2.1 Different phases of Waterfall Model

Department of CSE, BRECW Page No.6


3. Design
MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

3. Design
3.1 Architectures
Project architecture represents number of components we are using as a part of our project and
the flow of request processing i.e., what components in procession the request and in which
order. An architecture description is a formal description is a formal description and
representation of a system organized in a way that supports reasoning about the structure of the
system.

Architecture is of 2 types. They are

1. Software architecture

2. Technical architecture

3.1.1 Software Architecture


Client Browser

 Register and Login


User
 send mail
 View mail
 Delete mail

Database
 Login
Admin  View users
 Delete Users

 Store user registration


details
 Validate users and admin MYSQL
 Store otp and validate otp
 Store mails

Fig 3.1 Software Architecture

Department of CSE, BRECW Page No.7


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

The architecture of a system describes its major components, their relationships, and how they
interact with each other. Software architecture and design includes several contributory factors
such as Business strategy, quality attributes, human dynamics, design and IT environment.
Software Architecture typically refers to the bigger structures of a software system, and it deals
with how multiple software processes cooperate to carry out their tasks. Software design refers to
the smaller structures and it deals with the internal design of a single software process.

3.1.2 Technical Architecture

Front end
Middle-Ware

JavaScript
JSP
HTML Database
Java
CSS MYSQL

Fig 3.2 Technical Architecture

The technical architecture defines the technologies that are used to implement and support a
Business Intelligence solution that fulfills the information and data architecture requirements.
These technologies cover the entire BI life cycle of design, development, testing, deployment,
maintenance, performance tuning, and user support.

Department of CSE, BRECW Page No.8


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

3.2 UML Diagrams

3.2.1 Use case Diagrams

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram
defined by and created from a Use-case analysis. Its purpose is to present a graphical overview
of the functionality provided by a system in terms of actors, their goals (represented as use
cases), and any dependencies between those use cases. The main purpose of a use case diagram
is to show what system functions are performed for which actor. Roles of the actors in the system
can be depicted

Fig 3.3 Use Case Diagram of Admin

Department of CSE, BRECW Page No.9


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

Fig 3.4 Use Case Diagram of User

3.2.2 Class Diagram

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among the classes. It explains
which class contains information.

Department of CSE, BRECW Page No.10


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

Fig 3.5 Class Diagram

3.2.3 Sequence Diagrams

Sequence Diagrams Represent the objects participating the interaction horizontally and time
vertically. A Use Case is a kind of behavioral classifier that represents a declaration of an offered
behavior. Each use case specifies some behavior, possibly including variants that the subject can
perform in collaboration with one or more actors. Use cases define the offered behavior of the
subject without reference to its internal structure. These behaviors, involving interactions
between the actor and the subject, may result in changes to the state of the subject and

Department of CSE, BRECW Page No.11


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

communications with its environment. A use case can include possible variations of its basic
behavior, including exceptional behavior and error handling.

Fig 3.6 Sequence Diagram of Admin

Department of CSE, BRECW Page No.12


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

Fig 3.7 Sequence Diagram of User

Department of CSE, BRECW Page No.13


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

3.2.4 Activity Diagrams

Activity diagrams are graphical representations of Workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the Unified Modeling Language, activity
diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows the overall flow of control.

Fig 3.8 Activity Diagram of Admin

Fig 3.9 Activity Diagram of User

Department of CSE, BRECW Page No.14


MAIL RECEIVED AUNTHENTICATION SYSTEM DESIGN

Databases

Table 3.1 Registration

Table 3.2 Send Mail

Table 3.3 Receive Mail

Department of CSE, BRECW Page No.15


4. Implementation
MAIL RECEIVED AUNTHENTICATION SYSTEM IMPLEMENTATION

4. Implementation

4.1 Technologies

This project is developed using HTML, CSS, JAVASCRIPT as Client-side technologies, JSP
and MYSQL as server-side technologies in Windows environment. This system provides
optimized utilization of resources, improved productivity, and efficient management of
resources as it is completely computerized and has centralized database maintenance.

4.2 Pseudo Code

4.2.1 Composing a mail

<%@page contentType="text/html" pageEncoding="UTF-8"%>


<html>
<head>
<title>MAIL::composemail</title>
<% String email=(String)session.getAttribute("email");%>
<script type="text/javascript">
function validate()
{
var c=document.reg.email.value;
var d=document.reg.password.value;
if (c.indexOf("@gmail", 0) < 0)
{
alert("Please enter a valid e-mail address. Like @gmail");
document.reg.email.focus();
return false;
}
if (c.indexOf(".", 0) < 0)
{
alert("Please enter a valid e-mail address.");
document.reg.email.focus();
return false;
}
return true;
}
</script>
<style>
table.pos_left
{
top: 40px;
}
#p table, th, td
{
border: 2px solid #009999;

Department of CSE, BRECW Page 16


MAIL RECEIVED AUNTHENTICATION SYSTEM IMPLEMENTATION

border-collapse:collapse;
font-size: 20px;
}
a{
text-decoration: none;
}
[type=file]
{
width:0;
height:0;
}
</style></head>
<center>
<body style="background-
image:url('https://i.pinimg.com/originals/45/cf/a8/45cfa8e8fef45c356253cf9938a4cc9c.jpg');
background-repeat:no-repeat;background-size:1500px;">
<div style="background:dodgerblue;margin-top:50px; margin-bottom:
30px;color:white;margin-top:0px">

<center> <h1><br></h1><h2 style="text-align:center">MAIL RECEIVED


AUTHENTICATION SYSTEM</h2></center></div>
<CENTER><h1>Hi &nbsp;<font color="blue"
size="5"><%=email%></FONT></h1></center>
<table CELLPADDING="15" align="left" id="p">
<TR> <TD><a href="compose.jsp">Compose mail</a></TD></TR>
<TR> <TD><a href="inboxing.jsp">Inbox</a></TD></TR>
<TR> <TD><a href="sentmails.jsp">Sent mails</a></TD></TR>
<TR> <TD><a href="AllMails.jsp">AllMails</a></TD></TR>
<TR> <TD><a href="login.html">Logout</a></TD></TR>
</table>

<div>
<form name="reg" action="composedb.jsp" method="post" onsubmit="return
validate()">
<table class="pos_left" align="center" CELLPADDING="15" >
<tr>
<td>SENDTO:&nbsp;&nbsp;&nbsp;</td>
<td><input type="email" maxlength="100" name="sendto" size="70px" required></td>
</tr>
<tr>
<td>SUBJECT:&nbsp;&nbsp;&nbsp;</td><td><input type="text" maxlength="100"
name="subject" size="70px" required=""></td>
</tr><tr><td>BODY&nbsp;&nbsp;&nbsp;</td><td>
<textarea name="txt" rows="15" cols="70" id="fileList">
</textarea> </td>

<script>
updateList = function() {
var input = document.getElementById('files');

Department of CSE, BRECW Page 17


MAIL RECEIVED AUNTHENTICATION SYSTEM IMPLEMENTATION

var output = document.getElementById('fileList');


output.innerHTML = output.value;
for (var i = 0; i < input.files.length; ++i)
{
output.innerHTML += '\n' + input.files.item(i).name + '';
}
}
</script>
</tr> <tr><td colspan="3" align="right">
<input type="submit" value="Send" id="submit" width="30px" height="30px" >
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<input type="Reset" value="Reset"
width="30px" height="30px"></td>
</tr>
</div>
</table>
</form>
</body>
</html>

4.2.2 Status of Composed mail before receiver view

<%@page contentType="text/html" pageEncoding="UTF-8"%>


<%@page import="java.sql.*" %>
<%@ page import = "java.io.*,java.util.Date, javax.servlet.*" %>
<% String email=(String)session.getAttribute("email");%>
<%
String sendto=request.getParameter("sendto");
String subject=request.getParameter("subject");
session.setAttribute("subject",subject);
String body=request.getParameter("txt");
String status="waiting";

try
{
Class.forName("com.mysql.jdbc.Driver");
Connection con=DriverManager.getConnection("jdbc:mysql://127.0.0.1/mail","root","");
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select *from registration where Emailid='"+sendto+"'");
if(rs.next())
{
int i=st.executeUpdate("insert into sentmail
values('"+sendto+"','"+subject+"','"+body+"','"+email+"',now(),'"+status+"')");
int j=st.executeUpdate("insert into receivemail
values('"+sendto+"','"+subject+"','"+body+"','"+email+"',now(),'"+status+"')");
if(i>0||j>0)
{
%>

Department of CSE, BRECW Page 18


MAIL RECEIVED AUNTHENTICATION SYSTEM IMPLEMENTATION

<script>
alert("Mail sent successfully");
window.location="compose.jsp";
</script>

<%
}
}
else
{
%>

<script>
alert("Email Id Is Does not Exist");
window.location="compose.jsp";
</script>
<%
}
}
catch(Exception e)
{
out.println(e);
}
%>

4.2.3 Status of composed mail after receiver view

<%@page contentType="text/html" pageEncoding="UTF-8"%>


<html>
<%@page import="java.sql.*" %>
<%@ page import = "java.io.*,java.util.Date, javax.servlet.*" %>
<% String email=(String)session.getAttribute("email");%>
<%
String sendto=request.getParameter("email");
session.setAttribute("from",sendto);
String time=request.getParameter("time");
session.setAttribute("time",time);
String subject=request.getParameter("subject");
session.setAttribute("subject",subject);
String body=request.getParameter("body");
session.setAttribute("body", body);

try
{
Class.forName("com.mysql.jdbc.Driver");
Connection con =DriverManager.getConnection ("jdbc:mysql://127.0.0.1/mail", "root", "");
PreparedStatement ps=con.prepareStatement("update sentmail set status=now() "
+ "where sender='"+sendto+"' and subject='"+subject+"' ");
ps.executeUpdate();
%>

Department of CSE, BRECW Page 19


MAIL RECEIVED AUNTHENTICATION SYSTEM IMPLEMENTATION

<script type="text/javascript">
window.location="viewcontent.jsp";
</script>

<%
}
catch(Exception e1)
{
out.println(e1.getMessage());
}

%>

Department of CSE, BRECW Page 20


5. Testing
MAIL RECEIVED AUNTHENTICATION SYSTEM TESTING

5. Testing
5.1 Overview
Software testing is a process, to evaluate the functionality of a software application with
an intent to find whether the developed software met the specified requirements or not
and to identify the defects to ensure that the product is defect free in order to produce the
quality product.
As per the current trend, due to constant change and development in digitization, our
lives are improving in all areas. The way we work is also changed. We access our bank
online, we do shop online, we order food online and many more. We rely on software’s
and systems. What if these systems turnout to be defective? We all know that one small
bug shows huge impact on business in terms of financial loss and goodwill. To deliver a
quality product, we need to have Software Testing in the Software Development Process.
Some of the reasons why software testing becomes very significant and integral part in
the field of information technology are as follows.
1. Cost effectiveness
2. Customer Satisfaction
3. Security
4. Product Quality

5.2 Dimensions of Testing


There are many different dimensions to consider:
1. Layers of the application (database, APIs, UI)
2. Scale of testing (unit, module, integration, scenario)
3. Type of testing (functional, performance, security, etc.)
4. Methodology (exploratory, scripted manual, automated)

Department of CSE, BRECW Page No.21


MAIL RECEIVED AUNTHENTICATION SYSTEM TESTING

5.3 Test Cases

Test Case No. Input Expected Observed Status


Behavior Behavior
P=Passed

F=Failed
1 Login as Home page for Sender home P
Sender with Sender should page is
correct login be displayed displayed
credentials

2 Login as Error message Error message P


Sender with should be is displayed
incorrect login displayed
credentials

3 Sender sends A mail should Mail is sent to P


mail to the be sent to the the receiver
receiver receiver

4 View sent mail Displays a table Table of sent P


of sent mails mails is
displayed

5 View status of Displays the Status of sent P


sent mail status of sent mail is
mail displayed

6 Receiver Login Displays Receiver home P


receiver page is
Homepage displayed

7 View received Displays a table Table of P


mails of of received received mails
receiver mails is displayed

8 Receiver reads Displays the Content in the P

Department of CSE, BRECW Page No.22


MAIL RECEIVED AUNTHENTICATION SYSTEM TESTING

the mail received mail mail is


displayed

9 Sender views Displays the Status will be P


sent mails status of the updated after
sent mails receiver view

Table 5.1 Test Cases

Department of CSE, BRECW Page No.23


6. Screenshots
MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

6. Screenshots

Screenshot 6.1 Home Page

Screenshot 6.2 User Registration Page

Department of CSE, BRECW Page No. 24


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.3 User Login Page

Screenshot 6.4 Sender is Composing his Mail

Department of CSE, BRECW Page No. 25


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.5 Sent mails of User (Sender)

Screenshot 6.6 User (Receiver) login here

Department of CSE, BRECW Page No. 26


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.7 User (Receiver) home page

Screenshot 6.8 User (Receiver) Inbox

Department of CSE, BRECW Page No. 27


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.9 User (Receiver) opened her mail and viewed the content in mail

Screenshot 6.10 User (Sender) login here

Department of CSE, BRECW Page No. 28


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.11 Status Is Updated To Date and Time in Sender Side When Receiver Opened
Her Mail.

Screenshot 6.12 All mails of a User

Department of CSE, BRECW Page No. 29


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6 .13 Admin Login page

Screenshot 6.14 Admin can view all the users here

Department of CSE, BRECW Page No. 30


MAIL RECEIVED AUTHENTICATION SYSTEM SCREENSHOTS

Screenshot 6.15 Admin can delete users from here

Department of CSE, BRECW Page No. 31


7. Conclusion and Future Scope
MAIL RECEIVED AUNTHENTICATION SYSTEM CONCLUSION AND FUTURE SCOPE

7. Conclusion and Future Scope


7.1 Conclusion
• By using this project sender is aware of the fact that his message has been read.

• This also displays the time and date when the receiver opens the mail.

7.2 Future Scope

• Further modifications can be applied as of, change in the colour of notification along
with online status

• The sender can be made to receive a notification as soon as the receiver reads the mail

• As well as receiver will receive the message received notification.

Department of CSE, BRECW Page No. 32


8. References
MAIL RECEIVED AUTHENTICATION SYSTEM REFERENCES

8. References

8.1 Book References

• Html black book by Steven holzer, published by coriolis group,3rd edition

• Java database programming 2nd edition by pratik Patel and moss, published by
coriolis group

• Advanced java programming 1st edition by uttam k.roy, published by Oxford


University press

• Software engineering 7th edition by Roger Pressman, published by McGraw hill


education

8.2 Web References

https://www.codejava.net/coding/upload-files-to-database-servlet-jsp-mysql

https://www.tutorialspoint.com/uml/uml_standard_diagrams.htm

https://www.lucidchart.com/blog/types-of-UML-diagrams

Department of CSE, BRECW Page No. 33

You might also like