BTech Mini Project Report [Backup management System] Java project to backup important files to network storage with scheduling feature BTech Mini_Project Backup Computer_Science

(1)

Department of Computer Science, ASIET 1

(2)

1. INTRODUCTION

We know, most people in the Internet have a flat rate and they have hard disk much bigger than they ever use them. If you don't work with video application, it‘s really hard to fill modern Tera byte hard disks. we think, it may be a very good idea to implement a Backup system based on Network. You split your Hard disk in two Partitions. The working Partition and a two times bigger one to have space for the backup of other people via Network.

All you need is a pro gram, who backups your files to the free net. Because of the content related key and encryption, Network stores equal content to the same location. This creates a lot of space be avoiding the infinite duplication of common content like windows or other dat a applications and operating systems. This space can be used to store different versions of file who are user specific and under evolution. Also need is some additional forward error recover, called save set envelope, to keep the probability below a define d value.

The private files are secure, because the content has key is better than every content encryption password. Only if the file is known, it is possible by the neighbor peers to recognize the presents of this file during backup. This problem may be solved by the onion routing at the lead in of Network requests. The directories are also stored with the content related key and encryption system, so identically directories within distributed software are also stored on same locations. The main Dataset of the Backup system to needed start a recovery will be stored local on the computer and additional under a KSK who contains data to handle to an USK. This KSK must be a derivate build from a long user password, to create the opportunity to recover every time the whole hard disk with nothing more than a new computer and the knowledge of the master password.

(3)

(4)

2. SYSTEM ANALYSIS

System analysis is required to build and verify an effective system. It is the process of gathering and interpreting data and facts, diagnosing problems and using the information to recommend improvements to the system. In the development of software, structural analysis, information is collected from the existing d ocuments.

System analysis helps to understand the problem and emphasizes what is needed from the system. The various user requirements are identified and a new system is proposed so as to meet those requirements. System analysis is an approach to the study and solves the problem using computer based system; it provides a framework for visualizing the organizational facts that operate on the system.

2.1. SYSTEM DESCRIPTION

This project is intended to take backups‘ of sensitive are maintaine d as stream objects across a local network. Backup are done automatically over the networks to a backup server in the network. As with all computer system, there is always the potential for hardware malfunctions such as hard disk failures. Often, such maintenance is required due to the accidental and sometimes even deliberate modification or deletion of files on a system by its users. In some cases, such alterations can be undone easily, while in others, the only remedy is to reinstall a system from scratch . In such cases, it is of great benefit to administrators to have a backup of each available system that has been installed. Backups are done automatically over the network to a backup server at regular intervals and system administration done periodicall y so that data security is maintained. It is a software package that provides centrally managed, reliable backup facilities for a variety of workstations. It is an enterprise level backup product capable of protecting your most valuable data. Backups allow you to restore the availability and integrity of information resources following security breaches and accidents.

(5)

2.2. SCOPE OF THE PROJECT

The smart data backup server has the facility to take secured backups of the systems in the network. This application will enable the clients to schedule their backup and take urgent backup of only the required files when needed. The encryption property of the Smart - Data Backup server ensures security of the data. Also the clients can have a detailed report o f the backups As with all computer system, there is always the potential for hardware malfunctions such as hard disk failures. Often, such maintenance is required due to the accidental and sometimes even deliberate modification or deletion of files on a system by its users. In some cases, such alterations can be undone easily, while in others, the only remedy is to reinstall a system from scratch. Small businesses rely on the availability of their data to keep running, so data loss is arguably more catastrophic for them than for consumers. In fact, a recent study of small businesses had suffered data loss: "The top causes of small business' data loss included hardware/software failure (54 percent), accidental deletion (14 percent), computer viruses (22 percent) and theft (10 percent),"

In such cases, it is of great benefit to administrators to have a backup of each available system that has been installed .

Why Backups?

• Data can be corrupted by a variety of problems:

– Failure of the hard disk drive

– Failure of the hard disk controller – Motherboard failure

– Power outage or spike – Virus attack

(6)

Department of Computer Science, ASIET 6 – Malicious change or deletion of data

2.3. EXISTING SYSTEM

In existing system is implemented in intranet environment, where computers are connected under same domain.

Client and Server must have an active connection at schedule time for proper data backup.

LIMITATIONS OF THE EXISTING SYSTEM

 One of the main limitation of existing backup in our computer system is that it is only Implemented in local area network, where computers are connected under same domain

 Client and Server must have an active connection at schedule time for proper data backup

 Backup can be done only at particular moment/time. that is ,backing up of data can‘t be done by setting time(no scheduling)

 In ordinary backup system, if once we backup our data we can‘t view the backup details like backup day, backup time, schedule type, backup type. It doesn‘t provide old backup details

 We can‘t verify the data that we backed up: that is, it doesn‘t allow the user to view the details of current scheduled backup

 Any client can access/modify backed up data without the permission of the client who done the backup. It doesn‘t ensure data security

 Unauthorized user can backup and restore any system without the permission of admin

 Since the data are not automatically zipped large amount of memory is required to store the backed up data

 It is a time consuming process

 Existing backup system suffer data loss at higher rate because of accidental deletion, computer viruses, theft etc…

(7)

2.4. PROPOSED SYSTEM

The project is a software system where Back -ups are done automatically over the network to a back-up server at regular intervals and system administration done periodically so that data security is maintained. It is a software package that provides centrally managed, reliable backup facilities for a variety of workstations.

The programs permit you (or the system administrator) to manage backup, recovery, and verification of computer data across a network of computers of different kinds. In technical terms, it is a network Client/Server based backup program. The Backup System is relatively ea sy to use and efficient, while offering many advanced storage management features that make it easy to find and recover lost or damaged files. Due to its modular design, Backup System is scalable from small single computer systems to systems consisting of hundreds of computers located over a large network.

2.5. ADVANTAGES OF THE PROPOSED SYSTEM

Advantages:

1. Scheduling 2. Reports 3. Verification 4. Security

5. Authorized user login

6. File and data backup using automatic zip 7. Reduce data loss

(8)

Department of Computer Science, ASIET 8 The system protect against ev ery kind of data loss. This are

 User Mistakes, for example deleting something you still need  Software malfunction

 Hardware malfunction  Fire, Water, Storm

 Theft, Sabotage, Break-down, Robbery. Alternative solutions:

 A new Windows Computer comes for example with a hidden recovery partition. This solves particular problem (2) in relation to system software. If you use a second hard -disk, you can solve problem (3) by using a raid.

 If you are using software that create and maintains a set of snapshots, you may be able to solve (1) and (2), in combination with a second hard-disk also (3)

 . If you work with laptops, you have typical the problem, that there is only one internal disk. You may decide to use an add itional sever to make automatic backups.

 To protect against problem (4), you have two options: You may (A) decide to put data in a special, fire resistant box or you may (B) copy the data to a location far away. (A) Costs a lot of money and did not work automatically.

 If your business did not have the opportunity of different locations, you must rent space far away and upload every -kind, included all distributed stuff. (5) is the hardest problem.

 You have the need to keep your backup locations confidentia l, which is not so easy if you have huge traffic. Or you rent an ultra hard storage, like backup storage in the Switzerland including an Army guarantee.

 That's rarely expansive! But you can also solve (1) -(5) by a p2p backup solution running on a basis lik e something like a network based software application.

(9)

2.6. FUNCTIONAL REQUIREMENTS

HARDWARE SPECIFICATION

Network Storage Server

Processor Intel Pentium IV

Speed 2.4 GHz.

Memory 2 GB RAM

Hard Disk Drive 120 GB

Key Board 104 keys

Mouse Scroll Mouse

Monitor 15‖ SVGA Digital Color Monitor

DVD-RW 52 X

Network Device Ethernet LAN, Using Route/Switch

Client System

Processor Intel Pentium IV

Speed 2.4 GHz.

Memory 128 MB RAM

Hard Disk Drive 40 GB

Key Board 104 keys

Mouse Scroll Mouse

Monitor 15‖ SVGA Digital Color

(10)

SOFTWARE SPECIFICATION

Network Storage Server

Operating System Microsoft 2003 Server Runtime Support Jre1.6 or later

Network support TCP Socket & FTP Enabled Database Server SQL 2005 Server

Client System

Operating System Microsoft 2003 Server Runtime Support Jre1.6 or later

FEATURES OF JAVA

JAVA

Java has won acceptance as a major programming language in just a few years. It is a high-level third generation programming language, like C, FORTRAN, Smalltalk, Perl and many others. You can use Java to write computer applications that crunch numb ers, process words, play games, store data or do any of the thousands of other things computer can do.

Java Is Platform Independent

Java was designed to not only be cross -platform in source form like C, but also in compiled binary form. Sin ce this is frankly impossible across

(11)

Department of Computer Science, ASIET 11 processor architecture Java is compiled to an intermediate form called byte -code.

A java program never really executes natively on the host machine. Rater a special native program called the java interpreter reads the byte code and executes the corresponding native machine instructions. Thus to port Java programs to a new platform all that is needed is to port the interpreter and some of the library routines. Even the compiler is written in Java. The byte codes are precisely defined, and remain the same on all platforms.

The second important part of making Java cross -platform is the elimination of undefined or architecture depend constructs. Integers are always four bytes long, and floating point variab les follow the IEEE 754 standard for computer arithmetic exactly. However the virtual machine itself and some parts of the class library must be written in native code. These are not always as easy or quick to port as pure Java programs.

Java – JDK 1.6

The term Java actual refers to more than just a particular language like C or Pascal. Java encompasses several parts, including:

 A high level language – the Java language is a high level one that at a glance looks very similar to C and C++ but offers many u nique features of its own.

 Java byte code - a compiler, such as Sun's javac, transforms the Java language source code to byte code that runs in the JVM.

 Java Virtual Machine (JVM) – a program, such as Sun's java, that runs on a given platform and takes t he byte code programs as input and interprets them just as if it were a physical processor executing machine code.

 The Java Application Programming Interface (API):- The API is a large collection of ready-made software components that provide many useful capabilities, such as graphical user interface (GUI) widgets. It

(12)

Department of Computer Science, ASIET 12 is grouped into libraries of related classes and interfaces; these libraries are known as packages. The following figure depicts how the API and the Java Virtual Machine insulate the program f rom the hardware.

As a platform-independent environment, the Java platform can be a bit slower than native code. However, advances in compiler and virtual machine technologies are bringing performance close to that of native code without threatening portability.

Basic features that make java a powerful and popular

programming language:

Simple

There are various features that make the java as a simple language. Programs are easy to write and debug because java does not use the pointers explicitly. Java provides the bug free system due to the strong memory management. It also has the automatic memory allocation and deallocation system.

Platform Independent

The concept of Write-once-run-anywhere (known as the Platform independent) is one of the important key features of java language that makes java as the most powerful language. Not even a single language is idle to this feature but java is closer to this feature. The programs written on one platform can run on any platform provided the platform must have the JVM.

(13)

Department of Computer Science, ASIET 13 To be an Object Oriented language, any language must follow at least the four characteristics.

Inheritance: It is the process of creating the new classes and using the behavior of the existing classes by extending them just to reuse the existing code and adding the additional features as needed.

Encapsulation: It is the mechanism of combining the informa tion and providing the abstraction.

Polymorphism: As the name suggest one name multiple form, Polymorphism is the way of providing the different functionality by the functions having the same name based on the signatures of the methods.

Dynamic binding: Sometimes we don't have the knowledge of objects about their specific types while writing our code. It is the way of providing the maximum functionality to a program about the specific type at runtime. The linking of data and methods to where they are locat ed is done at run-time. New classes can be loaded while a program is running. Linking is done on the fly. Even if libraries are recompiled, there is no need to recompile code that uses classes in those libraries. This differs from C++, which uses static bi nding. This can result in fragile classes for cases where linked code is changed and memory pointers then point to the wrong addresses

As the languages like Objective C, C++ fulfills the above four characteristics yet they are not fully object oriented languages because they are structured as well as object oriented languages. But in case of java, it is a fully Object Oriented language because object is at the outer most level of data structure in java. No stand alone methods, constants, and variables a re there in java. Everything in java is object even the primitive data types can also be converted into object by using the wrapper class.

Robust

Java has the strong memory allocation and automatic garbage collection mechanism. It provides t he powerful exception handling and type checking mechanism as compare to other programming languages. Compiler checks the program whether there any error and interpreter checks any run

(14)

Department of Computer Science, ASIET 14 time error and makes the system secure from crash. All of the above fea tures make the java language robust.

Distributed

The widely used protocols like HTTP are developed in java. Internet Programmers can call functions on these protocols and can get access the files from any remote machine on the internet rather than writing codes on their local system.

Portable

The feature Write-once-run-anywhere makes the java language portable provided that the system must have interpreter for the JVM. This feature makes the java as a portable language.

Dynamic

While executing the java program the user can get the required files dynamically from a local drive or from a remote server thousands of miles away from the user just by connecting with the Internet.

Automatic Memory Management

Automatic garbage collection - memory management handled b y JVM. Secure

Java does not use memory pointers explicitly. All the programs in java are run under an area known as the sand box. Security manager determines the accessibility options of a class like reading and writing a file to the local disk. Java uses the public key encryption system to allow the java applications to transmit over the internet in the secure encrypted form. The byte code Verifier checks the classes after loading. Array index limit checking. Code pathologies reduced by

1. Byte code verifier - checks classes after loading

2. Class loader - confines objects to unique namespaces. Prevents loading a hacked "java.lang.SecurityManager" class, for example.

3. Security manager - determines what resources a class can access such as reading and writing to the local disk.

(15)

Department of Computer Science, ASIET 15 Performance

Java uses native code usage, and lightweight process called threads. In the beginning interpretation of byte code resulted the performance slow but the advance version of JVM uses the adaptive and just in time compilation technique that improves the performance.

Compiler/Interpreter Combo

Code is compiled to byte codes that are interpreted by Java virtual machines (JVM). This provides portability to any machine for which a virtual machine has been written. The two steps of compilation and interpretation allow for extensive code checking and improved security.

Several dangerous features of C & C++ eliminated: 1. No memory pointers

2. No preprocessor

3. Array index limit checking Multithreaded

As we all know several features of Java like Secure, Robust, Portable, dynamic etc; you will be more delighted to know another feature of Java which is Multithreaded.

Java is also a multithreaded programming language. Multithreading means a single program having different threads executing independently at the same time. Multiple threads execute instructions according to the program code in a process or a program. Multithreading works the similar way as multiple processes run on one computer.

Multithreading programming is a very interesting concept in Java. In multithreaded programs not even a single thread disturbs the execution of other thread. Threads are obtained from the pool of available ready to run threads and they run on the system CPUs. This is how Multithreading works in Java which you will soon come to know in details in later chapters.

Interpreted

(16)

Department of Computer Science, ASIET 16 interpreted language such as Java, programs run directly from the source code.

The interpreter program reads the source code and translates it on the fly into computations. Thus, Java as an interpreted language depends on an interpreter program.

The versatility of being platform independent makes Java to outshine from other languages. The source code to be written and distri buted is platform independent.

Another advantage of Java as an interpreted language is its error debugging quality. Due to this any error occurring in the program gets traced. This is how it is different to work with Java.

Built-in Networking

Java was designed with networking in mind and comes with many classes to develop sophisticated Internet communication s.

Architecture Neutral

The term architectural neutral seems to be weird, but yes Java is an architectural neutral language as well. The growing popularity of networks makes developers think distributed. In the world of network it is essential that the applications must be able to migrate easily to different systems , not only to computer systems but to a wide variety of hardware architecture and operating system architectures as well. The Java compiler does this by generating byte code instructions, to be easily interpreted on any machine and to be easily translated into native machine code on the fly. The compiler generates an architecture -neutral object file format to enable a Java application to execute anywhere on the network and then the compiled code is executed on many processors, given the presence of the Java runtime system. Hence Java was designed to support applications on network. This feature of Java has thrived the programming language .

(17)

ABOUT OPERATING SYSTEM - WINDOWS XP

Windows XP is a line of operating systems developed by Microsoft for use on general-purpose computer systems, including home and business desktops, notebook computers, and media centers. The name "XP" stands for ‗experience‘. It was codenamed "Whistler", after Whistler, British Columbia, as many Microsoft employees skied at the Whistler -Blackcomb ski resort during its development. Windows XP is the successor to both Windows 2000 Professional and Windows Me, and is the first consumer -oriented operating system produced by Microsoft to be built on the Windows NT kernel and architecture. Windows XP was first released on October 25, 2001, and over 400 million copies were in use in January 2006, according to an estimate in that month by an IDC analyst.[3] It is succeeded by Windo ws Vista, which was released to volume license customers on November 8, 2006, and worldwide to the general public on January 30, 2007.

The most common editions of the operating system are Windows XP Home Edition, which is targeted at home users, and Window s XP Professional, which has additional features such as support for Windows Server domains and two physical processors, and is targeted at power users and business clients. Windows XP Media Center Edition has additional multimedia features enhancing the ability to record and watch TV shows, view DVD movies, and listen to music. Windows XP Tablet PC Edition is designed to run the ink -aware Tablet PC platform. Two separate 64 -bit versions of Windows XP were also released, Windows XP 64 -bit Edition for IA-64 (Itanium) processors and Windows XP Professional x64 Edition for x86 -64.

Windows XP is known for its improved stability and efficiency over the 9x versions of Microsoft Windows. It presents a significantly redesigned graphical user interface, a change Micr osoft promoted as more user-friendl y than previous versions of Windows. New software management capabilities were introduced to avoid the "DLL hell" that plagued older consumer -oriented 9x versions of Windows. It is also the first version of Windows to use product activation to combat software piracy, a restriction that did not sit well with some users and privacy advocates. Windows XP has also been criticized by

(18)

Department of Computer Science, ASIET 18 some users for security vulnerabilities, tight integration of applications such as Internet Explorer and Windows Media Player, and for aspects of its default user interface.

(19)

(20)

3. SYSTEM DESIGN

3.1. DATA FLOW DIAGRAM

Database Design

The database may be defined as an organized collection of related information. The organized information serves as a base from which further recognizing can be retrieved desired information or processing the data. The most important aspect of building an a pplication system is the design of tables. In out present project the database consists of just single table.. The table structure shown below:

Levels of data flow diagram

(21)

Level - 1

(22)

Level - 2

(23)

Dataflow Diagram

Graphical description of a system‘s data and how the processes

transform the data is known as Data Flow Diagram (or DFD). This was first developed by Larry Constantine. This is also known as ―bubble chart‖.

Unlike detail flowcharts, DFDs do not supply detailed descriptions of modules but graphically describe a system‘s data and how the data interact with the system.

To construct data flow diagrams, we use  Arrows

 Circles

 Open-ended boxes, and  Squares

An arrow identifies dat a flow-data in motion. It is a pipeline through which information flows. Like the rectangle in flowcharts, circles circle stand for a process that coverts data/into in -formation. An open-ended box represents a data store-data at rest, or a temporary reposi tory of data. A square defines a source (originator) or destination of system data.

The following seven rules govern construction of Data Flow diagrams (DFD):

 Arrows should not cross each other.

 Squares, circles and files must bear names.

 Decomposed data flows must be balanced (all data flows on the decomposed diagram must reflect flows in the original diagram).

 No two data flows, squares, or circle can have the same name.

 Draw all data flows around the outside of the diagram.

 Choose meaningful names for data flows, processes and data stores. Use strong verbs followed by nouns.

 Control information such as record contents, passwords and validation requirements are not pertinent to a data -flow diagram.

(24)

3.2. SCREEN SHOTS

fig.1: Client Loign

(25)

fig.3: Registration Form

(26)

fig.4: Backup File Selection

(27)

fig.5: Backup Scheduling

(28)

fig.6: Restore

(29)

3.3. TABLE SPECIFICATION

SERVER CONFIGURATION

Column name

Data Type

Description

IP_Address Varchar(20) Uniquely identify the client

Port_Number Varchar(20) Port to connect

Remote_Folder Varchar(20) Server location for backup

USER ACCOUNT

Column Name

Data Type

Description

Name Varchar(20) Name of the user

Systemname Varchar(20) Name of the System

Systemnumber Int Number of the System

Portnumber Int Port to Connect

Username Varchar(20) User name to login

Password Varchar(20) Password to login

Typesofdata Varchar(120) Types of data to backup

REPORT

Column Name Data Type Description

Savepacname Varchar(100) Name of file to backup

Backuplevel Varchar(100) Incremental/Image copy

Backuptype Varchar(100) Backup to Server/Client

Scheduletype Varchar(100) Weekly/Daily

Backupday Varchar(100) Day of backup

Backuptime Varchar(100) Time of backup

(30)

3.4. MODULE DESCRIPTION

Modules

1. Network Backup Server

a) Client Account Authentication

b) Storage device Management

c) Data Replication (External Drive/Device/ System)

d) FTP Server

2. Client Backup Tool

a) Defining backup packs

Data security management (encryption)

b) Data Compression

c) Backup File Transfer (FTP)

Backup scheduling

d) Recover y management

e) Report (backup/Recovery)

1. Network Backup Server

a) Client Account Authentication

This module is intended to manage and authenticate an account for each client system. Client system information after registering

(31)

Department of Computer Science, ASIET 31 the account is send to the server for approval and Authentication. This assigns specific privileges for each registered client system. b) Storage Device managements

This module allocates the storage space and location in the backup server for storing the backup files that have been transferred. It also manages the temporary storage devices for secondary backup.

c) Data Replication

This creates the duplicates of files needed for ensuring the

security from data loss. This data can be maintained in the client system near the original data or can be transferred to the server and can be even maintained in secondary storage devices. d) FTP Server

This module follows File Transmission Protocol for the easy transfer of files from the server system to the connected client and vice versa. This overcomes complex procedures and the transmission delay of using other protocols.

2. Client Backup Tool

e) Defining Backup Packs

Manages the backup files by giving a pack name. These backup packs are described by assigning several attributes which gives the information about time, schedule and storage location of the files.

f) Data security management (encryption)

For the secure transmission of data, data encryption

mechanisms are used for converting the data into an encrypted format which can be decrypted only by the specific client.

(32)

Department of Computer Science, ASIET 32 g) Data Compression

Before transferring the files to the central server it is compressed to reduce the storage space. Thus even bulk of data can be easily transferred and saved in a minimum storage space.

h) Backup File Transfer (FTP)

This module is intended for the easy transfer of files from client systems to the connected server and vice versa .FTP (File Transmission Protocol) is used here which overcomes the complex procedures of other transmission protocols.

i) Backup scheduling

Defines a schedule for each backup packs by setting the week, day, date and time for the backup. The information such as which files are needed for backup, when the backup process will start, and where to store the files are received

dynamically from the user and saved as xml file. j) Recover y management

Data recovery module is used to recover the lost or damaged data from the central server when needed. The data be restored in the compressed format or we can decompress the data and download.

k) Report (backup/Recovery)

This module generates the reports about backup and recovery .it also provide information about the regi stered client systems and the types of data, date and time of backup created by them.

(33)

3.5. SYSTEM TEST PLAN

Login

Serial No. Module description Test

Case Expected Input

Expected Output Refer GUI Remark 1. Login User login Attempt to authenticate with valid username and password Login to

home page Fig 1 Successful

2. Login User login Attempt to authenticate with invalid username and password Redirected to same page with error message Fig 1 Failed 3. Login User Login Attempt to authenticate with valid username and password Login to

home page Fig1 Successful

4. Login User Login Attempt to authenticate with invalid username and password Redirected to same page with error message Fig 1 Failed 5. Login User Login If no values are entered in any field/any field is kept blank Warning message-Fill

all the fields

(34)

Register

Serial No.

Module

description Test Case Expected Input

Expected Output Refer GUI Remark 1. Register Registration for a new user If no values are entered in any field/any field is kept blank Error message-Enter data in all fields Fig 3 Failed 2. Register Registration for a new user Incorrect re-entering of password in confirm password’ field Error message-Password doesn’t match Fig 3 Failed 3. Register Registration for a new user

If new user enters existing username during registration

Username

not available Fig 3 Failed

4. Register

Registration for a new

user

When the user enters all the fields correctly Message: Registration completed Fig 3 Success

Configuration

Serial No. Module

Expected Output Refer GUI Remark 1. Configure Server configuration Entering IP address incorrectly by the user Error message-connection refused Fig 2 Failed 2. Configure Server configuration Entering port number incorrectly Error message-connection refused Fig 2 Failed 3. Configure Server configuration When user enters correct username & password Success message-server configured Fig 2 Success

(35)

Backup

Serial No.

Module

description Test Case

Expected Input Expected Output Refer GUI Remark

1. Backup Select files to Backup If null value is selected for ADD button Warning message-no files selected Fig 4 Failed

2. Backup Select files to Backup If no file is selected for backup Warning message-no files selected for backup Fig 4 Failed

3. Backup Select files to Backup Duplication of selected folder Message-folder already exist Fig 4 Failed 4. Backup Remove files from selected list If null value is selected for REMOVE button Error message-select at least one item Fig 4 Failed

Restore

Serial No. Module

Expected Output Refer GUI Remark 1. Restore Restoring backup If no values are entered in any field/any field is kept blank No items

selected Fig 6 Failed

2. Restore Restoring backup

If user select the location incorrectly

Invalid

location Fig 6 Failed

3. Restore Restoring backup After completing the restore function Message-data restoration completed Fig 6 Success

(36)

Decompress

Serial No.

Module

description Test Case

Expected Input Expected Output Refer GUI Remark 1. Decompress Decompress Restored Data If no value is entered in any field/any field is kept blank Warning-no null value accepted Fig 7 Failed 2. Decompress Decompress Restored Data When user select an invalid location Warning message-Invalid location Fig 7 Failed 3. Decompress Decompress Restored Data After completing the decompression process Message – Data decompression completed Fig 7 Success

(37)

(38)

4. TEST REPORT

SYSTEM TESTING

Software testing is a critical element of software quality assurance and represents the ultimate reviews of specification, design and coding. Testing present an interesting anomaly for the software. Testing is vital to the success of the system. Errors can be injected at any stage during development. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. During testi ng, the program to be tested is executed with set of test data and the output of the program for the test data is evaluated to determine if the programs is performing as expected. A series of testing are performed for the proposed system before the system is ready for user acceptance testing. The testing steps are:

 Unit Testing  Integration Testing  Validation testing  Output Testing  Acceptance Testing

Unit Testing

Unit testing focuses verification effort on the smallest unit of the software design, the module this is known as module testing. Since the proposed system has modules the testing is individually performed on each module. Using the details design description as a guide, important control paths are tested to uncover errors within the boundary of the module. This testing was carried out during programming stage itself. In this testing step each module is found to be working satisfactorily as regards to the expected output from the module.

Integration Testing

Data can be test across an interface; one module can have adverse effect on another, sub function when combined may not produced the desired

(39)

Department of Computer Science, ASIET 39 function. Integration testing is a systematic technique for constructing the program structure while at the same time conducting test to uncover errors associated within the interface.

Validation Testing

Validation testing can be defined in many ways, but a simple definition is that validation succeeds when the software functions in manner that is reasonably expected by the customer. Software validation is achieved through a series of black box tests that demonstrate conformity with requirement. After validation test has been conducted, one of two conditions exists.

 The function or performance characteristics confirm to specifications and are accepted

 A validation from specification is uncovered and a deficiency created.

Deviation or errors discovered at this step in this project is corrected prior to completion of the project with the help of the user by negotiating to establish a method for resolving deficiencies. Thus the proposed system under consideration has been tested by using validation testing and found to be working satisfactorily.

Output Testing

After performing the validation testing, the next ste p is output testing of the proposed system, since no system could be useful if it does not produce the required output in the specific format. The output generator or displayed by the system under consideration is tested by asking the users about the format required by them. Here the output is considered in two ways: One is on screen and the other is printed format. The output format on the screen is found to be correct as the format was designed in the system design phase according to the user needs. As fa r as hardcopies are considered it goes in terms with the user requirement. Hence output testing does not result any correction in the system.

(40)

Acceptance Testing

User acceptance of the system is key factor for the success of any system. The system under consideration is tested for user acceptance by constantly keeping in touch with prospective system and user at the time of developing and making changes whenever required

IMPLEMENTATION

Implementation is the stage of the project when the theoretica l design is turned into a working system. If the implementation stage is not properl y planned and controlled, it can cause chaos. Thus it can be considered to be the most crucial stage in achieving a successful new system and in giving the users confidence that the new system will work and be effective.

Normally this stage involves setting up a coordinating committee, which will act as a sounding board for ideas; complaints and problems. The first task is implementation planning; i.e. deciding on the metho ds and timescale to be adopted. Apart from planning, the two major tasks of preparing for implementation are education and training of users and testing of the system. Education of users should really have taken place much earlier in the project; at the implementation stage the emphasis must be on training in new skills to give staff confidence they can use the system. Once staff has been trained, the system can be tested.

After the implementation phase is completed and the user staff is adjusted to the changes created by the candidate system, evaluation and maintenance begin. The importance of maintenance is to continue to bring the new system to standards.

The activities of the implementation phase can be summarized as: -

 Implementation planning

 Education and training

(41)

.

T

ESTING AND IMPLEMENTATION

System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently before live operation commences. An elaborate testing of data is prepared and the system is tested using this test data. While testing error noted and corrections are made. The users are trained to operate the developed system. Both hardware and software securities are made to run the developed system successfully in future. Testing demonstrates that performance requirements appear to have been met.

TYPES OF TESTING DONE:

Two types of testing are white-box testing and black -box testing.

White-Box testing

White-box testing is a test case design method that uses the control structure of the procedural design to derive test cases. White -box testing of software is predicted on close examination of procedural detail.

Black-Box testing

The black-box testing focuses on the functional requirements of the software. It helps to find out errors in incorrect or missing functions, interface errors, errors in data structures, performance errors and initialization and termination errors. The black -box testing is applied during the later stages for the functional requirement evaluation.

Testing strategy

 Unit testing

Unit testing focuses verification effort on the smallest unit of the software design of the module .The unit test is normally white -box oriented, and the step can be conducted in parallel for multiple modules.

(42)

Department of Computer Science, ASIET 42  Condition Testing

The condition testing exercises on the conditions contained in a program module.

 Loop Testing

Loop testing is a testing technique that focuses exclusively on the validity of the loop constructs. In the case of the current system the loops are tested for validity purpose.

 Integration Testing

When the modules of the system are combined together to form the whole system, there will be the problem of interfacing. Integration testing is a systematic testing technique fo r constructing the program structure while conducting tests to uncover errors associated with interfacing.

 Graph Based Testing

A graph of important objects ad their relationship is created and then a series of test is devised that will cover the graph so that each object and relationship is exercised and error is covered

 Validation Testing

The definition for the validation testing is that the validation succeeds when software functions in a manner that can be reasonably expected by the customer. The expe ctations are defined in the software requirements specifications.

Validation criteria: If any field is kept blank then a dialogue box showing an error message will appears.

 Output Testing

After performing the validation testing, the next step is output testing of the proposed system since no system could be useful if it does not produce the

(43)

Department of Computer Science, ASIET 43 required output in the specific format. The output generated or displayed by the system under consideration is tested asking the users about the format required by then.

Here, the output is considered into ways: one is on the screen and the other is printed format. The output format on the screen is found to be correct as the format designed according to the user needs. For the hard copy also, the output comes out as specified by the user. Hence output testing doesn‘t result in any connection in the system.

 User Acceptance Testing

User acceptance testing of a system is the key factor for the success of any system. The System under consideration is tested for user acceptance by constantly keeping in touch with the prospective system users at time of developing and making the Digital Watermarking System.

The testing of the software began along with coding. Since the design was fully object-oriented, first the interfaces were developed and tested. Then unit testing was done for every module in the software for various inputs, such that each line of code at least once executed. After all modules w ere coded the integration test were carried out. Some minor errors were found in the output at the earlier stage and each of them was corrected. In the implementation of user interface part no major errors were found. After the software was completely developed, the testing was done. The output of the were correct and accurate during the time of demonstration after that no errors were reported.

IMPLEMENTATION

System implementation is the final phase i.e., putting the utility into action. Implementation is the state in the project where theoretical design turned into working system. The most crucial stage is achieving a new successful system and giving confidence in new system that it will work efficiently and effectively. The system is imp lemented only after thorough checking is done and if it is found working in according to the specifications.

(44)

Department of Computer Science, ASIET 44 It involves careful planning, investigation of the current system and constraints on implementation, design of methods to achieve. Two checking is done and if it is found working according to the specification, major task of preparing the implementation are educating, training the users.

The implementation process begins with preparing a plan for the implementation of the system. According to this plan, the activities are to be carried out, discussions made regarding the equipment and resources and the additional equipment has to be acquired to implement the new system. The most important in implementation stage is, gaining the users confidence that the new system will work and be effective. The system can be implemented only after through testing is done. This method also offers the greatest securit y since the existing system can take over if the errors are found or inability to handle certain type of transactions while using the new system.

 User Training

After the system is implemented successfully, training of the user is one of the most important subtasks of the developer. Even well designed and technically elegant systems can succeed or fail, because of the way they are operated and used. For this purpose user manuals are prepared and handled over to the user to operate the develop ed system.

Thus the users are trained to operate the developed system. Both the hardware and software securities are made to run the developed systems successfully in future. In order to put new application system into use, preparation of user and system documentation, conducting user training with demo, test run for some period to ensure smooth switching over the system are to be prepared

 Test Report

We made use of valid username/password or invalid username/password to test the first login page. Only i f the match is found the system moves into the next page. A similar procedure is a carried out in the registration process where if the username already exists the registration process fails.

(45)

Department of Computer Science, ASIET 45 Once the user enters into his home page he can search for the products and can view his history and the recent visited links these functions were tested for their functionality and was found to be working according to the specifications, provision for user to edit his password is also provided.

(46)

(47)

5. CONCLUSION

Disasters both natural and human -caused can threaten your precious files at any time: a fire, power surge, or leaking pipe could fry your system. Even without suffering a calamity, there are plenty of other threats to locally stored data—hard drive failure, accidental erasures, or a lost or stolen laptop could make you a victim of data loss. By data, here, we mean things like your irreplaceable family photos, videos, and music as well as documents .

Small businesses rel y on the availability of their data to keep running, so data loss is arguably more catastrophic for them than for consumers. In fact, a recent study of small businesses had suffered data loss: "The top causes of small business' data loss included hardware/software failure (54 percent), accidental deletion (54 percent), computer viruses (33 percent) and theft (10 percent),"

Secure Network Backup System, securely store your files away from your premises at on-site/off-site server locations, your data will stay intact and available even if your local disks are stolen or your premises suffer some disaster. With more and more emphasis on "cloud computing," i t only makes sense that backup should take advantage of this hot trend in technology.

(48)

(49)

6. FUTURE SCOPE

This project is mainly indented to take Backup of data in LAN and WAN. As future expansion it can be implement ed in World Wide Web. Another feature that can be implemented is ―incremental backup‖, which will enable to save storage space by smart backup. New technologies like ―Cloud Computing‖ can be used to make the backup system more effective and efficient.

(50)

(51)

7. REFERENCES

 Java2 complete reference: Herbert Schildt(Tata McGrawHill)

 Using java2 platform: Joseph Weber(PHI)

 Java2,AWT,Swing,XML and JavaBeans Programming BlackBook: Steven Holzner, Wiley Dreamtech

 Details about netbeans: http://roseindia.com

 Details about backup systems http://zamadacloudbackup.in http://archianetwork.com