Software Requirements Specification: For Steganosarous
Software Requirements Specification: For Steganosarous
Specification
For
STEGANOSAROUS
<Project>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
Table of Contents
1. Introduction 1
1.1 Purpose 1
1.2 Intended Audience and Reading Suggestions 1
1.3 Product Scope 1
1.4 References 1
2. Overall Description 2
2.1 Product Perspective 2
Performance of the Proposed (new) Steganographic system: 2
In the Proposed system, the ‘data packet ‘ is sent along with the CRC calculated on the data, through
the communication channel to the receiver. The time needed is same for sending the information
packet (either for sending data, or sending the CRC value) there by no propagation delay in the
system.Thus the operating speed of the system gets improved much. The data and CRC are sent
together, as a ‘data packet’ through the communication channel to the receiver.Though there is every
chance of hacking, even if the hacker hacks the system; he will not be able to distinguish the original
data from the CRC value, there by making the system secure and consistent for security
transmissions.By providing extra security, for the data sent (i-e)using ( Compression of data +
CRC).The propagation delay is overcame with the Proposed system.Thus we confine ourselves to the
“Proposed System” keeping in view of the drawbacks of the Existing system. 2
2.2 Product Functions 3
2.3 User Classes and Characteristics 3
2.4 Operating Environment 3
2.5 Design and Implementation Constraints 4
2.6 User Documentation 4
3. External Interface Requirements 4
3.1 User Interfaces 4
3.2 Hardware Interfaces 4
3.3 Software Interfaces 4
4. System Features 4
4.1 System Feature 1 4
Revision History
1.Introduction
1.1Purpose
Implement a secure system that protects data from various types of hackers when transmitted on
the network.
1.2Intended Audience and Reading Suggestions
Intended for Project Managers, Developers, End users and Quality Assurance engineers.
Sugested reading the document would be overall document description , product based
information gathering followed by Infrastructure requirement.
1.3Product Scope
Language : Java (Jdk1.4)
This project is developed in Java under Windows 98 platform. In this modern world of
computers, every noun in our vocabulary represents a class of objects sharing some set of
characteristics and functional traits.Java leads itself naturally in embodying these areas into its
own application domain. It has evolved a fantastic ability to generalize ,classify and generate
abstractions.
1.4References
1) Java a) Patrick naughton & Herbert schild
The complete reference-java 2
In the Proposed system, the ‘data packet ‘ is sent along with the CRC calculated on the data,
through the communication channel to the receiver. The time needed is same for sending the
information packet (either for sending data, or sending the CRC value) there by no propagation
delay in the system.Thus the operating speed of the system gets improved much. The data and
CRC are sent together, as a ‘data packet’ through the communication channel to the
receiver.Though there is every chance of hacking, even if the hacker hacks the system; he will not
be able to distinguish the original data from the CRC value, there by making the system secure
and consistent for security transmissions.By providing extra security, for the data sent (i-e)using (
Compression of data + CRC).The propagation delay is overcame with the Proposed system.Thus
we confine ourselves to the “Proposed System” keeping in view of the drawbacks of the Existing
system.
2.2P roduct Functions
● Secure transmission of data on network .
● Data to be made invisible using stenography.
● To detect damage or malicious script or viruses that would have alter the data on the
network
2.4Operating Environment
Software Requirement :
Operating System : 32 bit or Higher
Language : Java, JDK
Development Kit : JDK 1.3
Hardware Requirement(Minimum)
Processor : PII
Ram : 64 Mb
Hard Disk : 1 Gb
Monitor : VGA Color(256)
2.6User Documentation
The product is provided with built-in manual that would help the end user use the system for
functioning.
3.2Hardware Interfaces
The application concentrates on the data security and authentication and does not have direct
dependency on the network or protocols.
3.3Software Interfaces
The incoming data to the product would be raw text data and outgoing data would be the
container within which the data is hidden.
4.System Features
<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>
4.1System Feature 1
<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
The system has a high priority in its need for implementation as any form of data
that is transmitted is prone to hacking.
2. Stimulus/Response Sequences
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.