THERMODYNAMIC EVALUATION OF ORGANIC RANKINE CYCLE

ADissertation Work

Submitted as Major Project in Partial fulfillment for the award of Graduate Degree in Bachelor of Engineering in Information Technology.

Submitted to

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYABHOPAL (M.P)

Under the Guidance of Submitted ByMr. Prateek Buchke Himanshu agrawal (0105it071037) Ms. Fehreen Hasan Rizwan Qureshi(0105it071078)

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-1

(Department of Information Technology)

NOV-DEC – 2010

logo oist

CERTIFICATE

This is to certify that the project entitled “Image Steganography” being submitted

by Himanshu Agrawal, Rizwan Qureshi students of 7th Semester, Degree

in Information Technology have done their work as MAJOR PROJECT for Partial fulfillment of

the degree from RGPV, Bhopal (M.P.) is a record of bonafide work out by them under our

supervision.

Mr. Prateek Buchke Prof. Sreeja Nair Ms. Fehreen Hasan H.O.D.

Department Of (Information Technology) Information Technology

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-2

ACKNOWLEDGEMENT

I take the opportunity to express my cordial gratitude and deep sense of indebtedness to our guide Mr. Prateek Buchke and Ms. Fehreen Hasan for the valuable guidance and inspiration throughout the project duration. We feel thankful to them for his innovative ideas, which led to successful completion of this project work. We feel proud and fortune to work under such an

outstanding mentor in the field of “Image Steganography” They have always welcomed our problem and helped us to clear our doubt. We will always be grateful to them for providing us moral support and sufficient time.

We owe sincere thanks to Dr. K. Chaudhary, Director OIST and Prof. N. K. Mittal, Principal OIST, who helped us duly in time during our project work in the Department.

At the same time, We would like to thank Prof. Sreeja Nair (HOD, IT) and all other faculty members and all non-teaching staff of department of Information Technology for their valuable co-operation.

Himanshu Agrawal (0105IT071037)

Rizwan Qureshi(0105IT071078)

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-3

APPROVAL CERTIFICATE

This is to certify that the project entitled “Image Steganography” being submitted by

Himanshu Agrawal, Rizwan Qureshi students of 7th semester, Degree in Information

Technology have done their work as MAJOR PROJECT for Partial fulfillment of the degree

from RGPV, Bhopal (M.P.).

Mr. Prateek Buchke

Ms. Fehreen Hasan

Guide

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-4

(Department of Information Technology)

TABLE OF CONTENT

ABSTRACTLIST OF FIGURESLIST OF GRAPHLIST OF TABLE

CHAPTER 1: INTRODUCTION

1.1 Overview

1.2 Objective & Scope of project

1.3 Organization of Report

1.4 Existing System

CHAPTER 2: BACKGROUND & LITERATURE SURVEY

2.1 SRS

2.2 Feasibility report

2.2.1 Innovativeness & Usefulness

2.3 Proposed Model

CHAPTER 3: PROCESS MODEL

3.1 SDLC

3.2 Proposed Process Mode

3.3 Project Plan

3.4 Project Estimate & Scheduling

CHAPTER 4: DESIGN

4.1 Use case Diagram

4.2 Sequence Diagram

4.3 Activity Diagram

4.4 State Chart Diagram

4.5 Class Diagram

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-5

4.6 ER Diagram

4.7 DFD

4.8 Flow Chart

4.9 Algorithm

CHAPTER 5: TECHNICAL DETAILS

5.1 SOFTWARE Specification

5.2 HARDWARE Specification

CHAPTER 6: FUTURE WORKREFERENCEAPPENDIX

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-6

ABSTRACT

Steganography is the process of hiding a secret message within a

larger one in such a way that someone can not know the presence or contents

of the hidden message. The purpose of Steganography is to maintain secret

Communication between two parties. This paper will show how Steganography

is used in a modern context while providing a practical understanding of what

Steganography is and how to accomplish it

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-7

CHAPTER 1INTRODUCTION

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-8

There are so many methods to transferring the data like encryption or other methods. Generally we are using RSA technique for transfer the data from one place to another place by using two key's but this technique is not so secure because an export programmer can break these key's and decrypt the encrypted data easily so to overcome this problem steganography will be the best solution.In steganography we transfer data with the images which is very much secure way to transfer data. We use this methods where data is very much secrete and confidential like militaries data and banking data etc.

1.1 OVERVIEW:

Since the rise of the Internet one of the most important factors of information technology and communication has been the security of information. Cryptography was created as a technique for securing the secrecy of communication and many different methods have been developed to encrypt and decrypt data in order to keep

the message secret. Unfortunately it is sometimes not enough to keep the contents of a message secret, it may also be necessary to keep the existence of the message secret. The technique used to implement this, is called Steganography.

The word steganography 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.

The basic structure of Steganography is made up of three components: the

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-9

“carrier”, the message, and the key1. The carrier can be a painting, a digital image, an

mp3, even a TCP/IP packet among other things. It is the object that will ‘carry’ the

hidden message. A key is used to decode/decipher/discover the hidden message.

This can be anything from a password, a pattern, a black-light, or even lemon juice.

In steganography, we study techniques to achieve secret communication between two parties that are interested in hiding not only the content of a secret message but also the act of communicating it. To this aim, steganography algorithms (“stego algorithms”) embed the secret information into different types of “natural” cover data like sound, images, or video. The resulting altered data is referred to as stego-data and it must be perceptually indistinguishable from its natural cover. On the other hand, stego-analysis seeks to analyze (possibly altered) cover data to decide whether a message has been embedded in it or not. Thus, the problem can be seen as one of classification into two classes, namely, natural and stego-data.

Steganography differs from cryptography in the sense that where cryptography focuses on keeping the contents of a message secret, steganography focuses on keeping the existence of a message secret . Steganography and cryptography are both ways to protect information from unwanted parties but neither technology alone is perfect and can be compromised. Once the presence of hidden information is revealed or even suspected, the purpose of steganography is partly defeated . The strength of steganography can thus be amplified by combining it with cryptography.in this project we hide text and image both in image.

1.2 OBJECTIVE:

This project comprehends the following objectives:

(i) To produce security tool based on steganographic techniques.

(ii) To explore techniques of hiding data and image using steganography.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-10

SCOPE:The scope of the project as follow:

(i) Implementation of steganographic tools for hiding information includes text and image files .

(ii) in this we encrypt a very secret text message and also we encrypt a secret image.

ORGANIZATION OF REPORT:

our project is a stand alone application. This application is provide user to encrypt the text or image. This is provide security of our secret text and image. In this user first upload a image and then scan image and then write a text and encrypt this text with image. In this application we can also encrypt an image with in a image.

The Software Development Life Cycle (SDLC) is used to facilitate the

development of large software product in a systematic well-defined and cost

effective way. An information system goes to a series of phases from

conception to implementation this process called a SDLC. A Software

process model is an abstract representation of a software process. It is a

software development strategy that encompasses the process, methods and

tool layers plus the three generic phases viz. definition phase, development

phase and support phase. A process model is chosen based on the nature of

the project and application, the methods and tools to be used, and the control

and deliverables that are required.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-11

CHAPTER 2BACKGROUND & LITERATURE

SURVEY

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-12

2.1 Software requirement Specification

A requirements specification for a software system - is a complete

description of the behavior of a system to be developed. It includes a set

of use cases that describe all the interactions the users will have with the

software. Use cases are also known as functional requirements. In

addition to use cases, the SRS also contains non-functional (or

supplementary) requirements. Non-functional requirements are

requirements which impose constraints on the design or implementation

(such as performance engineering requirements, quality standards, or

design constraints).

Requirements Determination

Requirements determination is one of the most complicated and

prolonged part of developing a new system. It is the combination of

gathering and analyzing information about the existing system. The

primary objectives of the requirements determination are to understand

the existing policies, identify the problems of the current system and

collecting required data to develop a model of the new system.

The deliverables for requirements determination that I have

used are interview transcripts, business mission and strategy statements,

job descriptions of the employees, existing written documents and the

results of Joint Application Design (JAD) sessions.

The following sections will introduce the numerous

requirements of the system from the point of view of different users and

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-13

will introduce a number of decisions that have been made regarding

implementation. These sections also attempt to somewhat describe the

role of each user group in the system, discussing their individual roles

through the functions they can perform.

2.1.1.User Interface :-

The user interface for this system will have to be simple and clear. Most

importantly, the leave format easy to read, easy to understand and

accessible. The color scheme should be appropriate to provide

familiarity with the application and there should be no contrast issues.

2.2 Feasibility Report

Types of Feasibility

Economic Feasibility

Economic analysis is most frequently used for evaluation of the

effectiveness of the system. More commonly knows as cost/benefit

analysis the procedure is to determine the benefit and saving that are

expected from a system and compare them with costs, decisions is

made to design and implement the system. This part of feasibility

study gives the top management the economic justification for the

new system. This is an important input to the management the

management, because very often the top management does not like to

get confounded by the various technicalities that bound to be

associated with a project of this kind. A simple economic analysis

that gives the actual comparison of costs and benefits is much more

meaningful in such cases. In the system, the organization is most

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-14

satisfied by economic feasibility. Because, if the organization

implements this system, it need not require any additional hardware

resources as well as it will be saving lot of time.

Technical Feasibility :- Technical feasibility centers on the existing

manual system of the leave management process and to what extent it

can support the system. According to feasibility analysis procedure

the technical feasibility of the system is analyzed and the technical

requirements such as software facilities, procedure, inputs are

identified. It is also one of the important phases of the system

development activities.

The system offers greater levels of user friendliness combined

with greater processing speed. Therefore, the cost of maintenance can

be reduced. Since, processing speed is very high and the work is

reduced in the maintenance Point of view management convinces that

the project is operationally feasible.

Behavior Feasibility

People are inherently resistant to change and computer has been

known to facilitate changes. An estimate should be made of how

strong the user is likely to move towards the development of

computerized system. These are various levels of users in order to

ensure proper authentication and authorization and security of

sensitive data of the organization.

2.2.1 Innovativeness & Usefulness

Simple to set up, requires minimal user training and fully IT

supported.

Easy data uploads.

We are provide the security of our secret image and text data.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-15

Sender encrypt the text in image and send it and then receiver receive

this encrypted image and decrypt it read the secret message.

2.3 Proposed Model

2.3.1.FUNCTIONAL REQUIREMENTS (OR PRIMARY

FUNCTIONS)

Image: the main task ofsteganography is image. In this we firstly pick a

image and upload this image.

Text: this is an our secret message in a text form.

Encryption: in this we encrypt our text message into in image using

encryption.

Decryption: in this receiver decrypt the encrypted msg and read the

secret message.

2.3.2.NON-FUNTIONAL REQUIREMENTS (OR

SECONDARY ):

MORE EASY AND QUICK MANAGEMENT:

The data is stored at sight place and security firewalls can be

provided so that its management is easy.

PROJECT OBJECTIVE

This project is helpful to provide security of our secret image and text through image steganography. In this user pick a image and edit a text and

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-16

then encrypt the text in a image and finally when this image is encrypted then user can send this encrypted image and then receiver receive this and decrypt this image and read a secret message

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-17

CHAPTER 3PROCESS MODEL

3.1 SDLC (Software Development Life Cycle)

The SDLC (Software Development Life Cycle) is the entire process of

formal, logical steps taken to develop a software product. The

SDLC is basically the part of process in which coding/programming is

applied to the problem being solved by the existing or planned

application.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-18

A software development life cycle is a structure imposed on

the development of a software product. Similar terms include software

life cycle and software process. There are several models for such

processes, each describing approaches to a variety of tasks or

activities that take place during the process. Some people consider a

lifecycle model a more general term and a software development

process a more specific term. For example, we use for our software

development processes, the spiral lifecycle model.

There are several Software Development models, which are

Waterfall Model

Spiral Model

Concurrent development model

Component-based development model

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-19

Iterative model

Incremental model

Agile development model

3.1.1 SDLC Stages

The five stages of the SDLC are designed to build on one another,

taking the outputs from the previous stage, adding additional effort,

and producing results that leverage the previous effort and are directly

traceable to the previous stages.

This top-down approach is intended to result in a quality product that

satisfies the original intentions of the customer.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-20

Too many software development efforts go awry when the

development team and customer personnel get caught up in the

possibilities of automation. Instead of focusing on high priority

features, the team can become mired in a sea of “nice to have” features

that are not essential to solve the problem, but in themselves are highly

attractive. This is the root cause of a large percentage of failed and/or

abandoned development efforts, and is the primary reason the

development team utilizes the Waterfall SDLC.

3.1.1.1 Requirements Stage

The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements. These requirements define the major functions of the intended application, define operational data areas and reference data areas, and define the initial data entities. Major functions include critical processes to be managed, as well as mission critical inputs,

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-21

outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities. Each of these definitions is termed a Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a requirement title and textual description.

These requirements are fully described in the primary deliverables for this

stage: the Requirements Document and the Requirements Traceability

Matrix (RTM). the requirements document contains complete descriptions of

each requirement, including diagrams and references to external documents

as necessary. Note that detailed listings of database tables and fields are not

included in the requirements document. The title of each requirement is also

placed into the first version of the RTM, along with the title of each goal

from the project plan.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-22

The purpose of the RTM is to show that the product components

developed during each stage of the software development lifecycle

are formally connected to the components developed in prior stages.

In the requirements stage, the RTM consists of a list of high-level

requirements, or goals, by title, with a listing of associated

requirements for each goal, listed by requirement title. In this

hierarchical listing, the RTM shows that each requirement developed

during this stage is formally linked to a specific product goal. In this

format, each requirement can be traced to a specific product goal,

hence the term requirements traceability. The outputs of the

requirements definition stage include the requirements document, the

RTM, and an updated project plan.

3.1.1.2 Design Stage

The design stage takes as its initial input the requirements identified

in the approved requirements document. For each requirement, a set

of one or more design elements will be produced as a result of

interviews, workshops, and/or prototype efforts. Design elements

describe the desired software features in detail, and generally include

functional hierarchy diagrams, screen layout diagrams, tables of

business rules, business process diagrams, pseudocode, and a

complete entity-relationship diagram with a full data dictionary.

These design elements are intended to describe the software in

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-23

sufficient detail that skilled programmers may develop the software

with minimal additional input.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-24

When the design document is finalized and accepted, the RTM is updated to show that each design element is formally associated with a specific requirement. The outputs of the design stage are the design document, an updated RTM, and an updated project plan

3.1.1.3 Implementation Stage

The implementation stage takes as its primary input the design elements

described in the approved design document. For each design element, a set of

one or more software artifacts will be produced. Software artifacts include

but are not limited to menus, dialogs, data management forms, data reporting

formats, and specialized procedures and functions.Appropriate test cases will

be developed for each set of functionally related software artifacts, and an

online help system will be developed to guide users in their interactions with

the software.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-25

The RTM will be updated to show that each developed artifact is

linked to a specific design element, and that each developed artifact

has one or more corresponding test case items. At this point, the

RTM is in its final configuration. The outputs of the development

stage include a fully functional set of software that satisfies the

requirements and design elements previously documented, an online

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-26

help system that describes the operation of the software, an

implementation map that identifies the primary code entry points for

all major system functions, a test plan that describes the test cases to

be used to validate the correctness and completeness of the software,

an updated RTM, and an updated project plan.

3.1.1.4 Verification / Testing Stage

During the verification and test stage, the software artifacts, online

help, and test data are migrated from the development environment to

a separate test environment. At this point, all test cases are run to

verify the correctness and completeness of the software. Successful

execution of the test suite confirms a robust and complete migration

capability.

During this stage, reference data is finalized for production use and

production users are identified and linked to their appropriate roles.

The final reference data(or links to reference data source files) and

production user list are compiled into the Production Initiation Plan.

The outputs of the verification and test stage include an integrated set

of software, an online help system, an implementation map, a

production initiation plan that describes reference data and

production users, an acceptance plan which contains the final suite of

test cases, and an updated project plan.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-27

3.1.1.5. Maintenance Stage

Maintaining and enhancing software to cope with newly

discovered problems or new requirements can take far more time than

the initial development of the software. It may be necessary to add

code that does not fit the original design to correct an unforeseen

problem or it may be that a customer is requesting more functionality

and code can be added to accommodate their requests. If the labor

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-28

cost of the maintenance phase exceeds 25% of the prior-phases' labor

cost, then it is likely that the overall quality of at least one prior phase

is poor. In that case, management should consider the option of

rebuilding the system (or portions) before maintenance cost is out of

control.

Software Training and Support is important in maintenance and a lot

of developers fail to realize that. It would not matter how much time

and planning a development team puts into creating software if

nobody in an organization ends up using it. People are often resistant

to change and avoid venturing into an unfamiliar area, so as a part of

the deployment phase, it is very important to have training classes for

new clients of our software.

3.2 Proposed Process Model

We have used Spiral Model for the development of employee leave

management system because this model follow iteration, it has

combined elements of both design and prototyping-in-stages, in an

effort to combine advantages of top-down and bottom-up concepts. This

model of development combines the features of the prototyping model

and the waterfall model.

The following iteration have been followed during the use of spiral

model for our system.

The system requirements are defined in as much detail as

possible. This usually involves interviewing a number of users

representing all the external or internal users and other aspects of

the existing system.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-29

A preliminary design is created for the new system. This phase is

the most important part of "Spiral Model". In this phase all

possible (and available) alternatives, which can help in

developing a cost effective project are analyzed and strategies to

use them are decided. This phase has been added specially in

order to identify and resolve all the possible risks in the project

development. If risks indicate any kind of uncertainty in

requirements, prototyping may be used to proceed with the

available data and find out possible solution in order to deal with

the potential changes in the requirements.

A first prototype of the new system is constructed from the

preliminary design. This is usually a scaled-down system, and

represents an approximation of the characteristics of the final

product

A second prototype is evolved by a fourfold procedure:

evaluating the first prototype in terms of its strengths,

weaknesses, and risks;

defining the requirements of the second prototype;

planning and designing the second prototype;

constructing and testing the second prototype.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-30

3.2.1 Advantages of Proposed Model

Estimates (i.e. budget, schedule, etc.) become more realistic as

work progresses, because important issues are discovered earlier.

It is more able to cope with the (nearly inevitable) changes that

software development generally entails.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-31

Software engineers (who can get restless with protracted design

processes) can get their hands in and start working on a project

earlier.

3.3 Project Plan

The project plan establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches

The most critical section of the project plan is a listing of high-level product

requirements, also referred to as goals. All of the software product

requirements to be developed during the requirements definition stage flow

from one or more of these goals. The minimum information for each goal

consists of a title and textual description, although additional information

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-32

and references to external documents may be included. The outputs of the

project planning stage are the configuration management plan, the quality

assurance plan, and the project plan and schedule, with a detailed listing of

scheduled activities for the upcoming Requirements stage, and highlevel

estimates of effort for the out stages.

3.4 Project Estimate & Schedule

3.4.1 Project Estimate

We have estimated our project using COst COnstructive MOdel

(COCOMO).  The model uses a basic regression formula, with

parameters that are derived from historical project data and current

project characteristics. as a model for estimating effort, cost, and

schedule for software projects. COCOMO consists of a hierarchy of

three increasingly detailed and accurate forms. The first level, Basic

COCOMO is good for quick, early, rough order of magnitude

estimates of software costs, but its accuracy is limited due to its lack

of factors to account for difference in project attributes (Cost

Drivers) .

COCOMO applies to three classes of software projects:

Organic projects - "small" teams with "good" experience

working with "less than rigid" requirements

Semi-detached projects - "medium" teams with mixed

experience working with a mix of rigid and less than rigid

requirements

Embedded projects - developed within a set of "tight"

constraints (hardware, software, operational, ...)

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-33

The basic COCOMO equations take the form

Effort Applied = ab(KLOC)bb [ man-months ]

Development Time = cb(Effort Applied)db [months]

People required = Effort Applied / Development Time [count]

The coefficients ab, bb, cb and db are given in the following table.

Software project ab bb cb db

Organic 2.4 1.05 2.5 0.38

Semi-detached 3.0 1.12 2.5 0.35

Embedded 3.6 1.20 2.5 0.32

Basic COCOMO is good for quick estimate of software costs. Here

we calculate our estimation as

Effort Applied  = ab(KLOC)bb [ man-months ]

= 2.4(5)^1.05

= 13.01 [ man-months ]

Development Time = cb(Effort Applied)db [months]

= 2.5 (2.4)^0.38

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-34

= 6.42 [months]

People required  = Effort Applied / Development Time [man]

= 13.01/6.42

= 2.02 [man]

3.4.2 Project Schedule

Our project schedule is given below :

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-35

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-36

CHAPTER 4DESIGN

4.1 Use-Case Diagram

A use case diagram in the Unified Modeling Language (UML) is a type

of behavioral diagram defined by and created from a Use-case analysis.

Its purpose is to present a graphical overview of the functionality

provided by a system in terms of actors, their goals (represented as use

cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system

functions are performed for which actor. Roles of the actors in the

system can be depicted.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-37

4.2 Sequence Diagram

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-38

Sender

Add Image

Update Image

Edit Text/image

Encrypt Image

Send Image

Receiver

Receive Image

Decrypt Image

Decrypt Text/image

view key

«extend»

Use key

«extend»

4.3 Activity Diagram

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-39

4.4 State Chart Diagram

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-40

Write Text

Encrypt

Pick Image

Merge Image with Text or image

Send Image

Receive Message

Decrypt Image

Read Text or image

State diagrams are used to give an abstract description of the behavior of

a system. This behavior is analyzed and represented in series of events,

that could occur in one or more possible states. Hereby each diagram

usually represents objects of a single class and track the different states

of its objects through the system.

Sender Send Image Receiver

Idle

Turn On

[Encrypt] [Decrypt]

4.7 DFD (Data Flow Diagram)

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-41

A data flow diagram (DFD) is a graphical representation of the flow of

data through an information system. DFDs can also be used for the

visualization of data processing (structured design). On a DFD, data

items flow from an external data source or an internal data store to an

internal data store or an external data sink, via an internal process.

LEVEL 0

LEVEL 1

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-42

LEVEL 2

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-43

4.8. Flow Chart

A flowchart is a type of diagram that represents

an algorithm or process, showing the steps as boxes of various kinds,

and their order by connecting these with arrows. 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.

Flowcharts are used in analyzing, designing, documenting or managing

a process or program in various fields.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-44

Encrypt

Pick Image

Merge text or image with Image

Send the Image

Write text

CHAPTER 5 ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-45

Receive encrypted message

Decrypt message & view text or image

TECHNICAL DETAILS

5.1 SOFTWARE SPECIFICATION:

In order to send the data from one node to the other with efficiency the following software is to be needed

Operating System: XP

.NET AND C#

Image processing software (Any)

Text editor (Any).

BACK END: MS Access

5.2 HARDWARE SPECIFICATION

As Such no need for any Extra hardware in this software but there must be an adequate memory i.e. a large size Hard disk to support the encryption program.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-46

Main Memory (RAM) :

It is often referred to simply as memory, is the only one directly

accessible to the CPU. The CPU continuously reads instructions

stored there and executes them as required. Any data actively operated

on is also stored there in uniform manner. Random-access

memory (RAM) is a form of computer data storage. Today, it takes

the form of integrated circuits that allow stored data to be accessed in

any order (i.e., at random). "Random" refers to the idea that any piece

of data can be returned in a constant time, regardless of its physical

location and whether it is related to the previous piece of data. The

word "RAM" is often associated with volatile types of memory (such

as DRAM memory modules), where the information is lost after the

power is switched off. Many other types of memory are RAM as well,

including most types of ROM and a type of flash

memory called NOR-Flash.

Requirement :- 128 Mega Bytes or more.

Processor

This is the portion of a computer system that carries out the

instructions of a computer program, and is the primary element

carrying out the computer's functions. The central processing

unit (CPU) is the portion of a computer system that carries out the

instructions of a computer program, and is the primary element

carrying out the computer's functions. The central processing unit

carries out each instruction of the program in sequence, to perform the

basic arithmetical, logical, and input/output operations of the system.

This term has been in use in the computer industry at least since the

early 1960s. 

The form, design and implementation of CPUs have changed

dramatically since the earliest examples, but their fundamental

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-47

operation remains much the same. Early CPUs were custom-designed

as a part of a larger, sometimes one-of-a-kind, computer. However,

this costly method of designing custom CPUs for a particular

application has largely given way to the development of mass-

produced processors that are made for one or many purposes. This

standardization trend generally began in the era of discrete  transistor

mainframes and minicomputers and has rapidly accelerated with the

popularization of the integrated circuit (IC). The IC has allowed

increasingly complex CPUs to be designed and manufactured to

tolerances on the order of nanometers. Both the miniaturization and

standardization of CPUs have increased the presence of these digital

devices in modern life far beyond the limited application of dedicated

computing machines. Modern microprocessors appear in everything

from automobiles to cell phones and children's toys.

Hard Disk: Up to 200 MB of available space may be required.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-48

CHAPTER 6FUTURE WORK

6.1 FUTURE WORK:

6.1 Designing Database

6.1.1 Finalizing the Tables for the Prototype

6.1.2 Description of Tables

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-49

6.2 Designing the User Interface

6.3 Forms and Validations

6.4 Report Generation

6.5 Accessibility and Authentication

6.6 Implementation Phase

6.7 Testing.

REFRENCES:

[1] N.F. Johnson and S. Jajodia, Exploring steganography: Seeing the unseen, IEEE Computer, 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.

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-50

[3] N. Provos and P. Honeyman, Hide and seek: An introduction to steganography, IEEE Security and Privacy, 01 (3) (2003) 32-44.

[4] P. Moulin and R. Koetter, Data-hiding codes, Proceedings of the IEEE, 93 (12) (2005) 2083-2126.

[5] S.B. Sadkhan, Cryptography: Current status and future trends, in: Proceedings of IEEE International Conference on Information & Communication Technologies: From Theory to Applications, Damascus. Syria, April 19-23, 2004, pp. 417-418.

[6] G.J. Simmons, The prisoners’ problem and the subliminal channel, in: Proceedings of International conference on Advances in Cryptology, CRYPTO83, August 22-24, 1984, pp. 51-67.

[7] C. Kurak and J. McHugh, A cautionary note on image downgrading, in: Proceedings of the IEEE 8th Annual Computer Security Applications Conference, 30 Nov-4 Dec 1992, pp. 153-159.

[8] cf. section 1-133, "Color/Graphics Adapter", page 143 of ibm_techref_v202_1.pdf

[9] R.J Andersen and F.A.P Petitcolas. On the limits of steganography. IEEE Journal of Selected Areas in Communications,Special Issue on Copyright and Privacy Protection, 16(4):474–481, 1998.

[10] Jiri Fridrich. A new steganographic method for palettebased images. In Proceedings of the IS&T PICS conference, pages 285–289, Savannah, Georgia, April 1998.

LINKS:

http://www.google.com

http://www.wikipedia.com

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-51

ORIENTAL INSTITUTE OF SCIENCE & TECHNOLOGY P-52