AKS University Department of Computer Science & Engineering

“Secure Intra-Organizational Mailing System”

(Minor Project)

A Project Report Submitted

In Partial Fulfilment of the Requirement for the Degree of

MASTER OF COMPUTER APPLICATION

by
Kavita Ahirwar
B2292R10700057
Under the Supervision of Mr. Santosh Soni
Assistant Professor

Session: 2022-24

Department of Computer Science & Engineering

AKS University, Satna
(Madhya Pradesh)

KAVITA AHIRWAR 1 SECURE INTRA-ORG. MAILING SYSTEM

AKS University Department of Computer Science & Engineering

Declaration

I hereby declare that the work which is being presented in the report, entitled “Secure Intra-

Organizational Mailing System” in partial fulfilment for the award of Degree of Masters of

Computer Applications (MCA), submitted to the Department of Computer Science &

Engineering, AKS University, Satna (MP).

I have not submitted the matter presented in this report anywhere for any other Degree.

Kavita Ahirwar (B2292R10700057)

Masters of Computer Applications (MCA)

KAVITA AHIRWAR 2 SECURE INTRA-ORG. MAILING SYSTEM

AKS University Department of Computer Science & Engineering

Certificate

This is to certify that Kavita Ahirwar (B2292R10700057) worked on the project ‘Secure
Intra-Organizational Mailing System' from Aug 2023 to Nov 2023 and has successfully
completed the major project, in order to partially fulfil the requirements for the award of the
degree of Master of Computer Applications (MCA) under my supervision and guidance.

External Examiner Head of the Department

Internal Examiner Project Guide

KAVITA AHIRWAR 3 SECURE INTRA-ORG. MAILING SYSTEM

AKS University Department of Computer Science & Engineering

ACKNOWLEDGEMENT

The satisfaction that accompanies the successful completion of any task would be incomplete
without the mention of people whose ceaseless cooperation made it possible, whose constant
guidance and encouragement crown all efforts with success.

We are grateful to our project guide Professor Santosh Soni and Prof. Akhilesh A. Waoo the
Head of Department of Computer Science and Engineering and Information Technology, AKS
University Satna (M.P), for their guidance, inspiration and constructive suggestions that helped
us in the preparation of this project. They were always there guiding and correcting us with
attention and care. They took immense pain going through the project and also the
documentation and made the necessary corrections as and when required.

We would also take this opportunity to thank our Institution and other faculty members without
whom this project would have been a distant reality

KAVITA AHIRWAR 4 SECURE INTRA-ORG. MAILING SYSTEM

 AKS DEPARTMENT OF COMPUTER SCIENCE

CONTENTS

LIST OF FIGURES 8

LIST OF TABLES 8

CHAPTER 1 OBJECTIVE OF THE PROJECT 9

1.1 Abstract 9
CHAPTER 2 INTRODUCTION 10-11
2.1 Overview of Project 10
2.1.1 Login Module 10
2.1.2 Registration Module 10
2.1.3 Administration Module 11
2.1.4 Managing Harmful Keywords Module 11
2.1.5 User Module 11
2.1.6 Composing Mail Module 11
2.2 Global Use 11
CHAPTER 3 PROBLEM STATEMENT 12-13

CHAPTER 4 SYSTEM STUDY 14-23

4.1 Information Gathering 14
4.2 Feasibility Analysis 14
4.3 Feasibility Considerations 14
4.3.1 Economic Feasibility 15
4.3.2 Technical Feasibility 16
4.3.3 Behavioral Feasibility 16
4.4 Technology Used 16
4.4.1 Java 16-17
4.4.1.1 Importance of Java to Internet 17
4.4.1.2 Java Architecture 17
4.4.1.3 Compilation of Code 17
4.4.1.4 Compiling & Interpreting Java Source Code 17
4.4.2 JSP 18-19
4.4.2.1 Importance of Java to Internet 19-20
4.4.3 JDBC 20
4.4.3.1 What is JDBC 20

KAVITA AHIRWAR 5 SECURE INTRA-ORG. MAILING SYSTEM

 AKS DEPARTMENT OF COMPUTER SCIENCE

4.4.3.2 What does JDBC 20-21

4.4.4 My SQL (Structured Query Language) 21
4.4.4.1 Database 21-22
4.4.4.2 Normalization 22
4.4.5 HTML 22-23
6.2 Requirement Analysis 23
4.4.5.2 Basic HTML Tags 23
CHAPTER 5 SYSTEM ANALYSIS 24-25
5.1 Requirement Analysis 25
5.2 System Specifications 25
5.3 Request for Proposal 25
5.4 Evaluation and Validation 25
5.5 Vendor Selection 25
CHAPTER 6 SYSTEM DESIGN 26-32
6.1 The Primary Objective of design 26
6.2 Input Output Design 27
6.3 User Interface Design 27
6.4 System Architecture 28
6.5 UML Diagram 29
6.5.1 Unified Modelling Language 29
6.5.1.1 User Model View 29
6.5.1.2 Structural View Model 29
6.5.1.3 Behavioral Model View 29
6.5.1.4 Implementation Model View 29
6.5.1.5 Environmental Model View 29
6.6 Class Diagram 30
6.6.1 Admin 30
6.6.2 User 30
6.7 Sequence Diagram 31
6.7.1 Admin 31
6.7.2 User 31
6.8 Object Diagram 32
6.8.1 Admin 32
6.8.2 User 32
CHAPTER 7 DATA FLOW DIAGRAM 33
7.1 Context Level 33

KAVITA AHIRWAR 6 SECURE INTRA-ORG. MAILING SYSTEM

 AKS DEPARTMENT OF COMPUTER SCIENCE
7.2 Level 2 DFD 34
CHAPTER 8 DESC. OF DIFF. I/P VALDATION & CHECKS 35
8.1 Registratuon of Client 35
8.2 Login Client/Administrator 35
8.3 Compose Mail 35
8.4 Manage Keyword 35
CHAPTER 9 HARDWARE & SOFTWARE REQUIREMENT 36
9.1 Hardware requirement 36
9.2 Software requirement 36
9.3 Additional Tools 36
CHAPTER 10 SYSTEM TESTING 37-42
10.1 Testing 37
10.1.1 Unit Testing 38
10.1.1.1 Black Box Testing 38
10.1.1.2 White Box Testing 38-40
10.1.2 System Testing 41
10.1.3 Integration Testing 41
10.1.4 Acceptance Testing 41
10.2 Test Approach 42
10.2.1 Bottom-Up Approach 42
10.2.2 Top-Down Approach 42
10.3 Validation 42
CHAPTER 11 OUTPUT SCREENSHOTS 43-48
11.1 Home Page 43
11.2 Admin’s Login Page 44
11.3 Admin’s Main Page 44
11.4 Adding a Keyword 45
11.5 Displaying the Keyboard 46
11.6 User’s Registration 46
11.7 User’s Main Page 47
11.8 Composing a Mail by User 47
11.9 Alert list of Blocked Mail in Admin Page 48
11.10 Message in Inbox of other User 48
BIBLIOGRAPHY 49
Project Presentation (PPT) 50-66

KAVITA AHIRWAR 7 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

LIST OF FIGURES:
Figure 4.1 Compiling and Interpreting Java Source Code 18
Figure 6.1 Input Output Design 27
Figure 6.2 URL Pattern of System Architecture 28
Figure 6.3 Class Diagram for Admin 30
Figure 6.4 Class Diagram for User 30
Figure 6.5 Sequence Diagram for Admin 31
Figure 6.6 Sequence Diagram for User 31
Figure 6.7 Object Diagram for Admin 32
Figure 7.1 Context Level DFD 34
Figure 7.2 Level 1 DFD 34
Figure 11.1 It is the homepage where number of users’ login by entering
their Email ID and passwords. New user has to select the signup option to
create a user account and then he can login 34
Figure 11.2 Here admin’s login by entering his username and password 44
Figure 11.3 Here is admin home page where he/she has the ability to manage
keywords, encrypt keywords. Admin has a feature of viewing the blocked mails 44
Figure 11.4 Here admin adds numerous or harmful keywords by clicking the add button 45
Figure11.5 Here admin displays all the words which he/she had entered into the list 46
Figure 11.6 User page where he/she enters his/her personal details and gets registered
to Java Secure Mail page. .46
Figure 11.7 Here is User’s main page, it consists of compose mail, inbox and sent
mail. Here user can send mails, check the received mails and also able to
see the sent mails. 47
Figure 11.8 Here is the mail box where users can compose their mails 47

Figure 11.9 Here are the mails which had been got blocked in admin page
due to hazardous information in mail. 48

LIST OF TABLES:

Table 1 Unit Test Case for Administrator 39

Table 2 Unit Test Case for Administrator 40

KAVITA AHIRWAR 8 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

CHAPTER 1
OBJECTIVE OF THE PROJECT
Abstract
This Mailing system is designed to provide a communication channel inside an organization
between different clients (Organization staff) on the network. The main objective of the project is to
develop a fully functional Mailing System that enhances communications among the members of
the organization in a reliable, cost-effective and secure way. Thus it helps the organization to
improve the performance of its teams in the corporate sector. This system design shall be able to
provide the following facilities to the users:

1. System shall accept the mails from authorized users providing security. Submitted messages will
be delivered to appropriate person only. It provides the facility to review messages from the
respective folders. Effective Communication has become an integral part of organizations today

2. A project specific mailing system uses a database server to store mails information and the
organizational information such as user’s details including the personal information and information
requests. Teams members can be then access this information using the Mailing System. As
information changes, the server content can be easily updated with new or revised data. This
flexible approach allows geographically remote project teams to access timely, consistent and
accurate information without expensive typesetting, printing, distribution and mailing charges.

3. he objective of this project is to develop a secure mailing system that incorporates advanced
features for identifying offensive or anti-social elements within emails. The system is designed to
detect such elements through the use of specific keywords, managed by the administrator, who has
the authority to block them. Additionally, the project aims to enhance security within the
organization by identifying and flagging suspicious users who may send harmful content, such as
spam, viruses, or executable files. This heightened security ensures that members can communicate
securely, sharing sensitive information without the risk of exposure to the outside world.

KAVITA AHIRWAR 9 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Chapter 2
INTRODUCTION

Electronic mail (also known as email or e-mail) is one of the most commonly used services on the
Internet, allowing people to send messages to one or more recipients. Email was invented by Ray
Tomlinson in 1972. Many people are now using various email services to communicate with each
other. But some emails have harmful content in it that can affect our PC, Laptop,…etc. In this
project, suspicious users who send harmful emails are identified by determining the keywords used
by him/her. The keywords such as bomb, RDX, are found in the mails which are sent by the user.
All these blocked mails are checked by the administrator and identify the users who sent such mails.
This is very useful in real-time scenario in which you can resume the anti-social activities.

2.1 OVERVIEW OF PROJECT

1) Login Module
2) Registration Module
3) Administration Module
4) Managing harmful keywords Module
5) User Module
6) Composing Mail Module

2.1.1 Login Module

This module is used by administrator and users (who are authenticated) to login into the Java Secure
Mail. The login details of the specified person will be entered and hence can enter into the Java
Secure Mail. If a user is not authenticated then it notifies login details are not correct.

2.1.2 Registration Module

This module is used by the unauthenticated users who are unregistered. The users must register
themselves by unique username such that they can login into the Java Secure Mail. If a user of same

KAVITA AHIRWAR 10 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

username is already exists then it notifies user already exists. If password and confirm password is
not matched then it notifies password is not matched.

2.1.3 Administration Module

This module is used by the administrator to perform the functions like managing the keywords,
entering new keywords and to check out the block list of the discarded mails.

2.1.4 Managing harmful keywords Module

This module is used by the administrator to perform the functions like addition, deletion and
modification of the harmful keywords. The harmful keywords are sent to the database and hence
managed by the administrator. If keyword already exists then it tells to the administrator.

2.1.5 User Module

This module is used by the users to do operations like composing mail, checking out the mails in
inbox and finally sending the mails to the authenticated users by attaching a message or file.

2.1.6 Composing Mail Module

This module is used by the users for composing mail. In this module, user specifies header and
body of the file and attaches a file. Header contains address of the recipient and subject of mail.
Body contains actual description of mail

2.2 Global use - Despite what the World Wide Web offers, email remains the most important
application of the Internet and the most widely used facility it has. Now more than 600 million
people internationally use email. With the WWW, email started to be made available with
friendly web interfaces by providers such as Yahoo and Hotmail. Usually it’s free. Now that
email affordable, everyone wanted at least one email address, and the medium was adopted by
not just millions, but hundreds of millions of people. Email remains the No. 1 form of
communication in North America and Europe, cited by 87% and 74% respectively of those
polled its use as a main communications channel in the Asia-Pacific region is at just 58%,
according to Epsilon’s “Global Consumer Email Study.”

KAVITA AHIRWAR 11 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Chapter 3
PROBLEM STATEMENT

A great deal of business communication and workflow is centered on email, but we question
whether email is the ultimate long-term solution for communication and workflow processes. While
email is a good method for anyone in the world to contact you, that's also email's biggest problem.
Most communication, both business and personal, does not come from just anyone; it comes from
other members of your organization, partners, or team. It comes from "important people".

Email as a business communication mechanism has many inherent flaws:

 It's totally insecure

Confidential business documents sent over email are not confidential. These documents can be
read both inside and outside of your organization. For example, your system administrator can
read the latest draft of your strategic acquisition agreement or medical patient information.
 It's too open
our mailboxes are filling with junk mail, and the situation is getting worse every month. Due to
the inherent general delivery design of email, this problem cannot be prevented, even with the
best designed email filters.
 Email can be dangerous
Computer viruses are most commonly delivered through email because there is no certification
mechanism for email senders. In Microsoft Outlook, just clicking on an email can initiate a
new virus.
 Delivery is not guaranteed
Just like postal mail, email may be delivered, or maybe not. Take the recent example of
Harvard acceptance letters that were deleted by AOL, thinking they were junk mail.

KAVITA AHIRWAR 12 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

 Email is not real time

There is too much delay to have an active conversation, which is why more and more people
are turning to instant messaging solutions (which also have their own security problems).
 It lacks ubiquitous access
it is problematic for most users to access their email from all locations, such as at home or
while on the road. This is the primary reason why web-based email became popular.

If you consider email for managing workflow, it has a number of additional problems:

 It's a poor way to share files

they don't arrive in nicely organized directories that allow both parties see identical file and
directory structures.
 There's no application framework
Email is for message-oriented content. It has no concept of a standard framework to deliver
active applications.
 Its platform dependent
many organizations have members (such as development or graphics groups) who use systems
other than Microsoft Windows and Outlook, which means they are left out of certain activities.
 It's a haphazard workflow method
is email really the best possible driver of corporate and organizational workflow?

Email is adequate for communicating with the world-at-large, a general delivery mailbox, but most
business and organizational communications is oriented toward relatively small teams of working
relationships. Using email to drive internal business workflow is like running a business based on
receiving US postal mail as it arrives at the mailbox.

KAVITA AHIRWAR 13 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Chapter 4

SYSTEM STUDY

4.1 Information Gathering

The system being developed is economic with respect to Organization's point of view. It is cost
effective in the sense that has eliminated the paper posting work completely. The system is also
time effective because the mailing system is very fast which sends Email quickly as per the user or
organization requirement. The Emailing through JSM (Java Secure Mail) is secure, flexible and
pretend to virus, spam or hacking attack by outside world. The system also collects the information
of employee of organization who registered on it.

4.2 Feasibility Analysis

Many feasibility studies are disillusioning for both users and analysts. First, the study often
presupposes that when the feasibility document is being prepared, the analyst is in a position to
evaluate solutions. Second, most studies tend to overlook the confusion inherent in system
development the constraints and the assumed attitudes. If the feasibility study is to serve as a
decision document, it must answer three key questions:-
1. Is there a new and better way to do the job that will benefit the user?
2. What are the costs and savings of the alternative(s)?
3. What is recommended?
Once the feasibility study is done and proposal is approved, we move to the requirement analysis. A
feasibility study is the test to proposal according to its viability impact on the organization, ability to
meet user needs, and effective use of the resources. The objective of the feasibility is not to solve
the problem but to acquire a sense of its viability scope.

4.3 Feasibility considerations

Three key considerations are involved in the feasibility analysis: -
1. Economic
2. Technical
3. Behavioral.

KAVITA AHIRWAR 14 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

4.3.1 Economic Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness of a
proposed system. More commonly known as cost / benefit analysis; in this procedure we determine
the benefits and savings that are expected from a proposed system and compare them with costs.
We found the benefits outweigh the costs; we take a decision to design and implement the new
proposed system.
A system that can be developed technically and that will be used if installed must still be profitable
for the organization. The various financial and economic issues were raised during the preliminary
investigation. These issues were not of our concern in major and were studied by the management.
Since the system was developed for internal use of the organization. It was ensured that after this
system has been developed, it would save considerable time and efforts of the concerned
department.
The economic feasibility should demonstrate the net benefit of the proposed application in light of
the benefits and costs to the client. The large department have large amount of data, information.
Economic feasibility is send to different clients for approval and acknowledgement before moving
to next stage of system development process.
The following Economic Feasibility elements are expressed quantitatively in the analytical
worksheets and summarized in the business case.
The elements included
a. Increased agency revenue.
b. Decreased agency revenue.
c. Increased agency cost.
d. Decreased agency cost.
e. Other organizational benefits.
There isn’t an order or magnitude rule of thumb that applies generally.
The alternative dismissal/selection process depends on other things, such as, how well an alternative
meets the project purpose and need, and the totality of environmental impacts. What if an
alternative that cost 4 or 5 times more than other alternatives but in turn had 4 to 5 times less
environmental impacts? Depending on the type of resources and impacts, you might not be able to
rule that alternative out on the basis of dollar cost alone.

KAVITA AHIRWAR 15 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

4.3.2 Technical Feasibility

This is concerned with specifying equipment and software that will successfully satisfy the user
requirement. The technical needs of the system may vary considerably, but might include:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
This project is technically feasible as it has got all the features necessary to form a healthy
environment for communication. The concepts & technology used in this project is perfectly well
and secure. Any organization’s employee having an account on mailing system can access this
project and make full use of it.

4.3.3 Behavioural Feasibility

It is mainly related to human organizational and political aspects. The points to be considered are:
 What changes will be brought with the system?
 What organizational structures are disturbed?
 What new skills will be required? Do the existing staff members have these skills?
If not, can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual recommendations.
The system working is quite easy to use and learn due to its simple but attractive interface. User
requires no special training for operating the system. They can easily work and operate this system.

4.4 Technology Used

4.4.1 Java
Initially the language was called as “oak” but it was renamed as “java” in 1995.The primary
motivation of this language was the need for a platform-independent (i.e. architecture neutral)
language that could be used to create software to be embedded in various consumer electronic

KAVITA AHIRWAR 16 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
devices.
 Java is a programmer’s language

 Java is cohesive and consistent

 Except for those constraint imposed by the Internet environment. Java gives the
programmer, full control
Finally, Java is to Internet Programming where c was to System Programming.

4.4.1.1 Importance of java to the internet

Java has had a profound effect on the Internet. This is because; java expands the Universe of objects
that can move about freely in Cyberspace. In a network, two categories of objects are transmitted
between the server and the personal computer. They are passive information and Dynamic active
programs. in the areas of Security and probability. But Java addresses these concerns and by doing
so, has opened the door to an exciting new form of program called the Applet.

4.4.1.2 Java architecture

Java architecture provides a portable, robust, high performing environment for development. Java
provides portability by compiling the byte codes for the Java Virtual Machine, which is then
interpreted on each platform by the run-time environment. Java is a dynamic system, able to load
code when needed from a machine in the same room or across the planet.

4.4.1.3 Compilation of code

When you compile the code, the Java compiler creates machine code (called byte code) for a
hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed executed the byte
code. The JVM is created for the overcoming the issue of probability. The code is written and
compiled for one machine and interpreted on all machines .This machine is called Java Virtual
Machine.

4.4.1.4 Compiling And Interpreting Java Source Code

KAVITA AHIRWAR 17 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Java
Pc Java Byte interpreter
compiler code

Platform Java
Source Macintosh
independ interpreterm
code compiler
ent acintosh

SPARC Java
Compiler interpreter(
SPARC)

Fig. 4.1 Compiling and Interpreting Java Source Code

)))
During run-time the Java interpreter tricks the byte code file into thinking that it is running on a
Java Virtual Machine. In reality this could be an Intel Pentium windows 95 or sun SPARCstation
running Solaris or Apple Macintosh running system and all could receive code from any computer
through

4.4.2 JSP

The first Java Server Pages specification was released in 1999. Originally JSP was modelled after
other server-side template technologies to provide a simple method of embedding dynamic code
with static mark-up. When a request is made for the content of a JSP, a container interprets the JSP,
executes any embedded code, and sends the results in a response. At the time this type of
functionality was nothing terribly new, but it was and still is a helpful enhancement to Servlets.
JSP has been revised several times since the original release, each added functionality, and is
currently in version 2.0. The JSP specifications are developed alongside the Servlet specifications
and can be found on Sun Microsystems’
Java Server Pages product information page,http://java.sun.com/products/jsp. The functionality
defined by the JSP 2.0 specifications can be broken down as follows:
 JSP
The JSP specifications define the basic syntax and semantics of a Java Server Page. A basic Java
Server Page consists of plain text and markup and can optionally take advantage of embedded
scripts and other functionality for creating dynamic content.
 JavaBeans

KAVITA AHIRWAR 18 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
JavaBeans are not defined by the JSP specifications, but JSP does provide support for easily using

and manipulating them. Often objects used on the server-side of a Web Application are in the form
of what is commonly called a JavaBean.
 Custom Tags and JSP Fragments
JSP provides a mechanism for linking what would normally be static markup to custom Java code.
This mechanism is arguably one of the strong points of JSP and can be used in place of or to
complement embedded scripts of Java code.

 Expression Language
JSP includes a mechanism for defining dynamic attributes for custom tags. Any scripting language
can be used for this purpose; usually Java is implemented, but the JSP specification defines a
custom expression language designed specifically for the task. Often the JSP EL is a much simpler
and more flexible solution, especially when combined with JSP design patterns that do not use
embedded scripts.
Discussing the basics of JSP is the focus of this chapter. JavaBeans, Custom Tags, and the JSP
Expression Language are all fully discussed in later chapters after a proper foundation of JSP is
established.

4.4.2.1 JSP LIFE CYCLE

Much like Servlets, understanding JSP requires understanding the simple life cycle that JSP follows.
JSP follows a three-phase life cycle: initialization, service, and destruction, as shown in Figure 3-1.
This life cycle should seem familiar and is identical to the one described for Servlets.
While a JSP does follow the Servlet life cycle, the methods have different names. Initialization
corresponds to the jspInit() method, service corresponds to the _jspService() method, and
destruction corresponds to the jspDestroy() method. The three phases are all used the same as a
Servlet and allow a JSP to load resources, provide service to multiple client requests, and destroy
loaded resources when the JSP is taken out of service.

KAVITA AHIRWAR 19 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

JSP is designed specifically to simplify the task of creating text producing HttpServlet objects and
does so by eliminating all the redundant parts of coding a Servlet. Unlike with Servlets there is no
distinction between a normal JSP and one meant for use with HTTP. All JSP are designed to be
used with HTTP and to generate dynamic content for the World Wide Web. The single JSP
_jspService () method is also responsible for generating responses to all seven of the HTTP
methods. For most practical purposes a JSP developer does not need to know anything about HTTP,
nor anything more than basic Java to code a dynamic JSP.

4.4.3 JDBC
4.4.3.1 What is JDBC?
One can write a single program using the JDBC API, and the JDBC is a Java API for executing
SQL, Statements (As a point of interest JDBC is trademarked name and is not an acronym;
nevertheless, JDBC is often thought of as standing for Java Database Connectivity. It consists of a
set of classes and interfaces written in the Java Programming language. JDBC provides a standard
API for tool/database developers and makes it possible to write database applications using a pure
Java API.
Using JDBC, it is easy to send SQL statements to virtually program will be able to send SQL.
statements to the appropriate database. The Combination of Java and JDBC lets a programmer
writes it once and run it anywhere.

4.4.3.2 What does JDBC do?

Simply put, JDBC makes it possible to do three things
 Establish a connection with a database
 Send SQL statements
 Process the results

 JDBC Driver Types

 The JDBC drivers that we are aware of this time fit into one of four categories
 JDBC-ODBC Bridge plus ODBC driver

KAVITA AHIRWAR 20 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
 Native-API party-java driver
 JDBC-Net pure java driver
 Native-protocol pure Java driver
An individual database system is accessed via a specific JDBC driver that implements the
java.sql.Driver interface. Drivers exist for nearly all-popular RDBMS systems, through few are
available for free. Sun bundles a free JDBC-ODBC bridge driver with the JDK to allow access to a
standard ODBC, data sources, such as a Microsoft Access database, Sun advises against using the
bridge driver for anything other than development and very limited development.
JDBC drivers are available for most database platforms, from a number of vendors and in a number
of different flavours. There are four driver categories:
I. Type 1-JDBC-ODBC Bridge driver
II. Type 2-Native-API Party Java driver
III. Type 3-Net Protocol All Java Driver
IV. Type 4 Native Protocol All Java Driver

4.4.4 MySQL (Structured Query Language)

MySQL is a Relational Database Management System (RDBMS) that runs as a server providing
multi-user access to a number of databases .It is a cross platform database server ideal for both
small and large applications. It supports standard SQL for database creation. The data in MySQL is
stored in database objects called tables. The table is a collection of related data entries and it
consists of columns and rows. The system provided a simple interface for quick book searching,
lending and returning. The interface was designed to be mainly used for the common browsers,
making the system migration and usage easier.
4.4.4.1 Database
A Database is a collection of interrelated data stored with a minimum of redundancy to serve many
applications. The database design is used to group data into a number of tables and minimizes the
artificiality embedded in using separate files. The tables are organized to:
 Reduced duplication of data.

 Simplify functions like adding, deleting, modifying data etc..,

 Retrieving data
 Clarity and ease of use

KAVITA AHIRWAR 21 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
 More information at low cost
4.4.4.2 Normalization
Normalization is built around the concept of normal forms. A relation is said to be in a particular
normal form if it satisfies a certain specified set of constraints on the kind of functional
dependencies that could be associated with the relation. The normal forms are used to ensure that
various types of anomalies and inconsistencies are not introduced into the database.
 First Normal Form
A relation R is in first normal form if and only if all underlying domains contained atomic values
only.
 Second Normal Form
A relation R is said to be in second normal form if and only if it is in first normal form and every
non-key attribute is fully dependent on the primary key.
 Third Normal Form
A relation R is transitively depends on the primary key. said to be in third normal form if and only
if it is in second normal form and every non key attribute is non-transitively depend on the primary
key.

4.4.5 HTML
Hypertext Mark-up Language (HTML), the languages of the worldwide web (WWW), allows users
to produces web pages that included text, graphics and pointer to other web pages (Hyperlinks).
HTML is not a programming language but it is an application of ISO Standard 8879, SGML
(Standard Generalized Mark-up Language), but Specialized to hypertext and adapted to the Web.
The idea behind hypertext is one point to another point. We can navigate through the information
based on out interest and preference. A mark-up language is simply a series of items enclosed
within the elements should be displayed. Hyperlinks are underlined or emphasized works that load
to other documents or some portions of the same document.
HTML can be used to display any type of document on the host computer, which can be
geographically at a different location. It is a versatile language and can be used on any platform or
desktop

HTML provides tags (special codes) to make the document look attractive. HTML provides are not

KAVITA AHIRWAR 22 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
case-sensitive. Using graphics, fonts, different sizes, color, etc can enhance the presentation of the
document. Anything that is not a tag is part of the document itself.

4.4.5.1 Advantages

 A HTML document is small and hence easy to send over the net.It is small because it does
not include formatted information.
 HTML is platform independent
 HTML tags are not case-sensitive.
4.4.5.2 Basic HTML Tags
<!-- --> Specific Comments.
<HTML>…..</HTML> Start tag
<Title>……..</Title> Creates title of the page
<A>………..</A> Creates Hypertext links.
<B>………...</B> Creates hypertext links.
<Big>………</Big> Formats text in large-font
<Body>…….</Body> Contains all tags and text in the Html-document
<Center>……</Center> Creates Text
<DD>……….</DD> Definition of a term.
<TABLE>…..</TABLE> Creates table
<Td>…………</Td> Indicates table data in a table.
<Tr>………..</Tr> Designates a table row
<Th>……….</Th> Creates a heading in a table.

Chapter 5
KAVITA AHIRWAR 23 SECURE INTRA-ORG. MAILING SYSTEM
 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
SYSTEM ANALYSIS

Assuming that a new system is to be developed, the next phase is system analysis. Analysis
involved a detailed study of the current system, leading to specifications of a new system. Analysis
is a detailed study of various operations performed by a system and their relationships within and
outside the system. During analysis, data are collected on the available files, decision points and
transactions handled by the present system. Interviews, on-site observation and questionnaire are
the tools used for system analysis. Using the following steps it becomes easy to draw the exact
boundary of the new system under consideration:
 Keeping in view the problems and new requirements
 Workout the pros and cons including new areas of the system

All procedures, requirements must be analysed and documented in the form of detailed data flow
diagrams (DFDs), data dictionary, logical data structures and miniature specifications. System
Analysis also includes sub-dividing of complex process involving the entire system, identification
of data store and manual processes.
The main points to be discussed in system analysis are:
 Specification of what the new system is to accomplish based on the user requirements.
 Functional hierarchy shows the functions to be performed by the new system and their
relationship with each other.
 Function network which are similar to function hierarchy but they highlight those functions
which are common to more than one procedure.
 List of attributes of the entities - these are the data items which need to be held about each
entity (record).
The selection process should be viewed as a project and a project team should be formed with the
help of management. The selection process consists of several steps, which are discussed below:

5.1 Requirements analysis

The first step in selection understands the user's requirements within the framework of the
organization’s objectives and the environment in which the system is being installed.

KAVITA AHIRWAR 24 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

5.2 System specifications:

System specifications must be clearly defined. These specifications must reflect the actual
applications to be handled by the system and include system objectives, flowcharts, input-output
requirements, file structure and cost.
5.3 Request for proposal:
After the requirement analysis and system specifications have been defined, a request for proposal
is prepared and sent to selected vendors for bidding.
5.4 Evaluation and validation:
The evaluation phase ranks various vendor proposals and determines the one best suited to the user's
requirements. It looks into items such as price, availability and technical support. System validation
ensures that the vendor can, in fact, match his/her claims, especially system performance.
5.5 Vendor selection:
This step determines the vendor with the best combination of reputation, reliability, service record,
training, delivery time, lease/finance terms. The selected vendors are invited to give a presentation
of their system. The system chosen goes through contract negotiations before implementation.

Chapter 6
SYSTEM DESIGN

KAVITA AHIRWAR 25 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Based on the user requirements and the detailed analysis of a new system, the new system must be
designed. This is the phase of system designing. It is a most crucial phase in the development of a
system. Normally, the design proceeds in two stages:
 Preliminary or general design
 Structure or detailed design
Preliminary or general design: In the preliminary or general design, the features of the new
system are specified. The costs of implementing these features and the benefits to be derived are
estimated. If the project is still considered to be feasible, we move to the detailed design stage.
Structure or Detailed design: In the detailed design stage, computer oriented work begins in
earnest. At this stage, the design of the system becomes more structured. Structure design is a blue
print of a computer system solution to a given problem having the same components and inter-
relationship among the same components as the original problem

6.1 The primary objective of the design:

Of course, is to deliver the requirements as specified in the feasibility report. In general, the
following design objectives should be kept in mind:
 Practicality: The system must be stable and can be operated by the people with average
intellectual.

 Efficiency: This involves accuracy, timeliness and comprehensiveness of the system output.

 Cost: it is desirable to aim for a system with a minimum cost subject to the condition that it
must satisfy all the requirements.

 Flexibility: The system should be modifiable depending on the changing needs of the user. Such
modifications should not entail extensive reconstructing or recreation of software. It should also
be portable to different computer systems.

6.2 Input Output Design

For any system to work properly it is very necessary to keep a check over the input and output of
the system. In this system we have used MySQL database for storing and sending information. So it

KAVITA AHIRWAR 26 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
imposes an additional constraint that the data inputted by the user should conform to the standards
for creating a table in MySQL database. For example there cannot be 2 users having the same user
name in the registration table.

Fig. 6.1 Input Output Design

6.3 User Interface Design

Any project how so ever good it may be would become failure if the end user it is meant to cater
cannot use it. For the end user to reap full benefits of the project the project should have a good
interface. Interface is the way a project links with the end users; it accepts the inputs from the user
and gives output to the user. For a project to be successful it should have a clean and understandable
interface.

6.4 System Architecture

KAVITA AHIRWAR 27 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Below architecture diagram represents mainly flow of requests from users to database through
servers. In this scenario overall system is designed in three tires separately using three layers called
presentation layer, business logic layer and data link layer. This project was developed using 3-tier
architecture.

URL Pattern: Fig. 6.2 URL Pattern of System Architecture

Presentation
Layer

Response sent URL Request

from the sent through
servlet the browser
SERVLETS
AT THE
SERVER
SIDE
Reply from the Verifying or
database updating the
according to the database through a
statement statement

DATABASE

KAVITA AHIRWAR 28 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

6.5 UML Diagrams

6.5.1 Unified Modelling Language
The Unified Modelling Language allows the software engineer to express an analysis model using
the modelling notation that is governed by a set of syntactic semantic and pragmatic rules. A UML
system is represented using five different views that describe the system from distinctly different
perspective. Each view is defined by a set of diagrams, which is as follows.

6.5.1.1 USER MODEL VIEW

 This view represents the system from the user’s perspective.
 The analysis representation describes a usage scenario from the end-user’s perspective.
6.5.1.2 STRUCTURAL MODEL VIEW
 In this model the data and functionality are arrived from inside the system.
 This model view models the static structures.
6.5.1.3 BEHAVIORAL MODEL VIEW
It represents the dynamic of behavioral as parts of the system, depicting the interactions of
collection between various structural elements described in the user model and structural model
view.
6.5.1.4 IMPLEMENTATION MODEL VIEW
In this the structural and behavioral as parts of the system are represented as they are to be built.
6.5.1.5 ENVIRONMENTAL MODEL VIEW
In these the structural and behavioral aspects of the environment in which the system is to be
implemented are represented.
UML is specifically constructed through two different domains they are:
 UML Analysis modelling, this focuses on the user model and structural model views of the
system.
 UML design modelling, which focuses on the behavioral modelling, implementation
modelling and environmental model views.

KAVITA AHIRWAR 29 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

6.6 Class Diagrams

6.6.1 Admin

Keywords
Manage Keywords

Add Keywords()
Display Keywords()
Update Keywords()
Admin
Keywords
Alert Mails
Informative
Block List
Enter keywords() Alert Mails
check mails() Informative Mails

check mails()

Fig. 6.3 Class Diagram for Admin

6.6.2 User

Compose Mails
composing the mail

send the mail()

Sent Mails
User
Sent items
Mails
check the sent items()
Compose()
send()

Inbox
Received mails

check the received mails()

Fig. 6.4 Class Diagram for User

KAVITA AHIRWAR 30 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

6.7 Sequence Diagram

6.7.1 Admin

Admin Keywords Alert List Informative

Manage Keywords

Check Alert Mails

Check Informative Mails

Fig. 6.5 Sequence Diagram for Admin

6.7.2 USER

User Compose Mails Inbox Sent Items

Compose the mails to be sent

Check the mails

Check the sent mails

Fig. 6.6 Sequence Diagram for User

KAVITA AHIRWAR 31 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

6.8 Object Diagram

6.8.1 Admin

Fig. 6.7 Object Diagram for Admin

6.8.2 User

KAVITA AHIRWAR 32 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Chapter 7
DATA FLOW DIAGRAM

Graphical description of a system's data and how the processes transform the data is known as Data
Flow Diagram (or DFD).
Unlike detail flowcharts, DFD’s do not supply detailed descriptions of modules but graphically
describe a system's data and how the data interact with the system.
The following seven rules govern construction of data flow diagrams (DFD):
1. Arrows should not cross each other.
2. Squares, circles, and files must bear names.
3. Decomposed data flows must be balanced (all data flows on the decomposed
diagram must reflect flows in the original diagram).
4. No two data flows, squares, or circles can have the same name.
5. Draw all data flows around the outside of the diagram.
6. Choose meaningful names for data flows, processes, and data stores. Use strong
verbs followed by nouns.
If too many events seem to be occurring at a given point, an analyst can decompose a data
conversion (circle). The new data conversions form a parent-child relationship with the original data
conversion: the child circle.

7.1 Context Level

Compose Check data

Check Email
User Response 1.0 Admin
Email Suspicious
Scanning /Normal

Fig 7.1 Context Level DFD

KAVITA AHIRWAR 33 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

7.2 Level 1 DFD

Sender

Compose Response

0.0

Compose
Mail

Check Suspicious/
Email Normal

Fetch Data
Admin
Information
Database
Check
suspicious
mail Check
(.exe) file

1.0
1.1

Detect harmful Detect

keywords executable
File

Alert/Normal Alert/Normal
Email Email

Receiver

KAVITA AHIRWAR 34 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Fig 7.2 Level 1 DFD

CHAPTER 8
DESCRIPTIONS OF DIFFERENT INPUT VALIDATIONS AND CHECKS

Input is the term meaning either an entrance or changes which are inserted into a system and which
activate or modify a process. Validation is a process where data are subjected to series of tests to
determine the validity of a piece of data. There are a number of validations that is implemented in
this system. They are given below:
8.1 Registration of Client
Client who is un-authenticated can register through user register portal. Client has to enter the
personal information and choose a user name & password. If user name is already registered by
other user then JSM (Java Secure Mail) notifies “user name already exists”. If password and
confirm password is same then JSM registers client otherwise notifies “password and confirm
password is not same”.
8.2 Login client/administrator
Authenticate client/administrator can login and use the system. Client/administrator has to enter
user name and password. If user name and password are correct then JSM depicts
Client/administrator module based on who is entering in the system. If user name or password is
incorrect then JSM notifies “user name or password is not correct”.
8.3 Compose Mail
This module is used by client. If a registered user wants to send an Email to another registered user
then user has to compose a mail. In compose mail user has to enter header (address and subject) and
body of email. If address of the receiver is correct then JSM sends a mail otherwise notifies “user
name is not exists”. If user has harmful keyword as subject or attaches an .exe file then admin catch
and block this mail. Admin notifies to sender “Email that you sent has harmful content” and sends
an alert to the receiver “Email has harmful content”.
8.4 Manage Keyword
This module is used by administrator. In this module administrator can add, delete and modify
harmful keyword. If admin wants to add a harmful keyword then he has to enter a harmful keyword
name. If keyword already exits then JSM notifies “keyword already exists”. If admin wants to

KAVITA AHIRWAR 35 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
delete or modify a harmful keyword then he has to enter a harmful keyword name.

Chapter 9
HARDWARE AND SOFTWARE REQUIREMENTS

9.1 Hardware requirements

The project does not deal with any specific requirement about the h/w interfaces. It mainly deals
with user’s job to hide the data. The hardware require are basic fundamentals which are required to
run a program
Processor : Pentium-III (or) Higher
RAM : 64MB (or) Higher
Cache : 512MB
Hard disk : 10GB

9.2 Software requirements

Technology : Java, JSP and servlets

Web Technologies : HTML
Database : MySql
JDK Version : JDK1.6
Server : Tomcat5.5 or Glass Fish

9.3 Additional tools

HTML Designing : Dream weaver Tool
Development Tool kit : NetBeans 6.9

KAVITA AHIRWAR 36 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Chapter 10
SYSTEM TESTING
10.1 Testing
During systems testing, the system is used experimentally to ensure that the software does not fail.
In other words, we can say that it will run according to its specifications and in the way users
expect. Special test data are input for processing, and the results examined. A limited number of
users may be allowed to use the system so that analyst can see whether they try to use it in
unforeseen ways. It is desirable to discover any surprises before the organization implements the
system and depends on it. To test the working each test case is designed with the intent of finding
errors in the way the system will process it. There are two general strategies for testing software:
1. Code testing and
2. Specification testing.
In code testing, the analyst develops those cases to execute every instructions and path in a
program. Under specification testing, the analyst examines the program specifications and then
writes test data to determine how the program operates under specific conditions. Regardless of
which strategy the analyst follows, there are preferred practices to ensure that the testing is useful.
Testing includes three parts:-
1. Testing- Error detection and error removal of newly developed program, so that it produces
specific output with correctness of live and artificial data.
2. Verification- It is also a kind of testing of system in simulated environment using simulated data
(alpha testing). It is done to detect and wait error regarding end user and design specification we
were specified in the earlier phase.
3. Validations- It refers to process of using software in a live environment in order to find errors.
Feedback of validation phase generally produces change in software to deal with error and failure
that are uncovered. Transaction that are extended and person using the system and real and continue
for several months.
Testing is of different types some of them are given below:-
1. Unit Testing

KAVITA AHIRWAR 37 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
2. System Testing

10.1.1 Unit Testing

In unit testing the analyst tests the programs making up a system. For this reason, unit testing is
sometimes called program testing. Unit testing gives stress on the modules independently of one
another, to find errors. This helps the tester in detecting errors in coding and logic that are contained
within that module alone. The errors resulting from the interaction between modules are initially
avoided. For example, a hotel information system consists of modules to handle reservations; guest
check-in and check-out; restaurant, room service and miscellaneous charges; convention activities;
and accounts receivable billing. For each, it provides the ability to enter, modify or retrieve data and
respond to different types of inquiries or print reports. The test cases needed for unit testing should
exercise each condition and option. Test of individual module/program.
It is called program testing. Valid and invalid data are entered to generate possible error.
For Example: - Numeric error or Date error. It focuses in any module but not integrated part. It
does not consider any linking error. First stage of testing
Output – error free program. - All programs are working independently.

10.1.1.1 Black Box Testing

In this strategy some test cases are generated as input conditions that fully execute all functional
requirements for the program. This testing has been uses to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structure or external database access
 Performance errors
In this testing only the output is checked for correctness. The logical flow of the data is not checked.
10.1.1.2 White Box Testing
In this the test cases are generated on the logic of each module by drawing flow graphs of that
module and logical decisions are tested on all the cases. It has been uses to generate the test cases in
the following cases:
 Guarantee that all independent paths have been executed.
 Execute all logical decisions on their true and false Sides.

KAVITA AHIRWAR 38 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
 Execute all loops at their boundaries and within their operational bounds
 Execute internal data structures to ensure their validit

Unit Test Case for Administrator

TEST ID INPUT SPECIFICATION EXPECTED OUTPUT

Administrator is asked to enter appropriate
Login Page Login details (Email ID and password). If
login details are correct then user redirect to
the Client Page otherwise it shows “user
name or password is not correct”.
It has four links:
1. Managed Keyword
1 Admin Main Page
2. Display Keyword

3. Alert List

4. Informative Mail list

It will ask to click on a link and redirect the

user corresponding page.
It manages the harmful keywords like admin
1.1 can add, delete and modify the harmful
Manage Keywords keywords from the database. Harmful
keywords are the words that can recognise
harmful mails. Admin can also logout or go
to admin main page from it.
It will show all harmful keywords that have
1.2 Display Keyword been added by the user. Admin can also
logout or go to admin main page from it.
It will show all the suspicious mails that have
1.3 been sent by any user. Admin can recognise
Alert mail list antisocial users. Admin can download
Attachment of the mail from this page. User
can also logout or go to client main page from
it.
It will show all the informative mails that
1.4 Informative mails have been sent by any user. Admin can
download Attachment of the mail from this
page. User can also logout or go to client
main page from it.

KAVITA AHIRWAR 39 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

(Table 1)

Unit Test Case for user

TEST ID INPUT SPECIFICATION EXPECTED OUTPUT

It will ask to enter the user name,
Registration Page password and client personal details. If
user name is unique then it will register to
the user otherwise shows “User name
already exists”.
User is asked to enter appropriate Login
Login Page details (Email ID and password). If login
details are correct then user redirect to the
Client Page otherwise it shows “user name
or password is not correct”.
1 It has three links:
Compose Mail

Client Main Page Inbox

Sent Mail
It will ask to click on a link and redirect
the user corresponding page. User can also
logout or go to client main page from it.
It will ask the user to enter “to” (address
of recipient), subject, and attachment of
the file. If address of the recipient exits
then it will send the mail and notifies the
1.1 Compose page user otherwise shows “Email Id is not
exists”. Admin manages harmful content
in it. If subject matches with harmful
keyword or sender attaches .exe file then
admin generates an alert mail to the
recipient and also notifies to the sender.
User can also logout or go to client main
page from it.
It will show all the mails that have been
1.2 Inbox Page received by the user. Client can download
Attachment of the mail from this page.
User can also logout or go to client main
page from it.
It will show all the mails that have been
1.3 Sent Mail Page sent by the user. User can download
Attachment of the mail from this page.

KAVITA AHIRWAR 40 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
User can also logout or go to client main
page from it.

(Table 2)

10.1.2 System Testing

The important and essential part of the system development phase, after designing and developing
the software is system testing. We cannot say that every program or system design is perfect and
because of lack of communication between the user and the designer, some error is there in the
software development. The number and nature of errors in a newly designed system depend on
some usual factors like communication between the user and the designer; the programmer's ability
to generate a code that reflects exactly the systems specifications and the time frame for the design.
Theoretically, a newly designed system should have all the parts or sub-systems are in working
order, but in reality, each sub-system works independently
Testing is an important function to the success of the system. System testing makes a logical
assumption that if all the parts of the system are correct, the goal will be successfully activated.
Another reason for system testing is its utility as a user-oriented vehicle before implementation.
Testing of software after development all the modules are attached to make complete program.
 Test meets all requirements of the user.
 All necessary outputs should be tested.
 Installing of software.

System testing consists of the following three steps:

1. Program testing
2. String testing
3. User acceptance testing

10.1.3 Integrating Testing

Integration testing ensures that software and subsystems work together a whole. It tests the
interface of all the modules to make sure that the modules behave properly when integrated
together.
10.1.4 Acceptance Testing
It is a pre-delivery testing in which entire system is tested at client's site on real world data to find

KAVITA AHIRWAR 41 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
errors.

10.2 Test Approach

Testing can be done in two ways:
 Bottom-up approach
 Top-down approach

10.2.1 Bottom-up Approach

Testing can be performed starting from smallest and lowest level modules and proceeding one at a
time. For each module in bottom up testing a short program executes the module and provides the
needed data so that the module is asked to perform the way it will when embed within the larger
system. When bottom level modules are tested attention turns to those on the next level that use the
lower-level ones they are tested individually and then linked with the previously examined lower-
level modules.

10.2.2 Top-down Approach

This type of testing starts from upper level modules. Since the detailed activities usually performed
in the lower level routines are not provided stubs are written. A stub is a module shell called by
upper level module and that when reached properly will return a message to the calling module
indicating that proper interaction occurred. No attempt is made to verify the correctness of the
lower-level module.

10.3 Validation
The system has been tested and implemented successfully and thus ensured that all the requirements
as listed in the software requirements specification are completely fulfilled. In case of erroneous
input corresponding error messages are displayed

KAVITA AHIRWAR 42 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Chapter 11
OUTPUT SCREEN SHOTS
11.1 Home Page

Fig 11.1

It is the homepage where number of users’ login by entering their Email ID and passwords. New
user has to select the signup option to create a user account and then he can login.

KAVITA AHIRWAR 43 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

11.2 Admin’s Login Page

Fig. 11.2
Here admin’s login by entering his username and password

11.3 Admin’s Main Page

KAVITA AHIRWAR 44 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Fig 11.3

Here is admin home page where he/she has the ability to manage keywords, encrypt keywords.
Admin has a feature of viewing the blocked mails

11.4 Adding a Keyword

KAVITA AHIRWAR 45 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Fig 11.4

Here admin adds numerous or harmful keywords by clicking the add button.

11.5 Displaying the Keyword

KAVITA AHIRWAR 46 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Fig 11.5
Here admin displays all the words which he/she had entered into the list

11.6 User’s Registration

Fig. 11.6
User page where he/she enters his/her personal details and gets registered to Java Secure Mail page

11.7 User’s Main Page

KAVITA AHIRWAR 47 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Fig 11.7
Here is User’s main page, it consists of compose mail, inbox and sent mail. Here user can send
mails, check the received mails and also able to see the sent mails

11.8 Composing a Mail by User

Fig 11.8
Here is the mail box where users can compose their mails

11.9 Alert List of Blocked Mails in Admin Page

KAVITA AHIRWAR 48 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

Fig 11.9
Here are the mails which had been got blocked in admin page due to hazardous information in mail
11.10 Message in Inbox of Other User

Fig 7.4.10
This screen gives the message in inbox of another user. Here user can read the received mails and
can download attached file.

KAVITA AHIRWAR 49 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
BIBLIOGRAPHY

WEB REFERENCES
 http://google.com
 http://www.tutorialspoint.com

BOOKS REFERENCES
 The Complete Reference JAVA2 by Herbert Schildt Tata Mc Graw Hill India.
 JAVA Server Programming Black book Kogent Solutions Inc.
 Software Engineering by Pressman Tata Mc Graw Hill India.
 Data Base Management System by Korth

KAVITA AHIRWAR 50 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

PROJECT
PRESENTATION
(PPT)

KAVITA AHIRWAR 51 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

“Secure Intra-Organizational Mailing System”

(Minor Project)
A Project Report Submitted
In Partial Fulfilment of the Requirements for the Degree of

MASTER OF COMPUTER APPLICATION

by

Kavita Ahirwar
B2292R10700057
Under the Supervision of
Mr. Santosh Soni
Assistant Professor

Session: 2022-24
Department of Computer Science & Engineering
AKS University, Satna

CONTENT

KAVITA AHIRWAR 52 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

 Introduction
 Objective & Problem Statement
 System Study & Analysis
 System Design
 System Architecture
 Data Flow Diagram
 Hardware & Software required
 System Testing & Test Approach
 Output Screenshots
 Advantages & Disadvantages
 Future Enhancement
 Conclusion

INTRODUCTION

KAVITA AHIRWAR 53 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
The project is designed to revolutionize organizational
communication by developing a sophisticated platform that not
only ensures the security of sensitive information but also
addresses key challenges like identifying offensive content and
detecting suspicious users.

With modules such as Login, Registration, and Administration,

the system aims to provide a user-friendly environment for
seamless interaction. Employing technologies like Java and
MySQL, the project emphasizes feasibility, robust system design,
and thorough testing to create a reliable and cost-effective solution
for organizations globally.

OBJECTIVE & PROBLEM STATEMENT

• Objective:
1. Develop a Secure Mailing System: Create a robust and secure
platform for organizational communication.
2. Enhance Communication: Facilitate efficient and user-friendly
communication within the organization.

3. Address Security Challenges: Identify offensive elements, detect

suspicious users, and ensure the security of sensitive information.

KAVITA AHIRWAR 54 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
• Problem Statement:
1. Offensive Element Identification: Recognize and manage offensive
content within emails to maintain a secure communication
environment.
2. Suspicious User Detection: Implement measures to identify users
sending harmful data, such as spam, viruses, or executable files.
3. Organizational Security: Ensure the organization's sensitive data is
protected, providing a secure internal communication solution.

SYSTEM STUDY & ANALYSIS

System Study:
• Conducted an extensive information gathering phase to inform the
feasibility analysis.
• Evaluated economic, technical, and behavioral aspects to determine
project viability.
• Utilized a robust technology stack featuring Java, JSP, JDBC,
MySQL, and HTML.
• Emphasized a comprehensive understanding of project requirements
through systematic data collection.
• Ensured that the chosen technologies align with the project's goals
and objectives.
System Analysis:
• Delved into detailed system specifications, outlining the specific

requirements of the project.

• Initiated the vendor selection process, evaluating potential partners

KAVITA AHIRWAR 55 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
for the project.
• Focused on key design components, including Input-Output Design,
User Interface Design, System Architecture, and UML Diagram.
• Conducted an evaluation and validation process to select vendors that
align with project needs.
• Ensured that the design components emphasized the integration of
technology for a seamless and effective system architecture.

SYSTEM DESIGN
System Design Stages:
• Preliminary or General Design
• Structure or Detailed Design
Preliminary or General Design:
• Specify features of the new system.
• Estimate costs and benefits.
• Feasibility check before moving to detailed design.
Structure or Detailed Design:
• Computer-oriented work begins.
• Design becomes more structured.
• Blueprint of the system solution mirroring original problem.
Primary Design Objectives:
• Practicality: System stability for average users.
• Efficiency: Accuracy, timeliness, and comprehensiveness in
output.

KAVITA AHIRWAR 56 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
• Cost: Aim for minimum cost satisfying all requirements.
Input Output Design:
• Critical for proper system functioning.
• Utilize MySQL database for information storage.
• Data input must conform to MySQL table creation standards.

SYSTEM ARCHITECTURE
SYSTEM ARCHITECHTURE
• Architecture Overview:
• Represents the flow of requests from users to the database
through servers.
• Three-tier architecture design with distinct layers: presentation,
business logic, and data link layers.
• System Design Tiers:
• Developed using a three-tier architecture approach.
• Presentation Layer: Handles user interface and interaction.
• Business Logic Layer: Manages application logic and
processing.
• Data Link Layer: Facilitates communication between the
application and the database.
• Flow of Requests:

• Illustrates the systematic flow of user requests through the

designed architecture.

KAVITA AHIRWAR 57 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
• Servers play a central role in mediating interactions between
users and the database.
• Layered Structure:
• Ensures a structured separation of concerns in the system
design.
• Each layer focuses on specific functionalities, enhancing
maintainability and scalability.
• Project Development Approach:
• The project adopted a 3-tier architecture for efficient handling
of user requests, logical processing, and database interactions.

DATA FLOW DIAGRAM

KAVITA AHIRWAR 58 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Data Flow Diagram 1 (DFD1):
• Illustrates the initial stage of data flow within the system.
• Represents the flow of data from sources to destinations, outlining
the key processes and data entities.

Data Flow Diagram 2 (DFD2):

• Progresses from DFD1, providing a more detailed depiction of data
flow.
• Specifies the interactions between processes, data storage, and
external entities in the system.

HARDWARE & SOFTWARE REQUIRED

KAVITA AHIRWAR 59 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Hardware requirementsThe project does not deal with any specific
requirement about the h/w interfaces. It mainly deals with user’s job to
hide the data. The hardware require are basic fundamentals which are
required to run a program
• Processor : Pentium-III (or) Higher
• RAM : 64MB (or) Higher
• Cache : 512MB
• Hard disk : 10GB
Software requirements
• Technology : Java, JSP and servlets
• Web Technologies: HTML
• Database : MySql
• JDK Version : JDK1.6
• Server :Tomcat5.5 or Glass Fish

SYSTEM TESTING & TEST APPROACH

System Testing:
• Purpose:
• Ensure the software functions according to specifications.
• Confirm it runs as expected and meets user requirements.
• Testing Strategies:
• Code Testing: Executes every instruction and path in a
program.
• Specification Testing: Examines program specifications and

KAVITA AHIRWAR 60 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
writes test data based on conditions.
• Test Design:
• Test cases designed to find errors in how the system processes
data.
• Detect surprises or unforeseen uses before system
implementation.
• Testing Parts:
• Testing: Error detection and removal in a newly developed
program.
• Verification: Testing in a simulated environment using
simulated data.
• Validation: Live usage of the software to find and fix errors.
• Preferred Practices:
Regardless of testing strategy, ensure the testing is useful and
efficient

Test Approach:
• Bottom-Up Approach:
• Testing starts from the smallest and lowest-level modules.
• Progresses one module at a time, ensuring each works properly.
• Top-Down Approach:
• Testing begins with upper-level modules.
• Utilizes stubs for lower-level routines to simulate interactions.
• Testing Steps:

KAVITA AHIRWAR 61 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
• Integration Testing: Ensures software and subsystems work
together.
• Acceptance Testing: Pre-delivery testing at the client's site with
real-world data.
• Validation:
• Successful testing and implementation.
• Ensures all requirements in the software requirements
specification are fulfilled.
• Displays error messages for erroneous input.

• Analysis:
1. Precision and Accuracy:
1. Precise translation suggests high precision, crucial for accurate
predictions.
2. High accuracy implied by successful translations, showcasing
model effectiveness.
2. Recall:
1. Precise translated outputs indicate high recall, capturing true
positive cases effectively.
2. Model adept at recognizing and translating relevant sign
language gestures.
3. False Positives and False Negatives:
1. Absence of reported false positives or false negatives suggests
correct translations and minimal misclassification.
2. Rigorous evaluation required for critical insights.

KAVITA AHIRWAR 62 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
4. Continuous Monitoring and Refinement:
1. Translator accuracy increases with more epochs and images for
each gesture.
2. Ongoing monitoring through confusion matrix aids in
identifying and addressing evolving challenges.

OUTPUT SCREENSHOTS

ADVANTAGES &DISADVANTAGES

KAVITA AHIRWAR 63 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
Advantages of the Secure Intra-Company Mailing System:
1. Enhanced Communication:
1. Facilitates improved communication among organization
members.
2. Enables efficient exchange of information, leading to better
collaboration.
2. Security Assurance:
1. Provides a secure platform for communication within the
organization.
2. Helps in identifying and blocking offensive or harmful content,
ensuring a safe environment.
3. User-Friendly Interface:
1. Offers a user-friendly environment for organization members.
2. Enables easy use without requiring in-depth technical
knowledge.
Disadvantages of the Secure Intra-Company Mailing System:
1. Complex Implementation:
1. Implementing a secure mailing system can be complex.
2. Integration with existing systems and ensuring security
measures may pose challenges.
2. Resource Intensity:
1. Requires substantial resources, including time and financial
investment.

2. Ongoing maintenance and updates may demand continuous

KAVITA AHIRWAR 64 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
resources.
3. Potential Overlooking of Issues:
1. Despite security measures, there is a possibility of overlooking
certain issues.
2. Continuous monitoring and updates are necessary to address
emerging threats.

FUTURE ENHANCEMENT
1. The future enhancement plan includes the implementation of
advanced security measures, such as regular security audits and the
integration of blockchain for tamper-proof communication.
2. Ongoing user training and awareness programs will be a priority,
ensuring that employees are well-informed about cybersecurity best
practices and the evolving threat landscape.
3. Artificial Intelligence will play a crucial role, with plans to
implement predictive analysis for identifying potential security
threats and using AI-driven anomaly detection to recognize unusual
patterns.
4. Mobile optimization is on the agenda, with the development of a
dedicated mobile application and a responsive web interface to cater
to the increasing use of mobile devices.

KAVITA AHIRWAR 65 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE
CONCLUSION

In conclusion, the development of the Secure Intra-Company Mailing

System marks a significant stride towards fostering secure and efficient
communication within the organization.
The project's emphasis on advanced security measures, user training, and
artificial intelligence integration reflects a commitment to staying ahead of
evolving cybersecurity challenges.
The future enhancements, including mobile optimization and scalability
with cloud integration, underscore a proactive approach to meet the
dynamic needs of users
. As the system continues to evolve, it is poised to serve as a robust
communication platform, promoting seamless, secure, and user-friendly
interactions among organizational members.

KAVITA AHIRWAR 66 SECURE INTRA-ORG. MAILING SYSTEM

 AKS UNIVERSITY DEPARTMENT OF COMPUTER SCIENCE

THANK YOU

KAVITA AHIRWAR 67 SECURE INTRA-ORG. MAILING SYSTEM