PROJECT IMPLEMENTATION

1 Introduction

Visual Secret Sharing Schemes hide a Secret image in shares that appear noise like picture or
noiseless picture.VSS schemes suffer from a transmission risk problem while sharing shares
contains Secret Images. To address this problem, we proposed a natural-image-based VSS
scheme (NVSS scheme) that shares secret images via various carrier media to protect the secret
and the participants during the transmission phase. This Process involved sharing a secret image
over arbitrary selected natural images (called natural shares) and one noise-like share. The
natural shares can be photos or hand-painted pictures in digital form or in printed form. The
noise-like share is generated based on these natural shares and the secret image. The unaltered
natural shares are diverse and innocuous, thus greatly reducing the transmission risk problem.
We also propose possible ways to hide the noise like share to reduce the transmission risk
problem for the share. Experimental results indicate that the proposed approach is an excellent
solution for solving the transmission risk problem for the VSS schemes.

2 Tools and Technologies Used

TOOLS AND TECHNOLOGY USED:

Technology: JAVA, JSP, Servlet

Front End Design: HTML5, CSS3, Bootstrap, JavaScript, JSP.
Database: MYSQL
IDE: Eclipse Indigo, MYSQL Query Browser.

3 Methodologies/Algorithm Details

ALGORITHMS
A. Feature Extraction Algorithm (FE)
Where
B. (n, n) -NVSS Encryption/Decryption Algorithm

Where ,
C. The Share-Hiding Algorithm

4 Verification and Validation for Acceptance

In This Project we done following Verification and Validation-

VERIFICATION VALIDATION

1. Verification is a static practice of verifying 1. Validation is a dynamic mechanism of

Smart Crawler documents, design and validating / testing the actual product of Smart
code/program. Crawler.

2. It does not involve executing the code of 2. It always involves executing the code of
Smart Crawler. telemedicine.

3. It is human based checking of documents / 3. It is computer based execution of program

files of Smart Crawler. of Smart Crawler.

4. Target is requirements specification, 4. Target is actual product-a unit, a module, a

application and software architecture, high bent of integrated modules, and effective final
level, complete design, and database design o product of Smart Crawler.
of Smart Crawler etc.

5. Verification uses methods like 5. Validation uses methods like black box
 inspections/review, walkthroughs, and Desk- (functional) testing, gray box testing, and
checking of Smart Crawler. white box (structural) testing of Smart
Crawler.

6. Verification is done by development team to 6. Validation is carried out with the

provide that the software is as per the involvement of client of Smart Crawler.
specifications in the SRS document of Smart
Crawler.

7. It can catch errors that validation cannot 7. It can catch errors that verification cannot
catch. It is low level exercise. catch. It is High Level Exercise.

8. Verification is to check whether the 8. Validation is to check whether software

software conforms to specifications of Smart meets the customer expectations of Smart
Crawler. Crawler.

9. It, generally, comes first-done before 9. It generally follows after verification of

validation of Smart Crawler. Smart Crawler.

Explanation-

In the context of testing, Verification and Validation are very widely and commonly used
terms. Most of the times, we consider the terms same, but actually the terms are quite different.

There are two aspects of V&V tasks

1. Confirms to requirements (Producer view of quality)

2. Fit for use (consumers view of quality)

Producers view of quality, in simpler terms means the developers perception of the final
product.
Consumers view of quality means users perception of final product.
When we carry out the V&V tasks, we have to concentrate both of this view of quality.

To begin, lets try to understand the terms first and try to explore them with different standards.

What is Verification?

Verification is a process of evaluating the intermediary work products of a software development

lifecycle to check if we are in the right track of creating the final product.

Now the question here is: What are the intermediary products? Well, These can include the
documents which are produced during the development phases like, requirements specification,
design documents, data base table design, ER diagrams, test cases, traceability matrix etc. We
sometimes tend to neglect the importance of reviewing these documents but we should
understand that reviewing itself can find out many hidden anomalies when if found or fixed in
the later phase of development cycle, can be very costly.

In other words we can also state that verification is a process to evaluate the mediator products of
software to check whether the products satisfy the conditions imposed during the beginning of
the phase.

What is Validation?

Validation is the process of evaluating the final product to check whether the software meets the
business needs. In simple words the test execution which we do in our day to day life are actually
the validation activity which includes smoke testing, functional testing, regression testing,
systems testing etc