Software Requirements

Specification
for

Secure Data Transmission

Through Steganography

Version 1.0 approved

Prepared by :-
Saurabh Purohit
(0829cs071094)
Shahbaz Khan
(0829cs071096)
Surendra Rathore
(0829cs071107)

Sushila Devi Bansal College Of Tech. Indore

28 Sep 2010
Table of Contents
1. Introduction................................................................................................................................1
1.1 Purpose ............................................................................................................................................... 1
1.2 Document Conventions....................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions..................................................................................... 1
1.4 Product Scope..................................................................................................................................... 2
1.5 References........................................................................................................................................... 2
2. Overall Description....................................................................................................................2
2.1 Product Perspective............................................................................................................................. 2
2.2 Product Functions............................................................................................................................... 2
2.3 User Classes and Characteristics........................................................................................................ 2
2.4 Operating Environment....................................................................................................................... 3
2.5 Design and Implementation Constraints............................................................................................. 3
2.6 User Documentation........................................................................................................................... 3
2.7 Assumptions and Dependencies......................................................................................................... 3
3. External Interface Requirements............................................................................................. 3
3.1 User Interfaces.................................................................................................................................... 3
3.2 Hardware Interfaces............................................................................................................................ 3
3.3 Software Interfaces............................................................................................................................. 3
3.4 Communications Interfaces................................................................................................................. 4
4. System Features......................................................................................................................... 4
5. Other Nonfunctional Requirements.........................................................................................4
5.1 Performance Requirements................................................................................................................. 4
5.2 Safety Requirements........................................................................................................................... 4
5.3 Security Requirements........................................................................................................................ 4
5.4 Software Quality Attributes................................................................................................................ 4
6. Project Plan................................................................................................................................ 5
6.1 Team Members................................................................................................................................... 5
6.2 Division of Work................................................................................................................................ 5
6.3 Time Schedule..................................................................................................................................... 5
Software Requirements Specification for <Project> Page 1

1. Introduction
This SRS is a blueprint that represents the development life cycle of this product. It will serve as a
guideline for developers who are concerned with the functions performed and problems this system
solves.

1.1 Purpose

The proposed system is a product which is capable of hiding the information into other
information.The hidden information can be a text file, image file, audio file, video file or simply a
message. The Carrier file can also be one of text file, image file, audio file, and video file. The
product (software) should also support encryption and compression.

1.2 Document Conventions

The following are the list of conventions and acronyms used in this document and the project as
well:
Administrator: A login id representing administration privileges to the software
• User: A general login id assigned to administrator.
• Client: Intended users for the software
• SQL: Structured Query Language; used to retrieve information from a database
• SQL Server: A server used to store data in an organized format
• Layer: Represents a section of the project
• User Interface Layer: The section of the assignment referring to what the user interacts
with directly.
• Application Logic Layer: This is where all computations are completed.
• Data Storage Layer: The section of the assignment referring to where all data is recorded
• Data flow diagram:It shows the dataflow between the entities.
• Use Case: A broad level diagram of the project showing a basic overview
• Boolean: A true/false notation
• Interface: Something used to communicate across different mediums
• Unique Key: Used to differentiate entries in a database

1.3 Intended Audience and Reading Suggestions

The intended audiences for this document are:

• The team members.
• The administrative staff of S.D.Bansal College of tech. Indore who is the client.
• The Project Supervisor and Project Coordinator.
This document will be reviewed frequently by the above audiences to check if the different phases
of the project are being completed by meeting the given requirements.
Software Requirements Specification for <Project> Page 2

1.4 Product Scope

The proposed system is able to perform steganographic techniques on text files, image files, and
audio files and on video files as well. The product also supports encryption and compression. It
should also ensure that only authenticated users can open the software. The software also includes a
feature known as scheduler in the product with the help of which end user can schedule the
steganographic tasks for the future time as well.
There are two main functions that the software must be able to perform. One is the encode
operation, whereby the data from the source data file is inserted into the source image file, and the
output is saved in the target image file. The source image file must be of a valid JPEG file type,
and the source data file must be a valid, existing file of any data type.
The other main function that the software must perform is the decode operation, whereby the
data encoded in the given encoded JPEG image is extracted and saved to the output directory, using
the original name of the data file stored in the encoded image. The encoded image file must be of a
valid JPEG image.

1.5 References

Wikipedia:
1. http://en.wikipedia.org/wiki/Steganography
2. http://en.wikipedia.org/wiki/StegoText
Andrews S Tenanbaum (Computer Networks)

2. Overall Description

2.1 Product Perspective

There are several existing products which perform a superset of the functions of Steganography.
These products provide steganographic capabilities for not only JPEG images, but various other
media formats including BMP, WAV, and MP3 etc. Our Steganography software will use these
packages as a model, but it will not depend on or directly execute them. As it stands, our software
project will not make direct use of any external libraries, so it will be totally independent and self-
contained

2.2 Product Functions

There are two primary functions of the Steganography software. One of these is the encode
function. It will take the source data file, an unencoded image file, and target image file and
encode the data into the target image file. The other primary function of the software is the decode
function. It will take an encoded image file and decode the data, storing it in the target data file.

2.3 User Classes and Characteristics

• Administrator : They have full control over the software. Apart from using the basic
task,they have full control over the user management and they can also view the log file.
Software Requirements Specification for <Project> Page 3

• End User : They can perform the Steganographic task but have no control over the user
Management And log file

2.4 Operating Environment

The product will be operating in windows environment. The only requirement is a

computer system with internet connection in it.

2.5 Design and Implementation Constraints

The Product is developed using JAVA. The backend database for this is SQL Server.

2.6 User Documentation

The product will include user manual. The user manual will include product overview, complete
configuration of the used software (such as SQL server), technical details, backup procedure and
contact information which will include address and contact. There will be no online help for the
product at this moment. The databases will be created in the Microsoft SQL server.

2.7 Assumptions and Dependencies

The product needs following third party product.

• Microsoft SQL server to store the database.
• Java to develop the Product
• Internet connection to use the software.

3. External Interface Requirements

3.1 User Interfaces

The external user are military persons ,examination department officers etc.

3.2 Hardware Interfaces

The product will be operating in windows environment.

RAM -256 MB
Hard disk -40 GB

3.3 Software Interfaces

The Product is developed using JAVA. The backend database for this is SQL Server.
To make this software we are using Netbeans as front end.
Software Requirements Specification for <Project> Page 4

3.4 Communications Interfaces

The customer must connect to the internet to access the website :

1. Dial-up modem of 56kbps.
2. Broadband Internet.

4. System Features

4.1 Description and Priority

Encryption -For security perposes private data is added(Encrypted) with images or
audio.
Encryption -To convert encryption data into actual form decryption is necessary.

4.2 Stimulus/Response Sequences

It can be used by authenticate user which have provided user id and password.

4.3 Functional Requirements

REQ-1: Address bar for text file in which there is private messages.
REQ-2: Address bar for image file in which we encrypt the text.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The PC used must be atleast Pentium 4 machines or more so that it can give optimum performance.

5.2 Safety Requirements

Database may get crashed at any certain time due to virus or oprating system failure.Therefore it is
require to take database backup.

5.3 Security Requirements

User id and password will be provide to authencate user to maintain security or privacy ,protection
of the data used or created by the software.

5.4 Software Quality Attributes

1. Software is reliable.Authentication required for accessing the software.

2. Can be used for secure data transmission.
3. Software is usable.It is easy to understand.
4. Software is portable. It can be easily installed.
Software Requirements Specification for <Project> Page 5

6. Project Plan

6.1 Team Members

1. Saurabh purohit
2. Shahbaz khan
3. Surendra rathore

6.2 Division of Work

Analysis - Surendra rathore,

Design - Shahbaz khan,
Coding and testing - Saurabh purohit

6.3 Time Schedule

Analysis - First 4 weeks

Design - Next 6 weeks,