2.

ANALYSIS
Requirements engineering include two main activities:

Requirement elicitation

Requirement analysis

Requirement Elicitation:
Requirement elicitation results in the specification of the system that the client
understands, and analysis results in the analysis model that the developers can
unambiguously interpret. Requirement elicitation is the more challenging because it
requires the collaboration of several groups of participants with different
backgrounds.
Requirement elicitation is about communication among developers, clients,
and users for defining a new system. Failure to communicate and understand each
authors domain results in a system that is difficult to use or that simply fails to support
the users work. Errors introduced during requirement elicitation are expensive to
correct as they are usually discovered late in the process often as late as delivery.
Such errors include:
Missing functionality that the system should have supported.

Functionality that was incorrectly specified.

User interfaces that are misleading or unusable.

Functionality that is obsolete.

Requirement elicitation focuses on describing the purpose of the system. The

client, Developers and the users identify a problem area and define a system that
addresses that problem. Such a definition is called a system specification and serves
as a contract between the client and the developers.

Requirement Analysis:
A requirement is a feature that must be included in the system. Before the
actual design and implementation start, getting to know the system to be implemented
is of prime importance.
Main emphasis should be on:

The inputs to the system.

The outputs expected from the system.

The people involved in the working of the system.

The volume of DATA (INPUTS) and the amount of INFORMATION

(outputs) that will be involved.

With respect to the system itself, the following facts should be taking into
consideration
The major processes involved.

The main points of application.

The processing rules for the collected data.

The exceptions that may be present.

The checks that should be in place in order to avoid wrong entries.

PURPOSE OF THE SYSTEM:

The development of the project Steganography is based on

cryptographic features to the TEXT file data and also provides compression
/decompression features. Steganography is a Component suite that can be used
as a component in any application to provide the security to the text file.
Steganography provides several functions.
It will take the TEXT file and secret key as input and gives the Encrypted and
Bmp image file as output based on the user selection of algorithms..
It will take the Encrypted key and Bmp file as input and will give decrypted
and TEXT file
SCOPE OF THE SYSTEM:

This project is limited to encryption/decryption only. It can be used as a

component in another application.
EXISTING SYSTEM:

The present system consist no security features to the TEXT file data. In the
existing system the text file data is sending in the network channels without
encrypting the file data.
Drawbacks:
There is no confidentiality to TEXT file data in transmission of the file in the
networks.
There is no authentication to the TEXT file.
The intruders may attack the TEXT file.
Lake of Integrity, Access Control and Availability.
It will take more space in the transmission of the TEXT file.
PROPOSED SYSTEM :
OVER VIEW:

The proposed system is based on cryptography features to the TEXT file. The
TEXT file selected is converted into bitmap image file using algorithms. The
proposed system takes TEXT file and Encryption key as input and gives encrypted
Bmp file based on the selection of specified algorithm techniques. This system
provides security services and the conversion to the TEXT file.
Advantages:
This system provides security service like Confidentiality.
The system provides compression to the TEXT file.
The system maintains same format after providing security features.

FUNCTIONAL REQURIMENTS:

Functional requirements describe the interactions between the system and its
environment independent of its implementation. The environment includes the user
and any other external system with which the system interacts.
The following are the functional requirements for the proposed system.

The system takes text file and 16-bit secret key as input to the system.

After that it will generate a bmp image by using Encryption /Decryption

algorithms.

The encrypted data is saved using relevant Compression/Decompression

algorithms.

The compressed data is encoded/decoded in order to obtain final encrypted

data, which has to be represented in text format.
The above-mentioned requirements show only the possible interactions

between the system and its external world. The above description does not focus on
any of the implementation details.
NON-FUNCTIONAL REQUIREMENTS:

Non-Functional requirements describe the user visible aspects of the system

that are not directly related with the functional behavior of the system. Non-functional
requirements include quantitative constraints, such as response time or accuracy.

The algorithm that should be executed by the system has to be selected

by the user.

The user has to supply the key to the algorithms.

User interface and Human factor: The user need not be technically
sound, as these interfaces are explanatory.

Documentation: User manual is provided to the user for using the

system.

Hardware Considerations: This is the Minimum hardware to run the

corresponding this software. The system will not interact with other
hardware system.
RAM

64 MB

Hard Disk

4 MB

Processor

Celeron 833 MHz.

Performance Characteristics:
The operations done in this system are according to the
algorithms selected. Here the system just executes those operations .
So, here the performance will depend on the efficiency of the
algorithm used.

Error Handling and Extreme Conditions:

There may be cases where the user not providing sufficient
input parameters for the method he selected. In those cases exception
should be raised.

PSEUDO REQUIREMENTS:

Pseudo Requirements are requirements imposed by the client that restrict the
implementation of the system. Typical pseudo requirements are the implementation
language and the platform on which the system is to be implemented.
Pseudo requirements have usually no direct effect on the users view of the system.
The client has imposed that the system must be developed or written using JAVA, to
comply with the current company policy.
The minimum software requirements are:
Operating System

MS-DOS

Language

JAVA 1.5