Beruflich Dokumente
Kultur Dokumente
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
CONTENTS
1.
Introduction
1.1
1.2
2.
System Analysis
2.1
2.2
3.
Project Description
Data Flow Diagram
Database Design
7.
Hardware Specification
Software Specification
4.2.1 About the Software
System Design
5.1
5.2
5.3
6.
Technical Feasibility
Economical Feasibility
Operational Feasibility
System Specification
4.1
4.2
5.
Existing System
Proposed System
Feasibility Study
3.1
3.2
3.3
4.
Company Profile
About the Project
Testing Fundamentals
Unit Testing
Integration Testing
Acceptance Testing
Implementation
Maintenance
7.1
7.2
7.3
Corrective Maintenance
Adaptive Maintenance
Enhance Maintenance
8.
Screen Layout
9.
Conclusion
Bibliography
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
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.
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.
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.
4. System Specification
4.1. Hardware Requirements
Processor
Clock Speed
667 MHz
RAM
128 MB
Hard Disk
4 GB or higher
Monitor
Mouse
Keyboard
Cache Memory
11,011,968 Bytes
Virtual Memory
32 MB
Display Card
Operating System
: Windows 98/2000/XP/NT
Web Server
Web Browser
: Internet Explorer
Front-End Tool
: HTML
JavaScript
Back-End Tool
: Oracle 8.0
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:
4. The Web server retrieves the proper HTML file from disk or memory and
sends the files back to the browser.
5. The persons web browser interprets the HTML file and the results are
displayed in the browser window.
Server sends a
HTML back to
JSP
reqt to the JSP
Engine
engine
JSP page is
translated
to a servlet
And
JSP Engine sends
executed.
Servlet HTML
the server
a JSPs Page
Users
Computer
Server sends
S
E
R
V
E
R
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.
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 HTTPprotocol-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.
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.
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
users 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
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.
Components of DFD:
The basic components of DFD are following
Source/Destination
Process
Data Source
Loops
Decisions
Start
Login
No
Is
Valid?
Yes
File Transfer
Resource sharing
Chat
1. User Validation
LOGIN
Registration
User validation
Username,
Password
Username,
Password,
Key
Login
No
Valid
User
DB
Yes
File
Resource
Chat
Webpage
2. File Transfer
File Transfer
File
Exists
No
Yes
Yes
Virus
Virus
File
No
File
Transfer
Virus File
Error Page
If file length
Not equals
DAP
3. Mail
Compose
Inbox
Mail
DB
Received Messages
4. Resource Sharing
Floppy Drive
Client
Client
Requests
Had Drives
Server
Server
Responds
CD-Drive
Printer
Webpage Request
Page
Exists
Yes
Webpage View
6. Chat
No
Chat server
Client-1
Client-1
Data Type
Description
User
Pwd
Key
Varchar
Varchar
Varchar
Client code
Password
Key
Field Name
Data Type
Description
Virus
Number
Virus Name
Data Type
Description
Frm
To
Sub
Time
Msg
Varchar
Varchar
Varchar
Varchar
Varchar
Senders Name
Receivers Name
Subject
Time
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.
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.
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
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.
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.
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
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
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.
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.
Using JSP and Oracle 8.0, the system was developed. As a whole, the
system was wellplanned and designed.
11. Bibliography
Book Name
: Mastering JSP
Author
: A. Russell Jones
Book Name
Author
: Gregpuezek
Book Name
: Oracle 8.0
Author