Synopsis

Synopsis

“ADVANCED SECURED SYSTEM” deals with the Server based

Information and Maintenance of the Server. This system is used to reduce the workload
of the server. It provides mail services, chat services between the clients and it also
response to the client requests. This system is designed as a middleman between the
client and the server. This system provides all kinds of services to the clients like file
transfer, mail, chat etc... This system is cost-effective and provides a security like firewall
to the server. Though there are any software available in the market there is no popular
server in terms of cost and providing services. Developed in java platform will be an
advantage to this software. This can be used in various platforms.

The main objective of this software is to

• Speed up the data transfer
• Check for virus file
• Provide mail, chat services
• Strong authentication
• Sharing resources
• Flexibility
Acknowledgement
 Acknowledgement

We would like to express our deep gratitude and sincere thanks to all who helped us to
complete this project work successfully.

Our sincere thanks to Principal, Madurai Kamaraj University College, for having
provided us facilities to do our project.

Our deep gratitude goes to Mr. Suresh Kumar, B.E., Head of the Department, for granting
us opportunity to do the project.

We sincerely thankful to Mr. Henry project guide, for his valuable suggestions and
guidance at time of need.

Our joy finds no boundary to expose our thanks to Mr.K. Anand, M.C.A., for extending
great help needed for our project.

Great thanks to out family, our project associates, our most valuable dear friends and all
those directly or indirectly helped us in this endeavor.

Last but not the least we thank the Almighty God who makes everything happen.
 CONTENTS
1. Introduction

1.1 Company Profile

1.2 About the Project

2. System Analysis

2.1 Existing System

2.2 Proposed System

3. Feasibility Study

3.1 Technical Feasibility

3.2 Economical Feasibility
3.3 Operational Feasibility

4. System Specification

4.1 Hardware Specification

4.2 Software Specification
4.2.1 About the Software

5. System Design

5.1 Project Description

5.2 Data Flow Diagram
5.3 Database Design

6. System Testing And Implementation

6.1 Testing Fundamentals

6.2 Unit Testing
6.3 Integration Testing
6.4 Acceptance Testing
6.5 Implementation

7. Maintenance

7.1 Corrective Maintenance

7.2 Adaptive Maintenance
7.3 Enhance Maintenance
8. Screen Layout

9. Conclusion

10. Future Scope of the Project

11. Bibliography
1.1. Company Profile

Sky Soft Software Limited

SkySoft Software Limited is one of the leading Software Development

Companies in Chennai. This organization is collaborated with Lastech Software, it is
enterprises in designing and hosting of web pages of various companies, advertising the
product profiles of the same. It has also developed a package, Indoweb, an Indian
Language Software for Internet, using this company is able to design the web pages in
any Indian Language and host it through the service provider located in North America. It
has also recently launched the first website in the world to send mail in Tamil language;
the user need not download any Tamil Font in their system to run the package.

SkySoft Software (P) Ltd., has designed the website for TamilNadu and
Digital slides for Telugu website. This product was launched in the month of Aug.1996.

Setup in 1989, started the business of developing Regional Software in

DTP, Presentation Graphics and Image Processing Software. Recently the company has
launched Identification Card Software for printing of ID card for the Citizens of India.
The company’s Annual turnover averages Rs.1.2 Million. It operates in four state capitals
with resellers all over India.

The company maintains a news Magazine called TamilNadu Online on web,

which incidentally is the first ever Indian website Magazine on the web. The company
has so far trained more than 400 Professionals in JAVA, in a short span of 16 months.
Recently the company has opened an Office in Madurai and another one in Coimbatore.
1.2 ABOUT THE PROJECT

The Project ”ADVANCED SECURED SYSTEM” deals with the Server

maintenance for a company.

The project consists of following modules:

• File Transfer

• E-mail

• Resource Sharing

• Chat

• Web Page View

File Transfer:

File transfer is handled between client and the server. To share a file from
another client the requestor client sends the request to the server. The server then gets the
file from the client which provides the requested file. Then the server sends the file to the
requested client.

Mail:

With the advent of the Internet and its commercial

availability, the Universal e-mail have become a common
feature in today’s High-tech World. The ability to compose, sends, and
receives Electronic mail has been enormously popular. In this project
E-Mail can be sent to the recipient without having to enter into the
Web browser.
Resource Sharing:

Server provides all applications, files and messages. If a client wants

applications from the server, the server grant permission to the particular Client
according to their authentication level, i.e., applications are shared between server and
clients. The client access the printer which are attached to the server when a request is
provided. The applications from the server are sent to the requested client by the
provider. Resources include devices such as CD, Floppy and Printer. The client access
these devices which are attached to the server when a request is provided.

Chat:

Chatting is talking to other people who are using the Internet at the same
time you are. Usually, this "talking" is the exchange of typed-in messages requiring one
site as the repository for the messages and a group of users who take part from
anywhere on the Internet. In some cases, a private chat can be arranged between two
parties who meet initially in a group chat. Chats can be ongoing or scheduled for a

particular time and duration.

Web Page View:

The user requests a web page from the server. If the page is available in the

server then the server provide a copy of the page and open the page in the client location.
 2. System Analysis

2.1. Existing System

The existing system is present in SKYSOFT SOFTWARE LIMITED. There

are some problems in sharing resources .The existing system must use a third
party tool to share the resources, provide a mail service within the clients, to
provide sharing of messages between a group of users through chat services.
In existing system when more than one users try to access the resources of the
Server, then the server processing speed decreases. When network traffic arises,
then the data transfer will go down very slow and there is a chance of data to be
lost. There is low level security in the existing system .The cost factor will be
high to provide the services like mailing, chatting. It reduces the response time
experienced by the clients.

Problems associated with the Existing System

Cost-effectiveness

 Low level security

 Network Traffic

 Resource Sharing

 Low Reliability

 Performance problems

 Scalability
 2.2 Proposed System
The proposed system will provide a good security and improves the performance of
the server. It provides network security and gives access to the resources in
server. It improves the response time to clients. It provides robust
authentication. Table handling using Oracle would increase the ease in
handling data, quicker and timely retrieval of data is possible with flexibility
and portability. Keeping in view all these points and problems of the existing
system, the new system has been developed using Java Server Page and
Oracle.

Advantages of Proposed System

Increases the system Reliability

Centralized access

Minimum cost

 High security

 System design for better performance

 DAP Concept
 3. FEASIBILITY STUDY
It is both necessary and prudent to evaluate the feasibility of a project at
the earliest possible time. Months or years of effort, thousands and millions of dollars,
and untold professional embarrassment can be averted if an ill-conceived system is
recognized early in the definition phase.

Feasibility and risk analysis are related in many ways. If project risk is great,
the feasibility of producing quality software is reduced. During product engineering,
however, we concentrate our attention on four primary areas of interest.

3.1. Technical Feasibility

Technical feasibility is the need of hardware and software, which are needed to
implement the proposed system in the organization. Technical requirements are to be fulfilled to
make the proposed system work. This should be necessarily predetermined so as to make the
system more competent.

3.2. Economical Feasibility

The Economical feasibility must satisfy the needs of the technical feasibility and the
operational feasibility. It involves the economic feasibility of developing and implementing the
proposed system.

3.3. Operational Feasibility

The proposed system should use the internet level then the different types of end
users are involved in the system, so it solves the user’s needs and the organization needs. And it
supports the all users environment.
 4. System Specification
4.1. Hardware Requirements

 Processor Intel Pentium Family

 Clock Speed 667 MHz
 RAM 128 MB
 Hard Disk 4 GB or higher
 Monitor Display panel (640 x 480)
 Mouse Logitech Serial Mouse
 Keyboard Standard 104 enhanced keyboard
 Cache Memory 11,011,968 Bytes
 Virtual Memory 32 MB
 Display Card Super Video Graphics Adapter (SVGA)

4.2. Software Requirements

 Operating System : Windows 98/2000/XP/NT

 Web Server : Apache Tomcat 4.1.7
 Web Browser : Internet Explorer
 Front-End Tool : HTML
 Client side Script : JavaScript
 Server side Script : Java Server Pages
 Back-End Tool : Oracle 8.0
4.2.1. About the Software

HTML (Hyper Text Markup Language)

HTML came to existence in 1970. The development of HTML was initiated by Tim
Burners Lee was later taken over by Dan Cannolly, Dave Ragett. The ancestor of
HTML is SGML (Standard Generalized Markup Language). SGML was developed
by ISO (International Standard Organization) and was first used by the US DOD
(Department Of Defense).

SGML and HTML have a parent-child relationship. HTML can be referred to

as subset of SGML HTTP protocol used to transfer HTML pages.

JavaScript
Java script is a compact; object based scripting language for developing client
and server Internet applications.

Netscape Navigator 2.0 interprets JavaScript statements embedded directly

in an HTML page, and live wire enables you to create server-based applications similar
to common gateway interface (CGI) programs.

Using JavaScript in HTML

JavaScript can be embedded in an HTML document in two ways:

 As statements and functions using the script tag

 As events handlers using HTML tags
 JavaScript supports functions, again without any special declarative
requirements, functions can be properties of objects, executing as loosely typed methods,
JavaScript statements can get and set exposed properties to query the state or alter the
performance of an applet or plug in.

JAVA SERVER PAGES (JSP)

The best way to understand Java Server Pages work is by contrasting

a Web server that supports Java Server Pages with Web server that doesn’t. JSP is easy
to learn, robust, scalable, and cross-platform.
Prior to the introduction of Java server Pages, the main function of
Tomcat Server was to serve static HTML pages. When someone requested a web page
from a web site using Tomcat server, the server would fetch a static HTML file form disk
or memory and send it out to the person’s browsers. The primary responsibility of
Tomcat Server was to act as an efficient interface between browser and a bunch of files
sitting on the Web server’s hard drive.
Apache Tomcat Server was not different from other Web servers in
this respect .The main function of any Web server is to server HTML files. It’s important
to understand how this process of serving an HTML file is carried out, so here are the
steps.
1. A user enters the Internet address of an HTML file into the address bat of
Web browsers and passes enter to request a Web page.
2. The browser sends a request for the Web page to a Web server such as
Tomcat server, Personal web server.
3. HTML file because the requested file has the extension.htm or html.
4. The Web server retrieves the proper HTML file from disk or memory and
sends the files back to the browser.
5. The person’s web browser interprets the HTML file and the results are
displayed in the browser window.
What are Java Server Pages?

Java Server Pages (JSPs) are Web pages that contain server-side scripts in
addition to the usual mixture of text and HTML (Hypertext Markup Language) tags.
Server-side scripts are special commands you put in Web pages that are processed before
the pages are sent from your Personal Web Server to the Web browser of someone who's
visiting your Web site. . When you type a URL in the Address box or click a link on a
Web page, you're asking a Web server on a computer somewhere to send a file to the
Web browser (sometimes called a "client") on your computer. If that file is a normal
HTML file, it looks exactly the same when your Web browser receives it as it did before
the Web server sent it. After receiving the file, your Web browser displays its contents as
a combination of text, images, and sounds.

In the case of a Java Server Page, the process is similar, except there's
an extra processing step that takes place just before the Web server sends the file. Before
the Web server sends the Java Server Page to the Web browser, it runs all server-side
scripts contained in the page. Some of these scripts display the current date, time, and
other information. Others process information the user has just typed into a form, such as
a page in the Web site's guest book.
The Web server retrieves the proper HTML file from disk or memory and
sends the files back to the browser.

HOW DO JAVA SERVER PAGES WORK?

 A JSP page is just like any other HTML file. Java statements must be
placed within <% and %> tag delimiters. Only ode placed within these delimiters will be
executed as Java code.

Browser Reqt Server sends a

JSP
a JSPs Page reqt to the JSP
S Engine
E engine
User’s R JSP page is
Computer V translated
E to a servlet
R And
Server sends JSP Engine sends
executed.
HTML back to Servlet HTML
the server output back to server.

What Do Java Server Pages Look Like?

The appearance of a Java Server Page depends on who or what is

viewing it. To the Web browser that receives it, and Java Server Page looks just like a
normal HTML page. If a visitor to your Web site views the source code of a Java Server
Page, that's what they see: a normal HTML page. However, the file located in the server
looks very different. In addition to text and HTML tags, you also see server-side scripts.
This is what the Java Server Page looks like to the Web server before it is processed and
sent in response to a request.

INTEGRATING SCRIPTS INTO JAVA SERVER PAGES

An Java Server Page is primarily a scripting environment; we can

integrate scripts created with both JScript and VBscript into our Java Server Pages. It can
be used other scripting languages with Java Server Pages as well. Any scripting language
that has a scripting engine can be used in an Java Server Page.
 The easiest way to add a script to an Java server Page is by using the
script delimiters <% and %>. Any text enclosed within these delimiters will be processed
as a script.

What Do Server-Side Scripts Look Like?

Server-side scripts look a lot like HTML tags. However, instead of

starting and ending with lesser-than (<) and greater-than (>) brackets, they typically start
with <% and end with %>. The <% is called an opening tag, and the %> is called a
closing tag. In between these tags are the server-side scripts. You can insert server-side
scripts anywhere in your Web page--even inside HTML tags.

Using Variables, and Forms in Java Server Pages

Forms are a convenient way to communicate with visitors to your

Web site. Using forms, you can create a survey form and ask visitors to fill it out. When
they fill out the form, you can process the results automatically.
With forms, there are two steps: first you create the form, and then
you process it. To create a form for a Java Server Page, just create a standard HTML
form.
Java Server Pages provide a mechanism for processing forms that,
unlike CGI scripting, doesn't involve serious programming: the Request. Form.
Considering the form above, we may create the file bellow and get a response.

Creating a Variable
You'll probably want to do more with your forms than display their
contents in a Web page. For example, based on the contents of the form, you may want to
create a variable and insert that variable in different places of your response page. You
may need to create a variable. To do that, just make up a name and set it equal to the
contents of the field.
Implicit Objects

 Request
 Response
 Page Context
 Session
 Application
Request:
It defines an object that provides access to HTTP-protocol-specific header
information sent by the client.

Response:
It defines an object that provides the JSP with the capability to manipulate HTTP-
protocol-specific header information and return data to the client.

Page Context:
It provides access to the namespaces associated with a JSP page. It also provides
accessors to several other JSP implicit objects.

Session:
It is used to store objects in between client requests. It provides an almost state-full
HTTP interactivity.

Application:
It is most often used to access environment information. One of the more common
pieces of information accessed by the application object is objects that are stoed in the
Servlet Context. These objects are stored there so that they will be available the whole
time the servlet engine is running.
Features of JSP

 Platform independence:
The use of JSP adds versatility to a Web application by
enabling its execution on any computer.

 Enhanced performance:
The compilation process in JSP produces faster results or
output.

 Separation of logic from display:

The use of JSP permits the HTML specific static content and a
mixture of HTML, Java, and JSP specific dynamic content to be placed
in separate files.

 Ease of administration:
The use of JSP eliminates the need for high-level technical
expertise, thereby helping Web developers, designers, content creators, and content
managers to work together and develop Java-based applications in less time and with less
effort.

 Ease of use:
All JSP applications run on major Web servers and operating
systems, including Microsoft IIS, Netscape Enterprise Server, iPlanet
Web Server, and Apache Web Server. These applications are also
available on Windows NT, Windows 2000, and Solaris 7.

About Oracle 8.0:

Relational Database Components:

 The database component of Oracle is a Structured Query Language (SQL)
based, scalable, relational database with integrated Extensible Markup Language (XML)
support for Internet applications. Each of the following terms describes a fundamental
part of the architecture of the Oracle database component.
Database

A database is similar to a data file in that it is a storage place for data. Like a
data file, a database does not present information directly to a user; the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.

Database systems are more powerful than data files in that data is more highly
organized. In a well-designed database, there are no duplicate pieces of data are grouped
together in a single structure or record, and relationships can be defined between these
structures, and records.

When working with data files, an application must be coded to work with the
specific structure of each data file. In contrast, a database contains a catalog that
applications use to determine how data is organized. Generic database applications can
use the catalog to present users with data from different databases dynamically, without
being tied to a specific data format.

A database typically has two main parts: first, the files holding the physical
database and second, the database management system (DBMS) software that
applications use to access data. The DBMS is responsible for enforcing the database
structure, including:

 Maintaining relationships between data in the database.

 Ensuring that data is stored correctly, and that the rules defining data
relationships are not violated.
 Recovering all data to a point of known consistency in case of system failures.

5. System Design

Introduction:

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:

1. Preliminary or general design

2. 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 structure design is a blue print of a
computer system solution to a given problem having the same components and
interrelationship among the same components as the original problem. Input, output and
processing specification are drawn up in detail. In the design stage, the programming
language and the platform in which the new system will run are also decided.

There are several tools and techniques used for designing. These tools and
techniques are:

 Flowchart
 Data flow diagram
 Data dictionary
 Structured English
 Decision table
 Decision tree

In the system design part is considered after the successful compilation of the
problem analysis. The requirements which and specified in software requirements
specification is verified i.e. whether the requirement specified in it satisfies the user
needs.

5.1. Project Description

Advanced Secured System developed act as a middleman between the client and the
server. It reduces the work of the server and gives access to server resources to multiple
clients at same time. It reduces the response time experienced by the clients. This server
will be cost-effective when compared to other servers in the market. Other servers in real
time provide a single service. The server, which we have designed, is to meet the real
time requirements .To share our thoughts with other clients in a network we can use chat
services where we can exchange out views in the form of typed-in messages. Chatting
can be provided as private chat and as well as multi-chat. This system in addition checks
whether virus file have affected the system and acts as a firewall to save the system from
viruses. If it finds a virus it will report to the server what action to be taken against the
virus file. The server can delete the file from the system or it can block the virus or it can
repair the virus and quarantine the infected file. If the users are on-line they can share the
messages through chatting, if the users are on offline they can share their views through
sending mail to the users in the network who himself registered them as the clients of our
system.

User Registration:

Authentication is the technique by which a process verifies that its

communication partner is who it is supposed to be and not an intruder. In order to provide
authentication in this project USER NAME AND PASSWORD has been
designed.
 LOGIN
 NEW USER
LOGIN:
Login button is used to display the Login Dialog Box. It has two text
fields and one buttons. User Name and password are entered in their respective fields.
Entered user name and password are send to the server and checked with its database.
If valid user, then the user is permitted to enter into the system and their names are
added to the list boxes of both the client and the server. If invalid user then the user
exits out of the system.
USER:
User button is used to display the New User Dialog Box. It contains the
fields such as User Name, password, First Name, Last Name-mail address, Age, Sex,
phone Security Question Answer. The new user can enter into the system by giving
the details in their respective fields. If the user name and password are non-existence
they are considered as a valid user and sent to the server database.

Establish connection between a client and server. Store login ids of all users of
in the server database. Get the user name & password. Check for the correctness of user
name and password. If it is correct enable the user to use the services else move the user
to error page.

To provide a strong authentication for this system, each user will be provided with
a unique username and password. First the users must register in this system before they
access this system. In registration time, the users will have to answer the questions
provided by the system. The questions will be based on the networking side. If the users
answers the questions and the system will verify the answers and depending upon the
correct answers the system will generate a key. There are three types of categories
depending upon the key generated by the system.
First category of services will provide:
1. File Transfer
2. E-mail
3. Resource Sharing
4. Web page view
5. Chat
Second Category of services will provide:
1. File Transfer
2. E-mail
3. Web page View
Third category of services will provide
1. File Transfer
2. E-mail
Each time user enters the system it will check for strong authentication whether
the username and password is valid. If the authentication is valid, the services will be
provided to the user else the user will be move to error page. If the username a password
will be sometimes wrong by misspelled so the user can be once again redirected to the
main page.

File Transfer:
If a user wants to access a file in the server he must make a request to the server.
There are three steps followed in File transfer
1. File search
2. Virus File check
3. DAP Concept
First step in File search, it receives a request from the user. The request will
be a file name. First the server finds all root drives in the system. It then searches
for all folders in the system. Then it moves to search for all the subfolders in the
system and it searches the requested file name will reside in subfolder. If it exists
then it will took the file and move to next step i.e. virus check else it reports the
requested file does not reside in the system.
Second step will receive the file name and check whether the file name
matches with the updated virus file in the database. If it exists then the server will
report the requested file is virus file else then it will move to next phase which is
transferring the file.
Third step uses DAP concept, i.e. check the file length. If the requested file is
a valid one then the server starts to transfer the file from server to client location.
After transferring the file, the server check for the file length. It checks the length
of the file, before and after transmission .If it equals then the file transfer will be
completed else the file transfer is corrupted. Then again it will transfer the file,
until the file transfer is completed.

E-Mail:

Mail is one of the services provided by this system. The ability to compose, send
receive; delete electronic mail has been enormously popular. In this project, E-Mail
can be sent to the recipient without having to enter into the Web
browser. Electronic mail is one of the ways where we can send our
messages to a group of people. It is a mixture of text, drawings and
facsimile. Normally mail consists of two subsystems: the user agents,
which allow people to read and send email and the message transfer
agents, which move the messages fro the source to destination. The
message inside the envelope contains two parts: the header and the
body. The header contains control information for the user agents. The
body is entirely for the human recipient. To send an email a user must
provide the message, the destination address and possibly some other
parameters (e.g., the priority or security level). The message can be
produced with an editor built into the user agent. The destination
address must be in the format that the user agent can deal with. Many
user agents expect DNS addresses of the form mailbox@location.
When a user is started up to read an email, it will look at the
user’s mailbox
for incoming email before displaying anything on the screen. Then it
may announce the messages in the mailbox or display a on-line
summary of each one and wait for a command. In a sophisticated
system, the user can specify which fields to be displayed by providing
a user profile, a file describing the display format. The first field is
message no. The second field, Flags k meaning that the message is not
new but was read previously and kept in the mailbox. The third filed
tells how long the message is and the fourth field tells who send the
message. Finally, the subject field gives the brief summary what the
message is about.

Resource Sharing:

Resources may include, information retrieval, computer data processing,

transmission and storage, and any other functions performed, in whole or in part, by the
use of a computer, computer network, computer software, or computer program. In this
project Resources related to hardware and software are used.
Server provides all applications, files and messages. If a client wants
applications from the server, the server grants permission to the particular client
according to their authentication level, i.e., applications is shared to clients. The client
can access the printer, which are attached to the server when a request is provided. If the
printer is connected in the server, and one or more clients request for print options then
the server will provide a queuing system. Then the service will be provided to each user
according to queue formed in the server. If the printer is not connected it will sent an
error message. The provider sends the applications from the server to the requested client.
Resources include devices such as CD, Floppy and Printer. The clients access these
devices, which are attached to the server when a request is provided. If one or more users
request the same device then the server will maintain a queue and provide the services to
the users according the queuing system maintained in the server.
Authentication is provided to client to access the devices from the server.
The example devices that can be accessed like Floppy Drive, Printer. Directories & files
are displayed on client machine and can be saved on the client machine according to the
Provided authentication.

Web page View:

The user requests a webpage in the server, if the page resides in the server then
the copy of the page will given to the client. In this service the page will be transferred
and immediately opened at the client window. This service will provide that the page will
reside in the server and it will be opened in the client side without any requirements. This
service is entirely different from transferring a file from the server. In that service the file
will be transferred to the client side and it will be saved on the client side and the user
may open the file according to his wish. But in webpage view the file will not be saved
on the client side, it will be opened on the client side and source file may reside in server.

Chat:

Chatting means exchanging the information between the users. Usually this kind
of “talking” is the exchange of typed-in messages requiring one site as the repository for
the messages and a group of users who take part on the network. In some cases, a private
Chat can be arranged between two parties who meet initially in a group. Chat can be
ongoing or scheduled for a particular time and duration. Chat is one way of exchanging
our views. The chat can be selected on a certain topic such as politics, religion,
entertainment, education, business etc... The chat can be done with a group of people and
there are ways were we could exchange confidential matters through private chat. In our
system when we register ourselves as a user the system will provide you a username and
password. That username will be considered as your id for chatting.

5.2. Data Flow Diagram

A DFD is a modeling tool that allows us to show a system as a network of

processes (mini systems) connected to each other by paths of data.

Data Flow:
Each arrow in a DFD Represents a path (or pipeline of conveyer belt) of data,
called the Data Flow.

Process:
A process represents an automated or manual activity that transforms incoming
data flows to outgoing data flows.

Data-Store:
A Data-Store holds the data (for reference), which the system cannot remember.
External events and system responses ate From/To “Sources” or “Destination” of the
system.

Components of DFD:
The basic components of DFD are following

Source/Destination
 Process

Data Source

DFD are based on the strategy of structured techniques, Namely:

1. Graphics
2. Top Down Approach
3. Separation of logical from the physical
4. Partitioning

DFD is do not show

• How things begin & end
• Loops
• Decisions

System Flow Diagram

Start

Enter Username &

Password

Login

No Is
Valid?
 Yes

File Transfer Mail Resource sharing Web Page View Chat

Data Flow Diagram

1. User Validation

LOGIN

Registration
User validation
Username,
Password Username,
Password,
Login Key
Vali
No
d
DB
User
 Yes

File Mail Resource Chat Webpage

2. File Transfer

File Transfer

File No
Exists File Not Found

Yes

Yes
Virus Virus Error Page
Virus File
File
No

File

Transfer

If file length
Not equals
 DAP

If file length equals

File Transfer Completed

3. Mail

Mail

Inbox Compose

Mail

DB

Received Messages

4. Resource Sharing

Floppy Drive
 Client
Requests
Client Had Drives
Server
Server
Responds CD-Drive

Printer

5. Web Page View

Webpage Request

Page No
Exists Webpage Not Found

Yes

Webpage View

6. Chat

Chat server
 Client-1 Client-1

5.3. Database Design

Database Design is a crucial factor in the performance of a system both in

terms of system timings and in the case with which the system can be maintained or
modifies.

Table Name: Login

Field Name Data Type Description

User Varchar Client code
Pwd Varchar Password
Key Varchar Key

Table Name: Virus

Field Name Data Type Description

Virus Number Virus Name

Table Name: Mail

Field Name Data Type Description

Frm Varchar Sender’s Name
To Varchar Receiver’s Name
Sub Varchar Subject
Time Varchar Time
Msg Varchar Message

Input Design
 The goal of designing input data is to make entry easy, free from errors and
validations should be maintained such that end users feel comfortable and user friendly
while entering data into the system. When the programmer approach input design the first
task is to design the source document that captures the data and select media as used to
enter into the computer.

User Entry

In this user entry enter the user id and password. It is used for perform the
securable data operation.

6. SYSTEM TESTING AND IMPLEMENTATION

6.1. TESTING FUNDAMENTALS

Software testing is an important element of S/W quality assurance

and represents the ultimate review of specification, design and coding. The increasing

visibility of S/W as a system element and the costs associated with a S/W failure are

motivating forces for well planned, through testing.

Though the test phase is often thought of as separate and distinct

from the development effort--first develop, and then test--testing is a concurrent process

that provides valuable information for the development team.

There are at least three options for integrating Project Builder into

the test phase:

 Testers do not install Project Builder, use Project Builder functionality to

compile and source-control the modules to be tested and hand them off to

the testers, whose process remains unchanged.

  The testers import the same project or projects that the developers use.

 Create a project based on the development project but customized for the

testers (for example, it does not include support documents, specs, or

source), who import it.

A combination of the second and third options works best.

Associating the application with a project can be useful during the testing phase, as well.

We can create actions to automatically run test scripts or add script types and make them

dependent on the modules to test.

TESTING OBJECTIVES

There are several rules that can serve as testing objectives.

They are

1. Testing is a process of executing a program with the intent of finding an error.

2. A good test case is one that has a high probability of finding an undiscovered

error.

3. A successful test is one that uncovers an undiscovered error.

If testing is conducted successfully according to the objectives stated above, it

will uncover errors in the software. Also, testing demonstrates that software functions

appear to the working according to specification, that performance requirements appear

to have been met.

Testing Principles:
 All tests should be traceable to customer requirements. The objective of
software testing is to uncover errors.

Tests should be planned long before testing begins. Test planning can design as
soon as the requirements model is complete. All tests should be planned and designed
before any code has been generated.

The parento principle applies to software testing. The parento principle implies
that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent
of all program modules.

The testing should begin “in the small” and progress toward testing “in the
large”. To be more effective testing should be conducted by an independent third party.
By “most effective”, testing means that has the highest probability of finding errors.

A successful test case is one that uncovers an as-yet-undiscovered error.

Software testability is how a computer program can be tested. The following list of
categories shows that this software has been tested.

Software testing is often referred as verification and validation. Verification

refers to the set of activities that ensures that the software correctly implements the
specific function. Validation refers to a different set of activities that ensures that the
software that has been built is traceable to the customer requirements.

OBJECT ORIENTED TESTING

VALIDATION TESTING:

Validation testing is one, which checks the given data is a valid one, or

not. In our system, first stage username and password is checked. If it is a valid one, then
the services will provided to the user. Hence validation testing takes place at the earlier

part of our project. This is one of the most crucial one, which takes place at the all kind of

projects.

6.2.UNIT TESTING

Unit testing focuses the verification effort on the smallest unit of

S/W design i.e., the module. The unit testing is always white-box oriented and the step

can be conducted in parallel for modules.

During unit test, testers can use the same project or projects as the

developers, if functional units organize the project, or separate projects have been created

for functional units. The project or projects can also be exported, so unit test can take

place in a variety of environments and on a variety of platforms.

Unit testing comprises the set of test performed by an individual programmer prior
to integration of the unit into a larger system. There are different types of tests to be
performed on a programming unit. These may be classified as follows:

 Functional Tests
 Performance Tests
 Stress Tests
 Structure Tests

Functional Test cases involves exercising the code with normal input values
for which the expected results are known, as well as boundary values and special
values.
Performance Testing determines the amount of execution time spent in
Various parts of the unit, program throughput, response time and device
utilization by the program unit.
 Stress Tests are those tests designed to intentionally break the limit. A great
deal can be learnt about the strengths and limitations of a program by examining
the manner in which a program unit breaks.

Structure Tests are concerned with exercising the internal logic of a program and

traversing particular execution paths to exercise, deriving test date, determining the

criterion to be used, executing test cases.

UNIT TEST CONSIDERATIONS

The tests that occur as part of unit testing. The module ‘interface’ is

tested to ensure that information properly flows into and out of the program unit under

test. The ‘local data structures’ are examined to ensure that data stored temporarily

maintains its integrity during all steps in an algorithms execution.

‘Boundary Conditions’ are tested to ensure that the module operates

properly at boundaries established to limit or restrict processing. All ‘independent paths’

through the control structures are exercised to ensure that all statements in a module have

been executed at least once. Finally, all ‘error-handling paths’ are tested.

UNIT TEST PROCEDURES

Unit testing is considered an equivalent to the coding step. After the

source level code has been developed, reviewed and verified for correct syntax, unit test

case design begins since a module is not a stand alone program, ‘driver’ and/or ‘stub’

S/W must be developed for each unit test.

 In most applications, a driver is nothing more than a main program

that accepts test case data, passes such data to the module to be tested, and prints the

relevant results. The stubs serve to replace modules that are subordinates called by the

modules to be tested. A stub or a dummy stub or a dummy subprogram uses the

subordinate modules interface, may do minimal data manipulation, prints verification of

entry, and returns. The drivers and scrubs represent overhead i.e., both are S/W that must

be written but that is not delivered with the final S/W product. If the drivers and the stub

are kept simple, then the overhead is low.

In Our project, Unit testing takes place at every module. First stage

the file name is requested from the user. Then the server searches the file in the

system. If the file exists in the system then it will moves for virus checking. If the file

is a valid one then it will be transferred to the client location. After transferring the

file, it will check the length of the file before and after transmission. If the length

equals then the file transfer is completed otherwise we have to retransmit the file.

The Unit Test is carried out in this project, and is found successful. The

data is flowing correctly to all part of the project.

6.3. INTEGRATION TESTING

It addresses the issues associated with the dual problems of verification and program
construction. Black box test case design techniques are the most prevalent during
integration, although a limited amount of white box testing may be used to ensure
converge of major control paths. Integration testing is a systematic technique for
constructing the program structure while at the same time conducting tests to uncover
errors associated with interfacing. The objective is to take unit-tested modules and build
a program structure that has been depicted by design.
Incremental Integration Strategies are

 Top-Down Integration
 Bottom-Up Integration

Test cases were designed so that all units tested modules were executed
from the main module and the reports were generated to check the results with the
expected results.

After has been integrated, a set of high order tests are conducted, validation

criteria must be tested.

In our project, integration testing checks if the validation part is

correct then user will allow to move to next step i.e. the home page where all kinds

of services resides. It means it will maintain a bridge to move to other modules and

integrate them.

Integration testing is a systematic technique for constructing the program

structure while at the same time conducting test to uncover errors associated with

interfacing. The objective is to take unit-tested modules and build a program structure

that has been dictated by design.

TOP-DOWN INTEGRATION

This method is an incremental approach to the construction of

program structure. Modules are integrated by moving downward through the control

hierarchy, beginning with the main program module.

Importing the test project and setting up the testing environment

The process of importing a test project and

setting up a testing environment is the same as the process for importing a project and

setting up the environment for development.

Adding test scripts and test data to the project

You may need to add some items, such as test
scripts, to the project. In addition, you may need to add connection strings to database
accounts containing test data.

Remember that you can automate the running

of test scripts just as you can automate actions associated with the modules in your
application.

Modifying actions and macros to facilitate testing

If actions specifying "run with debugging"

have not already been provided, you can either modify existing actions to include a

debug flag, or create new actions.

 6.3. Acceptance Testing

This test was performed with the users of the system and made sure that
it performed as they expected. It was verified that all functionality required by the
user have been satisfied. So for, the system has been found defect free and is
working well.

6.4. IMPLEMENTATION

Once the system has been designed, the next step is to convert the

designed one in to actual code, so as to satisfy the user requirements as excepted. If the

system is approved to be error free it can be implemented.

When the initial design was done for the system, the department was

consulted for acceptance of the design so that further proceedings of the system

development can be carried on. After the development of the system a demonstration was

given to them about working of the system. The aim of the system illustration was to

identify any malfunctioning of the system.

Implementation includes proper training to end-users. The

implemented software should be maintained for prolonged running of the software.

Initially the system was run parallel with manual system. The

system has been tested with data and has proved to be error-free and user-friendly.

Training was given to end -user about the software and its features.
 7. MAINTENANCE

The term “software maintenance” is used to describe the

software engineering activities that occur following delivery of a software product to

the customer. The maintenance phase of the software life cycle is the time period in

which a software product performs useful work.

Maintenance activities involve making enhancement to

software products, adapting products to new environments and correcting problems.

Software product enhancement may involve providing new functional capabilities,

improving user display and modes of interaction, and upgrading external documents.

Adaptation of software to a new environment may involve moving the software to a

different machine. Problem correction involves modification and revalidation of

software to correct errors.

The enhancement of this project can be accomplished

easily. That is, any new functional capabilities can be added to the project by simply

including the new module in the homepage and giving a hyperlink to that module.

Adaptation of this project to a new environment is also performed easily.

7.1. Corrective Maintenance

 Even with the best quality assurance activities, it is likely that

they customer will uncover defects in the software. Corrective maintenance changes the

software to correct defects.

7.2. Adaptive Maintenance

An activity that modifies the software to properly interface with a

changing environment. The system has been modified so that various change include to

the new system.

In case of Fund Transfer, adoptive maintenance has been

performed, that is in earlier system (character based UNIX system) changes are fixed and

if any new changes are to be included, was a difficult task. Now provisions are given so

that the user can define various changes. Such as it designed to accommodate the new

change in further.

7.3. Enhancement Maintenance

As software is used, the customer/user will recognize additional

functions that will provide benefit. Perceptive maintenance extends the software beyond

its original functional requirements.

In the case of Advanced secured system can be added new

functions such that the user can able to retrieve the information in a user friendly and it

will be very helpful for future development.

8. Screen Layouts
 9. Conclusion

This project incorporates all requirements of a Server. This system has

been developed as versatile and uses friendly as possible keeping in mind the

advanced features in this technology.

This is precisely where the ADVANCED SECURED SYSTEM fit

into place. This System supports and improves many of the core functionality of the

organization. Using such a system helps the organization in minimizing the time and

money consumed in fulfilling the day-to-day functionality’s and cutting down the

expenses incurred on the same. The real world requirements was satisfied by this system

which provides all services like e-mail, chat… The File Transfer is very effective where

this system uses the concept of DAP. E-mail is one of the service which we can send mail

through the intranet. Resource sharing can be achieved through this system. In our day

today life, we have to move to third party to get mail, chat etc… But this problem is

solved using our system. So our system will be cost effective and used in any platform.

Using JSP and Oracle 8.0, the system was developed. As a whole, the
system was wellplanned and designed.
 10. Future Scope of the Project

The project will be more users friendly with the future enhancement of
having the mailing facility, which will intimate the users to send their messages to
internet itself. As well as verification mails, warning mails and news updates to be send
to the using the automatic mailing facility. The enhancement also consists of making
private chat more effectively and connecting to ftp server for file transfer in the internet.
Further, this project can be proposed to use EJB for further deployment purposes. This
facility will make the Server a complete one.
 11. Bibliography

Book Name : Mastering JSP

Author : A. Russell Jones
Book Name : JSP Developer’s Guide
Author : Gregpuezek
Book Name : Oracle 8.0
Author : Cassel & Palmer