A

PROJECT REPORT ON
< NAME OF PROJECT >

SUBMITTED BY

< NAME OF MEMBER1 >

< NAME OF MEMBER 2 >
< NAME OF MEMBER 3 >
< NAME OF MEMBER 4 >

UNDER THE GUIDANCE OF

PROF. <NAME OF GUIDE>

DEPARTMENT OF
 2010-2011

CERTIFICATE
This is to certify that the report on project entitled, <NAME OF PROJECT>
submitted by
< NAME OF INDIVIDUAL>
has been accepted as a partial fulfillment for
degree course of Mumbai University for the
academic year 2010-2011.

___________________
PROF. <NAME OF GUIDE> ____________________
(INTERNAL GUIDE) INTERNAL EXAMINER

___________________
Prof. ____________________
(H.O.D) EXTERNAL EXAMINER

____________________

(PRINCIPAL)

DEPARTMENT OF
 2010-2011

We feel privileged to express our deepest sense of gratitude and sincere thanks to
our project guide Prof. <Name of Guide> for his/her excellent guidance throughout our
project work. His/her prompt and kind help led to the completion of the dissertation
work.
We would also like to thank our H.O.D. Prof. for approving our project
and giving us ideas regarding the project.
We also wish to thank them for their patience and co-operation, which proved
beneficial for us.
We owe a substantial share of our success to the whole faculty and staff members
of , which provided us the
requisite facilities required to complete the project work.
Finally, we wish to express our sincere appreciation and thanks to our college
library and all those who have guided and helped us directly or indirectly for
accomplishing our goal.
SR. NO TITLE PAGE NO.

1 Introduction & Literature survey

1.1..Aim
1.2.Existing system
1.3.Proposed system
1.4. System modules
2 System requirement
2.1. Software requirement
2.2. Hardware requirement
3 Project Analysis And Design

4 Software Description
4.1.Java
5 Project Analysis And Design

6 System Design
6.1.Use Case Diagram
6.2.Activity Diagram
6.3.Flow Diagram 1
6.4.Flow Diagram 2
6.5.Flow Diagram3
7 Advantages & Disadvantages
7.1.Advantages
7.2.Disadvantages
8 Project estimation

9 Feasibility study
10.1.Financial feasibility study
10.2. Technical feasibility study
10 System implementation

11 Snapshot

12 Conclusion

13 Bibliography
1. INTRODUCTION

PROJECT PROBLEM AND RELEVANCE KNOWLEDGE

In the field of networking, the specialist area of network security consists of the
provisions made in an underlying computer network infrastructure, policies adopted
by the network administrator to protect the network and the network-accessible
resources from unauthorized access, and consistent and continuous monitoring and
measurement of its effectiveness (or lack) combined together.

The terms Network Security and Information Security are often used interchangeably.
Network Security is generally taken as providing protection at the boundaries of an
organization by keeping out intruders (hackers). Information Security, however,
explicitly focuses on protecting data resources from malware attack or simple
mistakes by people within an organization by use of Data Loss Prevention (DLP)
techniques. One of these techniques is to compartmentalize large networks with
internal boundaries. Employees have to cross these boundaries and be authenticated
when attempting to access protected information.
REQUIREMENTS GATHERING
The first phase of software project is to gather requirements. Gathering software
requirements begins as a creative brainstorming process in which the goal is to
develop an idea for a new product that no other software vendor has thought. New
software product ideas normally materialize as a result of analyzing market data and
interviewing customers about their product needs.
The main function of the requirements gathering phase is to take an abstract idea that
fills a particular need or that solves a particular problem and create a real world
project with a particular set of objectives, a budget, a timeline and a team.
Some of the highlights of the requirement gathering phase include
Collecting project ideas
Gathering customer requirements and proposed solutions
Justifying the project
Submitting the request for proposal
Getting the team in place
Preparing the requirements document

Collecting project ideas

Coming up with project ideas can prove expansion exercise.
Gathering customer requirements and proposed solutions

Focus on solving the customers particular problems and fulfilling the customers
needs.
Justifying the project
An important part of the requirements gathering phase is to decide whether a
particular project is more or less likely to make the company successful.
Submitting the request for proposal
The request for proposal is an important document that senior management uses
to decide which projects are likely to show a profit and therefore are worthy of
allocating a budget for further testing and study.
Getting the team in place
One of the requirements of every project is a team to work on the project. The
team includes the project sponsor, a project manager, analysts, developers, database
administrators, technical writers, quality assurance testers, trainers, release managers
and possibly others.
Preparing the requirements document
The Requirements Document (RD) becomes main input to analysis phase. It
includes a summary of the requirements to solve the objective of the project, the major
features of the product, a documentation plan, a support plan, and licensing issues.
ANALYSIS

The main function of the analysis phase is to look carefully at the requested
features with an eye toward the issue that each may create in the actual coding. This
phase is the time during which reasonably deliverable thoughts of each team member
can be decided.
The analysis phase depends on completing the deliverables that are provided
during the requirements gathering phase particularly, in the Requirement Documents.
After analyzing the requirements document phase, the project team members create
several deliverables, which act as input to other process. They are,
Project scope document(PSD)
This document is the most critical deliverable document in the analysis phase.
The PSD document prioritizes and limits the high level deliverables from the
Requirements Document to a manageable list in project phase. It also includes time
estimates for completing each requested feature. Project team and the product
marketing manager typically undergo extensive negotiations before all stakeholders
approve the PSD.

Work breakdown structure

Successful project management includes the ability to take complex tasks and
break them down into manageable chunks which can be achieved easily. The work
breakdown structure is first pass effort at the rate of defining the task. It is necessary
for completing project and assigning resources to those tasks.
 Baseline project schedule
Wide range of software tools can be used to schedule and track project. One
such tool is Microsoft project. By using the documents that are developed up to this
point, a baseline schedule in Microsoft project will be developed that serves as a
measuring stick for the duration of project.

2. SYSTEM REQUIREMENT

2.1.HARDWARE CONFIGURATION:
PROCESSOR : PENTIUM IV
HARD DISK CAPACITY : 40 GB
MONITOR :14 SAMTRON MONITOR
FLOPPY DISK DRIVE :1.44 MB
PRINTER : TVS 80 COLOR
INTERNAL MEMORY CAPACITY : 128 MB
KEYBOARD : LOGITECH OF 104 KEYS
CPU CLOCK :1.08 GHz
MOUSE : LOGITECH MOUSE

2.2.SOFTWARE CONFIGURATION:

OPERATING SYSTEM : WINDOWS XP

FRONT END : JDK1.6.0
4. SOFTWARE DESCRIPTION

TECHNOLOGY: 1) JAVA

Java:

Java is a new computer programming language developed by Sun

Microsystems. Java has a good chance to be the first really successful new computer
language in several decades. Advanced programmers like it because it has a clean,
well-designed definition. Business likes it because it dominates an important new
application, Web programming.

Features

Sun describes Java as

Simple
Object-oriented
Distributed
Robust
Secure
Architecture Neutral
Portable
Interpreted
High performance
Multithreaded
Dynamic.
Java is simple.

What it means by simple is being small and familiar. Sun designed Java as closely to
C++ as possible in order to make the system more comprehensible, but removed many
rarely used, poorly understood, confusing features of C++. These primarily include
operator overloading, multiple inheritance, and extensive automatic coercions. The
most important simplification is that Java does not use pointers and implements
automatic garbage collection so that we don't need to worry about dangling pointers,
invalid pointer references, and memory leaks and memory management.

Java is object-oriented.

This means that the programmer can focus on the data in his application and the
interface to it. In Java, everything must be done via method invocation for a Java
object. We must view our whole application as an object; an object of a particular
class. .

Java is distributed.

Java is designed to support applications on networks. Java supports various levels of

network connectivity through classes in java. net. For instance, the URL class
provides a very simple interface to networking. If we want more control over the
downloading data than is through simpler URL methods, we would use a
URLConnection object which is returned by a URL URL.openConnection () method.
Also, you can do your own networking with the Socket and Server Socket classes.
Java is robust.

Java is designed for writing highly reliable or robust software. Java puts a lot of
emphasis on early checking for possible problems, later dynamic (runtime) checking,
and eliminating situations that are error prone. The removal of pointers eliminates the
possibility of overwriting memory and corrupting data.

Java is secure.

Java is intended to be used in networked environments. Toward that end, Java

implements several security mechanisms to protect us against malicious code that
might try to invade your file system. Java provides a firewall between a networked
application and our computer.

Java is architecture-neutral.

Java program are compiled to an architecture neutral byte-code format. The primary
advantage of this approach is that it allows a Java application to run on any system
that implements the Java Virtual Machine. This is useful not only for the networks but
also for single system software distribution. With the multiple flavors of Windows 95
and Windows NT on the PC, and the new PowerPC Macintosh, it is becoming
increasing difficult to produce software that runs on all platforms.

Java is portable.

The portability actually comes from architecture-neutrality. But Java goes even further
by explicitly specifying the size of each of the primitive data types to eliminate
implementation-dependence. The Java system itself is quite portable. The Java
compiler is written in Java, while the Java run-time system is written in ANSI C with
a clean portability boundary.
Java is interpreted.

The Java compiler generates byte-codes. The Java interpreter executes the translated
byte codes directly on system that implements the Java Virtual Machine. Java's
linking phase is only a process of loading classes into the environment.

Java is high-performance.

Compared to those high-level, fully interpreted scripting languages, Java is high-

performance. If the just-in-time compilers are used, Sun claims that the performance
of byte-codes converted to machine code are nearly as good as native C or C++. Java,
however, was designed to perform well on very low-power CPUs.

Java is multithreaded.

Java provides support for multiple threads of execution that can handle different tasks
with a Thread class in the java. Lang Package. The thread class supports methods to
start a thread, run a thread, stop a thread, and check on the status of a thread. This
makes programming in Java with threads much easier than programming in the
conventional single-threaded C and C++ style.

Java is dynamic.

Java language was designed to adapt to an evolving environment. It is a more

dynamic language than C or C++. Java loads in classes, as they are needed, even from
across a network. This makes an upgrade to software much easier and effectively.With
the compiler, first we translate a program into an intermediate language called Java
byte codes ---the platform-independent codes interpreted by the interpreted on the
Java platform. The interpreter parses and runs each Java byte code instruction on the
computer. Compilation happen s just once; interpretation occurs each time the
program is executed.

Overview of the Swing

The Swing package is part of Java Foundation Classes (JFC) in the Java platform. The
JFC encompasses a group of features to help people build GUIs; Swing provides all
the components from buttons to split panes and tables.

Swing Features and Concepts:

It introduces Swings features and explains all the concepts we need to be able to use
Swing components effectively.

Swing Components and the Containment Hierarchy:

Swing provides many standard GUI components such as buttons, lists, menus and
textareas, which we combine to create our programs GUI. It also includes containers
such as windows and tool bars.
Layout Management:
Containers use layout managers to determine the size and position of the components
they contain. Borders affect the layout of Swing GUIs by making Swing components
larger. We can also use invisible components to affect layout.

Event Handling:
Event handling is how programs respond to external events, such as the user pressing
a mouse button. Swing programs perform all their painting and event handling in the
event-dispatching thread.
Painting:
Painting means drawing the components on-screen. Although its easy to customize a
components painting, most programs dont do anything more complicated than
customizing a components border.

Threads and Swing:

If we do something to a visible component that might depend on or affect its state,
then we need to do it from the event-dispatching thread. This isnt an issue for many
simple programs, which generally refer to components only in event -handling code.
However, other programs need to use the invoke Later method to execute component-
related calls in the event-dispatching thread.

More Swing Features and Concepts:

These are some of the major concepts we need to know to build Swing GUIsthe
containment hierarchy, layout management, event handling, painting, and threads.
These are some of the other important Swing features. They are

Features that JComponent provides

Icons
Actions
Pluggable Look and Feel support
Support for assistive technologies
Separate data and state models
5: PROJECT ANALYSIS AND DESIGN

Requirement analysis:

We divide requirement analysis into two parts:-

2.1.1 Functional Requirement
2.1.2 Nonfunctional Requirement

Functional Requirement: -
In functional requirement, we describe the module we require to
develop this project.

The project contains three modules. They are,

Lock computer

Unlock computer

Network Configuration
MODULE DESCRIPTION

LOCK COMPUTER
By processing the lock procedure we can lock the remote system.
In the network locking we need client system and server system to lock
the start menu, desktop and taskbar with the help of the password

UNLOCK COMPUTER
By processing the unlock procedure we can unlock the remote system.
With the help of password we can unlock the start menu, desktop and taskbar

NETWORK CONFIGURATION
This is the first module, which is used to select the IP address is going to
do the network lock process.
With the help of this network configuration, we can select the remote
system.

Nonfunctional Requirement: -
Nonfunctional requirement is nothing but the supporting system for the software or
project.
Following are the Hardware And Software requirement of the project: -

SYSTEM DESIGN
DESIGN
The design phase is the one, where the technical problems are really solved that makes
the project a reality. In this phase the relationship of the code, database, user interface,
and classes begin to take shape in the minds of the project team. During the design
phase, project team is responsible for seven deliverables:
Data model design
User interface design
Functional specifications
Documentation plan
Software Quality Assurance (SQA) test plan
Test cases
Detailed design specifications.
Data model or schema
The primary objective in designing the data model or schema is to meet the
high level software specifications that the requirement document outlines. Usually the
database administrator (DBA) designs the data model for the software project.
User interface
The user interface is the first part of the software application that is visible to the user.
The UI provides the user with the capability of navigating through the software
application. The UI is often known in the software industry as the look and feel aspect
of the software application. The design of the UI must be such that, the software
application provides an interface that is as user friendly and as cosmetically attractive
as possible.
Prototype
After the data model and UI design are ready, project team can design the prototype
for the project. Sales and marketing teams generally cannot wait to get prototype in
hands to show it off to sales prospects and industry trade shows.

Functional specification
It provides the definitive overview of what is included in the project. This deliverables
incorporates many of the documents that prepare to this point, gathering them into one
place for easy reference.
Documentation plan
The technical publications manager or the technical writer on the project writes the
documentation plan. The plan provides an overview of the software product
documenting, the recommended processes and procedures, and a list of document
deliverables for the project.
Detailed design specifications
It provides a high level view of the project. Detailed design specification, layouts the
blueprint of how to develop the project. The design specifications includes document
that has been created to design phase but in some cases, provides step by step
information on how to implement the specifications.
Software quality assurance test plan and test cases
Deliverables are software quality assurance test plan, test cases, test data, entrance test
plan test automation requirements.
6. SYSTEM DESIGN

6.1.USE CASE DIAGRAM

6.2.ACTIVITY DIAGRAM
6.3.Flow Diagram 1
ADMINISTRATOR

CONFIGURE
IPADDRESS

SELECT
REMOTE SYSTEM

6.4.Flow Diagram 2

ADMINISTRATOR
SYSTEM

SELECT SYSTEM

SPECIFY PASSWORD

LOCK SYSTEM

REMOTE SYSTEM
6.5.Flow Diagram3

ADMINISTRATOR
SYSTEM

SELECT SYSTEM

ENTER PASSWORD

UNLOCK SYSTEM

REMOTE SYSTEM
7. ADVANTAGES & DISADVANTAGES

7.1.ADVANTAGES

1. Reliable
2. Economical
3. Easy to use and implement.
4. Prevent unwanted access to systems.
5. When the remote computer is being locked by Network lock,
- None can access remote documents,
- browse the remote computer,
- or use programs on remote computer.

7.2.APPLICATIONS

In schools/colleges to restrict the access.

In offices, corporate houses.
In training institutions

8. Project Estimation

Duration: - 8 Months

Project Cost: - 4000 /- (Four Thousand Only)

9.FEASIBILITY STUDY
INTRODUCTION

A feasibility study is a preliminary study undertaken to determine and document a

projects visibility. Feasibility study involves detailed assessment of the need value &
practically of a proposed Enterprise, such as systems development. The results of this
study are used to make a decision whether or not to proceed with the project.
FEASIBILTY STUDY INCLUDES:
1. Technical Feasibility
2. Economical Feasibility
3. Schedule Feasibility
4. Operational Feasibility

A feasibility study is conducted to select the best system that meets the performance
requirements. A system required performance is defined by a statement of the
identification of specific system objective & the description of output.
The process to make changes in the current system in order to achieve new effective
system.
The feasibility study includes complete initial analysis of all related system. Therefore
the study must be conducted in a manner that will reflect the economic as well as
technical feasibility of the system proposal.

There are four major points to be covered in feasibility study

1. ECONOMIC FEASIBILITY
Economic feasibility is the most frequently used method for evaluating the
effectiveness of the candidate system that is proposed system, more commonly used
as cost/benefit analysis
The procedure is to determine the benefit and savings that are expected from the
candidate system and compare them with the cost, if the benefit over weight cost then
the decision is made to design and implement the system, other wise further
justification in the proposed system will have it be made, if it has chance to improve.
Cost estimate for a system we consider several elements.Hardware, Personnel,
Facility, Operation, Supply cost etc.
While developing the system we have to consider all the elements are completely
satisfied and according to organizations expectations.
2. TECHNICAL FEASIBILITY
In the technical feasibility the system analyst look between the requirements of the
organization, such as suggest input device which can enter a large amount of data in
effective time .Output devices which can produce output in a bulk in an effective
manner.
3. SCHEDULE FEASIBILITY
The estimation how long the system will take to develop & if it can be completed in a
given time period using some methods like payback period. The project will fail if it
takes too long to be completed before it is useful. Schedule should be maintained by
project team.
4. OPERATIONAL FEASIBILITY
Do the current work practices & procedures affect the working lives of those affected
by system?
For eg; system should be easily operable. There should not be complications for user
to enter details. It should also validate customers specification completely.
TESTING

Testing is a series of different tests that whose primary purpose is to fully exercise the
computer based system. Although each test has a different purpose, all work should
verify that all system element have been properly integrated and performed allocated
function. Testing is the process of checking whether the developed system works
according to the actual requirement and objectives of the system.

It is the stage of implementation, which ensures that system works accurately and
effectively before the live operation Commences. It is a confirmation that all are
correct and opportunity to show the users that the system must be tested with text data
and show that the system will operate successfully and produce expected results under
expected conditions.

Before implementation, the proposed system must be tested with raw data to ensure
that the modules of the system work correctly and satisfactorily. The system must be
tested with valid data to achieve its objective.

The philosophy behind testing is to find the errors. A good test is one that has a high
probability of finding an undiscovered error. A successful test is one that uncovers the
undiscovered error. Test cases are devised with this purpose in mind. A test case is a
set of data that the system will process as an input. However the data are created with
the intent of determining whether the system will process them correctly without any
errors to produce the required output.
Unit Test

The first test in the development process is the unit test. The source code is normally

divided into modules, which in turn are divided into smaller units called units. These

units have specific behavior. The test done on these units of code is called unit test.

Unit test depends upon the language on which the project is developed. Unit tests

ensure that each unique path of the project performs accurately to the documented

specifications and contains clearly defined inputs and expected results.

System Test

Several modules constitute a project. If the project is long-term project, several

developers write the modules. Once all the modules are integrated, several errors may

arise. The testing done at this stage is called system test.

System testing ensures that the entire integrated software system meets requirements.

It tests a configuration to ensure known and predictable results. System testing is

based on process descriptions and flows, emphasizing pre-driven process links and

integration points.

Functional Test

Functional test can be defined as testing two or more modules together with the intent

of finding defects, demonstrating that defects are not present, verifying that the
module performs its intended functions as stated in the specification and establishing

confidence that a program does what it is supposed to do.

Acceptance Testing

Testing the system with the intent of confirming readiness of the product and

customer acceptance.
10.SYSTEM IMPLEMENTATION
The purpose of System Implementation can be summarized as follows:

It making the new system available to a prepared set of users (the deployment),

and positioning on-going support and maintenance of the system within the

Performing Organization (the transition). At a finer level of detail, deploying the

system consists of executing all steps necessary to educate the Consumers on the use

of the new system, placing the newly developed system into production, confirming

that all data required at the start of operations is available and accurate, and validating

that business functions that interact with the system are functioning properly.

Transitioning the system support responsibilities involves changing from a system

development to a system support and maintenance mode of operation, with ownership

of the new system moving from the Project Team to the Performing Organization.

List of System implementation is the important stage of project when the

theoretical design is tuned into practical system. The main stages in the

implementation are as follows:

Planning
Training
System testing and
Changeover Planning
 Planning is the first task in the system implementation. Planning means
deciding on the method and the time scale to be adopted. At the time of
implementation of any system people from different departments and system analysis
involve. They are confirmed to practical problem of controlling various activities of
people outside their own data processing departments. The line managers controlled
through an implementation coordinating committee. The committee considers ideas,
problems and complaints of user department, it must also consider;

The implication of system environment

Self selection and allocation form implementation tasks
Consultation with unions and resources available
Standby facilities and channels of communication
The following roles are involved in carrying out the processes of this phase.

Detailed descriptions of these roles can be found in the Introductions to Sections I and

III.

_ Project Manager

_ Project Sponsor

_ Business Analyst

_ Data/Process Modeler

_ Technical Lead/Architect

_ Application Developers

_ Software Quality Assurance (SQA) Lead

_ Technical Services (HW/SW, LAN/WAN, TelCom)

 _ Information Security Officer (ISO)

_ Technical Support (Help Desk, Documentation, Trainers)

_ Customer Decision-Maker

_ Customer Representative

_ Consumer

The purpose of Prepare for System Implementation is to take all possible

steps to ensure that the upcoming system deployment and transition occurs smoothly,

efficiently, and flawlessly. In the implementation of any new system, it is necessary to

ensure that the Consumer community is best positioned to utilize the system once

deployment efforts have been validated. Therefore, all necessary training activities

must be scheduled and coordinated. As this training is often the first exposure to the

system for many individuals, it should be conducted as professionally and

competently as possible. A positive training experience is a great first step towards

Customer acceptance of the system.

During System Implementation it is essential that everyone involved be

absolutely synchronized with the deployment plan and with each other. Often the

performance of deployment efforts impacts many of the Performing Organizations

normal business operations. Examples of these impacts include:

_ Consumers may experience a period of time in which the systems that they depend

on to perform their jobs are temporarily unavailable to them. They may be asked to

maintain detailed manual records or logs of business functions that they perform to be

entered into the new system once it is operational.

_ Technical Services personnel may be required to assume significant implementation

responsibilities while at the same time having to continue current levels of service on

other critical business systems.

Technical Support personnel may experience unusually high volumes of support

requests due to the possible disruption of day-to-day processing.

Because of these and other impacts, the communication of planned deployment

activities to all parties involved in the project is critical. A smooth deployment

requires strong leadership, planning, and communications. By this point in the project

lifecycle, the team will have spent countless hours devising and refining the steps to

be followed. During this preparation process the Project Manager must verify that all

conditions that

must be met prior to initiating deployment activities have been met, and that the final

green light is on for the team to proceed. The final process within the System

Development Lifecycle is to transition ownership of the system support

responsibilities to
the Performing Organization. In order for there to be an efficient and effective

transition, the Project Manager should make sure that all involved parties are aware of

the transition plan, the timing of the various transition activities, and their role in its

execution.

Due to the number of project participants in this phase of the SDLC, many of

the necessary conditions and activities may be beyond the direct control of the Project

Manager. Consequently, all Project Team members with roles in the implementation

efforts must understand the plan, acknowledge their responsibilities, recognize the

extent to which other implementation efforts are dependent upon them, and confirm

their commitment.
System Implementation

First download, install and configure the J2SE development environment.

Downloading and Installing J2SE Software on Windows Platform

To download J2SE for development visit http://www.java.sun.com/j2se and download
J2SE on your machine. In this tutorial we have used jdk-1_5_0_06-windows-
i586.exe.The java 2Platform or (JDK) can be downloaded from the sun. Formerly
Known as the java Development kit ,or JDK, Downloading java is really about
downloading the java 2 plat form that comes in three editions , J2ME, J2SE and J2EE
, if you are learning java, then, you should start by downloading J2EE.

Once you have downloaded the j2se on your system, you are ready to install . In the
following section we will learn how to install jdk development environment on your
machine. here are the step to install JDK on your windows machine.

Step 1

Double click the JDK down loaded file, the executable extracts the required Contents
to the temporary directory and then License agreement screen appears. On the license
agreement page read and accept the license and the click the next button .
Step 2

The custom setup screen appears as follows.

Step 3

Click on the change button to change the installation directory to "c:\jdk1.5.0_06" as

shown in the following screen.
and click on the "OK" button. After clicking on the "OK" button installation begins:
Step 4

In the next window installer asks for the installing the runtime as shown in the
following screen:

Step 5

Click on next button install the J2SE runtime on your machine. Next screen shows the
browser selection:
Click on the "Next" button.

Step 6

Once the installation is finished it shows you the final screen indications the success.
Now you have successfully installed J2SE on your machine. Installer shows the
following final confirmation window as shown below:
Click on the "Finish" button to exit from the installer.
Configuirng to run on windows machine

Setting Environment Variables

Go to My computer Right click it and click on Properties

Click on Advanced Tab

Click On Environment Variables
Two variables are to be set

1.
Click on New

Enter Variable Name as: JAVA_HOME

Variable value : C:\Program Files\Java\jdk1.6.0_03 (this path is jdk version installed
on your machine)
Click ok

2.
Click on New

Enter Variable Name as: path

Variable value : C:\Program Files\Java\jdk1.6.0_03\bin (this path is jdk version
installed on your machine)

Click ok

After setting environment variables you can run the project from any drive not
necessary that the project has to be stored in bin directory of java
JINVOKE

Download J/Invoke from http://www.jinvoke.com/download, and extract the contents

of
the zip file.

jinvoke.jar - the J/Invoke runtime library

The jinvoke.jar file is the only runtime component needed by J/Invoke. It is a self
contained JAR file that includes the native libraries needed by J/Invoke at runtime.
When
a program using J/Invoke is run for the first time, it extracts a helper DLL called
jinvoke.dll to the same folder as jinvoke.jar. This DLL is used by J/Invoke internally
at
runtime. There is no need to configure the java library path or distribute the DLL
separately.
If you are using an IDE, add jinvoke.jar to your projects build path/classpath. If
using
the command line to compile or run your Java code, you will need to add jinvoke.jar
to
the classpath,
A Welcoming Example
import com.jinvoke.JInvoke;
import com.jinvoke.NativeImport;
public class HelloWindows {
@NativeImport(library="User32")
public static native int MessageBox(int hwnd,
String text,
String caption,
int type);
public static void main(String[] args) {
JInvoke.initialize();
MessageBox(0, "This MessageBox is a native Win32 MessageBox",
"Hello Windows", 0);
}
}

Calling the Win32 API

To make calling the Win32 API easier, the com.jinvoke.win32 package provides
helper
classes that contain J/Invoke function declarations for the most commonly used
Win32
DLLs. Import the class you need, and directly call the Java method corresponding to
the
Win32 API you want.
The available APIs are declared in a set of classes, one for each Windows DLL, as
shown
in the following table.
J/Invoke Win32 Helper Class DLL Name Functionality

The J/Invoke API

J/Invoke has a simple and easy-to-understand API: there are just three annotations,
three
classes and a couple of enumerations. Well start by briefly overviewing each one, and
then illustrate their use in several small examples.
First, the annotations:
The @NativeImport annotation - this provides the information needed to call a
function exported from a native DLL. We met this annotation in the first example
earlier in the chapter.
The @NativeStruct annotation - this annotation is used to represent a native
structure (a C struct) as a Java class.
The @Embedded annotation - this annotation is employed to define fixed-size
strings and arrays in structs.
Next, the classes:
The JInvoke class has just one static method initialize(). This method must be
called once in each class before any native methods marked with the
@NativeImport annotation are called. We saw initialize() in the first example of
this chapter.
The Callback class converts a Java method into a callback function that can be
called by native code.
The Util class provides numerous utility methods. These include ways to convert
Java types to native types and vice versa, methods for obtaining the size of structs,
pointers, and chars. GUI applications can make use of Util methods to convert
Windows icons into Java icons, and to obtain window handles for Java windows.
Finally, there are a couple of enumerations:
The CallingConvention enumeration is used to specify the calling convention
for a native method. By default, J/Invoke assumes a method employs the Win32
API default calling convention (Stdcall), so this enumeration isnt usually needed.
The Charset enumeration indicates how a Java String is converted when passed
to native code. This is used by the @NativeImport and @NativeStruct annotaions.
Since J/Invoke uses standard Java and JNI internally, it can be deployed using all the
standard Java deployment techniques. You can utilize J/Invoke with desktop
applications,
Java Web Start applications, applets, JSPs and servlets, web services, and Rich Client
Platform (RCP) applications built using the Eclipse or NetBeans frameworks.
You need to package jinvoke.jar with your application, and add it to the classpath
when
running the application. There are no additional components to deploy, nor any need
to
bundle JNI DLLs, change the PATH, or modify java.library.path.
The jinvoke.jar file contains all the Java classes and native libraries required by
J/Invoke.
The first time the application is run, J/Invoke will extract the native library
(jinvoke.dll
on Windows) and store it alongside jinvoke.jar. This native library is loaded by
J/Invoke
at runtime, and is transparent to the user. The J/Invoke documentation provides
walkthroughs for deployments employing Java Web Start and applets.
Remote Method Invocation (RMI)
Allows applications to call object methods located remotely, sharing resources
and processing load across systems.
Remote Method Invocation (RMI) facilitates object function calls between Java
Virtual Machines (JVMs).
Server Creates Remote Object
2. Server Registers Remote Object
3. Client requests object from Registry
4. Registry returns remote reference
(and stub gets created)
5. Client invokes stub method
6. Stub talks to skeleton
7. Skeleton invokes remote object Method
11. OutPut Screens:
SYSTEM MAINTENANCE

All system is dynamic and subjects to constantly changing requirements. Effort

must be devoted to adapting them and design must be flexible specified so that such

changes can be easily implemented. This activity is called system maintains. It

includes improvement of system functions and correction of errors.

Back up for the entire database files are taken and stored in secondary storage devices

like magnetic tapes and disks so that is possible to restore the system at the earliest. If

there is a breakdown or collapse, then the system gives provision to restore database

files. Storing data in a separate secondary device leads to an effective and efficient

maintains of the system.

The master file has flags for maintains. After the mentioned period, the rejection

suppliers, unused data in the files will be deleted in the master file. This method is the

increasing the memory to store the data.

12. CONCLUSION

The project entitled NETWORK LOCKING Has been developed o satisfy all
proposed requirements. The system is highly scalable and user friendly. Almost all
the system objectives have been met. The system has been tested under all criteria.
All phases of development were conceived using methodologies. The software
executes successfully by fulfilling the objectives of the project. Further extensions to
this system can be made required with minor modifications.
13. REFERENCES

Books Referred:

1. Scott Oaks, Henry Wong, Mike Loukides (Editor), Java Threads Java Series,
OReilly & Associates.
2. Patrick Naughton, Herbert Schildt, Java 2: The Complete Reference, Third
Edition, Tata McGraw-Hill Publishing Company Limited.
3. David Flanagan, Java in a Nutshell, 2nd Edition, May 1997.