Project Abstract

Title of Project: Image Steganography

 1- Name: Shail Kurhekar

1- PRN: 20220804026
Name of the group members
and PRN: 2- Name: Ishwar Bundele

2- PRN: 20220804057
 Title of the Project
Brief Description of the project:

Title: Image Steganography

Steganography is a technique where we put a hidden message by

simply covering it up within another image file or video file.
Steganography conceals sensitive information within computer files
and media files being the most eligible candidates.
The purpose of Steganography is covert communication- to hide
the existence of a message from Third Party / Intruder.
In this project , the messages may firstly be encrypted. The
sender embeds the secret message to be sent into a graphic file. This
results in the production of what is called stego-image. Additional
secret data may be needed in the hiding process e.g. a stegokey etc.
This stego-image is then transmitted to the recipient.
Project Proposal / Synopsis

Title:- Image Steganography

Introduction of the Project:-
 Steganography comes from the Greek Word, meaning Covered or Secret
Writing. Steganography is the method of hiding secret data in any
image/audio/video.
 This is an interesting project in which we will be given two options: Encode
and Decode. By clicking the Encode button secret message, the name of the
file should be entered and uploaded. After uploading the file the image will
be encoded with the secret message. By clicking the Decode button upload
the file that is to be decoded and after uploading the hidden text will be
displayed on the screen.
Problem Definition:-

 How can we send the message secretly to the destination?

 Using Steganography, information can be hidden in carriers such as images,
audio files, text files, videos and data transmissions.
 In this Project, we proposed a new framework of an image steganography
system to hide a digital text of a secret message in it.
Existing system:-

 In special domain, the hiding process such as least significant bit (LSB)
replacement, is done in special domain, while transform domain methods;
hide data in another domain such as wavelet domain.
 LSB method has intense affect on the statistical information of image like
histogram. Attackers could be aware of a hidden communication by just
checking the histogram if an image.
Objectives:-

 The objective of this Python project is to hide the message within the image
and then decode the image. It uses Tkinter, Stegano modules. Functions in
Python will also be used.
 The other goal of steganography is to avoid drawing suspicion to the existence
of a hidden message.
Purpose:-

The Purpose of Steganography is to conceal and deceive. It is a form of

conversion of communication and can involve the use of any medium to hide the
message. It’s not a form of Cryptography, because it doesn’t involve scrambling
data or using a key. Instead, it is a form of data hiding and data encryption and
can be executed in clever ways.
Scope:-

 The Scope of this project is to limit unauthorized access and provide better security
during message transmission. To meet the requirements, we use the simple and basic
approach of steganography.
 The proposed approach finds the suitable algorithm for embedding the data in an image
using steganography which provides the better security pattern for sending message
through a network.
Applicability:-

Steganography is applicable to, but limited to, the following area:-

 Confidential communication and secret data storing
 Protection of data alteration
 Access control system for digital content distribution
 Media Database Systems
The Areas differs in what feature of steganography is utilized in each system.
Feasibility Study:-

Feasibility is the term relates to practicality, possibility or convenience.

Feasibility study has 4 major aspects or dimensions regarding the development of
this software:-
 Technical Feasibility
 Economic Feasibility
 Operational Feasibility
 Organizational Feasibility
Planning and Scheduling:-
Software and Hardware Requirements:-
Hardware Specification Requirements:-
 Operating System -> any with VS Code or Pycharm.
 CPU-> Pentium 200MHz or above.
 Memory-> 32 MB or above.
 HDD Space-> 28MB or above.
Software Specification Requirement:-
 Front End of the mini-Project is supported by the programming language “Python”.
 Back End is supported by the Network interface and some algorithms based upon the
cryptography.
Conceptual Design and
UML Diagrams
 Flow Chart:

A flowchart is a type of diagram that represents a workflow or process. A

flowchart can also be defined as a diagrammatic representation of an algorithm,
a step-by-step approach to solving a task. The flowchart shows the steps as boxes
of various kinds, and their order by connecting the boxes with arrows.
 Data Flow Diagram:
In Software engineering DFD(data flow diagram) can be drawn to
represent the system of different levels of abstraction. Higher-level DFDs are
partitioned into low levels-hacking more information and functional elements.
Levels in DFD are numbered 0, 1, 2 or beyond. Here, we will see mainly 3 levels
in the data flow diagram, which are: 0-level DFD, 1-level DFD, and 2-level
DFD.

It is also known as a context diagram. It’s designed to be an

abstraction view, showing the system as a single process with its
relationship to external entities. It represents the entire system as a single
bubble with input and output data indicated by incoming/outgoing arrows.

0 - LEVEL DFD:
 1 - LEVEL DFD:

In 1-level DFD, the context diagram is decomposed into multiple

bubbles/processes. In this level, we highlight the main functions
of the
system and breakdown the high-level process of 0-level DFD into
subprocesses.
 2 - LEVEL DFD:
2-level DFD goes one step deeper into parts of 1-level DFD. It can
be used to plan or record the specific/necessary detail about the system’s
functioning.
 ER Diagram:
An Entity Relationship (ER) Diagram is a type of flowchart that
illustrates how “entities” such as people, objects or concepts
relate to each other within a system. ER Diagrams are most
often used to design or debug relational databases in the fields
of software engineering, business information systems,
education and research. 
 Class Diagram:
Class diagrams are one of the most useful types of diagrams in UML as
they clearly map out the structure of a particular system by modeling
its classes, attributes, operations, and relationships between objects.
 Activity Diagram:
An activity diagram is a behavioral diagram i.e. it depicts the
behavior of
a system. An activity diagram portrays the control flow from a
start point to a
finish point showing the various decision paths that exist while
the activity is
being executed.
 Usecase Diagram:
In the Unified Modelling Language (UML), a use case diagram can
summarize the details of your system's users (also known as actors) and
their
interactions with the system. To build one, you'll use a set of specialized
symbols
and connectors. An effective use case diagram can help your team
discuss and
represent:
❖ Scenarios in which your system or application interacts with people,
organizations, or external systems.
❖ Goals that your system or application helps those entities (known as
actors)
achieve.
❖ The scope of your system.
 Component Diagram:
Component diagram is a special kind of diagram in UML. The purpose is
also different from all other diagrams discussed so far. It does not describe the
functionality of the system but it describes the components used to make those
functionalities.
Component diagrams are used in modeling the physical aspects of objectoriented
systems that are used for visualizing, specifying, and documenting
component-based systems and also for constructing executable systems through
forward and reverse engineering. Component diagrams are essentially class
diagrams that focus on a system's components that often used to model the static
implementation view of a system.
Sequence Diagram:
A sequence diagram is a type of interaction diagram because it
describes how and in what order a group of objects works
together. These
diagrams are used by software developers and business
professionals to
understand requirements for a new system or to document an
existing
process. Sequence diagrams are sometimes known as event
diagrams or
event scenarios.
Sequence diagrams can be useful references for businesses and
other
organizations. Try drawing a sequence diagram to:
➢ Represent the details of a UML use case.
➢ Model the logic of a sophisticated procedure, function, or
operation.
➢ See how objects and components interact with each other to
complete a process.
➢ Plan and understand the detailed functionality of an existing
or future scenario.