Sai Final Project Team1
Sai Final Project Team1
1. INTRODUCTION
1.1 AIM
In proposed system, we use a click-based graphical password system. During
password creation, there is a small view port area that is randomly positioned on the image.
Users must select a click-point within the view port. If they are unable or unwilling to select a
point in the current view port, they may press the Shuffle button to randomly reposition the
view port. The view port guides users to select more random passwords. Therefore this works
encouraging users to select more random, and difficult passwords to guess.
1.2 OBJECTIVES
Unfortunately, these passwords are broken mercilessly by intruders by several simple
means such as masquerading, Eaves dropping and other rude means say dictionary attacks,
shoulder surfing attacks, social engineering attacks [10][1].To mitigate the problems with
traditional methods, advanced methods have been proposed using graphical as passwords.
The idea of graphical passwords first described by Greg Blonder (1996). For Blonder,
graphical passwords have a predetermined image that the sequence and the tap regions
selected are interpreted as the graphical password. Since then, many other graphical password
schemes have been proposed. The desirable quality associated with graphical passwords is
that psychologically humans can remember graphical far better than text and hence is the best
alternative being proposed. There is a rapid and growing interest in graphical passwords for
they are more or infinite in numbers thus providing more resistance. The major goal of this
work is to reduce the guessing attacks as well as encouraging users to select more random,
and difficult passwords to guess.
2. SYSTEM ANALYSIS
ECONOMICAL FEASIBILITY
TECHNICAL FEASIBILITY
SOCIAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.
2.3.2 ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on
the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies
used are freely available. Only the customized products had to be purchased.
2.3.3 SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.
The user interface helps the users upon the system in searching through the existing
data and required services. The operational user interface also helps in adding new data as
and when required. Also the user can update/delete the data if wish to. There is no restriction
or access rights for the user to access the system. The interface helps the users with all the
transactional states like data insertion, data deletion and data updation.
2.4.2.1FUNCTIONAL REQUIREMENTS
Non-functional requirements describe user-visible aspects of the system that are not
directly related to functionality of the system.
User Interface: A menu interface has been provided to the client to be user friendly.
Documentation: The client is provided with an introductory help about the client
interface and the user documentation has been developed through help hyperlink.
Performance Constraints: Requests should be processed within no time.Users
should be authenticated for accessing the requested data.
Error Handling and Extreme Conditions: In case of User Error, the System should
display a meaningful error message to the user, such that the user can correct his
Error. The high level components in proposed system should handle exceptions that
occur while connecting to database server, IOExceptions etc.
Quality Issues: Quality issues refer to how reliable, available and robust should the
system be? While developing the proposed system the developer must be able to
guarantee the reliability transactions so that they will be processed completely and
accurately. The ability of system to detect failures and recovery from those failures
refers to the availability of system. Robustness of system refers to the capability of
system providing information when concurrent users requesting for information.
Acceptance Criteria: The developer will have to demonstrate and show to the user
that the system works by testing with suitable test cases so that all conditions are
satisfied.
SYSTEM CONFIGURATION
Hardware System Configuration:
Database : MySQL
3. SYSTEM DESIGN
other system through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output.
Designing computer output should proceed in an organized, well thought out manner;
the right output must be developed while ensuring that each output element is
designed so that people will find the system can use easily and effectively. When
analysis design computer output, they should Identify the specific output that is
needed to meet the requirements.
Select methods for presenting information.
Create document, report, or other formats that contain information produced by the
system.
The output form of an information system should accomplish one or more of the following
objectives.
Convey information about past activities, current status or projections of the
Future.
Signal important events, opportunities, problems, or warnings.
Trigger an action.
Confirm an action.
3.2 HIGH LEVEL DESIGN
3.2.1 SYSTEM DESIGN
A System design is an architecture which identifies different working(possible)
systems interacting with our main working system.
Image Database
Process System
Database View
Handler Transaction
Basic building blocks of the UML. The vocabulary of UML encompasses three kinds of
building blocks:
Things
Relationships
Diagrams
ISpelling
Collaboration
Collaboration defines an interaction and is a society of roles and other elements that
work together to provide some cooperative behavior that’s bigger than the sum of all the
elements. Graphically, collaboration is rendered as an ellipse with dashed lines, usually
including only its name as shown below.
Chain of
Responsibility
Use Case
Use case is a description of a set of sequence of actions that a system performs that
yields an observable result of value to a particular thing in a model. Graphically, Use Case is
rendered as an ellipse with dashed lines, usually including only its name as shown below.
Place Order
Active Class
An active class is a class whose objects own one or more processes or threads and
therefore can initiate control activity. Graphically, an active class is rendered just like a class,
but with heavy lines usually including its name, attributes and operations as shown below.
SPOL
EMPLOYEE
DEATILS
Suspend ()
Flush ()
Component
Component is a physical and replaceable part of a system that conforms to and
rectangle with tabs, usually including only its name, as shown below.
orderform.java
Node
A Node is a physical element that exists at run time and represents a computational
resource, generally having at least some memory and often, processing capability.
Graphically, a node is rendered as a cube, usually including only its name, as shown below.
server
Interaction
An interaction is a behavior that comprises a set of messages exchanged among a set
of objects within a particular context to accomplish a specific purpose. Graphically, a
message is rendered as a direct line, almost always including the name if its operation, as
shown below.
Display
State Machine
A state machine is a behavior that specifies the sequence of states an object are an
interaction goes through during its lifetime on response to events, together with its responses
to those events. Graphically, a state is rendered as a rounded rectangle usually including its
name and its sub-states, if any, as shown below.
Waiting
Business Rules
Note
A note is simply a symbol for rendering constraints and comments attached to an
element or a collection of elements. Graphically a note is rendered as a rectangle with dog-
eared corner together, with a textual or graphical comment, as shown below.
3.4.4 REALIZATION:
Class Diagram
Use Case Diagram
Object Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
Class diagrams are the most common diagrams found in modeling object-oriented
systems. A class diagram shows a set of classes, interfaces, and collaborations and their
relationships. Graphically, a class diagram is a collection of vertices and arcs.
Contents:
Class Diagrams commonly contain the following things:
Classes
Interfaces
Collaborations
Dependency
Generalization
Association Relationships
Common Properties
A Use Case diagram is just a special kind of diagram and shares the same common
properties, as do all other diagrams- a name and graphical contents that are a projection into
the model. What distinguishes a use case diagram from all other kinds of diagrams is its
particular content.
Contents
Use Case diagrams commonly contain:
Use Cases
Actors
Dependency, generalization, and association relationships
Like all other diagrams, use case diagrams may contain notes and constraints. Use
Case diagrams may also contain packages, which are used to group elements of your model
into larger chunks. Occasionally, you will want to place instances of use cases in your
diagrams, as well, especially when you want to visualize a specific executing system.
Contents
Interaction diagrams commonly contain:
Objects
Links
Messages
Like all other diagrams, interaction diagrams may contain notes and constraints.
object that initiates the interaction at the left, and increasingly more sub-routine objects to the
right. Next, you place the messages that these objects send and receive along the Y-axis , in
order of increasing time from top to the bottomSequence diagrams have two interesting
features:
There is the object lifeline. An object lifeline is the vertical dashed line that
represents the existence of an object over a period of time. Most objects that
appear in the interaction diagrams will be in existence for the duration of the
interaction, so these objects are all aligned at the top of the diagram, with their
lifelines drawn from the top of the diagram to the bottom.
There is a focus of the control. The focus of control is tall, thin rectangle that
shows the period of time during which an object is performing an action, either
directly or through the subordinate procedure. The top of the rectangle is aligns
with the action; the bottom is aligned with its completion.
Contents
Sequence diagrams commonly contains
Objects
Object Life Line
Focus of Control
(a) For User Registration
Fork
Structured analysis states that the current system should be first understand correctly.
The physical DFD is the model of the current system and is used to ensurethat the current
system has been clearly understood. Physical DFDs shows actual devices, departments, and
people etc., involved in the current system
Logical DFDs are the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity this is
taken as the basis for drawing the system’s structure charts.
Basic Notation
The Basic Notation used to create a DFD’s are as follows:
Dataflow: Data move in a specific direction from an origin to a destination.
Process: People, procedures, or devices that use or produce (Transform) Data. The
physical component is not identified.
3.7 DESIGN
Design is the first step in moving from problem domain to the solution domain.
Design is essentially the bridge between requirements specification and the final solution.
The goal of design process is to produce a model or representation of a system, which can be
used later to build that system. The produced model is called the “Design of the System”. It
is a plan for a solution for the system.
(B)Level 1
4.1 INTRODUCTION
Software Environment
Java Technology
Java technology is both a programming language and a platform.
The Java Programming Language
The Java programming language is a high-level language that can be characterized by
all of the following buzzwords:
Simple
Architecture neutral
Object oriented
Portable
Distributed
High performance
Interpreted
Multithreaded
Robust
Dynamic
Secure
With most programming languages, you either compile or interpret a program so that
you can run it on your computer. The Java programming language is unusual in that a
program is both compiled and interpreted. With the compiler, first you translate a program
into an intermediate language called Java byte codes —the platform-independent codes
interpreted by the interpreter on the Java platform. The interpreter parses and runs each Java
byte code instruction on the computer. Compilation happens just once; interpretation occurs
each time the program is executed. The following figure illustrates how this works.
You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a Web
browser that can run applets, is an implementation of the Java VM. Java byte codes help
make “write once, run anywhere” possible. You can compile your program into byte codes on
any platform that has a Java compiler. The byte codes can then be run on any implementation
of the Java VM. That means that as long as a computer has a Java VM, the same program
written in the Java programming language can run on Windows 2000, a Solaris workstation,
or on an iMac.
Native code is code that after you compile it, the compiled code runs on a
specific hardware platform. As a platform-independent environment, the Java
platform can be a bit slower than native code. However, smart compilers, well-tuned
interpreters, and just-in-time byte code compilers can bring performance close to that
of native code without threatening portability.
What Can Java Technology Do?
4.2 ODBC
Microsoft Open Database Connectivity (ODBC) is a standard programming interface
for application developers and database systems providers. Before ODBC became a de facto
standard for Windows programs to interface with database systems, programmers had to use
proprietary languages for each database they wanted to connect to. Now, ODBC has made the
choice of the database system almost irrelevant from a coding perspective, which is as it
should be. Application developers have much more important things to worry about than the
syntax that is needed to port their program from one database to another when business needs
suddenly change.
Through the ODBC Administrator in Control Panel, you can specify the particular
database that is associated with a data source that an ODBC application program is written to
use. Think of an ODBC data source as a door with a name on it. Each door will lead you to a
particular database. For example, the data source named Sales Figures might be a SQL Server
database, whereas the Accounts Payable data source could refer to an Access database. The
physical database referred to by a data source can reside anywhere on the LAN.
The ODBC system files are not installed on your system by Windows 95. Rather, they are
installed when you setup a separate database application, such as SQL Server Client or Visual
Basic 4.0. When the ODBC icon is installed in Control Panel, it uses a file called
ODBCINST.DLL. It is also possible to administer your ODBC data sources through a stand-
alone program called ODBCADM.EXE. There is a 16-bit and a 32-bit version of this
program and each maintains a separate list of ODBC data sources.
From a programming perspective, the beauty of ODBC is that the application can be
written to use the same set of function calls to interface with any data source, regardless of
the database vendor. The source code of the application doesn’t change whether it talks to
Oracle or SQL Server. We only mention these two as an example. There are ODBC drivers
available for several dozen popular database systems. Even Excel spreadsheets and plain text
files can be turned into data sources. The operating system uses the Registry information
written by ODBC Administrator to determine which low-level ODBC drivers are needed to
talk to the data source (such as the interface to Oracle or SQL Server). The loading of the
ODBC drivers is transparent to the ODBC application program. In a client/server
environment, the ODBC API even handles many of the network issues for the application
programmer.
The advantages of this scheme are so numerous that you are probably thinking there
must be some catch. The only disadvantage of ODBC is that it isn’t as efficient as talking
directly to the native database interface. ODBC has had many detractors make the charge that
it is too slow. The availability of good ODBC drivers has improved a great deal recently. And
anyway, the criticism about performance is somewhat analogous to those who said that
compilers would never match the speed of pure assembly language. Maybe not, but the
compiler (or ODBC) gives you the opportunity to write cleaner programs, which means you
finish sooner. Meanwhile, computers get faster every year.
4.3 JDBC
In an effort to set an independent database standard API for Java; Sun Microsystems
developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access
mechanism that provides a consistent interface to a variety of RDBMSs. This consistent
interface is achieved through the use of “plug-in” database connectivity modules, or drivers.
If a database vendor wishes to have JDBC support, he or she must provide the driver for each
platform that the database and Java run on. To gain a wider acceptance of JDBC, Sun based
JDBC’s framework on ODBC. As you discovered earlier in this chapter, ODBC has
widespread support on a variety of platforms. Basing JDBC on ODBC will allow vendors to
bring JDBC drivers to market much faster than developing a completely new connectivity
solution.
JDBC was announced in March of 1996. It was released for a 90 day public review
that ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was
released soon after. The remainder of this section will cover enough information about JDBC
for you to know what it is about and how to use it effectively. This is by no means a complete
overview of JDBC. That would fill an entire book.
SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort
to support a wide variety of vendors, JDBC will allow any query statement to be
passed through it to the underlying database driver. This allows the connectivity
module to handle non-standard functionality in a manner that is suitable for its users.
Keep it simple
This goal probably appears in all software design goal listings. JDBC is no exception.
Sun felt that the design of JDBC should be very simple, allowing for only one method
of completing a task per mechanism. Allowing duplicate functionality only serves to
confuse the users of the API.
Networking.
And for dynamically updating the cache table we go for MS Access database.
Simple Architecture-neutral
Object-oriented Portable
Distributed High-performance
Interpreted multithreaded
Robust Dynamic
Secure
Java is also unusual in that each Java program is both compiled and interpreted.
With a compile you translate a Java program into an intermediate language called
Java byte codes the platform-independent code instruction is passed and run on the
computer.
Compilation happens just once; interpretation occurs each time the program is
executed. The figure illustrates how this works.
Java Interpreter
Program
Compilers My Program
You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a Java development
tool or a Web browser that can run Java applets, is an implementation of the Java
VM. The Java VM can also be implemented in hardware.
Java byte codes help make “write once, run anywhere” possible. You can compile
your Java program into byte codes on my platform that has a Java compiler. The
byte codes can then be run any implementation of the Java VM. For example, the
same Java program can run Windows NT, Solaris, and Macintosh.
4.4 NETWORKING
TCP/IP stack: The TCP/IP stack is shorter than the OSI one:
IP datagram’s
UDP
UDP is also connectionless and unreliable. What it adds to IP is a checksum for the
contents of the datagram and port numbers. These are used to give a client/server model -
see later.
TCP
Internet addresses
In order to use a service, you must be able to find it. The Internet uses an address
scheme for machines so that they can be located. The address is a 32 bit integer which gives
the IP address. This encodes a network ID and more addressing. The network ID falls into
various classes according to the size of the network address.
Network address
Class A uses 8 bits for the network address with 24 bits left over for other addressing.
Class B uses 16 bit network addressing. Class C uses 24 bit network addressing and class D
uses all 32.
Subnet address
Internally, the UNIX network is divided into sub networks. Building 11 is currently
on one sub network and uses 10-bit addressing, allowing 1024 different hosts.
Host address
8 bits are finally used for host addresses within our subnet. This places a limit of 256
machines that can be on the subnet.
Total address
Port addresses
A service exists on a host, and is identified by its port. This is a 16 bit number. To
send a message to a server, you send it to the port for that service of the host that it is
running on. This is not location transparency! Certain of these ports are "well known".
Sockets
#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol will be zero, and
type will depend on whether TCP or UDP is used. Two processes wishing to communicate
over a network create a socket each. These are similar to two ends of a pipe - but the actual
pipe does not yet exist.
JFreeChart is a free 100% Java chart library that makes it easy for developers to
display professional quality charts in their applications. JFreeChart's extensive feature set
includes:
A consistent and well-documented API, supporting a wide range of chart types;
A flexible design that is easy to extend, and targets both server-side and client-side
applications;
Support for many output types, including Swing components, image files (including
PNG and JPEG), and vector graphics file formats (including PDF, EPS and SVG);
JFreeChart is "open source" or, more specifically, free software. It is distributed under the
terms of the GNU Lesser General Public License (LGPL), which permits use in proprietary
applications.
Map Visualizations
Charts showing values that relate to geographical areas. Some examples include: (a)
population density in each state of the United States, (b) income per capita for each
country in Europe, (c) life expectancy in each country of the world. The tasks in this
project include:Sourcing freely redistributable vector outlines for the countries of the
world, states/provinces in particular countries (USA in particular, but also other areas);
Creating an appropriate dataset interface (plus default implementation), a rendered, and
integrating this with the existing XYPlot class in JFreeChart;
Testing, documenting, testing some more, documenting some more.
Dashboards
bars, and lines/time series) that can be delivered easily via both Java Web Start and an
applet.
Property Editors
The property editor mechanism in JFreeChart only handles a small subset of the
properties that can be set for charts. Extend (or reimployment) this mechanism to provide
greater end-user control over the appearance of the charts.
4.7MYSQL DATABASE
MySQL, the most popular Open Source SQL database management system, is
developed, distributed, and supported by MySQL. MySQL is a commercial company,
founded by the MySQL developers. It is a second generation Open Source company that
unites Open Source values and methodology with a successful business model.
A relational database stores data in separate tables rather than putting all the data in
one big storeroom. This adds speed and flexibility. The SQL part of “MySQL” stands for
“Structured Query Language.” SQL is the most common standardized language used to
access databases and is defined by the ANSI/ISO SQL Standard. The SQL standard has been
evolving since 1986 and severalversions exist. In this manual, “SQL-92” refers to the
standard released in 1992, “SQL:1999” refers to the standard released in 1999, and
“SQL:2003” refers to the current version of the standard. We use the phrase “the SQL
standard” to mean the current version of the SQL Standard at any time.
Open Source means that it is possible for anyone to use and modify the software.
Anybody can download the MySQL software from the Internet and use it without paying
anything. MySQL Server was originally developed to handle large databases much faster
than existing solutions and has been successfully used in highly demanding production
environments for several years. Although under constant development, MySQL Server today
offers a rich and useful set of functions. Its connectivity, speed, and security make MySQL
Server highly suited for accessing databases on the Internet.
Handles large databases. We use MySQL Server with databases that contain 50
million records. We also know of users who use MySQL Server with 60,000 tables
and about 5,000,000,000 rows.
Security
A privilege and password system that is very flexible and secure, and that allows host-
based verification.
Passwords are secure because all password traffic is encrypted when you connect to a
server.
4.8 CODING
Program Coding
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package imageprocess;
/**
*
* @author Administrator
*/
import java.awt.*;
import java.awt.event.*;
import java.awt.geom.Area;
import java.awt.geom.Path2D;
import java.awt.image.BufferedImage;
import java.io.ByteArrayOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStream;
import java.sql.*;
import java.sql.DriverManager;
import java.util.Random;
import javax.imageio.ImageIO;
import javax.swing.*;
/**
*
* @author Administrator
*/
public class CompareImage extends JFrame implements ActionListener
{
File file;
BufferedImage image;
static Image pic;
c=(JPanel)getContentPane();
c.setLayout(null);
c.setBackground(Color.WHITE);
picture.setBounds(50,100,400,325);
filename.setBounds(600,100,100,30);
filenametext.setBounds(720,100,300,30);
name.setBounds(600,150,100,30);
password.setBounds(600,200,100,30);
nametext.setBounds(720,150,100,30);
passwordtext.setBounds(720,200,100,30);
Browse.setBounds(530,400,100,20);
upload.setBounds(650,400,100,20);
Compare.setBounds(770,400,100,20);
viewport.setBounds(770,450,100,20);
c.add(picture);
c.add(filename);
c.add(filenametext);
c.add(name);
c.add(nametext);
c.add(password);
c.add(passwordtext);
c.add(viewport);
c.add(upload);
c.add(Compare);
c.add(Browse);
viewport.addActionListener(this);
upload.addActionListener(this);
Compare.addActionListener(this);
Browse.addActionListener(this);
FileInputStream fis;
String filename=filenametext.getText();
String name=nametext.getText();
String password=passwordtext.getText();
try
{
Class.forName("com.mysql.jdbc.Driver");
connection = DriverManager.getConnection("jdbc:mysql://localhost/image","root","");
int s = psmnt.executeUpdate();
}
catch(Exception ee)
{
else if(ae.getSource()==Compare)
{
String filename=filenametext.getText();
try
{
File file=new File(filename);
BufferedImage image=ImageIO.read(file);
}
catch(Exception ee)
{
}
}
else if(ae.getSource()==Browse)
{
JFileChooser chooser = new JFileChooser();
try {
chooser.setSelectedFile(f);
}
catch (IOException e1)
{
}
int retval = chooser.showOpenDialog(Browse);
if (retval == JFileChooser.APPROVE_OPTION){
File field = chooser.getSelectedFile();
filenametext.setText(field.getAbsolutePath());
else if(ae.getSource()==viewport)
{
System.out.println("aa");
}
}
}
}
}
5. TESTING
Unit testing
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All
decision branches and internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge
of its construction and is invasive. Unit tests perform basic tests at component level
and test a specific business process, application, and/or system configuration. Unit
tests ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.
Integration testing
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with
the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is
specifically aimed at exposing the problems that arise from the combination of
components.
Functional test
Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and
user manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input: identified classes of invalid input must be rejected.
Functions: identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures: interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key
functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes
must be considered for testing. Before functional testing is complete, additional tests
are identified and the effective value of current tests is determined.
System Testing
System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results. An example of system
testing is the configuration oriented system integration test. System testing is based on
process descriptions and flows, emphasizing pre-driven process links and integration
points.
White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most
other kinds of tests, must be written from a definitive source document, such as
specification or requirements document, such as specification or requirements
document. It is a testing in which the software under test is treated, as a black box
.you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.
8 User to view User has to select User has to view User viewed Pass
transaction ‘transaction Report’ the transaction the
reports. and enter the reports if transaction
password details. entered details reports.
are true else
return error
message.
6. RESULTS
A major advantage of Persuasive cued click point scheme is its large password space over
alphanumeric passwords. There is a growing interest for Graphical passwords since they are
better than Text based passwords, although the main argument for graphical passwords is
that people are better at memorizing graphical passwords than text-based passwords. Online
password guessing attacks on password-only systems have been observed for decade‟s
.Present-day attackers targeting such systems are empowered by having control of thousand
to million node botnets. In previous ATT-based login protocols, there exists a security-
usability trade-off with respect to the number of free failed login attempts (i.e., with no
ATTs) versus user login convenience (e.g., less ATTs and other requirements). In contrast,
PGRP is more restrictive against brute force and dictionary attacks while safely allowing a
large number of free failed attempts for legitimate users. PGRP is apparently more effective
in preventing password guessing attacks (without answering ATT challenges), it also offers
more convenient login experience, e.g., fewer ATT challenges for legitimate users. PGRP
appears suitable for organizations of both small and large number of user accounts.
It is not possible to develop a system that makes all the requirement of the user. The user
requirement keep changing as the system is being used.
Based on the future security issues can be improved using emerging technologies.
8. BIBLIOGRAPHY
REFERENCES
[1] Sonia Chiasson, P.C. van Oorschot, and Robert Biddle, “Graphical Password
Authentication Using Cued Click Points”ESORICS, LNCS 4734, pp.359-374,Springer-
Verlag Berlin Heidelberg 2007.
[2] Manu Kumar, Tal Garfunkel, Dan Boneh and Terry Winograd, “Reducing Shoulder-
surfing by Using Gaze based Password Entry”, Symposium On Usable Privacy and Security
(SOUPS) , July18-20, 2007, Pittsburgh, PA, USA.
[3] Zhi Li, Qibin Sun, Yong Lain, and D. D.Giusto, „An association-based graphical
password design resistant to shoulder surfing attack‟, International Conference on
Multimedia and Expo (ICME), IEEE.2005
[4] R. Dhamija and A. Perrig, "Deja Vu: A UserStudy Using Images for Authentication," in
Proceedings of9th USENIX Security Symposium,2000.
[6] L. Sobrado and J.-C. Birget, "Graphicalpasswords," The Rutgers Scholar, An Electronic
Bulletin forUndergraduate Research, vol. 4,2002.
[7] Sonia Chiasson, Alain Forget , RobertBiddle, P. C. van Oorschot, “User interfacedesign
affects security: patterns in click-basedgraphical passwords”, Springer-Verlag 2009.
[8] I. Jermyn, A. Mayer, F. Monrose, M. K.Reiter, and A.D. Rubin, "The Design andAnalysis
of Graphical Passwords," inProceedings of the 8th USENIXSecuritySymposium, 1999.
[10] A. Adams and M. A. Sasse, "Users are notthe enemy: why users compromise computer
security mechanisms and how to take remedialmeasures," Communicationsof the ACM, vol.
42,pp. 41-46, 1999.
[11] I. Jermyn, A. Mayer, F. Monrose, M. K.Reiter, and A.D. Rubin, "The Design
andAnalysis of Graphical Passwords," inProceedings of the 8th USENIXSecuritySymposium,
1999.