IMAGE STEGANOGRAPHY

PROJECT REPORT

Submitted by

MOHD ARSHAD
(1400118080)
&
MOHD ARSHAD KHAN
(1400118081)

in partial fulfillment for the award of the degree

of
Bachelor of Computer Application

INTEGRAL UNIVERSITY LUCKNOW

MAY 2017

1
 INTEGRAL UNIVERSITY LUCKNOW

CERTIFICATE

Certified that this project report “ IMAGE STEGANOGRAPHY ” is the

bonafide work of “ MOHD ARSHAD & MOHD ARSHAD KHAN ” who carried out
the project work under my supervision.

Dr. Tasneem Ahmad

Assignment Professor
Department of Computer Application
Integral University, Lucknow

2
 INTEGRAL UNIVERSITY LUCKNOW

CERTIFICATE

Certified that this report “ IMAGE STEGANOGRAPHY ” is the bonafide work of “

MOHD ARSHAD KHAN & MOHD ARSHAD ” who have successfully carried out
the project.

Mr. Mohd Faisal Dr. Mohd Faizan Farooqui

Project Coordinator Head
Department of Computer Application Department of Computer Application
Integral University, Lucknow Integral University, Lucknow

3
 DECLARATION
“ I hereby declare that this submission is my own work and that, to the best of my
knowledge and belief, it contains no material previously published or written by another
person nor material which has been accepted for the award of any other degree or
diploma of the university or other institute of higher learning, except where due
acknowledgement has been made in the text ”

Date …..................................
MOHD ARSHAD
…...................................
MOHD ARSHAD KHAN

4
 ACKNOWLEDGEMENT

It give me great pleasure to present before you my final year project report on “ IMAGE
STEGANOGRAPHY ” strictly under the guidance of “ Dr. Tasneem Ahmad ” He had
made sincere efforts to make the final year project more meaning full, complete,
compact and comprehensive. It's a great pleasure to you know that I have put my feeling
into practice.
At last we give our special thanks to our batch mates for all the valuable suggestion
without which this project could not be complete.

THANK YOU

5
 TABLE OF CONTENT

Sn.No. Topics Page No.

1. Abstract 07

2. Chapter
2.1 Introduction 08
2.2 Hardware & Software Requirement 10
2.3 Description of Software specification
2.4 Problem Identification 11
2.5 System Analysis & User Requirement 12
2.6 Feasibility Study 13
2.7 System Planning
2.8 Designing 15
2.9 Testing 18

3. Review of Previous work

4. Proposed work
4.1. Data Flow Diagram 22
4.2. Contex Diagram 24
4.3. Flow Chart
4.4. ER Diagram 25
4.5. SnapShot 26
5. Chart
5.1. Gantt Chart 35
5.2. Pert Chart 38 36

6. Conclusion & Future scope 37

7. Reference
8. Bio Data of Group Member 38

6
 Abstract:

Steganography is the art of hiding the fact that communication is taking place, by hiding
information in other information. Many different carrier file formats can be used, but
digital images are the most popular because of their frequency on the Internet. For
hiding secret information in images, there exists a large variety of steganographic
techniques some are more complex than others and all of them have respective strong
and weak points. Different applications have different requirements of the
steganography technique used. For example, some applications may require absolute
invisibility of the secret information, while others require a larger secret message to be
hidden. This paper intends to give an overview of image steganography, its uses and
techniques. It also attempts to identify the requirements of a good steganographic
algorithm and briefly reflects on which steganographic techniques are more suitable for
which applications.

7
 Introduction of the project

 As a society, humans have continually sought new and efficient ways to communicate.
Advancements of civilization introduced written language, telegraph, radio/television,
and most recently electronic mail. As more and more communication is conducted
electronically, new needs, issues, and opportunities are born. At times when we
communicate, we prefer that only the intended recipient have the ability to decipher the
contents of the communication.
 We want to keep the message secret. A common solution to this problem is the use of
steganography. While steganography masks the meaning of a communication, instances
exist where we would prefer that the entire communication process not be evident to any
observer that is, even the fact that communication is taking place is a secret. In this case,
we want to keep the communication hidden.
 Steganography is the art and science of invisible communication. This is accomplished
through hidinginformation in other information, thus hiding the existence of the
communicated information. The wordsteganography is derived from the Greek words
“stegos” meaning “cover” and “grafia” meaning “writing” defining it as “covered
writing”. In image steganography the information is hidden exclusively in images.
 Steganography can be used to hide or cover the existence of communication. A major
drawback to encryption is that the existence of data is not hidden. Data that has been
encrypted, although unreadable, still exists as data. If given enough time, someone could
eventually decrypt the data.
Steganography can be classified into various types, depending upon the cover medium
used. Cover medium may be text, image or audio or video file. Hence steganography
can be said to occur in three major types:
 Text Steganography
 Image Steganography
 Audio Steganography
 Vedio Steganograph
8
Now here I am going to discuss the type of the steganography on which my project is
based that is IMAGE STEGANOGRAPHY:
Image is the most common type of carrier used for steganography. The message in
encrypted form or in the original form is embedded as the secret message to be sent into
a graphic file. This results in the production of what is called a stego-image. Additional
secret data may be needed in the hiding process e.g. a stegokey. The stego-image is then
transmitted to the recipient. The recipient extracts the message from the carrier image.
The message can only be extracted if there is a shared secret between the sender and the
recipient.
Image steganography is about exploiting the limited powers of the human visual system
(HVS). Within reason, any plain text, cipher text, other images, or anything that can be
embedded in a bit stream can be hidden in an Image steganography has come quite far in
recent years with the development of fast, powerful graphical computers.
A image is composed of finite number of elements each of which has a particular
location and value (gray scale). The processing of these digital images by means of a
digital Computer is referred as digital image processing. Images are used for
steganography in following ways.

9
 Hardware and Software requirements

Hardware requirements

Sr.No Components Specification

1 Processor 2.6 GHz

2 Memory 512MB or higher

3 Hard disk 15GB or higher

Software specification

In the following table software specification given below .These are requirement in
our project.

Sr.No Components Specification

1 OS Windows XP or Higher version

2 Programming language JAVA

3 IDE My Eclipse 8.5

4 Documentation MSOffice 2007

10
Problem identification
Identification of need

The need of this project is to resolve the security problem occurring in the existing
system and provide a visual solution. The key goal behind developing this software is to
provide an easy and fast method for the information security.
Following point are given below.
 Steganography is very useful in the field of information technology because it
used for the purpose of information or data security.
 The objective of image steganography is providing availability, confidentiality
and integrity.
 It keeps data integrity means there will be no modification in content of
information during communication.
 Need in business area to secure confidential data.
 The need of this system is to provide authentication, secrecy and privacy to the
data.

11
 System Analysis User Requirement

Steganography is the technique of hiding secret or sensitive information. Steganography

is often confused with cryptography because the two are similar in the way that they
both are used to protect important information. The difference between two is that
steganography involves hiding information but cryptography cannot concern with the
hiding information so it appears that no information is hidden. In steganography if a
person or persons views the object that the information is hidden inside of he or she will
have no idea that there is any hidden information, therefore the person will not attempt
to decrypt the information.
Some objectives of image steganography are given below.
 Steganography is very useful in the field of information technology because it used for
the purpose of information or data security.
 The objective of image steganography is providing availability, confidentiality and
integrity.
 It keeps data integrity means there will be no modification in content of information
during communication.

12
 Feasibility study
All projects are feasible given unlimited resources and infinite time.....! Unfortunately,
the development of computer based system is more likely to be plagued by a scarcity of
resources and difficult delivery dates. It is both necessary and prudent to evaluate the
feasibility of the project at the earliest possible time. Months or years of effort, Money
loss and untold professional embarrassment can be averted I few better understand the
project at its study time.
This type of study determines if an application can and should be developed. Once it has
been determining that, application is feasible. After that analyst can go ahead and
prepares the project specification, which finalizes project requirements. Feasibility
studies are undertaken within tight time constraints.

1. Technical Feasibility

2. Operational Feasibility

3. Economic Feasibility

4. Legal Feasibility

Technical Feasibility

As we know the technical feasibility is concerned with specifying equipment and

software that will successfully satisfy the user requirement. The technical needs of the
system may vary considerably, but might include:

 The facility to produce outputs of advertisements, shopping and mailing in a given

time for ease of use.

 Response time under certain condition is minimal.

 Ability to process a certain volume of transaction at a particular speed.

 Facility to communicate data to distinct location. In examining the technical

feasibility, configuration of the system is given more importance than the actual make of
hardware. The configuration should give the complete picture about the system’s
requirements- how many workstations are required,
how these units are interconnected so that they could operate and communicate
smoothly. 13
Operational Feasibility

Proposed projects are beneficial only if they can be turned into information system that
will meet the financial management requirements of the business/organization. This test
of feasibility asks if the system will work when it developed and installed. Are there
major barriers to implementation?
Some of the important questions that are useful to test the operational feasibility of a
project are given below:

 Is there sufficient support for the project from the implementation? From user? If the
present 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 current business methods acceptable to the user? If they are not, user may
welcome a change that will bring about a more operational and useful system

 Have the user been involved in the planning and development of the Project? If they
are involved at the earliest stage of project development, the chances of resistance can
be possibly reduced.

 Will the proposed system cause harm? Will it produce poorer result in any case or
area?

 Will the performance of staff member fall down after implementation? Issue that

 Appears to be quite minor at the early stage can grow into major problem after
Implementation.

Economical Feasibility
Economic analysis is the most frequently used technique for evaluating the effectiveness
of the proposed system. More commonly known as cost/benefits analysis, the procedure
is to determine the benefits and savings that are expected from the purposed system and
compared with costs.If benefits outweigh cost, a decision is taken to design and
implement the system.Otherwise, further justification or alternative of the proposed
system will have to bemade if it has a chance of being approved. This is an ongoing
effort that improves inaccuracy at each phase of the system life cycle. The analysis part
also clears the doubt ofeconomic problems which could be possible in developing the
system. As alreadymentioned that the company has to just pay the developed software
cost and not otherinvestment is needed at the time of implementation of the new system
as the preliminaryrequirements already exist in the company. 14
Legal Feasibility
In the legal feasibility is necessary to check that the software we are going to develop is
legally correct which means that the ideas which we have taken for the proposed system
will be legally implemented or not so , it is also an important step in feasibility study.

SYSTEM DESIGN
Systems design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. One could see it as
the application of systems theory to product development. There is some overlap with
the disciplines of systems analysis, systems architecture and systems engineering. If the
broader topic of product development "blends the perspective of marketing, design, and
manufacturing into a single approach to product development," then design is the act of
taking the marketing information and creating the design of the product to be
manufactured. Systems design is therefore the process of defining and developing
systems to satisfy specified requirements of the user. Until the 1990s systems design had
a crucial and respected role in the data processing industry. In the 1990s standardization
of hardware and software resulted in the ability to build modular systems. The
increasing importance of software running on generic platforms has enhanced the
discipline of software engineering. Object-oriented analysis and design methods are
becoming the most widely used methods for computer systems design. The UML has
become the standard language in objectoriented analysis and design. It is widely used for
modeling software systems and is increasingly used for high designing non-software
systems and organizations.

Hide Module
This module is used to hide message into the image. No one can see that message as file.
This module requires any type of image and message and gives the only one image file
at destination. Here, it uses two data and then proceeds with a certain process of hiding
the message. It can use different types of image like JPEG, png, gif and other format but
image height and width are according to text length and the texts are according to the
image capacity.
Here, it loads the encrypted message and the image and then hide the encrypted message
into the image.

15
Seek Module
This module is used to get hidden information from the image file. It take the encrypted
message image file as an input ,and give two files after extraction; one is an image file
and another is the message file that is hidden into the image. Then, the loaded image is
used to retrieve the encrypted message so that the second user can decrypt it.

Encryption Module
Encryption module takes message and then using certain key and algorithm it encrypt
the message. Encryption module takes plain text as an input and converts it into the
cipher text.

Decryption Module
Decryption module take encrypted message and using certain process decrypt the
message it means that message can change its original form.

Process logic of each module

Encryption Module
Step1. This module receives message detail from user1.
Step2. This module receives encryption technique detail and decryption technique detail
from user1.
Step3.This module provides encrypted message file info to hide module.
Hide Module
Step1. This module receives encrypted message file info from encrypted module.
Step2. This module receives image file from user1.
Step3. This module provides image info, message info to user2.
Step4. This module provides encryption technique info and decryption technique info to
user2.
16
Seek Module
Step1. This module receives image detail, message detail, from user2.
Step2. This module receives encryption technique detail from user2.
Step3. These modules also receive key information.
Step4.This module provides encrypted message file info to decryption module.

Decryption Module
Step1. This module receives encrypted message file info from seek module.
Step2. This module provides decryption technique info to user2.

17
 Testing
Software testing is an investigation conducted to provide stakeholders with information
about the quality of the product or service under test. Software testing can also provide
an objective, independent view of the software to allow the business to appreciate and
understand the risks of software implementation. Test techniques include, but are not
limited to, the process of executing a program or application with the intent of finding
software bugs (errors or other defects). Software testing can be stated as the process of
validating and verifying that a software program/application/product:
1. meets the requirements that guided its design and development;
2. works as expected; and
3. can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be implemented at any
time in the development process. However, most of the test effort traditionally occurs
after the requirements have been defined and the coding process has been completed
having been shown that fixing a bug is less expensive when found earlier in the
development process. Although in the Agile approaches most of the test effort is,
conversely, on-going. As such, the methodology of the test is governed by the software
development methodology adopted.
Different software development models will focus the test effort at different points in the
development process. Newer development models, such as Agile, often employ test
driven development and place an increased portion of the testing in the hands of the
developer, before it reaches a formal team of testers. In a more traditional model, most
of the test execution occurs after the requirements have been defined and the coding
process has been completed. Testing can never completely identify all the defects within
software. Instead, it furnishes a criticism or comparison that compares the state and
behavior of the product against oracles—principles or mechanisms by which someone
might recognize a problem. These oracles may include (but are not limited to)
specifications, contracts,[3] comparable products, past versions of the same product,
inferences about intended or expected purpose, user or customer expectations, relevant
standards, applicable laws, or other criteria. Every software product has a target
audience. For example, the audience for video game software is completely different
from banking software. Therefore, when an organization develops or otherwise invests
in a software product, it can assess whether the software product will be acceptable to its
end users, its target audience, its purchasers, and other stakeholders. Software testing is
the process of attempting to make this assessment.

18
Types of Testing

Testing Techniques Used we will continuously test our project to insure thet it is fully
functional. In order to perform testing test cases are designed with the intent of finding
the errors in the project and help in removing those errors. Testing begins at the module
level and is conducted systmatically . It is generally conducted by independent test
groups or third party. Testing is done in our project remort controlling PC with help of
black box testing that exrcise all the functional requirement of the project test cases are
designed using this approaches by providing set of inoput conditions to get the expected
output.

Black Box Testing

Black-box testing treats the software as a "black box"—without any knowledge of

internal implementation. Black-box testing methods include: equivalence partitioning,
boundary value analysis, all-pairs testing, fuzz testing, model-based testing, exploratory
testing and specification-based testing.

 Specification-based testing: Specification-based testing aims to test the functionality

of software according to the applicable requirements. Thus, the tester inputs data into,
and only sees the output from, the test object. This level of testing usually requires
thorough test cases to be provided to the tester, who then can simply verify that for a
given input, the output value (or behavior), either "is" or "is not" the same as the
expected value specified in the test case. Specification-based testing is necessary, but it
is insufficient to guard against certain risks.

 Advantages and disadvantages: The black-box tester has no "bonds" with the code,
and a tester's perception is very simple: a code must have bugs. Using the principle,
"Ask and you shall receive," black-box testers find bugs where programmers do not. On
the other hand, black-box testing has been said to be "like a walk in a dark labyrinth
without a flashlight," because the tester doesn't know how the software being tested was
actually constructed. As a result, there are situations when (1) a tester writes many test
cases to check something that could have been tested by only one test case, and/or (2)
some parts of the back-end are not tested at all. Therefore, black-box testing has the
advantage of "an unaffiliated opinion", on the one hand, and the disadvantage of "blind
exploring", on the other

19
White Box Testing

White-box testing is when the tester has access to the internal data structures and
algorithms including the code that implements these.
Types of white-box testing
The following types of white-box testing exist:

 API testing (application programming interface) - testing of the application using

public and private APIs

 Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test
designer can create tests to cause all statements in the program to be executed at least
once)

 Fault injection methods - improving the coverage of a test by introducing faults to test
code paths

 Mutation testing methods

 Static testing - All types

Test coverage
White-box testing methods can also be used to evaluate the completeness of a test suite
that was created with black-box testing methods. This allows the software team to
examine parts of a system that are rarely tested and ensures that the most important
function points have been tested.
Two common forms of code coverage are:

 Function coverage, which reports on functions executed

 Statement coverage, which reports on the number of lines executed to

complete the test
They both return a code coverage metric, measured as a percentage.

Functional Testing

 Functional testing refers to activities that verify a specific action or function of the
code. These are usually found in the code requirements documentation, although some
development methodologies work from use cases or user stories. Functional tests tend to
answer the question of "can the user do this" or "does this particular feature work."
20
 • Non-functional testing refers to aspects of the software that may not be related to
a specific function or user action, such as scalability or other performance,
behavior under certain constraints, or security. Testing will determine the flake
point, the point at which extremes of scalability or performance leads to unstable
execution. Non-functional requirements tend to be those that reflect the quality of
the product, particularly in the context of the suitability perspective of its users.

System Testing

 System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system's compliance with its specified requirements. System
testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.

 As a rule, system testing takes, as its input, all of the "integrated" software components
that have successfully passed integration testing and also the software system itself
integrated with any applicable hardware system(s). The purpose of integration testing is
to detect any inconsistencies between the software units that are integrated together
(called assemblages) or between any of the assemblages and the hardware. System
testing is a more limited type of testing; it seeks to detect defects both within the
"interassemblages" and also within the system as a whole.

Various level Of Testing

Before implementation the system is tested at two levels:

Level 1
Level 2

Level 1 Testing (Alpha Testing)

Alpha testing is simulated or actual operational testing by potential users/customers or
an independent test team at the developers' site. Alpha testing is often employed for
offtheshelf software as a form of internal acceptance testing, before the software goes to
beta testing.

Level 2 Testing (Beta testing)

Beta testing comes after alpha testing and can be considered a form of external user
acceptance testing. Versions of the software, known as beta versions, are released to a
limited audience outside of the programming team. The software is released to groups of
people so that further testing can ensure the product has few faults or bugs. Sometimes,
beta versions are made available to the open public to increase the feedback field to a
maximal number of future users. 21
DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data
through an nformation system, modelling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be
elaborated.DFDs can also be used for the visualization of data processing (structured
design). A DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be stored. It
does not show information about the timing of process or information about whether
processes will operate in sequence or in parallel (which is shown on a flowchart). Data
flow diagrams were proposed by Larry Constantine, the original developer of structured
design, based on Martin and Estrin's "Data Flow Graph" model of computation. Starting
in the 1970s, data flow diagrams (DFD) became a popular way to visualize the major
steps and data involved in software system processes. DFDs were usually used to show
data flows in a computer system, although they could in theory be applied to business
process modelling. DFD were useful to document the major data flows or to explore a
new high-level design in terms of data flow.

TYPES OF DFD:

There are two types of DFDs, both of which support a top-down approach to systems
analysis, whereby analysts begin by developing a general understanding of the system
and gradually break components out into greater detail:

 Logical data flow diagrams - are implementation-independent and describe the

system, rather than how activities are accomplished.

Physical data flow diagrams - are implementation-dependent and describe the actual
entities (devices, department, people, etc.) involved in the current system. DFDs can
also be grouped together to represent a sub-system of the system being analyzed.

COMPONENTS OF DFD :

Data flow Diagram shows the flow of data. It is generally made of symbols given
below :

(1) A square shows the Entity

(2) A Circle shows the Process: -

(3) An open Ended Rectangle shows the data store : -

22
(4) An arrow shows the data flow :-

 The DFD can be up to several levels. The 0 level DFD states the flow of data in the
system as seen from the outward in each module.

 The first level DFD show more detail, about the single process of the 0 level DFD.

 The second level DFD can show even more details and so on.

Message detail, Key detail

Encryption detail
Encryption

Message info, Encryption

info, Key info

Hide Hidden message Image

Hidden Message Image

USER1 USER2
Encrypted message
detail, Image detail Seek Encrypted
message

Encrypted message,
Decryption Key detail

Decryption

Decrypted message

23
Contex Diagram

Message info, Image

Message detail, Image Info, Encryption info,
detail, Encryption detail, Image Decryption Info
USER Decryption detail
Steganography User

24
ERD(Entity Relationship Diagram)
Definition:
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to represent
entities. Diamonds are normally used to represent relationships and ovals are used to
represent attributes.

Entity Relationship (ER) diagram:

This diagramming technique is used to visually present a database schema or data model
and was original proposed by Chen in the 1970s. There are many different data
modeling notations; some are very similar to UML class diagrams (with the exception of
operations). However, the notation the used here is slightly different, as proposed by
Elmasri, et al. The database schema for this system is shown in figure. The table object
has been left out of the diagram because the table management feature set had been
dropped from the requirements before this stage of the design process.
Some important database design decisions are as follows:
To store the total price of an order with the order rather than calculating it on the fly
when looking at past orders. This is because the price of menu items could change at any
time, so the total price at the time of ordering must be stored so that the total price is not
incorrectly calculated in future. Similar to the previous point, the order receipt is stored
as a hard-copy and not regenerated when reviewing past orders because things such as
the restaurant name or VAT percentage are subject to change. Receipts stored need to be
exactly the same as the customer copy in case of dispute.

25
 Snapshot

Activity 1.
In this activity we are showing how to load the message.

26
Activity 2.

In this activity we are showing the location of the message.

27
Activity 3.

In this activity we are showing the message .

28
Activity 4.

In this activity we are encrypting the message and after that there is an key
generate.

29
Activity 5.

In this activity we are showing the encrypted message.

30
Activity 6.

In this activity we are loading the image and showing the location of that.

31
Activity 7.

In this activity we are showing loaded image and encrypted messag.

32
Activity 8.

In this activity we are decrypting the message with the help of previous key.

33
Activity 9.

In this activity we are showing the actual message.

34
 Chart.
Gantt chart.

Following Gantt chart given below:

Task Task Jul- Aug- Nov- Nov- Jan- Feb- Mar-

No. Aug Nov Dec Dec Feb Mar April
1 Requirement
Analysis
2 Design

3 Coding

4 Testing

5 Documentatio
n
6 Implementati
on
7 Final Review

35
Pert Chart
A PERT chart is a project management tools used to schedule, organize, and coordinate
tasks within a project. PERT stands for Program Evaluation Review Technique. A
PERT chart presents a graphic illustration of a project as network diagram consisting of
numbered nodes(either circles or rectangles) representing events, or milestones in the
project linked by labeled vectors (directional lines) representing tasks in the project. The
direction of the arrows on the lines indicates the sequence of tasks.

Programming Beta Testing

Alpha Testing
SRS And Design

3 5 8 10

10 15 30 10 10
1 2
4 6 7 9 11

Buy Hardware Writing

Manuals User Test
User
Requirement And
Analysis Installation Training

36
Conclusion

Steganography is a really interesting subject and outside of the mainstream cryptography

and system administration that most of us deal with day after day. Steganography can be
used for hidden communication. We have explored the limits of steganography theory
and practice. We printed out the enhancement of the image steganography system using
LSB approach to provide a means of secure communication. A stego-key has been
applied to the system during embedment of the message into the cover image. This
steganography application software provided for the purpose to how to use any type of
image formats to hiding any type of files inside their. The master work of this
application is in supporting any type of pictures without need to convert to bitmap, and
lower limitation on file size to hide, because of using maximum memory space in
pictures to hide the file. Since ancient times, man has found a desire in the ability to
communicate covertly. The recent explosion of research in watermarking to protect
intellectual property is evidence that steganography is not just limited to military or
espionage applications. Steganography, like cryptography, will play an increasing role in
the future of secure communication in the “digital world”.

37
Bio Data of group member

Bio Data of Group Member 1:

MOHD ARSHAD
Mob : 7860600875
mo.arshad0786@gmail.com
Moh - Western Dixitana
Gola Gokarannath 262802
Distt – Lakhim pur Kheri

Qualification
Bachelor of Computer Application (Integral University Lucknow 2017 ) - 61.6
High School (UP Board 2012)– 61.3%
Intemediat (UP Board 2014) – 58.9%

Mini Project
Online Bus Ticketing Management
(With Visual Basic as front end and MS Access as back end)
Pharmacy Aoutomation
(with Core Java and MySql)

Technical Skills
Operating System : DOS,Windows 2000,Windows XP,Windows 7,Windows 8
and 8.1,Windows 10,Learning Unix/Linux
Application Software : Office 2003,Office XP,Office 2007,Open
Office,LibreOffice4.2,Adob Photoshop,Coral Draw,Photoshop CS4
Programming Skills : C Language,HTML,CSS,core Java,MySql,Learning
JavaScript and Advance Java

Personal Information:
A young, determined hard and smart working person. I believe in task based
roles and complete ownership of work.
Languages Known:English, Hindi,Urdu
Hobbies:I love reading IT related books, playing Chess and Cricket,listening
music, surfing Internet,self-learning.

Other Information
Area of Interest:Software Development, Programming,Coding, App
Development,Technical Support, Support Engineer, Client service.

38
Personal profile
Father's Name : Mr. Late Athar Ali
Date of Brith : 27-09-1996

Declaration
I hereby declare that the details furnished above are true and correct to the best of my
knowledge and belief.

Date:
Place: Lucknow (Mohd Arshad)

39
Bio Data of Group Member 2:
MOHD ARSHAD KHAN
Mob : 9838605023
arshad05786@gmail.com
Vill -Gazi Pur
Post – Goura Chowki
Gonda

Qualification
Bachelor of Computer Application (Integral University Lucknow 2017 ) -68.25
High School (UP Board 2011)– 65.16%
Intemediat (UP Board 2013) – 58.80%

Mini Project
Hospital Management System
(With Visual Basic as front end and MS Access as back end)

Techmical Skills
Operating System : DOS,Windows 2000,Windows XP,Windows 7,Windows 8
and 8.1,Windows 10,Learning Unix/Linux
Application Software : Office 2003,Office XP,Office 2007,Open
Office,LibreOffice 4.2,Adob Photoshop,Coral Draw,Photoshop CS4

Programming Skills : C Language,HTML,CSS,core Java,MySql,Learning JavaScript

and Advance Java

Personal Information:
A young, determined hard and smart working person. I believe in task based
roles and complete ownership of work.
Languages Known : English, Hindi,Urdu
Hobbies :I love reading IT related books, playing Chess and Cricket,listening
music,surfing Internet, self-learning.

Other Information
Area of Interest:Software Development, Programming,Coding, App
Development,Technical Support, Support Engineer, Client service.

Personal profile
Father's Name : Mr. Mohd Naeem Khan
Date of Brith : 15-08-1995
Declaration
I hereby declare that the details furnished above are true and correct to the best of my
knowledge and belief.
Date:
Place: Lucknow (Mohd Arshad Khan)

40