INTRODUCTION

The following is an attempt to put together a complete, yet reasonably flexible template for the specification of software designs. In devising this template, we have gleaned information from many sources, including various texts on Software Engineering (Pressman), Object-Oriented Development (Ali Bahrami).It is everyones desire that a completed software design specification meet the following criteria:

It should be able to adequately serve as training material for new project members, imparting to them enough information and understanding about the project implementation, so that they are able to understand what is being said in design meetings, and won't feel as if they are drowning when they are first asked to create or modify source code.

It should serve as "objective evidence" that the designers and/or implementers are following through on their commitment to implement the functionality described in the requirements specification.

It needs to be as detailed as possible, while at the same time not imposing too much of a burden on the designers and/or implementers that it becomes overly difficult to create or maintain.

PURPOSE
A cross compilation tool is a tool which runs on one system and produces code which runs on another system. In the normal case, a compiler produces code which runs on the same system as the one on which the compiler runs. When it is necessary to distinguish this case from the cross compilation case, such a compiler is called a native compiler. A compiler which produces programs which run on a different system is a cross compilation compiler, or simply a cross compiler . The goal of the project is to develop an application tool for access, monitor and control of Linux file system and Windows file system. Normally it is possible to view windows file system under Linux by using the MOUNT command. But it is not possible to view Linux file system in windows. So for this we have to log off and go to respective operating systems to view or do any operations. When CROSS TOOL starts, we should see a split window. In the upper half you'll see your DOS drives, in the lower half you will see your LINUX drives. So we can perform any operations as of our use.

SCOPE
By developing this CROSS TOOL we reduce time in access, monitor and control by using the tool under any platform. The main scope of developing this application is that if any kernel file of Linux gets corrupted we can replace the corrupted file instead of replacing the Linux operating system. So it reduces the need of installing the operating system.

SOFTWARE REQUIREMENTS: J2sdk1.4.2 Windows XP, Linux.

HARDWARE REQUIREMENTS: Hard disk RAM Processor : : : 40 GB 128mb Pentium

Hardware Interfaces
Processor Processing Speed Primary memory Cache Hard Disk Capacity Connection Monitor Keyboard Mouse CD Drive : : : : : : : : : : Intel Pentium IV 600 MHz 256 MB RAM 512 KB 10GB(Partitioned) TCP/IP 15 Color Monitor 101 Keys Standard Serial Mouse 52X

Software Interfaces
Operating System Front End Back End : : : Windows and Linux Java Java and C

MODULE DECOMPOSTION
There are two main modules in the CROSS TOOL application. They are

GUI MODULE BACKEND MODULE

1. MODULE 1 DESCRIPTION
The first module consists of GRAPHICAL USER INTERFACE (GUI) to user. In this module we develop the front screen visible to the user. This module consists of creation of frames. When CROSS TOOL starts, we should see a split window. In the upper half of the first frame we see WINDOWS drives, in the lower half of the second frame we will see LINUX drives. So we can perform any operations as of our use.

2. MODULE 2 DESCRIPTION
The second module consists BACKEND MODULES for the description of tree concept, navigation tress and images. Images are used for icons which represents symbols or signs for a document or file. Navigation trees are trees which are used for easy navigation or browsing of drives or directories or files in the respective operating systems.