Project Report

PROJECT REPORT
ON
Data Hide Into Audio And Video
SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR
Tilak Mahrashtra Viduapeeth,

Pune
for the partial fulfilment of the degree
BACHELOR OF COMPUTER APPLICATION
BY
Mr. AKSHAY PHALKE (PRN:-04414600025)
Mr. ABHISHEK DANGAT (PRN:-04414600029)
UNDER THE GUIDANCE OF

MR.S.J Vishwakarma & Asst.Prof. Namita Tiwari
Through
TILAK MAHARASHTRA
VIDYAPEETH
NAVI MUMBAI-410-210
2016-2017
"Acknowledgement"
"Data Hide Into Audio &Video"
PROJECT REPORT ON AS PER OF THE CURRICULAM OF
"BACHELOR OF COMPUTER APPLICATI0NS"

With immense please we are presenting "data hide into audio and video"
project report as part of the curriculam of "bachelor of computer
application".we wish to thank all the people who gave us unending support.
i / we express my / our profound thanks to our head of department

Mrs."Asst.Prof.Pournima.K.Jangle.".Project guide Asst.Prof.S.J.Vishwakarma
And Asst Prof Mrs."Namita Tiwari" and all those who have indirectely guided
and helped us in preparation of this project
MR.ABHISHEK DANGAT (PRN:-04414600029)
MR.AKSHAY PHALKE (PRN:-04414600025)
Name Of The Examinar:-
_____________________________________
Signature Of The Examinar:-
_____________________________________
Data Hide into Audio & Video
INDEX
1
TITLE
Page no
1
Introduction 1
1.1
What is Steganography?
7
1.2
What is Authentication?
8
1.3
Methods of Authentication
8
1.4
Steganography Concept
9
1.5
Motivation
10
1.6
Objective
10
2
Problem Definition
2.1
Existing Approach
12
2.2
Purpose Approach
13
3
Requirement Specification
3.1
Software Requirement
15
3.2
Hardware Requirement
15
4
Literature Survey
4.1
Introduction
17
4.1.1
Technical Feasibility
17
4.1.2
Operational Feasibility
17
4.1.3
Economical Feasibility
18
4.2
Software Requirement and Analysis
19
General
19
4.2.1
Module Description
20
5
Testing and planning
5.1
Testing
23
5.2
Testing Methodology
23
5.3
Purpose
28
5.4
Planning
28
5.5
Gantt Chart
29
5.6
PERT Chart
31
6
System Design
6.1
Purpose
34
6.2
Project Development Approach
34
6.3
Data Flow Diagram
35
6.4
Flow Chart
36
6.5
Use Case Diagram
38
7
Advantages
40
8
Needs and Applications
42
9
Screen Shots
45
10
Conclusion
51
11
References
52
Abstract
The Internet as a whole does not use secure links, thus information in transit
may be vulnerable to interception as well. The importance of reducing a chance
of the information being detected during the transmission is being an issue now
days. Some solution to be discussed is how to pass information in a manner that
the very existence of the message is unknown in order to repel attention of the
potential attacker. Besides hiding data for confidentiality, this approach of
information hiding can be extended to copyright protection for digital media. In
this research, we clarify what steganography is, the definition, the importance as
well as the technique used in implementing steganography. We focus on the Least
Significant Bit (LSB) technique in hiding messages in an audio and video. The
system enhanced the LSB technique by randomly dispersing the bits of the
message in the image and thus making it harder for unauthorized people to
extract the original message. Audio steganography is concerned with hiding
information in a cover (host) audio signal in an imperceptible way. Hidden
information from the stego, or data-embedded audio & video signal, is retrieved
using a key similar to the one that was employed during the hiding phase. Least
Significant Bit (LSB) modification technique is the most simple and efficient
technique used for audio steganography. Proposed technique has been tested
successfully on a .wav file at a sampling frequency of 3000 samples/second with
each sample containing 8 bits. It is very important for effective and successful
embedding process to select appropriate pixels in the video frames, which are
used to store the secret data. We use video based Steganography because of large
size and memory requirements. Hiding information in a carrier file we use least
significant bit (LSB) insertion technique. In Least significant bit (LSB) insertion
technique, for hiding information we change LSB of video file with the
information bits .This paper will focus on hiding information in specific frames of
the video and in specific position of the frame by LSB substitution.
Chapter 1
Introduction
1
1.1 What is Steganography?
Steganography is the art and science of writing hidden messages in such a way that no
one, apart from the sender and intended recipient, suspects the existence of the
message, a form of security through obscurity. The word steganography is of Greek
origin and means "concealed writing" from the Greek words steganos meaning
"covered or protected", and graphic meaning "writing. The first recorded use of the
term was in 1499 by Johannes Trithemius in his Steganographia, a treatise on
cryptography and steganography disguised as a book on magic. Generally, messages
will appear to be something else: images, articles, shopping lists, or some other cover
text and, classically, the hidden message may be in invisible ink between the visible
lines of a private letter. The advantage of steganography, over cryptography alone, is
that messages do not attract attention to themselves. Plainly visible encrypted
messages no matter how unbreakable will arouse suspicion, and may in themselves be
incriminating in countries where encryption is illegal Therefore, whereas cryptography
protects the contents of a message, steganography can be said to protect both
messages and communicating parties. Steganography includes the concealment of
information within computer files. In digital steganography, electronic
communications may include steganographic coding inside of a trans-port layer, such
as a document file, image file, program or protocol. Media files are ideal for
steganographic transmission because of their large size. As a simple example, a sender
might start with an innocuous image file and adjust the color of every 100th pixel to
correspond to a letter in the alphabet, a change so subtle that someone not specifically
looking for it is unlikely to notice it.
2
Introduction
1.2 What is Authentication?
Authentication is a process in which the credentials provided are compared to those on

file in a database of authorized users information on a local operating system or
within an authentication server. If the credentials match, the process is completed and
the user is granted authorization for access. The permissions and folders returned
define both the environment the user sees and the way he can interact with it,
including hours of access and other rights such as the amount of allocated storage
space.
The process of an administrator granting rights and the process of checking user
account permissions for access to resources are both referred to as authorization. The
privileges and preferences granted for the authorized account depend on the users
permissions, which are either stored locally or on the authentication server. The
settings defined for all these environment variables are set by an administrator.
1.3 Methods of Authentication:
Authentication means verifying the identity of someone (a user, device, or an entity)

who wants to access data, resources, or applications. Validating that identity
establishes a trust relationship for further interactions. Authentication also enables
accountability by making it possible to link access and actions to specific identities.
Oracle allows a single database instance to use any or all methods. Oracle requires
special authentication procedures for database administrators, because they perform
special database operations. Oracle also encrypts passwords during transmission to
ensure the security of network authentication.
3
To validate the identity of database users and prevent unauthorized use of a database
user name, you can authenticate users by using any combination of the methods
described in the following sections:
1.4 Steganography Concepts
The modern formulation of steganography is often given in terms of the prisoners

problem where Alice and Bob are two inmates who wish to communicate in order to
hatch an escape plan. However, all communication between them is examined by the
warden, Wendy, who will put them in solitary contentment at the slightest suspicion of
covert communication. Specifically, in the general model for steganography, we have
Alice wishing to send a secret message m to Bob. In order to do so, she "embeds" m
into a cover-object c, and obtains a stego-object s. The stego-object s is then sent
through the public channel. Thus we have the following definitions:
Cover-object: refers to the object used as the carrier to embed messages into. Many
different objects have been employed to embed messages into for example images,
audio, and video as well as structures, and html pages to name a few.
Stego-object: refers to the object which is carrying a hidden message. so given a cover
object, and a messages the goal of the steganographer is to produce a stego object
which would carry the message.
In a pure steganography framework, the technique for embedding the message is
unknown to Wendy and shared as a secret between Alice and Bob. However, it is
generally considered that the algorithm in use is not secret but only the key used by
the algorithm is kept as a secret between the two parties, this assumption is also
known as Kirchhoffs principle in the field of cryptography. The secret key for ex:
,can be a password used to seed a pseudo random number generator to select pixel
locations in an cover object for embedding the secret message.
4
1.5 Motivation:
The primary reason for selecting steganography among the list of possible project
topics was due to the unfamiliarity of the word that twigged an interest in the subject.
Another motivation for researching the topic was after reading an online article in the
USA Today titled "Terror groups hide behind Web encryption" that claims terrorists
and, in particular, Osama bin Laden and the al-Qaida network, may be using
steganography to communicate with each other in planning terrorist attacks. It is
thought that images with hidden messages are placed on bulletin boards or dead drops
for other terrorists to pick up and retrieve hidden messages. Thus far, this supposition
has yet to be proven.
1.6 Objective
The goal of steganography is hide the fact that communication is taking place. So, a
fundamental requirement of this steganography system is that the hider message
carried by stego-media should not be sensible to human beings.
The other goal of steganography is to avoid drawing suspicion to the existence of a
hidden message. This approach of information hiding technique has recently became
important in a number of application area.
5
This project has following objectives:
.To product security tool based on steganography techniques.

To explores techniques of hiding data using encryption
module of this
To extract techniques of getting secret data using decryption
module.
Providing Security.
Chapter 2
Problem Definition
6
PROBLEM DEFINITION
2.1 Existing System
To protect important information we use cryptography. Steganography is different

from cryptography, where the existence of the message itself is not disguised, but the
content is obscured. Steganography could be considered as the dark cousin of
cryptography. Cryptography assures privacy whereas Steganography assures secrecy.
For e.g. Sending of encrypted credit card details over the internet is well known to a
malicious user. But, the actual content is randomized or confused and hence not
revealed. But, in Steganography the fact that the credit card details is being sent is
kept secretly (as the message or the image appears innocent). The advantage of
steganography over cryptography alone is that messages do not attract attention to
themselves, to messengers, or to recipients. An unhidden coded message, no matter
how unbreakable it is, will arouse suspicion and may in itself be incriminating, as in
some countries encryption is illegal.
To protect important information we use cryptography. Steganography is different

from cryptography, where the existence of the message itself is not disguised, but the
content is obscured. Steganography could be considered as the dark cousin of
cryptography. Cryptography assures privacy whereas Steganography assures secrecy.
7
For e.g. Sending of encrypted credit card details over the internet is well known to a
malicious user. But, the actual content is randomized or confused and hence not
revealed. But, in Steganography the fact that the credit card details is being sent is
kept secretly (as the message or the image appears innocent). The advantage of
steganography over cryptography alone is that messages do not attract attention to
themselves, to messengers, or to recipients. An unhidden coded message, no matter
how unbreakable it is, will arouse suspicion and may in itself be incriminating, as in
some countries encryption is illegal.
2.2 Proposed System
Encryption software protects internet connected computers from crackers and other
online intruders. The technology is widely used to encrypt credit card information,
bank account numbers and other type of financial records so they can send safely and
securely across the internet. Protect much of the intellectual content thats marketed on
the web, such as music, Videos, articles, and software, restricting its availability to
paying customers. This system helps to hide the information while sending the
important and confidential documents in video files; it will be invisible for the third
person. This system is helpful for the defense and security departments sending and
receiving the confidential matters in emergency situations.
Encryption software protects internet connected computers from crackers and other
online intruders. The technology is widely used to encrypt credit card information,
bank account numbers and other type of financial records so they can send safely and
securely across the internet. Protect much of the intellectual content thats marketed on
the web, such as music, Videos, articles, and software, restricting its availability to
paying customers. This system helps to hide the information while sending the
important and confidential documents in video files; it will be invisible for the third
person. This system is helpful for the defense and security departments sending and
receiving the confidential matters in emergency situations.
8
Chapter 3
Requirement Specification
9
REQUIREMENT SPECIFICATION
3.1 Software Requirements
A set of programs associated with the operation of a computer is called software.

Software is the part of the computer system which enables the user to interact with
several physical hardware devices.
The minimum software requirement specifications for developing this project are as
follows:
Operating System : Windows XP /2000
Technologies : Microsoft visual studio 2010(C#)
10
3.2 Hardware Requirement Specification
The Collection of internal electronic circuits and external physical devices used in
building a computer is called Hardware.
The minimum hardware requirement specification for developing this project is as

follows:
Processor : Pentium IV
RAM : 512MB RAM
Hard Disk : 10GB
11
Chapter 4
Literature Survey
LITERATURE SURVEY
4.1 Introduction
A feasibility study is a high-level capsule version of the entire System analysis and
Design Process. The study begins by classifying the problem definition. Feasibility is
to determine if its worth doing. Once an acceptance problem definition has been
generated, the analyst develops a logical model of the system. A search for alternatives
is analyzed carefully. There are 3 parts in feasibility study.
4.1.1 Technical Feasibility
Evaluating the technical feasibility is the trickiest part of a feasibility study.

This is because, at this point in time, not too many detailed design of the system,
making it difficult to access issues like performance, costs on (on account of the kind
12
of technology to be deployed) etc. A number of issues have to be considered while

doing a technical analysis. Understand the different technologies involved in the
proposed system before commencing the project we have to be very clear about what
are the technologies that are to be required for the development of the new system.
Find out whether the organization currently possesses the required technologies. Is the
required technology available with the organization?
4.1.2 Operational Feasibility
Proposed project is beneficial only if it can be turned into information systems that
will meet the organizations operating requirements. Simply stated, this test of
feasibility asks if the system will work when it is developed and installed. Are there
major barriers to Implementation? Here are questions that will help test the
operational feasibility of a project:
Is there sufficient support for the project from management from users? If the
current system is well liked and used to the extent that persons will not be able
to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users
may welcome a change that will bring about a more operational and useful
systems.
Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in

general and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered. In the
existing manual system, the new system was considered to be operational feasible.
4.1.3 Economic Feasibility
Economic feasibility attempts 2 weigh the costs of developing and implementing a

new system, against the benefits that would accrue from having the new system in
13
place. This feasibility study gives the top management the economic justification for
the new system. A simple economic analysis which gives the actual comparison of
costs and benefits are much more meaningful in this case. In addition, this proves to
be a useful point of reference to compare actual costs as the project progresses. There
could be various types of intangible benefits on account of automation. These could
include increased customer satisfaction, improvement in product quality better
decision making timeliness of information, expediting activities, improved accuracy of
operations, better documentation and record keeping, faster retrieval of information,
better employee morale
4.2 SOFTWARE REQUIREMENTS ANALYSIS
General
The first step in developing anything is to state the requirements. This applies just as
much to leading edge research as to simple programs and to personal programs, as
well as to large team efforts. Being vague about your objective only postpones
decisions to a later stage where changes are much more costly.
The problem statement should state what is to be done and not how it is to be
done. It should be a statement of needs, not a proposal for a solution. A user manual
for the desired system is a good problem statement. The requestor should indicate
14
which features are mandatory and which are optional, to avoid overly constraining
design decisions. The requestor should avoid describing system internals, as this
restricts implementation flexibility. Performance specifications and protocols for
interaction with external systems are legitimate requirements. Software engineering
standards, such as modular construction, design for testability, and provision for future
extensions, are also proper.
Many problems statements, from individuals, companies, and government

agencies, mixture requirements with design decisions. There may sometimes be a
compelling reason to require a particular computer or language; there is rarely
justification to specify the use of a particular algorithm. The analyst must separate the
true requirements from design and implementation decisions disguised as
requirements. The analyst should challenge such pseudo requirements, as they restrict
flexibility. There may be politics or organizational reasons for the pseudo
requirements, but at least the analyst should recognize that these externally imposed
design decisions are not essential features of the problem domain.
A problem statement may have more or less detail. A requirement for a

conventional product, such as a payroll program or a billing system, may have
considerable detail. A requirement for a research effort in a new area may lack many
details, but presumably the research has some objective, which should be clearly
stated.
Most problem statements are ambiguous, incomplete, or even inconsistent.

Some requirements are just plain wrong. Some requirements, although precisely
stated, have unpleasant consequences on the system behavior or impose unreasonable
implementation costs. Some requirements seem reasonable at first but do not work out
as well as the request or thought. The problem statement is just a starting point for
understanding the problem, not an immutable document. The purpose of the
subsequent analysis is to fully understand the problem and its implications. There is no
reasons to expect that a problem statement prepared without a fully analysis will be
correct.
The analyst must work with the requestor to refine the requirements so they
represent the requestors true intent. This involves challenging the requirements and
15
probing for missing information. The psychological, organizational, and political

considerations of doing this are beyond the scope of this book, except for the
following piece of advice: If you do exactly what the customer asked for, but the result
does not meet the customers real needs, you will probably be blamed anyway.
4.2.1 Module Description
This system is divided into three modules:
1. Sending message
2. Encryption module
3. Decryption module.
4. Receiving message
1.Sending message
The sender can send a message to the destination more securely. This can be
done by attaching a video file to the message. So the third party can be unaware
the secret message. They think that a video file is sending and they not at all
know about this secret sending of the message.
16
2. Encryption module
In this a sender can encrypt a file by entering a key.The same key must be
entered
Same key must entered during the decryption process.
3.Decryption Module
This process can be done by entering the key that previously entered during the
Encryption process. If the entered key is wrong the message wont be received
correctly.
4.Recieving Message
In this the Receiver can receive the hidden message by the decryption process.
In This the user enter the same key as the sender sends.The receiver can receive the
message by correctly entering the key.
17
Chapter 5
Testing and Planning
TESTING
18
5.1 Testing:
The process of executing a system with the intent of finding an error.

Testing is defined as the process in which defects are identified, isolated,
subjected for rectification and ensured that product is defect free in order to
produce the quality product and hence customer satisfaction.
Quality is defined as justification of the requirements
Defect is nothing but deviation from the requirements
Defect is nothing but bug.
Testing --- The presence of bugs
Testing can demonstrate the presence of bugs, but not their absence
Debugging and Testing are not the same thing!
Testing is a systematic attempt to break a program or the AUT
Debugging is the art or method of uncovering why the script /program did not
execute properly.
5.2 Testing Methodologies:
Black box Testing: is the testing process in which tester can perform testing
on an application without having any internal structural knowledge of
application.
Usually Test Engineers are involved in the black box testing.
White box Testing: is the testing process in which tester can perform testing
on an application with having internal structural knowledge.
Usually The Developers are involved in white box testing.
Gray Box Testing: is the process in which the combination of black box and
white box techniques are used.
19
Levels of Testing
Module1 Module2 Module3
Units Units Units
i/p Integration o/p i/p Integration o/p
System Testing: Presentation + business +Databases
UAT: user acceptance testing
Fig Levels of testing
STLC (SOFTWARE TESTING LIFE CYCLE)
Test Planning: 1.Test Plan is defined as a strategic document which

describes the procedure how to perform various testing on the
total application in the most efficient way.
2. Objective of testing,
3. Areas that need to be tested,
4. Areas that should not be tested,
5. Scheduling Resource Planning,
20
Test Development: 1. Test case Development (check list)
2. Test Procedure preparation. (Description of the test cases)
Test Execution: 1. Implementation of test cases. Observing the result.
Result Analysis: 1. Expected value: is nothing but expected behavior
Of application.
2. Actual value: is nothing but actual behavior of the
application
Bug Tracing: Collect all the failed cases, prepare documents.
Reporting: Prepare document (status of the application)
Types Of Testing:
Smoke Testing: is the process of initial testing in which tester looks for the
availability of all the functionality of the application in order to perform detailed
testing on them. (Main check is for available forms)
Sanity Testing: is a type of testing that is conducted on an application initially to

check for the proper behavior of an application that is to check all the functionality are
available before the detailed testing is conducted by on them.
Regression Testing: is one of the best and important testing. Regression testing is the
process in which the functionality, which is already tested before, is once again tested
whenever some new change is added in order to check whether the existing
functionality remains same.
Re-Testing: is the process in which testing is performed on some functionality which

is already tested before to make sure that the defects are reproducible and to rule out
the environments issues if at all any defects are there.
21
Static Testing: is the testing, which is performed on an application when it is not been
executed. ex: GUI, Document Testing
Dynamic Testing: is the testing which is performed on an application when it is being
executed. ex: Functional testing.
Alpha Testing: it is a type of user acceptance testing, which is conducted on an
application when it is just before released to the customer.
Beta-Testing: it is a type of UAT that is conducted on an application when it is
released to the customer, when deployed in to the real time environment and being
accessed by the real time users.
Monkey Testing: is the process in which abnormal operations, beyond capacity
operations are done on the application to check the stability of it in spite of the users
abnormal behavior.
Compatibility testing: it is the testing process in which usually the products are
tested on the environments with different combinations of databases (application
servers, browsersetc) In order to check how far the product is compatible with all
these environments platform combination.
Installation Testing: it is the process of testing in which the tester try to install or try
to deploy the module into the corresponding environment by following the guidelines
produced in the deployment document and check whether the installation is successful
or not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the formal
testing where in test case document is used, with out that test case document testing
can be done of an application, to cover that testing of the future which are not covered
in that test case document. Also it is intended to perform GUI testing which may
involve the cosmetic issues.
22
TCD (Test Case Document):
Test Case Document Contains
Test Scope (or) Test objective

Test Scenario
Test Procedure
Test case
This is the sample test case document for the Acadamic details of student project:
Test scope
Test coverage is provided for the screen Acadamic status entry form of a
student module of university management system application
Areas of the application to be tested
Test Scenario
When the office personals use this screen for the marks entry, calculate the
status details, saving the information on students basis and quit the form.
Test Procedure
The procedure for testing this screen is planned in such a way that the data
entry, status calculation functionality, saving and quitting operations are tested
in terms of Gui testing, Positive testing, Negative testing using the
corresponding Gui test cases, Positive test cases, Negative test cases
respectively
23
5.4 Purpose
The purpose of Software Project Planning is to establish reasonable plans for

performing the software engineering and for managing the software project. Software
Project Planning involves developing estimates for the work to be performed,
establishing the necessary commitments, and defining the plan to perform the work.
5.5 Planning Phase
The software planning begins with a statement of the work to be performed and other
constraints and goals that define and bound the software project (those established by
the practices of the Requirements Management key process area). The software
planning process includes steps to estimate the size of the software work products and
the resources needed, produce a schedule, identify and assess software risks, Iterating
through these steps may be necessary to establish the plan for the software project
(i.e., the software development plan).
24
5.6 Gantt Chart
A Gantt chart can be developed for the entire project. It depicts a part of a software
project schedule that emphasizes the concept scooping task for a new software
project. All project tasks (for concept scooping) are listed in the left hand column.
The horizontal bars show the time needed to complete an activity.
A Gantt chart is a graphical representation of the duration of tasks against the

progression of time. It is a useful tool for planning and scheduling projects. It is
helpful when monitoring a projects progress.
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements
of a project. Terminal elements and summary elements comprise the work
breakdown structure of the project. Some Gantt charts also show the dependency
relationships between activities.
Although a Gantt chart is useful and valuable for small projects that fit on a single
sheet or screen, they can become quite unwieldy for projects with more than about
30 activities. Larger Gantt charts may not be suitable for most computer displays. A
related criticism is that Gantt charts communicate relatively little information per
unit area of display. That is, projects are often considerably more complex than can
be communicated effectively with a Gantt chart.
Gantt charts only represent part of the triple constraints of projects, because they
focus primarily on schedule management. Moreover, Gantt charts do not represent
the size of a project or the relative size of work elements, therefore the magnitude of
a behind-schedule condition is miss communicated. If two projects are the same
number of days behind schedule, the larger project has a larger impact on resource
utilization, yet the Gantt does not represent this difference.
25
5.7 PERT chart
26
Complex projects require a series of activities, some of which must be performed

sequentially and others that can be performed in parallel with other activities. This
collection of series and parallel tasks can be modeled as a network.
The Program Evaluation and Review Technique (PERT) is a network model that
allows for randomness in activity completion times. PERT was developed in the late
1950s for the U.S.
Navys Polaris project having thousands of contractors. It has the potential to

reduce both the time and cost required to complete a project.
PERT is a method to analyze the tasks involved in completing a given project,
especially the time needed to complete each task, and identifying the minimum
time needed to complete total project.
A PERT event: is a point that marks the start or completion of one or more tasks. It
consumes no time and uses no resources. It marks the completion of one or more
tasks, and is not "reached" until all of the activities leading to that event have been
completed.
A predecessor event: an event (or events) that immediately precedes some other
event without any other events intervening. It may be the consequence of more
than one activity.
A successor event: an event (or events) that immediately follows some other event
without any other events intervening. It may be the consequence of more than one
activity.
27
28
Chapter 6
System Design
SYSTEM DESIGN
6.1 Purpose
29
The purpose of design document is to build the project in a manner specified and
developed the project in such a way that it is able to satisfy the user requirement and
develop according the requirement of user.
6.2 Project Development Approach
The development of this project has been performed in a systematic manner,

adopting the systems Approach. UML diagrams have been used that provide a better
insight to the user requirements.
6.3 Data Flow Diagram
30
DFD is a graphical representation technique for showing functions as well as data

flow within the system. It is used for modeling
31
This diagrammatic representation can give a step-by-step solution to a given

problem. Process operations are represented in these boxes, and arrows connecting
them represent flow of control. Data flows are not typically represented in a
flowchart, in contrast with data flow diagrams; rather, they are implied by the
sequencing of operations.
32
33
6.5 Use Case Diagram
Use case diagrams model the functionality of system using actors and use cases. Use
case diagram visually represents what happens when an actor interacts with a
system. This approach uses a combination of text and pictures in order to improve
the understanding of requirements. The use case describes what of a system and not
how. They only give functional view of the system.
Terms used:
Actor: Actor is an external agent that lies outside the system model but interacts
with it in some or the other way. An actor may be a person, machine or an
information system that is external to the system model. An actor is represented by a
stick figure and is not a part of the system itself. Customers, users, external devices
interacting with the system are treated as actors.
Use cases: It is initiated by the user with a particular goal in mind, and completes
success-fully when that goal is satisfied. it describes the sequence of interactions
between actors and the system necessary to deliver the services that satisfies the
goal. It also includes possible variants of this sequence. The system is represented
by the rectangular box that contains oval shaped use cases. The actors are
represented by the sticks as shown in figure above. The use case can be described
as: Figure 4.4 shows the Use Case Diagram.
34
35
Chapter 7
Advantages
Advantages:
36
Audio and video based Steganography has the potential to conceal more
information:
Audio video files are generally larger than images
Our hearing can be easily fooled
Slight changes in amplitude can store vast amounts of information
Another aspect of audio and video Steganography that makes it so attractive is its
ability to combine with existing cryptography technologies.
Users no longer have to rely on one method alone. Not only can
information be encrypted, it can be hidden altogether.
Security:
Many attacks that are malicious against image Steganography

algorithms (e.g. geometrical distortions, spatial scaling, etc.) cannot
be implemented against audio and video Steganography schemes.
Consequently, embedding information into audio and video seems
more secure due to less steganalysis techniques for attacking to
audio. Audio and video Steganography in particular addresses key
issues brought about by the MP3 format, P2P software, and the need
for a secure broadcasting scheme that can maintain the secrecy of the
transmitted information, even when passing through insecure
channels.
Many sources and types make statistical analysis more difficult:

Greater amounts of information can be embedded without
audible degradation
37
Chapter 8
Needs and Application
Needs and Application
The advantage of steganography, over cryptography alone, is that messages do not

attract attention to themselves. Plainly visible encrypted messages no matter how
unbreakable will arouse suspicion, and may in themselves be incriminating in
countries where encryption is illegal. Therefore, whereas cryptography protects the
contents of a message, steganography can be said to protect both messages and
communicating parties.
Steganography includes the concealment of information within computer files. In

digital steganography, electronic communications may include steganographic
coding inside of a transport layer, such as a document file, image file, program or
38
protocol. Media files are ideal for steganographic transmission because of their large
size. As a simple example, a sender might start with an in-nocuous image file and
adjust the color of every 100th pixel to correspond to a letter in the alphabet, a
change so subtle that someone not specifically looking for it is unlikely to notice it.
Confidential communication and secret data storing
The "secrecy" of the embedded data is essential in this area.
Historically, steganography have been addressed in this area. Steganography

provides us with:
(A) Potential capability to hide the existence of confidential data
(B) Hardness of detecting the hidden (i.e., embedded) data
(C) Enhancing the secrecy of the encrypted data
Protection of data alteration
We take advantage of the fragility of the embedded data in this application area.We
asserted in the Home Page that "the embedded data can rather be fragile than be
very robust." Actually, embedded data are fragile in most steganography programs.
Especially, GTECH Hide & View program embeds data in an extremely fragile
manner.
Access control system for digital content distribution

39
In this area embedded data is "hidden", but is "explained" to publicize the content.
Today, digital contents are getting more and more commonly distributed over
Internet than before. For example, music companies release new albums on their
Webpage in a free or charged manner. However, in this case, all the contents are
equally distributed to the people who can make access to the page. So, an ordinary
Web distribution scheme is not suited for a "case-by-case" and "selective"
distribution. Of course it is always possible to attach digital contents to e-mail
messages and send them to the customers. But it will takes a lot of cost in time and
labor.
Media Database systems
Media data (photo picture, movie, music, etc.) have some association with other
information. A photo picture, for instance, may have the following.
(1) The title of the picture and some physical object information
(2) The date and the time when the picture was taken
(3) The camera and the photographer's information
40
Chapter 9
Screen Shots
Screen Shots
41
This is our login page for security purpose
In this form four buttons are given as shown
Here we Enter text and enter text and select carrier file to encrypt
42
43
44
45
46
This form is specially design for only local user (local user can decrypt file only)
Conclusion
The proposed approach in this project uses a new steganographic approach
called audio and video steganography. The application creates a stego audio and
video in which the personal data is embedded and is protected with a password
which is highly secured. The main intention of the project is to develop a
steganographic application that provides good security. The proposed approach
provides higher security and can protect the message from stego attacks. The image
resolution doesnt change much and is negligible when we embed the message into
the audio and video and the audio and video is protected with the personal
password. So, it is not possible to damage the data by unauthorized person. We used
the Least Significant Bit algorithm in this project for developing the application
which is faster and reliable and compression ratio is moderate compared to other
algorithms. The compression depends on the document size as well as the carrier
audio and video size. Steganography has its place in security. It is not intended to
replace cryptography but supplement it. Hiding a message with steganography
methods reduces the chance of a message being detected. However, if that message
is also encrypted, if discovered, it must also be cracked (yet another layer of
protection).
47
References
1) N.F. Johnson and S. Jajodia, Exploring steganography: Seeing the unseen 31(2)
(1998) 26- 34
2) J.C. Judge, Steganography: Past, present, future. SANS Institute publication,

http://www.sans.org/ reading_room/whitepapers/stenganography/552.php, 2001.
3) S.B. Sadkhan, Cryptography: Current status and future trends
4) G.J. Simmons, The prisoners problem and the subliminal channel
48
5) N.F. Johnson and S. Jajodia. Steganalysis of images created using current

steganography software. In Proc. the Second Inform. Hiding Workshop LNCS,
volume 1525, pages 273 289. Springer-Verlag
6) R. Machado. Ez stego. http://www. stego.com.
7)J. J. Chae, B. S. Manjunath, Data Hiding in Video,Proceedings of the 6th IEEE

International Conference on Image Processing, 1999, pp.311-315.
8) Westfeld A, F5-A Steganographic Algorithm, Proceeding of 4th International

Conference on Information Hiding, LNCS 2137, Springer-Verlag, 2001, pp.289-
302.
49
50

Project Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Project Report

Загружено:

Авторское право:

Доступные форматы

PROJECT REPORT

Data Hide Into Audio And Video

SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR

Tilak Mahrashtra Viduapeeth,

BACHELOR OF COMPUTER APPLICATION

Mr. AKSHAY PHALKE (PRN:-04414600025)

Mr. ABHISHEK DANGAT (PRN:-04414600029)

UNDER THE GUIDANCE OF

"BACHELOR OF COMPUTER APPLICATI0NS"

i / we express my / our profound thanks to our head of department

MR.ABHISHEK DANGAT (PRN:-04414600029)

MR.AKSHAY PHALKE (PRN:-04414600025)

Name Of The Examinar:-

Signature Of The Examinar:-

1.1 What is Steganography?

1.2 What is Authentication?

Authentication is a process in which the credentials provided are compared to those on

1.3 Methods of Authentication:

Authentication means verifying the identity of someone (a user, device, or an entity)

1.4 Steganography Concepts

The modern formulation of steganography is often given in terms of the prisoners

steganography to communicate with each other in planning terrorist attacks. It is

has yet to be proven.

The other goal of steganography is to avoid drawing suspicion to the existence of a

important in a number of application area.

This project has following objectives:

.To product security tool based on steganography techniques.

2.1 Existing System

To protect important information we use cryptography. Steganography is different

To protect important information we use cryptography. Steganography is different

2.2 Proposed System

3.1 Software Requirements

A set of programs associated with the operation of a computer is called software.

Operating System : Windows XP /2000

Technologies : Microsoft visual studio 2010(C#)

3.2 Hardware Requirement Specification

The minimum hardware requirement specification for developing this project is as

RAM : 512MB RAM

Hard Disk : 10GB

4.1.1 Technical Feasibility

Evaluating the technical feasibility is the trickiest part of a feasibility study.

of technology to be deployed) etc. A number of issues have to be considered while

4.1.2 Operational Feasibility

Early involvement reduces the chances of resistance to the system and in

4.1.3 Economic Feasibility

Economic feasibility attempts 2 weigh the costs of developing and implementing a

4.2 SOFTWARE REQUIREMENTS ANALYSIS

Many problems statements, from individuals, companies, and government

A problem statement may have more or less detail. A requirement for a

Most problem statements are ambiguous, incomplete, or even inconsistent.

probing for missing information. The psychological, organizational, and political

4.2.1 Module Description

This system is divided into three modules:

Same key must entered during the decryption process.

Testing and Planning

The process of executing a system with the intent of finding an error.

5.2 Testing Methodologies:

Module1 Module2 Module3

Units Units Units

i/p Integration o/p i/p Integration o/p

System Testing: Presentation + business +Databases

UAT: user acceptance testing

Fig Levels of testing

STLC (SOFTWARE TESTING LIFE CYCLE)