Credit Score Analaysis Project

ABSTRACT
Banks and credit card companies use credit scores of the consumers. This banks and
Credit Card Score Company lend money to the consumers based on the credit score of the
consumer. Consumer can have poor, fair, good or excellent credit scores. Based on these credit
score banker and credit company provide money to the consumer. We here proposed a web
based application that keeps track of people’s credit scores. This system can be used by the
consumers to know their credit score. User must register himself by adding the personal details
and credit card and credit details. System will provide user with credentials to access the system.
User can access his personal details as well as his credit details. Here we applied a unique
algorithm to calculate the credit score of the consumers. System will calculate the credit score
based on following parameters such as number of credit card, year of first credit car, number of
loans, expense, income etc. Using these parameters system will calculate the credit of each
consumer and will display the credit score value. System will also display whether the consumer
credit score is poor, fair, good or excellent. This system is helpful for the consumer to know
about their credit score. This system is fully functional and user friendly project.
CHAPTER 1
INTRODUCTION
OVER VIEW
Credit score-based purchases can be categorized into two types: 1) physical card and 2)
virtual card. In a physical-card based purchase, the cardholder presents his card physically to a
merchant for making a payment. To carry out fraudulent transactions in this kind of purchase, an
attacker has to steal the credit card. If the cardholder does not realize the loss of card, it can lead
to a substantial financial loss to the credit card company. In the second kind of purchase, only
some important information about a card (card number, expiration date, secure code) is required
to make the payment. Such purchases are normally done on the Internet or over the telephone.
To commit fraud in these types of purchases, a fraudster simply needs to know the card
details. Most of the time, the genuine cardholder is not aware that someone else has seen or
stolen his card information. The only way to detect this kind of fraud is to analyze the spending
patterns on every card and to figure out any inconsistency with respect to the “usual” spending
patterns. Fraud detection based on the analysis of existing purchase data of cardholder is a
promising way to reduce the rate of successful credit card frauds. Since humans tend to exhibit
specific behaviorist profiles, every cardholder can be represented by a set of patterns containing
information about the typical purchase category, the time since the last purchase, the amount of
money spent, etc. Deviation from such patterns is a potential threat to the system.
Security a major Concern:
1. Security concerns arising because both customer data and program are residing in
Provider Premises.
2. Security is always a major concern in Open System Architectures

Data centre Security?
1. Professional Security staff utilizing video surveillance, state of the art intrusion detection
systems, and other electronic means.
2. When an employee no longer has a business need to access datacenter his privileges to
access datacenter should be immediately revoked.
3. All physical and electronic access to data centers by employees should be logged and
audited routinely.
Data Location:
1. When user uses the cloud, user probably won't know exactly where your data is hosted,
what country it will be stored in?
2. Data should be stored and processed only in specific jurisdictions as define by user.
3. Provider should also make a contractual commitment to obey local privacy requirements
on behalf of their customers,
4. Data-centered policies that are generated when a user provides personal or sensitive
information, that travels with that information throughout its lifetime to ensure that the
information is used only in accordance with the policy
Backups of Data:
1. Data store in database of provider should be redundantly store in multiple physical

location.
2. Data that is generated during running of program on instances is all customer data and
therefore provider should not perform backups.
3. Control of Administrator on Databases.

Data Sanitization:
1. Sanitization is the process of removing sensitive information from a storage device.
2. What happens to data stored in a cloud computing environment once it has passed its
user’s “use by date”
3. What data sanitization practices does the cloud computing service provider propose to
implement for redundant and retiring data storage devices as and when these devices are
retired or taken out of service.
Network Security:
1. Denial of Service: where servers and networks are brought down by a huge amount of
network traffic and users are denied the access to a certain Internet based service.
2. Like DNS Hacking, Routing Table “Poisoning”, XDoS attacks
3. QoS Violation : through congestion, delaying or dropping packets, or through resource

hacking.
4. Man in the Middle Attack: To overcome it always use SSL
5. IP Spoofing: Spoofing is the creation of TCP/IP packets using somebody else's IP

address.
6. Solution: Infrastructure will not permit an instance to send traffic with a source IP or
MAC address other than its own.
How secure is encryption Scheme:
1. Is it possible for all of my data to be fully encrypted?
2. What algorithms are used?
3. Who holds, maintains and issues the keys? Problem:

4. Encryption accidents can make data totally unusable.
5. Encryption can complicate availability Solution
6. The cloud provider should provide evidence that encryption schemes were designed and
tested by experienced specialists.
Information Security:
1. Security related to the information exchanged between different hosts or between hosts
and users.
2. This issues pertaining to secure communication, authentication, and issues concerning

single sign on and delegation.
3. Secure communication issues include those security concerns that arise during the
communication between two entities.
4. These include confidentiality and integrity issues. Confidentiality indicates that all data
sent by users should be accessible to only “legitimate” receivers, and integrity indicates
that all data received should only be sent/modified by “legitimate” senders.
5. Solution: public key encryption, X.509 certificates, and the Secure Sockets Layer (SSL)
enables secure authentication and communication over computer networks.
CHAPTER 2
LITERARY SURVEY
Ghosh and Reilly have proposed credit card fraud detection with a neural network. They
have built a detection system, which is trained on a large sample of labeled credit card account
transactions. These transactions contain example fraud cases due to lost cards, stolen cards,
application fraud, counterfeit fraud, mail-order fraud, and no received issue (NRI) fraud.
Recently, Syeda et al. have used parallel granular neural networks (PGNNs) for improving the
speed of data mining and knowledge discovery process in credit card fraud detection. A
complete system has been implemented for this purpose.
Stolfo et al. suggest a credit card fraud detection system (FDS) using metalearning
techniques to learn models of fraudulent credit card transactions. Metalearning is a general
strategy that provides a means for combining and integrating a number of separately built
classifiers or models. A metaclassifier is thus trained on the correlation of the predictions of the
base classifiers. The same group has also worked on a cost-based model for fraud and intrusion
detection . They use Java agents for Metalearning (JAM), which is a distributed data mining
system for credit card fraud detection.
A number of important performance metrics like True Positive—False Positive (TP-FP)

spread and accuracy have been defined by them. Aleskerov et al. present CARDWATCH, a
database mining system used for credit card fraud detection. The system, based on a neural
learning module, provides an interface to a variety of commercial databases. Kim and Kim have
identified skewed distribution of data and mix of legitimate and fraudulent transactions as the
two main reasons for the cmplexity of credit card fraud detection . Based on this observation,
they use fraud density of real transaction data as a confidence value and generate the weighted
fraud score to reduce the number of misdetections. Fan et al. suggest the application of
distributed data mining in credit card fraud detection. Brause et al. have developed an approach
that involves advanced data mining techniques and neural network algorithms to obtain high
fraud coverage. Chiu and Tsai have proposed Web services and data mining techniques to
establish a collaborative scheme for fraud detection in the banking industry.
With this scheme, participating banks share knowledge about the fraud patterns in a
heterogeneous and distributed environment. To establish a smooth channel of data exchange,
Web services techniques such as XML, SOAP, and WSDL are used. Phua et al. have done an
extensive survey of existing data-mining-based FDSs and published a comprehensive report.
Prodromidis and Stolfo use an agent-based approach with distributed learning for detecting
frauds in credit card transactions.
It is based on artificial intelligence and combines inductive learning algorithms and

metalearning methods for achieving higher accuracy. Phua .suggest the use of metaclassifier
similar to infrauddetectionproblems.TheyconsidernaiveBayesian, C4.5, and Back Propagation
neural networks as the base classifiers. A metaclassifier is used to determine which classifier
should be considered based on skewness of data. Although they do not directly use credit card
fraud detection as the target application, their approach is quite generic. Vatsa et al. have
recently proposed a game-theoretic approach to credit card fraud detection. They model the
interaction between anattackerandanFDSas a ltistagegamebetween two players, each trying to
maximize his payoff. The problem with most of the abovementioned approaches is that they
require labeled data for both genuine,as well as fraudulent transactions, to train the classifiers.
Getting real-world fraud data is one of the biggest problems associated with credit card fraud
detection.
Also, these approaches cannot detect new kinds of frauds for which labeled data is not
available. In contrast, we present a Hidden Markov Model (HMM)-based credit card FDS, which
does not require fraud signatures and yet is able to detect frauds by considering a cardholder’s
spending habit.Wemodel a credit card transaction processing sequence by the stochastic process
of an HMM. The details of items purchased in individual transactions are usually not known to
an FDS running at the bank that issues Credit score to the cardholders. This can be represented as
the underlying finite Markov chain, which is not observable. The transactions can only be
observed through the other stochastic process that produces the sequence of the amount of
money spent in each transaction. Hence, we feel that HMM is an ideal choice for addressing this
problem. Another important advantage of the HMM-based approach is a drastic reduction in the
number of False Positives (FPs)—transactions identified as malicious by an FDS although they
are actually genuine.
EXISTING SYSTEM
In case of the existing system the fraud is detected after the fraud is done that is, the fraud
is detected after the complaint of the card holder. And so the card holder faced a lot of trouble
before the investigation finish. And also as all the transaction is maintained in a log, we need to
maintain a huge data. And also now a days lot of online purchase are made so we don’t know the
person how is using the card online, we just capture the IP address for verification purpose. So
there need a help from the cyber crime to investigate the fraud. To avoid the entire above
disadvantage we propose the system to detect the fraud in a best and easy way.
 The Traditional detection method mainly depends on database system and the education
of customers, which usually are delayed, inaccurate and not in-time.
 After that methods based on discriminate analysis and regression analysis are widely used
which can detect fraud by credit rate for cardholders and credit card transaction.
 For a large amount of data it is not efficient.
PROBLEM RECOGNITION
 The high amount of losses due to fraud and the awareness of the relation between loss
and the available limit have to be reduced.
 The fraud has to be deducted in real time and the number of false alert has to be
minimized.
PROPOSED SYTEM
In proposed system, we present a Hidden Markov Model (HMM).Which does not require
fraud signatures and yet is able to detect frauds by considering a cardholder’s spending habit.
Card transaction processing sequence by the stochastic process of an HMM. The details of items
purchased in Individual transactions are usually not known to any Fraud Detection System (FDS)
running at the bank that issues Credit score to the cardholders. Hence, we feel that HMM is an
ideal choice for addressing this problem. Another important advantage of the HMM-based
approach is a drastic reduction in the number of False Positives transactions identified as
malicious by an FDS although they are actually genuine.
An FDS runs at a credit card issuing bank. Each incoming transaction is submitted to the
FDS for verification. FDS receives the card details and the value of purchase to verify, whether
the transaction is genuine or not. The types of goods that are bought in that transaction are not
known to the FDS. It tries to find any anomaly in the transaction based on the spending profile of
the cardholder, shipping address, and billing address, etc. If the FDS confirms the transaction to
be of fraud, it raises an alarm, and the issuing bank declines the transaction.
ADVANTAGE
 The detection of the fraud use of the card is found much faster that the existing
system.
 In case of the existing system even the original card holder is also checked for
fraud detection. But in this system no need to check the original user as we
maintain a log.
 The log which is maintained will also be a proof for the bank for the transaction
made.
 We can find the most accurate detection using this technique.
 this reduce the tedious work of an employee in the bank
CHAPTER 3
SYSTEM STUDY
FEASIBILITY STUDY
When complex problem and opportunities are to be defined, it is generally desirable to

conduct a preliminary investigation called a feasibility study. A feasibility study is conduct to
obtain an overview of the problem and to roughly assess whether feasible solution exists prior to
committing substantial resources to a project. During a feasibility study, the system analyst
usually works with representatives from the departments(s) expected to benefit from the solution.
Every project is feasible if given unlimited resource and infinite time. Unfortunately, the
development of computer based systems is more likely to be plagued by scarcity of resources
and difficult delivery of data it is both necessary and prudent to evaluate the feasibility of a
project at the earliest possible time. Precious time and money can be saved and untold
professional embarrassment can be averted if an ill conceived system is recognized early in the
definition phase. So a detailed study is carried out to check the workability of the system.
Feasibility study is undertaken to evaluate its workability, impact on the organization,

ability to meet user needs, and effective se of resources. The main objective of feasibility study is
to test the technical, operational and economical feasibility of developing the computer system.
Thus, during feasibility analysis for this project the following three primary areas of interest
were considered very carefully. The feasibility of a project can be ascertained in terms of
technical factors, economic factors, or both. A feasibility study is documented with a report
showing all the ramification of the project.
The primary objective of a feasibility study is to assess three types of feasibility.
1) Technical feasibility: can a solution be supported with existing technology?
2) Economical feasibility: is existing technology cost effective?
3) Operational feasibility: will the solution work in the organization if implemented?

3.1 TECHNICAL FEASIBILITY
A systems development project may be regarded as technically feasibility or ‘practical’ if

the organization has the necessary expertise and infrastructure to develop, install, operate and
maintain the proposed system. Organizations will need to make this assessment based on:
• Knowledge of current and emerging technological solutions.
• Availability of technically qualified staff in house for the duration of the project and
subsequent maintenance phase.
• Availability of infrastructure in house to support the development and maintenance of the

proposed system.
• Where necessary, the financial and/or technical capacity to procure appropriate

infrastructure and expertise from outside.
• Capacity of the proposed system to accommodate increasing levels of use over the
medium term and capacity of the proposed system to meet initial performance expectations and
accommodate new functionality over the medium term.
The existing computer system has a good hardware configuration and good software facilities in
such a way that any alteration can be implemented with slight modifications of the existing
process. Hence this project is technically feasible.
3.2 ECONOMIC FEASIBILITY
A systems development project may be regarded as economically feasible or ‘good

value’ to the organization if its anticipated benefits outweigh its estimated costs. However, many
of the organizational benefits arising from record keeping projects are intangible and may be
hard to quantify. In contrasts, many development costs are easier to identify.
These costs may include the time, budget and staff resources invested during the
design and implementation phase as well as infrastructure, support, training and maintenance
costs incurred after implementation. In these high risk situations it may be appropriate
assessments of financial feasibility.
3.3. OPERATIONAL FEASIBILITY
A systems development project is likely to be operationally feasible if it meets the

‘needs’ and expectations of the organization. User acceptance is an important determinant of
operational feasibility.
FEASIBILITY STUDY OF THE PROPOSED SYSTEM
The feasibility study of the proposed system has been carried out in all the three areas.
Technical Feasibility
The proposed system can be easily developed using resources available in the
organization. Hence it is technically feasible.
3.4 ECONOMIC FEASIBILITY
The proposed system can be easily developed using the resources available in the
organization and they do not invest in procurement of additional hardware or software. The cost
of developing the system, including all the phases have been taken into account and it is strict
minimum. Hence the system is economically feasible.
3.5 OPERATIONAL FEASIBILITY
The system has been developed after extensive discussion with the end user and all the
operational requirements has been taken into account during the planning and implementation
stages. Hence the system is operationally feasible.
CHAPTER 4
SOFTWARE REQUIREMENTS
4.1 HARDWARE REQUIREMENTS:

The minimum hardware requirements are as follows:
Processor : Pentium series
RAM(Primary Processor) : 512 MB RAM
Hard Disk Capacity : 20GB
Monitor : Colors/SVGA(800 x 600)
Printer : Laser Compatible
4.2 SOFTWARE REQUIREMENTS:
The software used is as follows:
Operating System Windows XP
Platform Microsoft .Net Frame Work
Front End ASP.NET and C# 2008
Back End Microsoft SQL Server 2005

4.2.1 SOFTWARE METHODOLOGY USED
Problem & Assign requirements to Design System

Literature Survey Modules Architecture
Develop Testing of Integrate Validate

Modules Modules System System
Fig 1.1: Addition of extra modules (Future Enhancements)
4.2.1 INCREMENTAL SOFTWARE METHODOLOGY
“Incremental Developmental Software Methodology” is followed in this project. As new

modules are completed, they can be integrated with the existing modules so that the system can
be enhanced with each delivered module. Whenever the customer needs to enhance the system
they can implement those modules and the customer need not have to wait until the entire system
is delivered. Since in this model we can have better perception of every model properly and bugs
and errors can be rectified with much more greater ease. Incremental development is an in-
between approach which combines the advantage of both waterfall model as well as evolutionary
model.
4.2 SYSTEM ENVIRONMENT
4.2 FRONT END USED:
Microsoft Visual Studio dot Net is used as front end tool. The reason for selecting
Visual Studio dot Net as front end tool is as follows.
4.2.1 FEATURES OF MICROSOFT VISUAL STUDIO DOT NET:
 Visual Studio .Net has flexibility, allowing one or more language to interoperate to
provide the solution. This Cross Language Compatibility allows us to do projects
at faster rate.
 Visual Studio. Net has Common Language Runtime, which allows the entire
component to converge into one intermediate format and then interact.
 Visual Studio. Net provides excellent security when an application is executed in
the system
 Visual Studio.Net has flexibility, allowing us to configure the working
environment to best suit our individual style. We can choose between a single and
multiple document interfaces, and we can adjust the size and positioning of the
various IDE elements.
 Visual Studio. Net has Intelligent feature that makes the coding easy and also
dynamic help provides very less coding time.
 The working environment in Visual Studio.Net is often referred to as Integrated
Development Environment because it integrates many different functions such as
design, editing, compiling and debugging within a common environment.
 After creating a Visual Studio. Net application, if we want to distribute it to others
we can freely distribute any application to anyone who uses Microsoft windows.
We can distribute our applications on disk, on CDs, across networks, or over an
intranet or the internet.
 Toolbars provide quick access to commonly used commands in the programming

environment. We click a button on the toolbar once to carry out the action
represented by that button. By default, the standard toolbar is displayed when we
start Visual Basic dot Net. Additional toolbars for Many parts of Visual Studio are
context sensitive. Context sensitive means we can get help on these parts directly
without having to go through the help menu. For example, to get help on any
keyword in the Visual Basic language, place the insertion point on that keyword in
the code window and press F1.
 Visual Studio interprets our code as we enter it, catching and highlighting most
syntax or spelling errors on the fly. It’s almost like having an expert watching over
our shoulder as we enter our code.
4.2.3 FEATURES OF. NET
Microsoft .NET is a set of Microsoft software technologies for rapidly building and
integrating XML Web services, Microsoft Windows-based applications, and Web solutions.
The .NET Framework is a language-neutral platform for writing programs that can easily
and securely interoperate. There’s no language barrier with .NET, there are numerous
languages available to the developer including Managed C++, C#, Visual Basic and Java
Script. The .NET framework provides the foundation for components to interact seamlessly,
whether locally or remotely on different platforms. It standardizes common data types and
communications protocols so that components created in different languages can easily
interoperate.
“.NET” is also the collective name given to various software components built upon
the .NET platform. These will be both products (Visual Studio.NET and Windows.NET
Server, for instance) and services (like Passport, .NET My Services, and so on).
4.2.4 THE .NET FRAMEWORK
The .NET Framework has two main parts:
1. The Common Language Runtime (CLR).
2. A hierarchical set of class libraries.
The CLR is described as the “execution engine” of .NET. It provides the

environment within which programs run. The most important features are
 Conversion from a low-level assembler-style language, called
Intermediate Language (IL), into code native to the platform being
executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such
features.
 The following features of the .NET framework are also worth
description.
MANAGED CODE
The code that targets .NET, and which contains certain extra Information
“metadata” to describe itself. While both managed and unmanaged code can run in the
runtime, only managed code contains the information that allows the CLR to guarantee, for
instance, safe execution and interoperability.
MANAGED DATA
With Managed Code comes Managed Data. CLR provides memory allocation and
Deal location facilities, and garbage collection. Some .NET languages use Managed Data by
default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do
not. Targeting CLR can depending on the language using, impose certain constraints on the
features available. As with managed and unmanaged code, one can have both managed and
unmanaged data in .NET applications, data that doesn’t get garbage collected but instead is
looked after by unmanaged code.
COMMON TYPE SYSTEM
The CLR uses something called the Common Type System (CTS) to strictly enforce
type-safety. This ensures that all classes are compatible with each other, by describing types
in a common way. CTS define how types work within the runtime, which enables types in
one language to interoperate with types in another language, including cross-language
exception handling. As well as ensuring that types are only used in appropriate ways.
COMMON LANGUAGE SPECIFICATION
The CLR provides built-in support for language interoperability. To ensure that you
can develop managed code that can be fully used by developers using any programming
language, a set of language features and rules for using them called the Common Language
Specification (CLS) has been defined. Components that follow these rules and expose only
CLS features are considered CLS-compliant.
THE CLASS LIBRARY
.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The
root of the namespace is called System; this contains basic types like Byte, Double, Boolean,
and String, as well as Object. All objects derive from System. Object. As well as objects,
there are value types. Value types can be allocated on the stack, which can provide useful
flexibility. There are also efficient means of converting value types to object types if and
when necessary.
The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.
The class library is subdivided into a number of sets (or namespaces), each providing
distinct areas of functionality, with dependencies between the namespaces kept to a
minimum.
LANGUAGES SUPPORTED BY .NET
The multi-language capability of the .NET Framework and Visual Studio .NET
enables developers to use their existing programming skills to build all types of applications
and XML Web services. The .NET framework supports new versions of Microsoft’s old
favorites Visual Basic and C++ (as VB.NET and Managed C++), but there are also a
number of new additions to the family.
Visual Basic .NET has been updated to include many new and improved language
features that make it a powerful object-oriented programming language. These features
include inheritance, interfaces, and overloading, among others. Visual Basic also now
supports structured exception handling, custom attributes and also supports multi-threading.
Visual Basic .NET is also CLS compliant, which means that any CLS-compliant
language can use the classes, objects, and components you create in Visual Basic .NET.
Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of
migrating existing C++ applications to the new .NET Framework.
VB is Microsoft’s new language. It’s a C-style language that is essentially “C++ for
Rapid Application Development”. Unlike other languages, its specification is just the
grammar of the language. It has no standard library of its own, and instead has been
designed with the intention of using the .NET libraries as its own.
Microsoft Visual J# .NET provides the easiest transition for Java-language

developers into the world of XML Web Services and dramatically improves the
interoperability of Java-language programs with existing software written in a variety of
other programming languages.
Active State has created Visual Perl and Visual Python, which enable .NET-aware
applications to be built in either Perl or Python. Both products can be integrated into the
Visual Studio .NET environment. Visual Perl includes support for Active State’s Perl Dev
Kit.
Other languages for which .NET compilers are available include
 FORTRAN
 COBOL
 Eiffel
4.3 BACK END USED:
Microsoft SQL SERVER 2005 is used as back end tool. The reason for selecting SQL
SERVER 2000 as a back end tool is as follows:
4.3.1 FEATURES OF SQL SERVER 2005
The OLAP Services feature available in SQL Server version 7.0 is now called SQL
Server 2005 Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services. Analysis Services also includes a new data mining component. The
Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server
2000 Meta Data Services. References to the component now use the term Meta Data Services.
The term repository is used only in reference to the repository engine within Meta Data Services.
SQL-SERVER database consist of five type of objects.
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO
1) TABLE:
A database is a collection of data about a specific topic. We can View a table in two
ways,
a) Design View
b) Datasheet View
a)Design View
To build or modify the structure of a table, we work in the table design view. We can
specify what kind of datas will be holded.
b)Datasheet View
To add, edit or analyses the data itself, we work in tables datasheet view mode.
2) QUERY:
A query is a question that has to be asked to get the required data. Access
gathers data that answers the question from one or more table. The data that make up the answer
is either dynaset (if you edit it) or a snapshot (it cannot be edited).Each time we run a query, we
get latest information in the dynaset. Access either displays the dynaset or snapshot for us to
view or perform an action on it, such as deleting or updating.
3) FORMS:
A form is used to view and edit information in the database record. A form displays only
the information, we want to see in the way we want to see it. Forms use the familiar controls
such as textboxes and checkboxes. This makes viewing and entering data easy.
We can work with forms in several views. Primarily there are two views,
They are,
a) Design View
b) Form View
a) Design View
To build or modify the structure of a form, we work in form’s design view. We can add
control to the form, that are bound to fields in a table or query, includes textboxes, option
buttons, graphs and pictures.
4) REPORT:
A report is used to view and print the information from the database. The report can
ground records into many levels and compute totals and average by checking values from
many records at once. Also the report is attractive and distinctive because we have control
over the size and appearance of it.
5) MACRO:
A macro is a set of actions. Each action in a macro does something, such as opening a form
or printing a report .We write macros to automate the common tasks that work easily and
save the time.
1.1.1. FEATURES OF SQL PROCEDURES
SQL procedures are characterized by many features. SQL procedures:
 Can contain SQL Procedural Language statements and features which support the
implementation of control-flow logic around traditional static and dynamic SQL
statements.
 Are supported in the entire DB2 family brand of database products in which many if not
all of the features supported in DB2 Version 9 are supported.
 Are easy to implement, because they use a simple high-level, strongly typed language.
 SQL procedures are more reliable than equivalent external procedures.
 Adhere to the SQL99 ANSI/ISO/IEC SQL standard.
 Support input, output, and input-output parameter passing modes.
 Support a simple, but powerful condition and error-handling model.
 Allow you to return multiple result sets to the caller or to a client application.
 Allow you to easily access the SQLSTATE and SQLCODE values as special variables.
 Reside in the database and are automatically backed up and restored.
 Can be invoked wherever the CALL statement is supported.
CHAPTER 5
SYSTEM IMPLEMENTATION
MODULE DESCRIPTION:
IMPLEMENTATION
Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus it can be considered to be the most critical stage in achieving a successful
new system and in giving the user, confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the existing system
and it’s constraints on implementation, designing of methods to achieve changeover and
evaluation of changeover methods.
MODULES:
1. New card
2. Login
3. Security information
4. Transaction
5. Verification
MODULE DESCRIPTION
NEW CARD
In this module, the customer gives there information to enroll a new card. The
information is all about there contact details. They can create there own login and password for
there future use of the card.
LOGIN
In Login Form module presents site visitors with a form with username and password
fields. If the user enters a valid username/password combination they will be granted access to
additional resources on website. Which additional resources they will have access to can be
configured separately.
SECURITY INFORMATION
In Security information module it will get the information detail and its store’s in
database. If the card lost then the Security information module form arise. It has a set of
question where the user has to answer the correctly to move to the transaction section. It contain
informational privacy and informational self-determination are addressed squarely by the
invention affording persons and entities a trusted means to user, secure, search, process, and
exchange personal and/or confidential information.
TRANSACTION
The method and apparatus for pre-authorizing transactions includes providing a

communications device to a vendor and a credit card owner. The credit card owner initiates a
credit card transaction by communicating to a credit card number, and storing therein, a
distinguishing piece of information that characterizes a specific transaction to be made by an
authorized user of the credit card at a later time. The information is accepted as "network data" in
the data base only if a correct personal identification code (PIC) is used with the communication.
The "network data" will serve to later authorize that specific transaction. The credit card owner
or other authorized user can then only make that specific transaction with the credit card.
Because the transaction is pre-authorized, the vendor does not need to see or transmit a PIC.
VERIFICATION
Verification information is provided with respect to a transaction between an initiating

party and a verification-seeking party, the verification information being given by a third,
verifying party, based on confidential information in the possession of the initiating party. In
verification the process will seeks card number and if the card number is correct the relevant
process will be executed. If the number is wrong, mail will be sent to the user saying the card no
has been block and he can’t do the further transaction.
SYSTEM ARCHITECTURE
DATA
WAREHOUSE
(CUSTOMER
DATA)
FRAUD RULE RULES FILTER &

SET ENGINE PRIORITY
GENETIC
ALGORITHM
MODULE DIAGRAM
Start
New Card
Login
Security Information
Transaction Verification
Stop
UML DIAGRAMS
New Card
User Login
Store Info
Verification Transaction
CLASS DIAGRAM
OBJECT DIAGRAM
Login Transaction
Verification Security Info
Complete
Transaction
STATE DIAGRAM
Request Add Login Transa

Information ction
ACTIVITY DIAGRAM
New Account
Security
Yes
Account
CheckSec
No
Login.
Pay Complete
Purchase. Verification
Transaction
SEQUENCE DIAGRAM
New Account Login Transaction Verification Security Complete

Transaction
User Info
Login Info
Transaction Details
Security Info
Verification Details
COLLABORATION DIAGRAM
New Account
1: User Info
Login Complete Transaction
2: Login Info 5: Verification Details
Transaction 3: Transaction Details Verification 4: Security Info Security

COMPONENT DIAGRAM
Verification
Transactio
n
Security
Detail
User
Account
details
E-R DIAGRAM
Security
HAS
Account History
Transaction
HAS
Account
Details
HAS
User
Security
details
Verification
Card No. Account Details
Security
DATAFLOW DIAGRAM
Account Details
User Login
Transaction Security
Verificati
on
Complete Transaction
PROJECT FLOW DIAGRAM
User Account Area Start Verification

Transaction
User Security
User
User
Login Login
Details
Account
Transact Verificat Complete
Details
ion ion n
Securit
y
CHAPTER 6
SYSTEM DESIGN
The most creative and challenging phase of the system life cycle is system design. The
term design describes a final system and the process by which it is developed. It refers to the
technical specifications that will be applied in implementing the candidate system. It also
includes the construction of programs and program testing. The key question involved here
is “How the problem should be solved”.
System design is a solution for the question of how to approach to the creation of a new
system. This important phase is composed of several steps. It provides the understanding and
procedural details necessary for implementing the system recommended in the feasibility study.
Emphasis is on translating the performance requirements into design specifications. Design goes
through logical and physical stages of development. Logical reviews the present physical system;
prepares input and output specifications; makes edit, security, and control specifications; details
the implementation plan; prepares a logical design walkthrough. Physical design maps out the
details of the physical system, plans the system implementaion, devises a test and
implementation plan and specifies any new hardware and software.
The first step is to determine how the output is to be produced and in what format.
Samples of output and input are presented. Second, input data and master files have to be
designed to meet the requirement of the proposed output. The operational phases are handled
through program construction and testing, including a list of programs needed to meet the
system’s objectives and complete documentation. Finally details related to justification of the
system and estimate of the impact of the candidate system on the user and organization are
documented and evaluated by management as a step toward implementation.
The final report prior to the implementation phase includes procedural flowcharts, record
layouts and a workable plan for implementing the candidate system. Information on personnel,
money, hardware, facilities, and their estimated cost must also be available. At this point,
projected costs must be close to actual costs of implementation.
INPUT DESIGN
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to put
transaction data in to a usable form for processing can be achieved by inspecting the computer to
read data from a written or printed document or it can occur by having people keying the data
directly into the system. The design of input focuses on controlling the amount of input required,
controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The
input is designed in such a way so that it provides security and ease of use with retaining the
privacy. Input Design considered the following things:
1. What data should be given as input?
2. How the data should be arranged or coded?
3. The dialog to guide the operating personnel in providing input.
4. Methods for preparing input validations and steps to follow when error occur.
OBJECTIVES
1.Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.
2. It is achieved by creating user-friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to be free from
errors. The data entry screen is designed in such a way that all the data manipulates can be
performed. It also provides record viewing facilities.
3.When the data is entered it will check for its validity. Data can be entered with the help
of screens. Appropriate messages are provided as when needed so that the user
will not be in maize of instant. Thus the objective of input design is to create an input
layout that is easy to follow
OUTPUT DESIGN
A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
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. It is the most important and direct
source information to the user. Efficient and intelligent output design improves the system’s
relationship to help user decision-making.
1. 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.
2.Select methods for presenting information.
3.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
1. Future.
2. Signal important events, opportunities, problems, or warnings.
3. Trigger an action.
4. Confirm an action.
Then the user can login to the system by providing username and password. If the login is
succeeded he can provide the port number to which server is listening and select all the other
menus. First tab called ‘Home’ contains a JTree having the root Peer to Peer and 2 sub nodes
PrivetShare and PublicShare. Client side coding is done in such away that at the time of
installation itself there creates 3 folders in the C: drive called Peer to Peer, PublicShare,
PrivateShare. Actually PrivateShare and PublicShare are the folders inside the folder Peer to
Peer. They are organized in such away that each user can create folders under Peer to Peer. Also
they can create a new file under the folder Peer to Peer. Actually Peer-to-Peer contains his
private files and folders. Also he can copy files from anywhere in the system to the folder Peer to
Peer or any folder created by him under Peer to Peer. Our project is aimed at sharing of files
between clients. While sharing a user can share his file to all the users or one or more particular
users. That is, he can share his files either publicly or privately. I done the coding so that the
folder PrivateShare always hold the files, which are shared privately by the user. Other files,
which are shared, have to copy to the folder PublicShare.
I already mentioned that the first tab in the GUI contains a JTree. It always shows the
contents of these 3 folders. In the menu there is a menu item called ‘Share Files’ to share files for
other users.
I added a menu item in the menu ‘utilities’ named ‘create folder’ to create new folders in
Peer to Peer. Then the tree in the first tab is updated to reflect the changes. Other menus included
are ‘create file’, ‘copy files’, ‘share files’, etc. By expanding the tree and selecting one of the
files we can view it’s contents. The user can edit the file, delete the file and save the changes.
Second tab contains another tree named ‘Shared Files’ which displays the names of all the files
that are shared by other users to the current user. Actually these files are originally located in
other clients.
SAMPLE CODE
Aboutproject.cs
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class Products : System.Web.UI.Page

{
DataAccess data = new DataAccess();
int total = 0;
protected void Page_Load(object sender, EventArgs e)
{
data.DBDataAdapter("select productList.proid as [Transaction Id],productList.pname as

[Product Name],productList.prate as [Product Rate],productList.pqty as [Quantity],ptotal as
[Product Total] from productList where proId=" + Convert.ToInt32(Session["traId"].ToString()),
gvProducts);
gvProducts.FooterRow.Cells[2].Text = "Your Toatal Amount is : ";
data.DBReaderOpen("select ptotal from productList where proId=" +

Convert.ToInt32(Session["traId"].ToString()));
if (data.dr.HasRows)
{
while (data.dr.Read())
{
total +=Convert.ToInt32( (data.dr["ptotal"].ToString()));
}
}
gvProducts.FooterRow.Cells[3].Text = total.ToString();
}
protected void ibPay_Click(object sender, ImageClickEventArgs e)
{
Session["amt"] = total;
Response.Redirect("pgTransaction.aspx");
}
}
New Card.aspx
<%@ Page Language="C#" MasterPageFile="~/Master.master" AutoEventWireup="true"

CodeFile="pgNewCard.aspx.cs" Inherits="pgNewCard" Title="Untitled Page" %>
<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
<table style="width: 490px; height: 340px">
<tr>
<td style="width: 46px; height: 21px">
</td>
<asp:Label ID="lblerror" runat="server" Font-Bold="True" Font-Size="Larger"
ForeColor="Red"
Text="Sorry The Card Number Already Exisit" Visible="False"
Width="285px"></asp:Label></td>
</td>
</tr>
<tr>
<br />
<asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Size="Small"
Height="12px"
Text="CARD NUMBER :" Width="115px"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtCardNo" runat="server" MaxLength="16" Width="155px"
Height="20px" AutoPostBack="True"
OnTextChanged="txtCardNo_TextChanged"></asp:TextBox></td>
</td>
</tr>
<tr>
<td style="width: 46px">
<br />
Height="12px"
Text="ACCOUNT NUMBER:" Width="124px"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtACNO" runat="server" MaxLength="20"
Width="153px" Height="20px"></asp:TextBox></td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
ControlToValidate="txtACNO"
ErrorMessage="RequiredFieldValidator" Font-Bold="True" Font-
Size="Large">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
Height="13px"
Text="BANK NAME :" Width="118px"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtBankName" runat="server" Height="22px"
Width="230px"></asp:TextBox></td>
ControlToValidate="txtBankName"
</tr>
<tr>
<br />
Height="23px"
Text="ACCOUNT HOLDER NAME :" Width="141px"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtACName" runat="server" Width="190px"
Height="24px"></asp:TextBox></td>
ControlToValidate="txtACName"
</tr>
<tr>
<br />
<br />
<br />
Text="ADDRESS"
Width="115px"></asp:Label><br />
</td>
<asp:TextBox ID="txtAddress" runat="server" Height="47px"
TextMode="MultiLine" Width="251px"></asp:TextBox></td>
ControlToValidate="txtAddress"
</tr>
<tr>
<td style="width: 46px; height: 59px;">
<br />
Text="CREDIT LIMIT"
<br />
</td>
<asp:TextBox ID="txtAmt" runat="server" Width="92px"
Height="22px"></asp:TextBox></td>
ControlToValidate="txtAmt"
</tr>
<tr>
<br />

  </td>
<div
style="text-align: center">
<tr>
<asp:LinkButton ID="btnSubmit" runat="server" Font-Bold="True" Font-
Names="Palatino Linotype"
Font-Size="Large"
OnClick="btnSubmit_Click">SUBMIT</asp:LinkButton></td>
<asp:LinkButton ID="LinkButton1" runat="server"
CausesValidation="False" Font-Bold="True"
Font-Names="Palatino Linotype" Font-
Size="Large">CANCEL</asp:LinkButton></td>
</tr>
</table>
</div>
</td>
</td>
</tr>
</table>
</asp:Content>
Login.aspx

CodeFile="pgLogin.aspx.cs" Inherits="pgLogin" Title="Untitled Page" %>

<div style="text-align: center">

<table>
<tr>
<table>
<tr>
<asp:Label ID="Label1" runat="server" Text="UserName" Font-
Bold="True"></asp:Label></td>
<asp:TextBox ID="txtUName" runat="server" Height="21px"
Width="155px" Font-Size="Medium"></asp:TextBox>
</td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2"
runat="server" ControlToValidate="txtUName"
ErrorMessage="UserName
Required">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<asp:Label ID="Label2" runat="server" Text="Password" Font-
Bold="True"></asp:Label></td>
<asp:TextBox ID="txtPass" runat="server" Height="24px"
Width="155px" Font-Size="Medium" TextMode="Password"></asp:TextBox>
</td>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1"
runat="server" ControlToValidate="txtPass"
ErrorMessage="Password
Reqiured">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
</td>
<asp:ValidationSummary ID="ValidationSummary1" runat="server"
Height="32px" Width="123px" Font-Bold="True" />
<br />
<div style="text-align: left">
<asp:Label ID="Label3" runat="server" Font-Bold="True"
ForeColor="Red" Text="Invalid User Or Password"
Visible="False" Width="151px"></asp:Label>
</div>
<br />
</td>
</td>
</tr>
</table>
<tr>
<asp:LinkButton ID="btnLogin" runat="server" Font-Size="Large"
OnClick="btnLogin_Click">Login</asp:LinkButton></td>
<asp:LinkButton ID="btnCancel" runat="server" Font-Size="Large"
CausesValidation="False" OnClick="btnCancel_Click">Cancel</asp:LinkButton></td>
</tr>
</table>
</div>
<div style="text-align: right">
<br />
</div>
</td>
</tr>
</table>
<div style="text-align: right">
<table>
<tr>
<asp:HyperLink ID="HyperLink1" runat="server" Font-Bold="True" Font-
Italic="True"
Font-Names="Palatino Linotype" Font-Size="Large" ForeColor="Blue"
NavigateUrl="~/pgNewCard.aspx">New User?</asp:HyperLink></td>
</tr>
</table>
</div>

<br />
</div>
</div>
</asp:Content>
Login.cs
using System;
using System.Data;
using System.Web;
public partial class pgLogin : System.Web.UI.Page

{
{
Session.Clear();
Session.Clear();
}
protected void btnLogin_Click(object sender, EventArgs e)
{
data.DBReaderOpen("Select * from Login where Uname='" + txtUName.Text + "' and pwd
= '" + txtPass.Text + "'");
{
data.dr.Read();
string roll = data.dr["Roll"].ToString();
if (roll.ToString() == "Admin")
{
Response.Redirect("pgadmin.aspx");
}
else
{
Session["uid"] = data.dr["uid"].ToString();
Response.Redirect("pgUsers.aspx");
}
}
else
{
Label3.Visible = true;
}
}
protected void btnCancel_Click(object sender, EventArgs e)
{
Response.Redirect("pgHome.aspx");
}
}
Newuser.aspx
CodeFile="pgNewUser.aspx.cs" Inherits="pgNewUser" Title="Untitled Page" %>
<tr>
</td>
<asp:Label ID="lblError" runat="server" Font-Bold="True" Font-Size="Larger"
ForeColor="Red" Visible="False" Width="285px"></asp:Label></td>
</td>
</tr>
<tr>
<br />
<asp:Label ID="Label17" runat="server" Text="Card Number" Width="94px" Font-
Bold="True"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtCardNo" runat="server" AutoPostBack="True" Height="20px"
MaxLength="16"
OnTextChanged="txtCardNo_TextChanged" Width="168px" Font-Bold="True"
Font-Size="Small"></asp:TextBox></td>
<asp:RangeValidator ID="RangeValidator2" runat="server"
ControlToValidate="txtCardNo"
MaximumValue="9999999999999999" MinimumValue="1111111111111111"
Font-Bold="True" Type="Double">*</asp:RangeValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label1" runat="server" Text="First Name" Font-Bold="True"
<br />
</td>
<asp:TextBox ID="txtFName" runat="server" Height="20px"
ControlToValidate="txtFName"
ErrorMessage="Name Is Required" Font-
Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label2" runat="server" Text="Last Name" Font-Bold="True"
<br />
</td>
<asp:TextBox ID="txtLName" runat="server" Height="20px"
</td>
</tr>
<tr>
<br />
<asp:Label ID="Label3" runat="server" Text="Desired Login Name" Width="145px"
Font-Bold="True"></asp:Label><br />
<br />
</td>
<asp:TextBox ID="txtLogin" runat="server" Height="20px"
ControlToValidate="txtLogin"
ErrorMessage="Login Name Required" Font-
</tr>
<tr>
</td>
<asp:LinkButton ID="btnAvail" runat="server" CausesValidation="False"
OnClick="btnAvail_Click"
Width="127px" Font-Bold="True" Font-Size="Larger" ForeColor="Blue">Check
Availablility</asp:LinkButton>
<br />
<asp:Label ID="lblAvail" runat="server" ForeColor="Red" Text="Sorry The
UserName Not Available"
Visible="False" Width="285px" Font-Bold="True" Font-
Size="Larger"></asp:Label></td>
</td>
</tr>
<tr>
<br />
<asp:Label ID="Label4" runat="server" Text="Password" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtPass" runat="server" Height="20px"
Width="156px" TextMode="Password"></asp:TextBox></td>
ControlToValidate="txtPass"
ErrorMessage="Password Rrequired" Font-
</tr>
<tr>
<br />
<asp:Label ID="Label5" runat="server" Text="Confirm Password" Width="145px"
<br />
</td>
<asp:TextBox ID="txtConPass" runat="server" Height="20px" Width="156px"
TextMode="Password"></asp:TextBox></td>
<asp:CompareValidator ID="CompareValidator1" runat="server"
ControlToCompare="txtPass"
ControlToValidate="txtConPass" ErrorMessage="Password Mismatch" Font-
Bold="True">*</asp:CompareValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label6" runat="server" Text="Email" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtEmail" runat="server" Height="20px"
<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"
ControlToValidate="txtEmail"
ErrorMessage="Invalid Email" ValidationExpression="\w+([-+.']\w+)*@\w+([-
.]\w+)*\.\w+([-.]\w+)*" Font-Bold="True">*</asp:RegularExpressionValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label15" runat="server" Text="Phone No" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtPhone" runat="server" Height="20px"
ControlToValidate="txtPhone"
ErrorMessage="*" MaximumValue="999999999999999" MinimumValue="111"
Type="Double"></asp:RangeValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label14" runat="server" Text="Date Of Birth" Width="145px" Font-
</td>

<table>
<tr>
<asp:TextBox ID="txtDate" runat="server" Height="20px"
MaxLength="10" Width="158px"></asp:TextBox></td>
<td>
</td>
<td>
</td>
<asp:Label ID="Label18" runat="server" Text="(dd/mm/yyyy)"
Width="117px" Font-Bold="True"></asp:Label></td>
</tr>
</table>
</div>
</td>
ControlToValidate="txtDate"
ErrorMessage="DOB Required" Font-
</tr>
<tr>
<br />
<asp:Label ID="Label8" runat="server" Text="Gender" Width="145px" Font-
<br />
</td>
<asp:DropDownList ID="ddlGender" runat="server" Width="79px">
<asp:ListItem Selected="True">Male</asp:ListItem>
<asp:ListItem>Female</asp:ListItem>
</asp:DropDownList></td>
ControlToValidate="ddlGender"
ErrorMessage="Gender Is Required" Font-
</tr>
<tr>
<br />
<asp:Label ID="Label9" runat="server" Text="AddressLine 1" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtAdd1" runat="server" TextMode="MultiLine" Height="50px"
Width="224px"></asp:TextBox><br />
</td>
ControlToValidate="txtAdd1" Font-Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label10" runat="server" Text="Addresss Line 2" Width="145px"
</td>
<br />
<br />
<asp:TextBox ID="txtAdd2" runat="server" TextMode="MultiLine" Height="51px"
ControlToValidate="txtAdd2" Font-Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label11" runat="server" Text="City" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtCity" runat="server" Height="20px"
ControlToValidate="txtCity" Font-Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label12" runat="server" Text="State" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtState" runat="server" Height="20px"
ControlToValidate="txtState" Font-Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label13" runat="server" Text="Country" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtCountry" runat="server" Height="20px"
ControlToValidate="txtCountry" Font-Bold="True">*</asp:RequiredFieldValidator></td>
</tr>
<tr>
<br />
<asp:Label ID="Label7" runat="server" Text="Pincode" Width="145px" Font-
<br />
</td>
<asp:TextBox ID="txtPin" runat="server" Height="20px"
Width="95px"></asp:TextBox>
</td>
ControlToValidate="txtPin"
ErrorMessage="*" MaximumValue="9999999999" MinimumValue="11"
Type="Double"></asp:RangeValidator></td>
</tr>
<tr>
<asp:Label ID="Label16" runat="server" Text="Terms of Service" Width="141px"
</td>
<br />
<asp:TextBox ID="txtTerms" runat="server" TextMode="MultiLine" Font-
Bold="False" Font-Names="Times New Roman" Font-Size="Medium" Height="93px"
ReadOnly="True" Width="340px">Terms of Service
</asp:TextBox></td>
</td>
</tr>
<tr>
</td>
<table>
<tr>
<asp:RadioButtonList ID="rblTerms" runat="server" Font-Bold="True"
Height="53px" Width="208px">
<asp:ListItem Value="1"> I Accepted</asp:ListItem>
<asp:ListItem Value="0"> I Am Not
Accepted</asp:ListItem>
</asp:RadioButtonList></td>
</tr>
</table>
</div>
</div>
</td>
</td>
</tr>
<tr>
</td>
<tr>
<asp:LinkButton ID="btnSub" runat="server"
Font-Bold="True" Font-Names="Tahoma" Font-Size="Large"
OnClick="btnSub_Click">SUBMIT</asp:LinkButton></td>
<asp:LinkButton ID="btnCancel" runat="server" CausesValidation="False"
Font-Bold="True"
Font-Names="Tahoma" Font-Size="Large"
OnClick="btnCancel_Click">CANCEL</asp:LinkButton></td>
</tr>
</table>
</div>
</td>
</td>
</tr>
</table>
</asp:Content>
Newuser.cs
using System;
using System.Data;
using System.Web;
using System.Data.SqlClient;
public partial class pgNewUser : System.Web.UI.Page

{
{
txtCardNo.Focus();
}
protected void btnAvail_Click(object sender, EventArgs e)
{
data.DBReaderOpen("select * from Login Login where UName='" + txtLogin.Text + "'");
{
lblAvail.Text = "UserName Not Available";

lblAvail.Visible = true;
txtLogin.Focus();
}
else
{
lblAvail.Text = "UserName Available";
lblAvail.Visible = true;
txtPass.Focus();
}
}
protected void txtCardNo_TextChanged(object sender, EventArgs e)

{
data.DBReaderOpen("select * from userinfo where cardNo='" + txtCardNo.Text + "'");
{
lblError.Text = "Sorry The Card Number Already Exisit";
lblError.Visible = true;
txtCardNo.Focus();
rblTerms.Enabled = false;
}
else
{
lblError.Visible = false;
rblTerms.Enabled = true;
txtFName.Focus();
}
protected void btnCancel_Click(object sender, EventArgs e)

{
}
protected void btnSub_Click(object sender, EventArgs e)
{
if (Convert.ToInt32( rblTerms.SelectedItem.Value) == 1)
{
int uid = 0;
data.DBReaderOpen("select max(Uid)from userinfo");
{
data.dr.Read();
string ss = data.dr[0].ToString();
if (ss == "")
{
uid = 101;
}
else
{
uid = Convert.ToInt32(ss.ToString()) + 1;
}
data.DBOpen();
data.cmd = new SqlCommand("userInfo_SP", data.cn);
data.cmd.CommandType = CommandType.StoredProcedure;
data.cmd.Parameters.Add(new SqlParameter("@mode", 1));

data.cmd.Parameters.Add(new SqlParameter("@FirstName", txtFName.Text));
data.cmd.Parameters.Add(new SqlParameter("@LastName", txtLName.Text));
data.cmd.Parameters.Add(new SqlParameter("@Uid", uid));
data.cmd.Parameters.Add(new SqlParameter("@UName", txtLogin.Text));
data.cmd.Parameters.Add(new SqlParameter("@pwd", txtPass.Text));
data.cmd.Parameters.Add(new SqlParameter("@Email", txtEmail.Text));
data.cmd.Parameters.Add(new SqlParameter("@DOB",
Convert.ToDateTime(txtDate.Text)));
data.cmd.Parameters.Add(new SqlParameter("@Gender",
ddlGender.SelectedItem.ToString()));
data.cmd.Parameters.Add(new SqlParameter("@address1", txtAdd1.Text));
data.cmd.Parameters.Add(new SqlParameter("@address2", txtAdd2.Text));
data.cmd.Parameters.Add(new SqlParameter("@city ", txtCity.Text));
data.cmd.Parameters.Add(new SqlParameter("@state", txtState.Text));
data.cmd.Parameters.Add(new SqlParameter("@country", txtCountry.Text));
data.cmd.Parameters.Add(new SqlParameter("@pincode", Convert.ToInt32(txtPin.Text)));
data.cmd.Parameters.Add(new SqlParameter("@phone", Convert.ToInt32(txtPhone.Text)));
data.cmd.Parameters.Add(new SqlParameter("@CardNo", txtCardNo.Text));
try
{
data.cmd.ExecuteNonQuery();
}
catch (Exception ex)
{
}
data.DBCmdClose();
Session["Uid"] = uid;
Response.Redirect("pgSecurity.aspx");
}
else
{
lblError.Text = "You Must Accept the Terms and Conditions";
lblError.Visible = true;
}
}
}
SAMPLE SCREENS
SOFWARE DESIGNING
SYSTEM DESIGN
The most creative and challenging phase of system lifecycle is the system design. System design
is the process that states the details of how a system will meet the requirements identified during
system analysis. When the analyst prepares logical system design, they specify the user needs at
level of detail that virtually determines information flow into and out of the system and the
required data source. First step in the design is to determine how the output is to be produced and
in what format. Secondly, input data and master files have to be designed to meet the
requirement of proposed output. Finally, the end of the design phase, the system flow chart will
be ready which is used as the base of coding phase.
SYSTEM FLOW CHART
A high level view of the organization of a system can be shown by system flowchart. The
rectangular boxes represent original aggregates of computer software. It is often very useful
diagram for the system designers who must develop overall system architecture of hardware and
software to implement the user requirements. There is one situation where the system flowcharts
could be a useful modeling tool: At the end of the system analyst’s activity, when the user
implementation model is being developed. At this point, the user, the system analyst, and the
implementation team discuss the implementation constraints that must be imposed upon the
system: these include such things as the determination of the automation boundary and the
human interface. Input design is creative as well as technical activity, which includes the
following tasks.
 Approaching the terms of reference.

 Designing the format medium of files.
 Determining methods of data capture and data input.
 Designing forms.
INPUT DESIGN
The input of a system can be defined as the information that is provided to the system. This is
used for future processing by the system to obtain meaningful information, which helps in
decision-making. Input design is the process of converting user-oriented inputs to a computer-
based format. Input is a part of overall system design, which requires special attention.
Inaccurate input data are the most common cause of errors in error processing. Input design can
control errors entered by data entry operators. Entered data have to be checked for their accuracy
and direction of errors. Appropriate error message have to be displayed. When an invalid data is
entered, the user should not be allowed to type it.
OUTPUT DESIGN
The computer output is the most important and direct source of information to the user. Efficient
and intelligible output design improves the system’s relationship with the user and helps in
decision-making. Output design was studied going actively during the study phase. The objective
of the output design is defined the contents and format of all documents and reports in an
attractive and useful format.
Types of Outputs
 External output
 Internal output
 Operational outputs
 Interactive outputs
Output generally refers to the results and information that are generated by the system. It can be
in the form of operational documents and reports. The major form of output is a hard copy from
the printer. Once the output requirements are identified, the output devices used also should be
determined. Factors like compatibility of the output device with the system and response time
requirement should be considered while descending the output device to be utilized.
DEVELOPMENT MODEL
The development phase focuses on how the engineer attempts to develop the system. It also deals
with how data are to be structured, how the function is to be implemented within software
architecture, how procedural details are to be implemented, how interfaces are characterized,
how the design will be translated into a programming language, and how testing will be
performed. The methods applied during the development phase will vary but three specific
technical tasks should always occur.
 Software design
 Code generation
 Software testing
The classical life cycle model or the linear sequential model is a systematic and sequential
approach to software development. It progress through analysis, design, coding, testing and
support.
ANALYSIS
The requirements gathering process is intensified and focused on software. The nature of the
programs to be built, the software engineer must understand the information domain for the
software, as well as required function, behavior, performance and interface. Requirements for
both the system and software are documented and reviewed with the customer.
DESIGN
Software design actually a multistep process that focuses on four attributes of a program: data
structure, software architecture, interface representations and procedural detail. The design
process translates the requirements into a representation of the software that can be assessed for
the quality before coding begins.
CODE GENERATION
The design must be translated into a machine-readable form. The code generation step performs
this task. If the design is performed in a detailed manner, code generation can be accomplished
mechanistically. The requirement was converted into code.
CHAPTER 7
SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub assemblies, assemblies and/or a finished product. It is the
process of exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
6.2 TYPES OF TESTING
6.2.1 UNIT TESTING
Unit testing involves the design of test cases that validate that the internal program logic
is functioning properly, and that program input 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.
Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.
Test Strategy and approach:
Field testing will be performed manually and functional tests will be written in detail.
Test objectives:
 All field entries must work properly.

 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.
 Features to be tested
6.2.2 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.
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.
The task of the integration test is to check that components or software applications, e.g.
components in a software system or – one step up – software applications at the company level –
interact without error.
6.2.3 FUNCTIONAL TESTING
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.
6.2.4 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, emphsizing pre-driven process links and integration points.
6.2.5 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.
6.2.6 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.
6.2.7 ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.
TEST RESULTS
All the test cases mentioned above passed successfully. No defects encountered.
CHAPTER 8
CONCLUSION
We have presented a framework and an approach for multilevel monitoring of service

systems. It draws inspiration from the language-action perspective and extends recent work
related to commitments. The key contributions, specific to the use of language-action
perspective, include the following:.
Specification of an ontology of communicative acts that adds semantic content to
messages. Support for the specification of policies that address standard and extended effects of
communicative effects for multilevel monitoring
CHAPTER 9
BIBLIOGRAPHY
Good Teachers are worth more than thousand books, we have them in Our Department
References Made From:
1. User Interfaces in C#: Windows Forms and Custom Controls by Matthew MacDonald.
2. Applied Microsoft® .NET Framework Programming (Pro-Developer) by Jeffrey Richter.
3. Practical .Net2 and C#2: Harness the Platform, the Language, and the Framework by
Patrick Smacchia.
4. Data Communications and Networking, by Behrouz A Forouzan.
5. Computer Networking: A Top-Down Approach, by James F. Kurose.
6. Operating System Concepts, by Abraham Silberschatz.
7. M. Armbrust, A. Fox, R. Griffith, A. D. Joseph, R. H. Katz, A. Konwinski, G. Lee, D.

A. Patterson, A. Rabkin, I. Stoica, and M. Zaharia, “Above the clouds: A berkeley view
of cloud computing,” University of California, Berkeley, Tech. Rep. USB-EECS-2009-
28, Feb 2009.
8. “The apache cassandra project,” http://cassandra.apache.org/.
CHAPTER 10
BOOKS & WEBSITES
Books:
• Pro ASP.NET 3.5 in C# 2008 (Apress)
• Unleashed ASP.NET 2.0 (SAMS Publication)
• ASP.NET Bible
• The Complete Reference Asp.net
• Professional VB.NET 3.5 with Visual Basic (Wrox)
Sites Referred:
http://www.sourcefordgde.com
http://www.networkcomputing.com/
http://www.ieee.org
http://www.almaden.ibm.com/software/quest/Resources/
http://www.computer.org/publications/dlib
http://www.ceur-ws.org/Vol-90/

Credit Score Analaysis Project

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Credit Score Analaysis Project

Uploaded by

Copyright:

Available Formats

ABSTRACT

Security a major Concern:

2. Security is always a major concern in Open System Architectures

1. Data store in database of provider should be redundantly store in multiple physical

3. Control of Administrator on Databases.

1. Sanitization is the process of removing sensitive information from a storage device.

2. Like DNS Hacking, Routing Table “Poisoning”, XDoS attacks

3. QoS Violation : through congestion, delaying or dropping packets, or through resource

4. Man in the Middle Attack: To overcome it always use SSL

5. IP Spoofing: Spoofing is the creation of TCP/IP packets using somebody else's IP

How secure is encryption Scheme:

1. Is it possible for all of my data to be fully encrypted?

2. What algorithms are used?

3. Who holds, maintains and issues the keys? Problem:

5. Encryption can complicate availability Solution

2. This issues pertaining to secure communication, authentication, and issues concerning

A number of important performance metrics like True Positive—False Positive (TP-FP)

It is based on artificial intelligence and combines inductive learning algorithms and

When complex problem and opportunities are to be defined, it is generally desirable to

Feasibility study is undertaken to evaluate its workability, impact on the organization,

The primary objective of a feasibility study is to assess three types of feasibility.

1) Technical feasibility: can a solution be supported with existing technology?

2) Economical feasibility: is existing technology cost effective?

3) Operational feasibility: will the solution work in the organization if implemented?

A systems development project may be regarded as technically feasibility or ‘practical’ if

• Knowledge of current and emerging technological solutions.

• Availability of infrastructure in house to support the development and maintenance of the

• Where necessary, the financial and/or technical capacity to procure appropriate

3.2 ECONOMIC FEASIBILITY

A systems development project may be regarded as economically feasible or ‘good

A systems development project is likely to be operationally feasible if it meets the

FEASIBILITY STUDY OF THE PROPOSED SYSTEM

3.4 ECONOMIC FEASIBILITY

3.5 OPERATIONAL FEASIBILITY

4.1 HARDWARE REQUIREMENTS:

Processor : Pentium series

RAM(Primary Processor) : 512 MB RAM

Hard Disk Capacity : 20GB

Monitor : Colors/SVGA(800 x 600)

Printer : Laser Compatible

4.2 SOFTWARE REQUIREMENTS:

The software used is as follows:

Operating System Windows XP

Platform Microsoft .Net Frame Work

Front End ASP.NET and C# 2008

Back End Microsoft SQL Server 2005

Problem & Assign requirements to Design System

Develop Testing of Integrate Validate

Fig 1.1: Addition of extra modules (Future Enhancements)

4.2.1 INCREMENTAL SOFTWARE METHODOLOGY

“Incremental Developmental Software Methodology” is followed in this project. As new

4.2 FRONT END USED:

4.2.1 FEATURES OF MICROSOFT VISUAL STUDIO DOT NET:

 Toolbars provide quick access to commonly used commands in the programming

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the

COMMON LANGUAGE SPECIFICATION

THE CLASS LIBRARY

Microsoft Visual J# .NET provides the easiest transition for Java-language

4.3.1 FEATURES OF SQL SERVER 2005

SQL-SERVER database consist of five type of objects.