Safehands

SAFEHANDS
MAR ATHANASIOS COLLEGE FOR ADVANCED STUDIES

TIRUVALLA
Affiliated to
MAHATMA GANDHI UNIVERSITY, KOTTAYAM
SAFE HANDS
PROJECT REPORT
Submitted by
SHEEBA ABRAHAM THAZHAYIL
Reg No: 60746
Submitted in partial fulfillment of the requirement for the

Award of the degree of
MASTER OF COMPUTER APPLICATIONS
(2005-2008)
Department of Computer Applications

MACFAST, Tiruvalla
SAFE
HANDS

TIRUVALLA
CERTIFICATE
This is to certify that the project report entitled SAFE HANDS submitted in partial
fulfillment of the requirement for the award of the degree of Master of Computer
Applications of Mahatma Gandhi University, Kottayam is a bonafied record of
project work done by SHEEBA ABRAHAM THAZHAYIL, Reg. No. 60746 during
the year 2008.
Mr. Ajith G.S Mr. Tiji Thomas

Internal Guide Head of the department, MCA
Rev. Dr Abraham Mulamoottil

Principal
SAFE
HANDS

TIRUVALLA
CERTIFICATE
Certified that the candidate SHEEBA ABRAHAM THAZHAYIL was examined by

us in the project work entitled SAFE HANDS and viva-voice examination held on …
…………………………..
Internal Examiner External Examiner

Date:
SAFE HANDS
DECLARATION
I, SHEEBA ABRAHAM THAZHAYIL do hereby declare that the project work

entitled “SAFE HANDS” done for MIND PARLOUR LEARNING SYSTEMS
PVT. LTD. is in partial fulfillment of the requirement for the award of the Degree of
MASTER OF COMPUTER APPLICATIONS is a report of the original work done
by me under the supervision and support of Mr. Ajith G.S , Internal Guide, Lecturer,
Mar Athanasios College For Advanced Studies, Tiruvalla. A similar work has not been
submitted earlier to Mahatma Gandhi University, for a course of study from Mar
Athanasios College For Advanced Studies, Tiruvalla.
SHEEBA ABRAHAM THAZHAYIL

Reg No. 60746
Place: Tiruvalla
Data:
SAFE HANDS
ACKNOWLEDGEMENT
An undertaking like this would not have been possible without the support of a
number of persons of various talents. I make use of this opportunity to express my
gratitude who have helped me to bring out the project entitled SAFE HANDS.
First and foremost, I thank GOD Almighty for giving me the opportunity to complete
this project successfully. I am grateful for all his blessings and his great care.
I am highly obliged to our Principal, Rev. Dr. Abraham Mulamoottil, for being the
source of inspiration and for his complete co-operation throughout my MCA course. I
express my deep sense of gratitude to our Director, Dr. M S Samuel for his
encouragement and support throughout this project.
I hereby solicit my heartfelt thanks to Mr. Tiji Thomas, Head of MCA Department,
for providing me constant support and help throughout this project.
I am very much grateful and indebted to my Internal Guide, Mr. Ajith G.S, for his
constant guidance and advice that helped me to compile, print and present this project
work at the right time in the right way.
I sincerely thank Mr. Sajeev Nair, Chief Mentor of Mind Parlour Learning
Systems Pvt. Ltd. for giving me the permission to do my project work at his
prestigious company. Also, my profound gratitude goes to Mrs. Preetha Anil,
Project Guide, Mind Parlour Learning Systems. I acknowledge her inestimable
support and extensive guidance showered on me.
I thank my family and friends for their constant encouragement and moral support.
Sheeba Abraham Thazhayil

SAFE HANDS
ABSTRACT
The technological revolution has caused a boom in the field of computers. With the
development of computers and software’s, much tedious work for workers has
become a simple job. Taking into consideration the present scenario, the project
entitled “SAFE HANDS” is a software designed for user’s help. This project is a step
taken to provide insurance services over the internet. The main focus of the project
has been on life, vehicle and health insurance.
In any insurance, various operations such as applying for policies and loans, renewal
and revival of policies, premium calculation, payment and receiving bills, checking
policy status as well as filing of claims are mostly done manually. The work is
usually done using paper and computer is used as a calculating device and a storage
device to some extent, and there are some records that are stored in files. When it
comes to retrieving or searching some information, it becomes hectic and tedious job
to do so. It also creates a lot of confusion and chaos leading to delay of work. Thus, it
slows down the overall performance of the insurance administration and management.
SAFE HANDS is very effective in producing accurate results with in a short period of
time and thereby providing a great support in transferring any confidential
information without the fear of losing it on to the wrong hands. While comparing with
other top three insurance companies such as Bajaj Allianz, Oriental and LIC only
SAFE HANDS clubs life, health and vehicle insurance. This software brings you its
flying colors of efficiency. It helps the Administrator to manage the various services
of insurance conveniently and effectively.
SAFE HANDS
TABLE OF CONTENTS
DECLARATION
...........................................................................................................1
ABSTRACT...........................................................................................3
1.INTRODUCTION.................................................................................5
1.1 ORGANIZATION PROFILE......................................................................................... ..5
1.2 ABOUT THE PROJECT................................................................................ ..............6
1.3 OBJECTIVE OF THE PROJECT............................................................... .......................1
1.SYSTEM ANALYSIS.............................................................................3
1.4 INTRODUCTION................................................................................. ....................3
2.3 PROPOSED SYSTEM............................................................................................ ...5
BENEFITS OF THE PROPOSED SYSTEM...................................................6
1.5 FEASIBILITY STUDY........................................................................ ........................6
1.5.1 Economic Feasibility.......................................................................... .....7
1.5.2 Technical Feasibility...................................................... .........................7
1.5.3 Behavioral Feasibility......................................................... ....................7
1.6 PROJECT DESCRIPTION....................................................................... .....................8
2.SYSTEM REQUIREMENT AND SPECIFICATION.......................................9
1.7 HARDWARE REQUIREMENTS (MINIMUM)...........................................................9
CLIENT WORKSTATIONS / DESKTOPS.................................................. ................9
10
1.8 SOFTWARE REQUIREMENTS (MINIMUM)..........................................................10
1.9 SOFTWARE OVERVIEW......................................................................................... ..11
3.3.2 Languages and Tools used........................................ ..........................13
PHP 13
FOLLOWING ARE SOME OF THE FEATURES OF PHP:...................................................... .........15
FAST AND EASY............................................................................................ ...........15
THERE ARE REALLY ONLY THREE THINGS THAT WE KNOW FOR SURE WHEN IT COMES TO COMPRISING SPEEDS OF
WEB PROGRAMMING LANGUAGES. FIRST, APPLICATIONS WRITTEN IN C WILL BE THE FASTEST. SECOND,
PROGRAMMING IN C IS RATHER DIFFICULT AND WILL TAKE MUCH LONGER THAN ANY OF OTHER LANGUAGES
MENTIONED SO FAR. THIRD, COMPARISONS BETWEEN LANGUAGES ARE EXTREMELY DIFFICULT. FROM EVERYTHING
WE KNOW, WE FEEL SAFE IN SAYING THAT PHP IS AS FAST AS ANYTHING OUT THERE. PHP OFFERS THE BEST
OPPORTUNITY TO DEVELOP POWERFUL WEB APPLICATIONS QUICKLY. THAT GENERALIZATION MADE, WE DO
BELIEVE THERE ARE OTHER EXCELLENT REASONS FOR CHOOSING PHP............................................15
CROSS PLATFORM................................................................................................ .....15
IN THE RUNDOWN OF WEB ARCHITECTURE, WE MENTIONED THAT PHP WOULD RUN ON WINDOWS 2000/
NT AND UNIX AND WITH BOTH IIS AND APACHE. BUT THE CROSS-PLATFORM ABILITIES OF PHP GO FAR
BEYOND THESE PLATFORMS. IF WE HAPPEN TO BE USING NETSCAPE, ROXEN, OR JUST ABOUT ANYTHING ELSE, IT
IS LIKELY THAT PHP WILL WORK WITH IT. YES, ASP CAN BE RUN ON LINUX AND COLD FUSION AND CAN
WORK ON SOLARIS AND LINUX, AND JSP IS ADAPTABLE ACROSS MANY PLATFORMS. PHP ALSO WORKS WELL
ON A VARIETY OF SYSTEMS AS ANY OTHER AVAILABLE PRODUCT. .......................................... ........15
ACCESSES EVERYTHING...................................................................................... .........15
JAVASCRIPT....................................................................................................... ....16
BASIC ARCHITECTURE................................................................................ ................18
THE SERVER............................................................................................ ..............18
WEBSERVER....................................................................................................... ....19
APACHE ........................................................................................ ..................19
MIDDLEWARE.......................................................................... ...............................20
PHP BELONGS TO A CLASS OF LANGUAGES KNOWN AS MIDDLEWARE. THESE LANGUAGES WORK CLOSELY WITH
THE WEB SERVER TO INTERPRET THE REQUESTS MADE FROM THE WORLD WIDE WEB, PROCESS THESE
REQUESTS, INTERACT WITH OTHER PROGRAMS ON THE SERVER TO FULFILL THE REQUESTS, AND THEN INDICATE
TO THE WEB SERVER EXACTLY WHAT TO SERVE TO THE CLIENT’S BROWSER. THE MIDDLEWARE IS WHERE YOU
WILL BE DOING THE VAST MAJORITY OF YOUR WORK. IN ADDITION TO PHP, THERE ARE SEVERAL LANGUAGES
SAFE HANDS
THAT PERFORM SIMILAR FUNCTIONS. SOME OF THE MORE POPULAR CHOICES ARE ASP, PERL, AND COLD
FUSION............................................................................................... ..................20
RELATIONAL DATABASES.................................................................................. ............20
4. SYSTEM DESIGN...............................................................................4
4.1 SYSTEM DESIGN PRINCIPLES ......................................................... ..........................4
4.1.1 Logical Design ......................................................................... ..........17
4.1.2 Physical Design ............................................................... ...................19
4.1.3 Architectural Design ..................................................................... ......32
4.2 I/O DESIGN.......................................................................... ..........................32
4.3SYSTEM FLOW DIAGRAM...................................................................................... ..36
1.10 CONTEXT FLOW DIAGRAM....................................................................... .............38
1.11 DATA FLOW DIAGRAM............................................................... .........................38
5.SYSTEM TESTING.............................................................................10
5.2TESTING METHODS.......................................................................................... ....12
5.2.1Unit Testing....................................................................... ...................12
5.2.2Integration Testing........................................................ .......................13
5.2.3Validation Testing.................................................................. ...............13
5.2.4 User Acceptance Testing.................................................. ...................13
5.2.5 System Testing............................................................................ .........14
3.SYSTEM IMPLEMENTATION AND MAINTENANCE.................................28
1.12 IMPLEMENTATION............................................................................ ...................28
4.SCOPE FOR FUTURE ENHANCEMENTS................................................32
5.CONCLUSION...................................................................................34
9.
INTRODUCTION
ANNEURE...........................................................................................33
DOCTOR DETAILS
DATE 06.10.2008.................................................................... ............................39
USER DETAILS
DATE 06.10.2008................................................................................40
LIFEINSURANCE POLICY HOLDERS DATE
06.10.2008 .......................................................41
VEHICLEINSURANCE POLICY HOLDERS DATE
06.10.2008 .......................................................42
HEALTHINSURANCE POLICY HOLDERS
DATE 06.10.2008 ..............................................43
6.REFERENCES...................................................................................66
SAFE HANDS
SAFE HANDS
1. INTRODUCTION
1.1 Organization Profile
Mind Parlour Learning Systems Pvt. Ltd. provides the IT backbone for the
clients business. The expert technical team understands the application
requirements thoroughly, prepares architecture, develops, tests and finally
implements it. They rely on industry-standard software development practices
and rigorously test the applications to ensure defect-free delivery.
By judicious blend of Business analysis & Management with latest

technology, they develop state-of-the-art custom software & web based
applications. Mind Parlour enables reduction in time for resources spent for a
business process to take place for the clients and serves to eliminate functional
bottlenecks. They also traines and develops best practices methodology for
application development using C, C++, Java, .Net and PHP and also creates
new applications, providing full lifecycle support.
Mind Parlour Learning Systems, believes that "trust is the most valuable asset
that they earn from the customers”. This is the reason why they have gone out
of the way to ensure that every single project which is undertaken in the past
years has delivered real value to the customers and also the success-secret that
has helped them to convert short-term engagements into long-term
relationships. They also combine the best of emerging technologies with the
still valuable components of legacy systems.
Technology in mind and the enthusiasm at heart is what this company is all
about. Their vision is “to develop and deliver a value product to their
customers with high quality and cost effectiveness and with a focus on speed”.
Their mission is “to develop the high end technology solutions with constant
innovation, continuous improvement and value added services”.
Page | 5
SAFE HANDS
1.2 About the Project
SAFE HANDS is the key to all financial needs. It gives the freedom to make choices
by giving a sense of security and offers various products that fulfill the savings and
protection needs. The main focus of the project has been on life, vehicle and health
insurance. Through “SAFE HANDS” website, one can obtain the information about
the company. He can then apply for an insurance class of his interest such as life,
vehicle or health insurance and thereby, also requesting for more services and
information about the new policies. Once a policy is held, the user can avail certain
online services that are meant for policyholders. Thus, policyholders get a desired
lump sum after a specified period. However, the protection also continues for an
extended period. SAFE HANDS also gives the double benefit of life insurance along
with easy liquidity through lump sum cash, thereby, providing money periodically
when needed. If anything happens, the beneficiary would get another sum assured
along with the bonuses, for SAFE HANDS life comes first always. The administrator
is the super user or the person who manages the entire system. He also communicates
the information he receives, to the corresponding representatives of the insurance
company. Above all, SAFE HANDS helps to stay protected for tomorrow by giving
the flexibility of receiving a specified percentage of the Sum Assured at specified
intervals.
Page | 6
SAFE HANDS
1.3 Objective of the Project
The main objectives of the system are as follows: -
 To make avail for users, about the different categories of insurance and various
services carried out. The services include premium calculation, to know details
about nearest doctors or offices, also, to know in-depth about the new policies
the benefits there under of various insurance and thereafter can apply for an
insurance class of their choice such as life, vehicle or health insurance. At any
cost of time, permitting the users to directly contact the company.
 To develop a system where the insurance policyholders can avail some of the
insurance services online. Some of the online services such as, to log into their
accounts and request for more information about the new policies. Another
services such as to apply for policies and loans, renewal and revival of
policies, calculating premiums, paying online and to receive bills. To file
claims and check policy status the premiums due, the bonuses attached, the
surrender values and also to view the premium calendar as well as to get
information with regard to the nearest doctors or offices for any further
transactions are also some of the other important services to be considered.
 To provide, administrator with various services such as to add new plans,

branches and doctors, confirm or remove policyholders, issue or cancel loans,
to clear the doubts encountered for the users, at any cost of time as well as
setting premium rate and to receive information about the claims that are
posted.
Page | 1
SAFE HANDS
SYSTEM ANALYSIS
SAFE HANDS
1. SYSTEM ANALYSIS
1.4 Introduction
System Analysis is a standard procedure to organize and co-ordinate the various

activities of understanding the existing system or the system that needs to be
designed and implemented according to the user requirements. In any system
analysis, the first step is to study and understand the problem that needs to be
solved for the project to be undertaken. It is usually attained through preliminary
interview with the person or the organization’s personnel requesting the analysis
of the existing system. The feasibility study of the proposed system is done
through detailed study of the present system. Graphical tools like DFD’s are used
to construct the data flow and transform models of the system.
2.2 Existing System
For designing a new system, first we want to identify the costs and problems in
the existing system. For this, the existing system is examined. Normally a person
or a policyholder usually travels to the insurance office/company to either apply
for a new policy, renew a policy, to file a claim or to make relevant enquiries.
The payments of the premiums are made at the office itself. The policyholder
pays the premium amount by cash, cheque or credit card. At the time of making
a claim he has to submit the necessary and relevant documents in support of his
claim. The personnel at the insurance company will scrutinize the claim and take
the appropriate action. The company representatives will assist the customer or
policyholder in applying for a policy. The claims section representatives will
assist in filing a claim. All operations that are carried out by the insurance
company are in this fashion. As a result the customer tends to be visiting the
insurance office a number of times, which can at times be frustrating and tedious.
SAFE HANDS
Limitations of Existing System
The restrictions in the existing system are normally a policyholder usually travels
to the insurance company to either apply for a new policy, renew a policy or to file
a claim or to make relevant enquires, this is really time consuming. Travelling
expenses for each payment of the premium for the policyholder may not be
affordable. As forms are to be filled manually by the users, the chances of number
of bugs are increased and this leads to wastage of forms as well as the users have
to submit their relevant documents for verification which causes more the number
of visit to an insurance company. The agents have to go through number of files
which is tedious and time consuming. Apart from that there are chances of
inaccurate data entry and calculations that would lead to chain of problems. Also
there are security problems like unauthorized data views and access. Files
consume lots of space and it is a time consuming process to locate the
corresponding files. The other top three insurance companies are Bajaj Allianz,
Oriental and LIC. Here, through Bajaj Allianz, one can avail only services of life
and motor insurance. Also, other company such as Oriental and LIC provides
services for vehicle and life insurance to the users. So the key limitations of
existing system are as follows: -
 Lack of accuracy of data as the existing system is done manually.
 Includes manual work containing lots of paper of work
 The existing system lacks security of data because all the information are kept
in files and unauthorized persons may get access to them.
 More time consumption.
 Access of information is difficult.
 Lack of Validation.
 More storage area needed due to redundancy of data.

SAFE HANDS
2.3 Proposed System
The “SAFE HANDS” is an attempt to improve the existing Insurance process

by providing some of the services and operations over the company’s website.
A person can look at the “SAFE HANDS” website to obtain information about
the various categories of insurance and the services and operations provided by
it. Users can apply for a policy of their interest. Also, providing online
registration solves customer inconvenience. All essential documents can be
uploaded for verification, issues such as fingerprints and signatures are all
digitized. Existing policy holders can log into their accounts and check the
details of their policy, can get details of the various new policies, the benefits
there under, the premiums payable. Policyholders can get information with
regard to the status of the policy, the premiums due, the bonuses attached, the
surrender values, revival possibilities and loans available, as well as can also
locate nearest offices for any further transactions. Premiums can be paid
without having to go to the office of the insurer, by direct debit to the
policyholder’s credit card or bank account. The users, through “SAFE
HANDS”, sitting at his place of work, can obtain information about the
different branches as well as about the doctors of their near by places. Also, at
any cost of time, the users are permitted to contact directly thereby, solving
further clarifications. Only “SAFE HANDS” clubs all the information
regarding life, vehicle as well as health insurance.
Characteristics of the proposed System
 Can be easily accessible from a distant place

 Accuracy
 User Friendly
 Secure
 Increased Speed
SAFE HANDS
Benefits of the Proposed System
 Ease to implement.
 Fewer visits to insurance office.
 Elimination of data redundancy.
 Decreased response time.
 User friendly and easily accessible.
 Quick information retrieval.
 Hides the intricacies of the system from the end user.
 Validation checking is really an outstanding.
 Authorized users can only login. .
1.5 Feasibility Study
The initial investigation points to a question whether the project is feasible. A

feasibility study is conducted to identify the best system that meets all the
requirements. This entails identification description, an evaluation of proposed
systems and the selection of the best system for the job.
The result of a feasibility study is a formal proposal. The proposal summarizes

what is known and what is going to be done. It consists of:
• Statements of the problem.

• Summary of the findings and recommendations.
• Detail of the finding.
• Recommendations and conclusion.
The feasibility study determines whether the proposed system is flexible or

not. The SAFE HANDS is flexible and reduces cost. This present project
develops a system where the insurance policyholders and users can avail some
of the insurance services online and thereby minimizing his/her visit to the
SAFE HANDS
insurance office. The costs incurred from implementing this system is trifle
with respect to the benefits it gives.
The requirements of the system are specified with a set of constraints such as
system objectives and description of the outputs. It is then the duty of the
analyst to evaluate the feasibility of the proposed system to generate the above
results. The key factors to be considered during the feasibility study are:
1.5.1 Economic Feasibility

Economic feasibility is the most important and frequently used method for
evaluating the effectiveness of the proposed system. It is very essential
because the main goal of the proposed system is to have economically
better result along with the increased efficiency. The tool used in cost is
cost-benefit analysis. It is the comparative study of the cost versus the
benefit and savings that are expected from the proposed system. It reduces
unnecessary wastage of human hours and expenses.
1.5.2 Technical Feasibility

The main consideration given at this juncture is to the study of the
available resources of the organizations, where the project is to be
developed and implemented. Here the system analyst evaluates the
technical merits of the system given emphasis on the performance,
reliability, maintainability and productivity. The user needs a printer or
some other hardware to be added to the system that will raise the technical
complexity. Then the user has to check whether the system will support the
addition or not. This involves financial considerations to accommodate
technical enhancements.
1.5.3 Behavioral Feasibility

Behavioral feasibility determines how much effort will go into educating,
selling and training the user staff on a candidate system. People are
inherently resistant to change and computing has been known to facilitate
SAFE HANDS
change. Since the change is user friendly, user training is a very easy
matter.
1.6 Project Description
The Project entitled “SAFE HANDS” is a step taken to provide insurance services
over the internet. Insurance is a system under which individuals, business and other
organizations or entities in exchange for payment of sum money called premium are
guaranteed compensation of losses resulting from certain perils under specified
conditions in a contract. The main focus of the project has been on life, vehicle and
health insurance. The project is mainly divided into three modules for developing the
software. General User Module, PolicyHolder Module and Administrator Module.
A person viewing “SAFE HANDS”, website can obtain the information about the
company. He can then apply for an insurance class of his choice such as life, vehicle
or health insurance. He can also requests for more services such as premium
calculation, getting in-depth information about the new policies the benefits there
under as well as can obtain the details of nearest doctor locations and branch locations
for further transactions. At any cost of time, the users are permitted to directly contact
the company thus getting more information regarding a particular matter.
Once a policy is held, the user can avail certain online services that are meant for
policyholders. Online services include logging into their accounts and requesting for
more information about the new policies the benefits there under, applying for
policies and loans, renewal and revival of policies, calculating various premiums,
paying online and receiving bills, filing of claims, checking the policy status, the
premiums due, the bonuses attached, the surrender values and also checking the
premium calendar when the next premium has to be paid as well as obtaining
information with regard to the nearest doctors or offices for any further transactions.
The administrator is the super user or the person who manages the entire system. He
is responsible for adding and removing policyholders. He is the one who receives the
application send by the users who have shown interest in a particular policy. He also
receives information about the claims that have been posted as well as the details of
persons who have requested for more information regarding a particular matter be
furnished to them. The administrator then communicates the information he receives
to the corresponding representatives of the insurance company. The administrator is
provided with services such as adding new plans, branches and doctors, confirming or
SAFE HANDS
removing policyholders, issuing or canceling loans, premium rate setting as well as

clearing the doubts encountered for the users, at any cost of time.
SAFE HANDS
SYSTEM REQUIREMENTS
AND
SPECIFICATION
SAFE HANDS
2. SYSTEM REQUIREMENT AND SPECIFICATION
SAFE HANDS involves the following hardware and software requirements

and specifications.
1.7 HARDWARE REQUIREMENTS (Minimum)
WEB SERVER / DATABASE SERVER
PROCESSOR : Pentium IV or greater
MEMORY : 512 MB
HARD DISK DRIVE : 80 GB
KEYBOARD : Standard Keyboard
MOUSE : Standard Scroll Mouse
MONITOR : 17” SVGA Color Monitor.
CD-ROM : CD-RW or DVD-RW
CLIENT WORKSTATIONS / DESKTOPS
PROCESSOR : Pentium
MEMORY : 512 MB
HARD DISK DRIVE : 40 GB
KEYBOARD : Standard Keyboard
MOUSE : Standard Scroll Mouse
MONITOR : 17” SVGA Color Monitor.
Page | 9
SAFE HANDS
1.8 SOFTWARE REQUIREMENTS (Minimum)
SERVER SIDE:
OPERATING SYSTEM : Linux/Windows XP Professional
LANGUAGE : PHP
DATABASE : MySQL
WEBSERVER : Apache
CLIENT SIDE:
OPERATING SYSTEM : Linux/Windows
BROWSER : IE 6
Page | 10
SAFE HANDS
1.9Software Overview
3.3.1 Operating System
Windows NT is a family of operating systems produced by Microsoft, the first

version of which was released in July 1993. It was originally designed to be a
powerful high-level-language-based, processor-independent, multiprocessing,
multi-user operating system with features comparable to UNIX. It was
intended to complement consumer versions of Windows that were based on
MS-DOS. NT was the first fully 32-bit version of Windows, whereas it’s
consumer-oriented counterparts, Windows 3.1x and Windows 9x, were 16-
bit/32-bit hybrids. Windows 2000, Windows XP, Windows Server 2003,
Windows Vista, Windows Home Server, and Windows Server 2008 are based
upon the Windows NT system, although they are not branded as Windows NT.
FEATURES
 Reliability: The Windows NT operating system provides superior reliability,

so you can use it as a foundation for mission-critical applications. This
reliability makes Windows NT an ideal client workstation and network server
because both types of systems need to be up and running as much as possible.
 Performance: Windows NT was also designed to be a high-performance
operating system, as the following features demonstrate:
 True 32-bit design: Windows NT was written using 32-bit code
exclusively, providing an inherent speed advantage over operating systems
containing 16-bit technology. Windows 95, by contrast, continues to
employ 16-bit code for some of its functionality.
Page | 11
SAFE HANDS
 Multitasking and multiprocessing features: Windows NT’s preemptive

multitasking allows smooth and even simultaneous execution of all
running processes. Its multiprocessor support, lets the operating system
become instantly more powerful by spreading processes — and individual
threads of execution within processes — across multiple CPUs.
 Portability: Portability in Windows NT means that it isn’t tied to any
single architecture or technology; it can be ported to different types of
hardware without being completely rewritten. Windows NT offers the
following portability features:
 Modular, microkernel architecture
 Installable file system support
 Compatibility: Windows NT is compatible with the majority of existing

applications on the market. Specifically, it contains separate application
subsystems (or environments), each providing support for a different type of
application. Initially, this support would include MS-DOS, 16-bit Windows,
32-bit Windows, POSIX, and OS/2 1.x character-mode applications. Windows
NT is expandable to support future applications as well.
 Scalability: Windows NT is scalable; that is, it had to be able to take
advantage of increased hardware resources in larger, more powerful systems
without having to be rewritten. For example, on a multiprocessor system,
Windows NT divides tasks evenly across all processors to optimize the speed
of system operations.
 Security: Windows NT incorporates security features required by the U.S.
government and large businesses. These security features include such items
as an encrypted security database, permissions at the file level and the user
level, and a sophisticated user database design that would scale to the
enterprise level.
Page | 12
SAFE HANDS
3.3.2 Languages and Tools used
PHP
PHP (recursive acronym for "PHP: Hypertext Preprocessor") is a widely-used Open

Source general-purpose scripting language that is especially suited for Web
development and can be embedded into HTML. As it is mainly focused on server-side
scripting, so we can do anything any other CGI program can do, such as collect form
data, generate dynamic page content, or send and receive cookies. But PHP can do
much more. There are three main areas where PHP scripts are used.
• Server-side scripting. This is the most traditional and main target field for
PHP.The PHP parser (CGI or server module), a web server and a web browser
are needed to make this work. We need to run the web server, with a connected
PHP installation. We can access the PHP program output with a web browser,
viewing the PHP page through the server. All these can run on our home
machine if we are just experimenting with PHP programming.
• Command line scripting. We can make a PHP script to run it without any
server or browser. We only need the PHP parser to use it this way. This type of
usage is ideal for scripts regularly executed using cron (on *nix or Linux) or
Task Scheduler (on Windows). These scripts can also be used for simple text
processing tasks.
• Writing desktop applications. PHP is probably not the very best language to
create a desktop application with a graphical user interface, but if we know
PHP very well, and would like to use some advanced PHP features in our
client-side applications we can also use PHP-GTK to write such programs. We
also have the ability to write cross-platform applications this way. PHP-GTK
is an extension to PHP, not available in the main distribution.
PHP can be used on all major operating systems, including Linux, many Unix variants
(including HP-UX, Solaris and OpenBSD), Microsoft Windows, Mac OS X, RISC
OS, and probably others. PHP has also support for most of the web servers today. This
includes Apache, Microsoft Internet Information Server, Personal Web Server,
Netscape and iPlanet servers, Oreilly Website Pro server, Caudium, Xitami,
OmniHTTPd, and many others. For the majority of the servers PHP has a module, for
the others supporting the CGI standard, PHP can work as a CGI processor.
Page | 13
SAFE HANDS
So with PHP, we have the freedom of choosing an operating system and a web server.
Furthermore, we also have the choice of using procedural programming or object
oriented programming, or a mixture of them. Although not every standard OOP
feature is implemented in PHP 4, many code libraries and large applications
(including the PEAR library) are written only using OOP code. PHP 5 fixes the OOP
related weaknesses of PHP 4, and introduces a complete object model.
With PHP we are not limited to output HTML. PHP's abilities includes outputting
images, PDF files and even Flash movies (using libswf and Ming) generated on the
fly. We can also output easily any text, such as XHTML and any other XML file. PHP
can autogenerate these files, and save them in the file system, instead of printing it
out, forming a server-side cache for your dynamic content.
One of the strongest and most significant features in PHP is its support for a wide
range of databases. Writing a database-enabled web page is incredibly simple. The
databases which are currently supported are: Ingres ,PostgreSQL, dBase, IBM DB2,
MySQL ,Direct MS-SQL ,mSQL ,Oracle (OCI7 and OCI8) and much more.
We also have a database abstraction extension (named PDO) allowing us to

transparently use any database supported by that extension. Additionally PHP
supports ODBC, the Open Database Connection standard, so we can connect to any
other database supporting this world standard.
PHP also has support for talking to other services using protocols such as LDAP,
IMAP, SNMP, NNTP, POP3, HTTP, COM (on Windows) and countless others. We
can also open raw network sockets and interact using any other protocol. PHP has
support for the WDDX complex data exchange between virtually all Web
programming languages. Talking about interconnection, PHP has support for
instantiation of Java objects and using them transparently as PHP objects. We can also
use our CORBA extension to access remote objects.
PHP has extremely useful text processing features, from the POSIX Extended or Perl
regular expressions to parsing XML documents. For parsing and accessing XML
documents, PHP 4 supports the SAX and DOM standards, and we can also use the
XSLT extension to transform XML documents. PHP 5 standardizes all the XML
extensions on the solid base of libxml2 and extends the feature set adding
SimpleXML and XMLReader support.
At last but not least, there are many other interesting extensions, the mnoGoSearch
search engine functions, the IRC Gateway functions, many compression utilities
(gzip, bz2, zip), calendar conversion, translation...
Page | 14
SAFE HANDS
Following are some of the features of PHP:
 Fast and easy

There are really only three things that we know for sure when it
comes to comprising speeds of Web programming languages. First,
applications written in C will be the fastest. Second, programming in
C is rather difficult and will take much longer than any of other
languages mentioned so far. Third, comparisons between languages
are extremely difficult. From everything we know, we feel safe in
saying that PHP is as fast as anything out there. PHP offers the best
opportunity to develop powerful Web applications quickly. That
generalization made, we do believe there are other excellent reasons
for choosing PHP.
 Cross platform
In the rundown of Web architecture, we mentioned that PHP would
run on Windows 2000/ NT AND UNIX and with both IIS and
Apache. But the cross-platform abilities of PHP go far beyond these
platforms. If we happen to be using Netscape, Roxen, or just about
anything else, it is likely that PHP will work with it. Yes, ASP can be
run on Linux and Cold Fusion and can work on Solaris and Linux,
and JSP is adaptable across many platforms. PHP also works well on
a variety of systems as any other available product.
 Accesses everything
Whatever we need to use, it is more than likely that PHP has a built-in set of
functions that makes us get whatever we need very easy.
 Constantly being improved
There are thousands of very technical, very talented programmers out there
who love to spend their time creating great, and mostly free, software. In an
active project such as PHP, there are a variety of developers looking to improve
the product almost daily. It is truly remarkable. If we happen to find a bug, we
can submit a report to a mailing list that the core developers read. Depending
on its severity, it is likely that the bug will be addressed within a couple of
hours to a couple of days.
Page | 15
SAFE HANDS
 Your peers will support you
Most languages have active mailing lists and development sites. PHP is no
exception. If we run into trouble – if there’s a bug in our code we just can’t
figure out or we can’t seem to fathom some function or another – someone
among the hundreds subscribed to PHP mailing lists will be happy to check and
fix your code. The open-source nature of PHP creates a real feeling of
community. When we get into trouble, our PHP- hacking brethren will feel our
pain and ease it.
 It’s free
If you have a computer, Windows, Apache, and PHP are all completely free.
JavaScript
Netscape Navigator was the first successful mainstream web browser, and as
such, moved web technologies along quickly. However, Netscape often was
ridiculed by standards organizations for implementing new technologies and
extensions to existing technologies before the standards were in place (much
like Microsoft is being used chastised today for ignoring existing standards in
its development of the Internet Explorer). One such technology was
JavaScript.
Originally named Live Script, JavaScript was created by Brendan Eich of

Netscape and included in version 2.0 of the browser (released in 1995). For
the first time developers were able to affect how a web page could interact
with the user. Instead of making constant trips to the server and back for
simple tasks such as data validation, it became possible to transfer this small
bit of processing to the browser. This ability was very important at a time
when most Internet users were connected through a 28.8Kbps modem, turning
every request to the server into a waiting game.
HTML (HyperText Markup Language)
HyperText Markup Language (HTML) is used for creating Hypertext on the

web. Conceived as a semantic markup language to mark the logical structure
of a document, HTML gives users a way to identify the structural parts of a
document. Learning HTML involves finding out what tags are used to mark
the parts of a document and how these tags are used in creating an HTML
document. The World Wide Web is built on three important standards. They
are:-
Page | 16
SAFE HANDS
• URL (Uniform Resource Locator)- URL provides a standard way to specify

the location of any piece of accessible data on the global Internet.
• HTTP (Hyper Text Transfer Protocol)- HTTP that can directly access and
transfer individual piece of data located anywhere on the network
• HTML (Hyper Text Markup Language)- HTML provides a way of enriching

text documents with a variety of markup, including “Links” specifying the
URL of other piece of data. It is a versatile language allowing authors to
format text and create relationship (called Hypertext Links) between text and
another document (or another portion of the same document) to write
HTML.HTML is the Make-Up-Language, a set of indicators that define text
and document objects and can be incorporated right in our favourite word
processor.
 HTML is a way to express information and ideas in Hypertext. Based on a

philosophy of marking up the meaning of a text rather than its appearance,
HTML gives the developer a great deal of flexibility in defining semantics
structures in a document but discourages attempts to manipulate the
appearance of text in any particular browser.
 HTML itself is written in text files following a specific format for elements
and entities. Head elements identify information about a document, such as its
title, that is not displayed directly in a browser. Body elements such as
headings, lists, block quotes, preformatted text and physical and semantic
character highlights mark structure of a document. The image element embeds
in line images in a document. Entities are special characters that a developer
can have displayed in most browsers.
 To create HTML files, a developer should make a template to hold the basic
tags to mark the head, body and address parts of a document. Based on this
template a developer can add headings, paragraphs, lists and links. Horizontal
rules and inline images can improve the appearance of an HTML file.
Comments, the ADDRESS element, or a revision link in the head of the file,
which can help, document a file.
 The guidelines to make anchors, nesting elements, physical and semantic tags
can help a developer be prepared for special situations or struggles with the
structure of a document. Finally, a careful examination of a document in a
variety of browsers might reveal a variety of anomalous displays- nicks and
cuts – that can be cured by removing spaces or fixing errors in the HTML
itself.
Page | 17
SAFE HANDS
Package Used
LAMP (Linux, Apache, MySQL and PHP) / WAMP (Windows, Apache, MySQL and
PHP)
Basic Architecture
At the most basic level, the Web works off of client/server architecture. Simply stated,
that means that both a central server and a client application are responsible for some
amount of processing. In other words, all the work is done on the central computer.
The Client
The applications you can develop with MySQL and PHP make use of a single client:
the Web browser. This is not the only possibility for Internet-based applications. For
very sophisticated applications that require more client-side processing or that need to
maintain state, a Java applet may be necessary. But unless we are coding something
like a real-time chat program, client-side Java is completely unnecessary. So the only
client we should be concerned is the Web browser. The applications will lead in the
browser. As you probably already know, the primary language of browsers is the
hypertext language or HTML.HTML provides a set of tags that describe how a Web
page should look.
The Server
Almost all of the work Web applications takes place on the server. A specific
application, called a Web server, will be responsible for communicating with the
browser. A relational database server stores whatever information the application
requires. Finally, we need a language to broker requests between the Web server and
the database server; it will also be used to perform programmatic tasks on the
information that comes to and from the Web server. Figure below represents this
Page | 18
SAFE HANDS
R e la t i o n a l D a t a b a s e
( M y S Q L , O r a c le ,M S S Q L )
M id d l e w a r e
W eb S erver
P H P ,A S P , JS P ,
(A p a c h e ,I I S )
C o ld F u s io n
In t ern e t
W eb Bro w ser
( I n te r n e t E x p lo r e r , N e ts c a p e )
F ig u r e : - A r c h it e c t u r e O f W e b A p p lic a t i o n s
Webserver
The Web server has what seems to be a fairly straightforward job. It sits there, running
on top of our operating system, listening for requests that somebody on the Web might
make, responds to those requests, and serves out the appropriate Web pages. In reality,
it is a bit more complicated than that, and because of the 24/7 nature of the Web
server is major issue. There are many Web servers out there, but two Web servers
dominate the market. They are Apache and Microsoft’s Internet Information Server
(IIS).
APACHE
The Apache Web server is the most popular Web server. Like Linux, MySQL, and
PHP, it is an open-source project. Not surprisingly, Apache works best in Unix
environments, but also runs just fine under Windows. Apache makes use of third-party
modules. Because it is open source, any one with the skill can write code that extends
the functionality of Apache. PHP will most often run as an Apache extension, known
as an Apache module. Apache is a great Web server. It is extremely quick and
amazingly stable. The most frequently stated complaint about Apache is that, like
many places of UNIX there are limited graphical tools with which we can manipulate
the application. We can alter Apache by specifying options on the command line or by
altering text files. When we come to Apache for the first time, all this can be a bit
opaque.
Page | 19
SAFE HANDS
The Apache history project is an attempt to capture some of the history of the Apache
webserver project, and the other projects that have grown out of and a long side of it,
before it passes out of memory. Apache is important not only as an excellent piece of
software but as an example of how free software development is supported to work.
So this project strives not only to highlight important historical events, but also
important philosophical decisions made over the years, which made Apache
successful.
The project is still in the formative stages and this page is put up mainly as a
placeholder until we get some of the initial work done and have something to put
here. The Apache HTTP Server project is an effort to develop and to maintain an open
source HTTP server for modern operating systems including UNIX and Windows NT.
The goal of this project is to provide a secure, efficient and extensible server that
provides HTTP services in sync with the current HTTP standards.
Apache has been the most popular webserver on the Internet since April 1996.The
October 2003 Net craft webserver survey found that more than 64% of the websites
on the internet are using Apache thus making it more widely used than all other
webservers combined.
Middleware
PHP belongs to a class of languages known as middleware. These
languages work closely with the Web server to interpret the
requests made from the World Wide Web, process these requests,
interact with other programs on the server to fulfill the requests,
and then indicate to the Web server exactly what to serve to the
client’s browser. The middleware is where you will be doing the
vast majority of your work. In addition to PHP, there are several
languages that perform similar functions. Some of the more
popular choices are ASP, Perl, and Cold Fusion.
Relational databases
Relational Database Management Systems (RDBMSs) provide a great way to store

and access complex information. They have been around for quite a while. In fact,
they predate the Web, Linux, and Windows NT, so it should be no surprise that there
are many RDBMSs to choose from. All of the major databases make use of the
Structured Query Language (SQL). Some of the more popular commercial RDBMSs
are Oracle, Sybase, Informix, Microsoft’s SQL server, and IBM’S db2. In addition to
MySQL, there are now two major open-source relational databases. Postgres has been
major alternative to MySQL in the open-source arena for sometime.
Page | 20
SAFE HANDS
The Evolution of the Web
When Tim Berners-Lee crafted the first proposal for the World Wide Web in 1990, the
idea was fairly simple: to create a “web” of interconnected information using
hypertext and Uniform Resource Identifiers (URIs). The ability to link disparate
documents from all around the world held a huge potential for scholarly endeavors,
where people would be able to access referenced material almost instantly. Indeed, the
first version of the Hypertext Markup Language (HTML) featured little more than
formatting and linking commands, a platform not for building rich interactive
software but rather for sharing the kinds of textual and illustrative information that
dominated the late age of print. It was from these static web pages that the Web grew.
As the Web evolved, businesses soon saw potential in the ability to distribute
information about the products and services to the masses. The next generation of the
Web saw an increased ability to format and display information, as HTML also
evolved to meet the needs and match the expectations of these new media-savvy
users. But a small company called Netscape would soon be ready to push the
evolution of the Web forward at a much faster pace
Page | 21
SAFE HANDS
SYSTEM DESIGN
Page | 22
SAFE HANDS
4. SYSTEM DESIGN
4.1 System Design Principles
The most creative and challenging phase of the system development life
cycle is the 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 first step in the system designing is to determine how the output is to
be produced and in what format. Samples of the output and input are also
presented. In the second step input data and master files are to be designed to
meet the requirements of the proposed output. The processing phases are handled
through program construction and testing, including a list of the programs
needed to meet the system’s objectives and complete documentation.
Finally details related to justification of the system and an estimate of the

impact of the candidate system on the users and the organization are documented
and evaluated by management as a step towards implementation. The final report
prior to the implementation phase includes procedure flow chart, record layouts,
and a workable plan for implementing the candidate system.
The SAFEHANDS must have a client and server, which connect through
the network. The front end is handled by PHP and MySQL handles the backend.
SAFE HANDS
4.1.1 Logical Design
Logical Design aims at establishing the requirements of the users, which

the new system must satisfy. In this stage, the system has to identify the
relationships required between various items of data and the grouping of items of
data together into records. This is known as logical data structure, which is
required to produce the output that the user requires. Once this is agreed, the
logical design can be turned into a physical system with more detailed design. The
main focus of the project has been on life, vehicle and health insurance. The
project is divided into following three modules for developing the software.
 General User Module: Users viewing “SAFE HANDS”, website can obtain
the information about the company. After thoroughly traversing through the
website, the users according to their wish can apply for an insurance class of
their interest such as life, vehicle or health insurance. After traversing,
through SAFE HANDS, users will be having in-depth knowledge about
various new plans the benefits there under and other services such as premium
calculation of various different categories of insurance say life, vehicle and
health as well as obtaining the details of nearest doctor locations and branch
locations for further transactions. At any cost of time, the users can directly
contact the company and also know more about the company by using about
us screen. The users are permitted to visit the frequently asked questions
screen, which is provided with the answers that are frequently asked as well as
by using the sitemap screen, the layout of the entire website links along with
their sub links are shown. Anyone can use this screen to navigate through
SAFE HANDS.
Page | 17
SAFE HANDS
 Policy Holder Module. Once a policy is held, the user can avail certain online
services that are meant for policyholders. Online services include logging into
their accounts and viewing their current policies and its details such as policy
type and number, sum assured and benefit period, premium and mode of
payment, start date and maturity date, policy status whether its renewal or
revival, any surrender values whether any bonuses are attached or any dues in
paying premium as well as the details of insurer and nominee, they are also
provided to check the premium calendar when the next premium has to be
paid, allows to apply for loans and also to request for more information about
the new policies the benefits there under and thereby, applying for that policy,
by allowing online payment of premiums as well as receiving bills, also
enables to post claims and provides permission to edit changes in account as
well as obtaining information with regard to the nearest doctors or offices for
any further transactions.
 Administrator Module. The administrator is the super user or the person who
manages the entire system. He is responsible for adding and removing
policyholders as well as issuing or canceling loans. He is the one who receives
the application send by the users who have shown interest in a particular
policy. He also receives information about the claims and decides whether to
issue or cancel those claims of different categories of insurance say life,
vehicle and health that have been posted as well as obtains the details of
persons who have requested for more information regarding a particular matter
be furnished to them. The administrator then communicates the information he
receives to the corresponding representatives of the insurance company. The
administrator is provided with services such as adding new plans , doctors,
setting premium rates ,confirming or removing policyholders of life, vehicle
and health insurance and generating various reports such as branch and doctor
Page | 18
SAFE HANDS
details, users who all are confirmed as well as of confirmed policy holders in
life, vehicle and health insurance.
4.1.2 Physical Design
Once the logical system is agreed, the detailed design of the physical
system can commence.During the physical design process, we convert the data
gathered during the logical design phase into a description of the physical
database structure. Physical design decisions are mainly driven by query
performance and database maintenance aspects.
Database Design
Database is defined as an integrated collection of related data. Database is

designed, built and populated with data for a specific purpose. It has an intended
group of users and some preconceived applications in which these users are
interested. A database can be of any size and of varying complexity.
The database design is a logical development in the methods used by the

computers to access and manipulate data stored in the various parts of the
computer systems. The overall objective in the development of database
technology has been to treat data as an organizational resource and as an
integrated whole.
Data design is the first design of the three design activities that are
conducted during software engineering .The impact of data structure on program
structure and procedural complexity causes data design to have a profound
influence on software quality. The concepts of shared memory and semaphores
provide the foundation for an approach to data design.
Page | 19
SAFE HANDS
The main objectives of database are data integration, data integrity and
data independence.
 Data Integration: In a database, information from several files are coordinated,

accessed and operated upon as though it is in a single file. Logically, the
information is centralized physically and the data may be located on different
bases and in a widely scattered geographical location connected through data
communication facility.
 Data Integrity: In a database all data are stored in one place only and it allows
each application to access it. This approach results in more consistent
information.
 Data Independence: This objective seeks to allow change in the content and
organization of physical data without re-programming the application.
DBMS
DBMS is a general-purpose software that facilitates the processing of

defining, constructing and manipulating databases for various applications. A
computerized database may be created and maintained either by a group of
application programs written specifically for that task or by a database
management system. DBMS allow the data to be protected and organized
separately from other resources like hardware, software and programs. It’s a
software package, which contains components that are not found in other data
management packages. The significance of DBMS is the separation of data as
seen by the programs and data as stored on the direct access storage devices that is
the difference between the logical and physical data.
MYSQL
MySQL is the most popular Open Source SQL database management

system, which is developed, distributed and supported by MySQLAB. MySQLAB
is a commercial company that unites Open Source values and methodologies with
a successful business model. Not only is MySQL the world’s most popular Open
Page | 20
SAFE HANDS
Source database, it has also become the database of the choice for a new
generation of applications built on the LAMP stack (LINUX, Apache, MySQL,
PHP/PERL, PYTHON). MySQL runs on more than 20 platforms including
LINUX, Windows, OS/X, HP-UX, AIX, Netware, giving you the kind of
flexibility that puts you in control. MySQL offers a comprehensive range of
certified software, support, training and consulting.
MySQL is a multi-threaded, multi-user database management system.

MySQL’s implementation of a relational database is an abstraction on top of a
computer’s file system. The relational database abstraction allows collection of
data items to be organized as a set of formally described tables. Data can be
accessed or reassembled from these tables in many different ways, which do not
require any re-organization of the database tables themselves.
The important features are:
 MySQL is a relational database management system.

 Robust Transaction Support.
 MySQL is an Open Source database.
 Web and Data warehouse
 Strong data protection
 Comprehensive Application Development
 MySQL database server is very fast, reliable and easy to use.
 Scalability and Flexibility
 MySQL Server works in client/server or embedded systems.
 A large amount of contributed MySQL software is available.
Page | 21
SAFE HANDS
FOURTEEN TABLES FORM THE DATABASE FOR THIS PROJECT.
1. Table Name :Branch_locator
Total Fields :8
Purpose :Stores the details of branches.
F ie ld Typ e N ull D e fa u l t E x tra A ction

b r a n c h _ id in t( 1 0 ) N o a u t o _ in c re m e n t P r im a r y k e y
b ranc h_ c o d e in t( 1 5 ) N o 0
b ranc h_ ad dress va r c h a r (3 0) N o
b r a n c h _ c ity va r c h a r (2 5) N o
b r a n c h _ d is t va r c h a r (2 5) N o
b ranc h_ p hn o in t( 1 5 ) N o 0
b ra nc h_ s ta te va r c h a r (2 5) N o
b r a n c h _ p in int(2 0 ) N o 0
2. Table Name :Plan_details
Total Fields :9
Purpose :Stores the details of various plans.
Page | 22
SAFE HANDS
F ie ld Typ e N u ll D e fa u l t E xtr a A c tio n

p la n _ id in t(1 1 ) N o a u to _ in c r e m e n t P rim a r y k e y
p la n _ ty p e varc ha r(2 5 ) N o
t ab ula r _ p r e m ium flo a t N o 0
p la n _ re b a te 1 flo a t N o 0
p la n _ d a b flo a t N o 0
p la n _ e p d b flo a t N o 0
im age varc ha r(5 0 ) N o
3. Table Name :Doctor_locator
Total Fields :13
Purpose :Stores the information of various doctors.
F ie ld Type N u ll D e fa u l t E xtr a A c ti o n
do c _ id in t(1 1 ) N o a u to _ in c re m e n t P r im ary k e y
do c _ c o de in t(1 1 ) N o 0
do c _ n am e v arc ha r (2 0 ) N o
do c _add v arc ha r (5 0 ) N o
do c _ la n d lin e n o in t(2 0 ) N o 0
do c _ m o b no in t(2 0 ) N o 0
do c _ lo c v arc ha r (2 5 ) N o
do c _ e m a il v arc ha r (2 5 ) N o
do c s al_ lim it d o ub le N o 0
do c _ c ity v arc ha r (2 5 ) N o
do c _ d ist v arc ha r (2 5 ) N o 0
do c _ s ta te v arc ha r (2 0 ) N o
do c _ p in in t(2 0 ) N o 0
Page | 23
SAFE HANDS
4. Table Name :User_registration
Total Fields :23
Purpose :Stores the information of users.
Page | 24
SAFE HANDS
F ie ld T yp e N ull D e fa u l t E xtr a A ctio n

u s e r _ id in t(1 1 ) N o a u to _ in c re m e n t P rim a ry k e y
u ser_ u nam e va r c h a r (2 0) N o
user_pw d va r c h a r (2 0) N o
u ser_ c pw d va r c h a r (1 0) N o
u s e r _ fn am e va r c h a r (2 0) N o
u s e r _ ln a m e va r c h a r (2 0) N o
u ser_ g en de r va r c h a r (5 ) N o
user_dob d a te tim e N o 0 0 0 0 - 0 0 -0 0
0 0 :0 0 :0 0
u s e r _ m a rit als ta tu s b in a ry ( 1 ) N o
u s e r _ o c c u p atio n va r c h a r (2 0 ) N o
u s e r _ in c o m e do ub le N o 0
u s e r _ la n d lin e n o in t(1 8 ) N o 0
u s e r _ m o b ile n o in t(1 8 ) N o 0
u s e r _ e m a ilid va r c h a r (2 0 ) N o
u ser_ ad d1 va r c h a r (2 5 ) N o
u ser_ ad d2 va r c h a r (2 5 ) N o
u s e r _ c ity va r c h a r (1 1 ) N o
u s e r _ d is t va r c h a r (1 1 ) N o
u s e r _ s ta te va r c h a r (1 1 ) N o
u s e r _ c o u n try va r c h a r (1 1 ) N o
u s e r _ p in in t(1 1 ) N o 0
u s e r _ p r ivil e g e b in a ry ( 1 ) N o
u s e r _ c o n fi rm b in a ry ( 1 ) N o
5. Table Name :Family_details
Total Fields :5
Page | 25
SAFE HANDS
Purpose :Stores the information of family members.
F ie ld T ype N ull D e fa u l t E xtra A ctio n

fa m ily _ id i n t( 1 1 ) N o au to _ in c r e m e n t P r im a r y K e y
u s e r_ id i n t( 2 0 ) N o 0
fa m ily _ sp o u se n a m e va rc h ar(2 0 ) N o
d o b _ spo use d a te tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
fa m ily _ n o _ o f _ c h ild r e n i n t( 1 1 ) N o 0
6. Table Name : Children_details
Total Fields :6
Purpose :Stores the information of Children.
F ie ld T ype N ull D e fa u l t E x tr a A ctio n

c hi ld_ id i nt(1 1 ) N o a uto _ in c re m e nt P rim ary ke y
u s e r_ id i nt(1 1 ) N o 0
c hi ld_ n a m e va rc h ar(1 1 ) N o
c hi ld_ d o b d a te tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
c hi ld_ g e n de r va rc h ar(4 ) N o
p rio rity i nt(1 1 ) N o 0
7. Table Name : Payment_details
Total Fields :7
Page | 26
SAFE HANDS
Purpose :Stores the details of online payment.
F ie ld Typ e N ull D efault E x tra A c tion

p a y _ id int(1 1 ) N o a u to _ in c re m e n t P ri m a r y K e y
p o lic y _ n o int(1 1 ) N o 0
p a y m e n t_ d ate d a te tim e N o 0 000-0 0-00
0 0 :0 0 :0 0
tra n s a c tio n _ id v arc h a r (1 1 ) N o
b o n u s _ d a te d a te tim e N o 0 000-0 0-00
0 0 :0 0 :0 0
bo n us_ am nt do ub le N o 0
las t_ te r m _ p a id d a te tim e N o 0 000-0 0-00
0 0 :0 0 :0 0
8. Table Name :Policy_applied
Total Fields :15
Purpose :Stores the details of applied policies.
F ie ld Typ e N ull D e fa u l t E xtr a A c tion

p o lic y _ ap p ly id in t( 1 1 ) N o a u to _ in c r e m e n t P r im a ry K e y
u s e r_ id in t( 1 1 ) N o 0
p o lic y _ in s u re r va r c h a r (2 1 ) N o
p o lic y _ n o m in e e va r c h a r (2 0 ) N o
p o lic y _ n o in t( 1 1 ) N o 0
p la n _ id in t( 4 ) N o 0
p o lic y _ su m _ as s u re d do ub le N o 0
p o lic y _ m o d e _ o f _ p a y in t( 2 0 ) N o 0
p o lic y _ p re m iu m do ub le N o 0
p o lic y _ sta rt_ d a te d a te N o 0 0 0 0 -0 0 -0 0
p o lic y _ b e n e fit_ p e rio d in t( 4 ) N o 0
l as t_ te rm va r c h a r (1 1 ) N o
p ay_id in t( 1 1 ) N o 0
p o lic y _ lo a n _ iss u e bin ary (1 ) N o
p o lic y _ c o n firm bin ary (1 ) N o
9. Table Name :Life_claim
Page | 27
SAFE HANDS
Total Fields :11
Purpose :Stores the information of users who have claimed for life
insurance.
F ield Type N ull D e fa u l t E xtr a A ctio n

life c laim _ id in t(1 1 ) N o a u to _ in c re m e n t P rim a ry K e y
u s e r_ id in t(1 1 ) N o 0
p o lic y _ n o in t(1 1 ) N o 0
d o c _ id in t(1 1 ) N o 0
c a us e _ o f_ d e a th v arc ha r(1 1 ) N o
d a te _ tim e _ d e a th d ate tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
c la im _ am o u n t f lo a t N o 0
c la im _ d a te d ate tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
b ill_ n o in t(1 1 ) N o 0
life _ c la im _ sta tu s b ina ry(1 ) N o
iss u e d _ d a te d ate tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
10. Table Name :Loan_details
Total Fields :7
Purpose :Stores the details of loan.
F ie ld Type N ull D efault E x tr a Ac tio n

l o a n_ id in t(1 1 ) N o a u to _ in c re m e n t P rim a ry K e y
lo an_n o in t(1 1 ) N o 0
lo an_am o un t d o u b le N o 0
l o a n _ d a te d ate tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
l o a n_ in te re st flo a t N o 0
l o a n_ is s ue b ina ry(1 ) N o
Page | 28
SAFE HANDS
11. Table Name :Vehicle_registration
Total Fields :17
Purpose :Stores the information of users who have registered for vehicle
. insurance.
F ield Type N ull D e fa u l t E x tr a A c tio n

v e h ic le _ id in t(1 1 ) N o a u to _ in c r e m e n t P r im a ry K e y
u s e r_ id in t(1 1 ) N o 0
i n s u ra n c e _ sta rtd a te d ate tim e N o
m o d e _ p o li c y b ina ry(1 ) N o
re g is tra tio n _ n o v a rc h a r ( 1 0 ) N o
v e h ic le _ ty p e v a rc h a r ( 5 0 ) N o
v e h ic le _ p ric e flo a t N o 0
d a te _ o f_ re g d ate N o 0 0 0 0 - 0 0 -0 0
y e a r _ m a n u fa c tu r e d ate N o 0 0 0 0 - 0 0 -0 0
e n g in e _ n o in t(1 1 ) N o 0
c h a s s is_ n o in t(1 1 ) N o 0
n o _ o f _ p as s e n g e rs in t(1 1 ) N o 0
m o d e l_ no v a rc h a r ( 1 1 ) N o
v e h ic le _ g v w v a rc h a r ( 1 1 ) N o
m a k e _ o f_ v e h ic le v a rc h a r ( 1 1 ) N o
ve h_ u s e rc o nfirm b ina ry(1 ) N o
Page | 29
SAFE HANDS
12. Table Name :Vehicle_claim
Total Fields :15
Purpose :Stores the information of users who have claimed for vehicle
insurance.
F ield Type N ull D e fa u l t E xtra A ctio n

v e h c laim _ id in t(1 0 ) N o au to _ in c re m e n t P r im a r y K e y
v e h ic le _ id in t(1 0 ) N o 0
u s e r_ id in t(1 0 ) N o 0
d riv e r_ id in t(1 1 ) N o 0
d riv e r_ n am e var c ha r(1 5 ) N o
d riv e r_ a d d re s s var c ha r(2 5 ) N o
d riv e r_ a g e var c ha r(1 1 ) N o
d riv e r_ p h n o var c ha r(1 1 ) N o
d riv e r_ lic e n s e var c ha r(1 5 ) N o
h o s p i tal_ ad d re ss var c ha r(2 5 ) N o
c la im e d _ am n t d o u b le N o 0
v e h _ c la im _ sta tu s b in a ry (1 ) N o
i ss ue d_ da te d ate tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
Page | 30
SAFE HANDS
13. Table Name :Health_registration
Total Fields :13
Purpose :Stores the information of users who have registered for health
insurance.
F ie ld T yp e N ull D e fa u lt E xtr a A c ti o n
h e a lth _ id in t(1 1 ) N o a u to _ in c re m e n t P rim ar y k e y
u s e r_ id in t(1 1 ) N o 0
insure r va r c h a r (25 ) N o
d o c _ id in t(1 1 ) N o 0
s u m _ in s u r e d do ub le N o 0
p r e m iu m flo a t N o 0
s ta rtd a te da te t im e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
p aym o d e in t(1 1 ) N o 0
b e n e fitp e rio d in t(2 0 ) N o 0
n o m ine e _ na m e va r c h a r (25 ) N o
n o m ine e _ ad dr e ss va r c h a r (50 ) N o
h e a lth _ u se rc o n firm b in ary (1 ) N o
14. Table Name :Health_claim
Total Fields :9
Purpose :Stores the information of users who have claimed for health
insurance.
F ie ld Type N ull D e fa u l t E xtra A c tio n

h e a lth c la im _ id in t(1 1 ) N o au to _ i n c re m e n t P ri m a r y k e y
u s e r _ id in t(1 1 ) N o 0
d a te o f_ h o s p ital is a tio n d at e tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
d is c h arg e _ d a te d at e tim e N o 0 0 0 0 -0 0 -0 0
0 0 :0 0 :0 0
re a so n _ h o s p ita lis e va r c h ar(2 5 ) N o
c la im _ am n t flo at N o 0
h e a lth _ c laim _ s ta tu s b in a ry (1 ) N o
Page | 31
SAFE HANDS
4.1.3 Architectural Design
The primary objective of architectural design is to develop a modular

program structure and represent the control relationships between modules. In
addition, architectural design, melds program structure and data structure,
defining interfaces that enable data to flow throughout the program.
Architectural design represents the structure of data and program

components that are required to build a computer based system. It considers
the architectural style that the system will take the structure and properties of
the components that constitute the system and interrelationships that occur
among all architectural components of the system. Architectural design begins
with data design and then proceeds to the derivation of one or more
representations of architectural structure of the system. Alternative
architectural styles or patterns are analyzed to derive the structure that is best
suited to customer requirements and quality attributes. Once an alternative has
been selected the architecture is elaborated using an architectural design
method.
4.2 I/O Design
Input Design
The input design is the link that ties the information system into the user’s
world. Input specification describes the manner in which data enters the
system for processing. Input design feature can ensure the reliability of the
system and produce results from accurate data, or they can result in the
production of erroneous information. Input Design consists of
• Developing specifications and procedures for data preparation.
• Steps necessary to input data into a usable form for processing.
• Data entry, the activity of putting data into the computer processing.
Page | 32
SAFE HANDS
Objective of input design:
 Controlling the amount of input required.
 Avoids delay.
 Avoiding errors in data.
 Avoiding un-necessary steps.
 Keeping the process simple.
Input Designs are aimed at reducing the chances of errors. Adequate validation
checks are incorporated to ensure error free data storage.
SAFE HANDS has the following input screens:
o Home Page: This is the home page for all the users associated with the
system, i.e. Administrator, PolicyHolders and General Users. Each user
home page differs from the other. Home page contains links for
traversing through the site as Home, About Us, Contact Us, FAQ’s,
Site Map, Life, Vehicle, Health, Branch Locator, Doctor Locator,
Premium Calculator and Help, which leads to respective pages. A
SignIn link is also provided for the authorized users to login.
o Login Screen: The screen is used to login administrator and

policyholders of the insurance company. The administrator and user
are differentiated by their user name and password. The correct
username and password lead to their own area of use. The logged in
users are provided with the appropriate controls for the alteration of
contents.
Page | 33
SAFE HANDS
o Administrator Screen: Administrator login leads to administrator’s

page where he can add new plans and doctors, issue or cancel the
posted claims as well as loan availability and confirm or reject life,
vehicle and health insurance policyholders as well as users.
o PolicyHolder Screen: PolicyHolders can make use of the screens by

logging in to their respective accounts. He/She can view his/her policy
as well as renew policies if it nears its online. They can make use of
the claims facility, by posting claims. Also, can select new plans and
calculate their premium, if interested can apply for the policy.
o Users Screen: Users screen provides information about the different

kinds of policies that they are dealing with. This screen can be
accessed by anyone even by a person who is not an administrator or a
policyholder of the company. The company currently deals with life,
vehicle and health insurance. A person can view the different types of
Life, Vehicle and Health insurance coverage schemes, calculate the
premium at the same time and can apply for it if he/she is interested.
o SiteMap Screen: The sitemap screen shows the layout of the entire
website links along with their sub links. Anyone can use this screen to
navigate through the site.
Page | 34
SAFE HANDS
Output Design
Output refers to the results and information that are generated by the system. For
many end users output is the main reasoning for developing the system and the basis
on which they will evaluate the usefulness of the applications. Designing output,
system analyst must accomplish the following.
• Determine what information is present.

• Display or print the information and select the Output medium.
• Arrange the presentation of information in an acceptable format.
• Decide how to distribute the output to intended receipts.
The objectives of output design are: convey information about past activities, current
status or projections of the future, signal important events, opportunities, problem or
warnings, trigger an action and confirm an action. The output, on going activity
almost from the beginning of the project follows the principles of form design. The
output includes both CRT display and printed reports. SAFE HANDS has the
following output screens:
Output screens, which are generated as reports are as follows:

o User Details
o Branch Details
o Doctor Details
o Life Insurance Policy Holder Details
o Vehicle Insurance Policy Holder Details
o Health Insurance Policy Holder Details
o Online Payment Details
Output screens, which are generated on CRT display, are as follows:

o Plan Details
o Branch Details
o Doctor Details
o Claim Details
o User Details
o Policy Status Details
o Online Payment Details
o Life Insurance Policy Holder Details
Page | 35
SAFE HANDS
o Vehicle Insurance Policy Holder Details

o Health Insurance Policy Holder Details
4.3System Flow Diagram
Page | 36
SAFE HANDS
Page | 37
SAFE HANDS
1.10Context Flow Diagram
Level-0 DFD
R eq uest R espo n se
A dm in is tr a to r A d m in is t r a t o r
SAF E HAN D S
P o li c y H o l d e r R e q u e st R esp o nse P o li c y H o ld e r
G en e r a l U s er s R e sp G e n er al U s e r s
e st o nse
R eq u
1.11Data Flow Diagram
Data flow diagram is the commands used during problem analysis. They are useful
in understanding a system and can be effectively used for portioning during the
analysis. A DFD shows the flow of data through a system. It is used to describe and
analyze the amount of data through a system-manual or automated-including the
processes, stores of data, and delays in the system. Data flow diagrams are the central
tool and the basis from which other components are developed. The transformation of
data from input to output through processes may be described logically and
independently of the physical components. It shows the movements of data through
the different transformations or processes in the system.
Data flow diagrams (DFD) depict how data interact with a system. They are also
known as data flow graphs, bubble charts or pert networks. Data flow diagrams are
extremely useful in modeling many aspects of a business function because they
systematically subdivide a task into its basic parts; helps the analyst to understand the
Page | 38
SAFE HANDS
system that they are trying to model. Data flow diagrams uses a variety of symbols to
represent a provider of data such as a customer or management.
Named circles or bubbles show the processes, and named arrows entering or leaving
the bubbles represent data flows. A rectangle represents a source or sink, and is a net
originator or consumer of data. A source or a sink is typically outside the main system
or study. Data move in a specific direction from an origin to a destination. Processes
can be people, procedures or devices that use or produce data. External sources or
destinations of data, which may be people, programs, organizations or other entities,
interact with the system but are outside with its boundary. In the data store, data are
stored or referenced by a process in the system. The data store may represent
computerized or non-computerized devices.
DFD can be hierarchically organized, which helps in partitioning and analyzing large
systems. Such DFDs together are called leveled DFD set. A leveled DFD set has a
starting DFD, which is a very abstract representation of the system, identifying the
major inputs and outputs and the major processes in the system. Then each process is
refined and a DFD is drawn for the processes.
The DFD provides additional information that is used during the analysis of the
information domain and serves as a basis for modeling of function. The DFD may be
used to represent a system or software at any level of abstraction. In fact, the DFDs
may be portioned into levels that represent increasing information flow and function
details. Therefore, the DFD provides a mechanism for functional modeling as well as
information flow modeling.
Data flow analysis permits analysis to isolate areas of interest in the organization and
study then by examining the data that enter the process and seeing how they are
changed when they leave the process. As analyst gathers facts and details, their
increased understanding of the process leads them to ask questions about specific part
of the process, which leads to still additional investigation.
Page | 39
SAFE HANDS
The symbols appearing in the DFD are as follows:
Circle, which represents a process that transforms

incoming data into outgoing flow.
Arrows, which shows the data flow.
Rectangle, which defines sources or destination

of data.
Open rectangle, which shows the data source.
Page | 40
SAFE HANDS
Level-1 DFD
L if e
ls
d e ta i 1.1
L i fe
L o g in
A d m i n is t r a t o r
V e h i cle
S AFE HA N D S d e ta ils
V e h ic le
P o li c y H o l d e r L o g in 1 .2
G e n e r a l U s er s
L o g in He
a lt
h de
ta i
ls
H e a lt h
1 .3
Page | 41
SAFE HANDS
Level-2 DFD: Administrator
P l a n _ d e t a ils
U s e r _ R e g is t r a t i o n
d
plan _i
U sern am e
U s ern a m e
P a ssw o rd
P a ssw o rd
A d m in is tr a to r N ew life c la im _ id
P la n s
&
&
2.1 B r a n c h _ d e t a i ls
ta i n
is su e
a
L if e _ c laim
ls
pl
Lo c laim
de
e
g in h _ id is s u
bran c
b ra n c h N ew c ancel
to r
_ id
do c s SAFE d e ta ils
B ranc h es c l a im
m
il L if e
d e ta
la i
l
HANDS 2 .2 cance
ec
c la i m
l if
s ta tu s
el
2 .3 .1
ve
nc
n
ls
l if e
hc
lo a
c la im
ca
ta i
N ew C la i m
lai
im
d e ta i l s cla ils
de
m _
D o ctors p S ta tu s
h o o lic det
a
id
2 .6 de ld y 2 .3
ta e r veh V eh ic le
ic l V e h i c le _ c l a im
is s
ils
Loan P o l ic y claim e c l a im
ue
E li g i b i li t y
_ id
h o ld e r s d e ta s t a tu s
he
ils
lt h
to r
2.5
a lt
2 .4 2 .3 . 2
cla ta ils
h ea icy li f e
d
de
_i
h
im
do c
o l pol
rs i
m
p
ld e h ol cy is s u e
lai
ho ders
hc
H e a lt h c l a im
ve
c l a im
v e h ic l e
h o ld e r s
D o c t o r _ d e t a i ls
p o lic y
H e a lt h L if e s t a tu s
is s u e
h e a l t h c la
e
can cel
p o li c y 2 .3.3
is s u
p o lic y ca
h o ld e r s nc
h o ld e r s el
2 .4.3 2 . 4 .1
im _ i d
V e h ic l e
p o l ic y co
is s u e nf
irm c ancel
h o ld e r s
lo a n
re je c t
c an c e l 2 .4 . 2 c la im H e a lth _ c laim
lo a n re
co n
t
je
ec
ct c o n f ir m
re j
f irm
p o l ic y h e a lt h c l a i m _ i d
r e je c t
firm
lo an _ id
h o ld e r s
r e je c t p o li c y
con
id
lo a n _
p o l ic y h o ld e r s
h o ld e r s c o n f ir m
p o l ic y
p o l ic
p lyid
h o ld er s
p o l ic y _ a p
y _ap
id
L o a n _ d e t a i ls
lth _
h e alth _ id
p ly id
hea
_ id
v e h icle
ic le
v eh
_ id
H e a l t h _ r e g is t r a t io n
P o li c y _ a p p li e d
V e h i c l e _ r e g is t r a t io n
Page | 42
SAFE HANDS
Level-2 DFD : PolicyHolder

life claim _ id
L if e
c la i m s
L if e _ c la im
e 2 .1 .1
lif im
a s
c l ta il
de v e h ic le V eh ic le
V e h ic l e _ c la i m
cla im c la i m s id
P o li c y H o l d e r P o s tin g d e ta ils 2 .1 .2 v e h c la i m _ id
s e r _ r e g i s t r a t io n h e alth im _
U
C la i m s th c l a
c la im heal
d o c to r _ i d 2 .1 H e a lt h
d e ta ils H e a l t h _ c la i m
c la i m s
Use
2 .1 .3
p as V ie w
rn
h e a lt p o l i c y _ a p p l y id
h
&
U se &
am e
sw o
d e t im
a ils
D o c to r _ lo c a to r P o li c y p o l ic
y
c la
P as
D o ctor
rn a
d e t a il
rd
Lo
2 .2 H e a lt h
y
s
sw o
l ic
L o c a to r
m
veh i
gi
ls
c le
e
p o li c y
po
ta i
n
p o li c
rd
2 .9 P o lic y _ a p p li e d
de
y
c ale d e t a il V e h ic l e 2 .2 .1
B r a n c h _ lo c a to r do n s
c to d eta d e r p o l ic y
ils
r d l 2 .2 .2
B ranc h eta p o if e
li c p p ly id
ils SAF E de
tai y p o li c y _ a
br Lo cator ls
an b ra n c h d e t a ils H AN D S
ch 2 .8 p o l ic y _
L if e
l o a n i ty
_i a p p ly i d
c a l c u la t o r
p r e m iu m
d P r e m iu m p o li c y
b il
d e ta i l s
lo an
_ id e l ig i i l s C a len d a r 2 .2 .3
d e ta
s ta lic y
Loan 2 .3 ca life
de tu s
l
de en d P o l ic y _ a p p l ie d
po
ls
L o a n _ d e t a i ls E li g i b ili t y
ta i
ta e
ils r
id 2.7
y_ L if e
pa p ly
id
he
v e le n d ls
P r e m iu m
c a l ta ils
P o li c y P r e m iu m _ap
c a e ta cy
hi er
alt r
de
lth p o li
en
S ta tu s C a l c u la t o r C a le n d e r
cl
d
a
h
h e lic y s
e
de
P a y m e n t _ d e t a il s 2 .6 2 .4 2 .3 .1
i
po atu
st H e a lth
P r e m iu m
cal
p re la tio n
C a le n d e r V e h ic le
life
p o if e
s ta licy
p o ic le
cu
m iu
ca lc u la t
2 . 3 .3
p rem iu m
H e a lt h P r e m iu m
l
v e h ic le
tu
s t a lic y
h
P o li c y C a le n d e r
tu s
ve
p aym en t
d e ta ils
S t at u s 2.3.2
p o lic y
po
c alc u latio n
io n
p re m iu m
lic
2 .6 .3
h ea lt h
L if e
y
L if e
_a
P o li c y
_ app l
pp
P r e m iu m
S ta tu s
ly
V eh ic le C a l c u la t o r
id
y id
2 .6 .1
P r e m iu m 2 .4 .1
V e h ic le C a lc u la t o r P o l ic y _ a p p l ie d
pl
P o l ic y 2 .4 .2 an
_ id
S ta tu s
2 .6 .2
id
H e alth
y
P l a n _ d e t a il s
appl
P r e m iu m
pr
li f e u m
e m u la t
ca
C a lc u l a t o r
cy_
lc
i
p a y _ id
v
pay
2.4.3 p ehi
p o li
c a re m c le
e
_ id
lc iu
ul m A p p ly
at
pay
e P o li c y
_ id
h e a lth
O n l in e p rem iu
m
P ay m e n t c a lc u l
a te
2.5 ent
pay m
s
d eta il
P a y m e n t _ d e t a i ls
id
pay _
Page | 43
SAFE HANDS
Level-2 DFD : General Users
B r a n c h _ lo c a to r
ch B ranc h
an
b r tails L o c at o r h _ id
de branc
G e n er al U s e r s 2 .4
d o c_
id
d o c to r
d e t a il s D o c to r
Lo L o c a to r D o c t o r _ lo c a to r
g in SAFE 2.3
HANDS
P r e m iu m P l a n _ d e t a il s
p re m
d e tail
C a l c u la t o r
u se r
iu m
d e ta i 2 .2
ls
id
s
p la n _
veh
ic
u se le
N ew User d e ta r v eh icl
e _ id
ils
R e g is t r a t i o n
2.1 V eh ic le
2 .1 .2
V e h ic l e _ r e g is t r a t io n
li f e r
e
u s ta ils
de
d eta ils
h e alth
user
L if e
2 .1 .1
id
u s e r_
H e a lt h
2 .1 .3
us
id
er
h e alth _ id
us er_
_i
d
U s e r _ r e g is t r a t i o n
H e a lt h _ r e g is t r a t i o n
Page | 44
SAFE HANDS
SYSTEM TESTING
Page | 45
SAFE HANDS
5. SYSTEM TESTING
5.1 Testing Strategies
The software engineering process may be viewed as a spiral, as illustrated

in Figure 5. Initially, system engineering defines the role of software and leads to
software requirement analysis, where the information domain, function,
behavior, performance, constraints and validation criteria for the software are
established. Moving inwards along the spiral, we come to design and finally
coding. To develop computer software, we spiral in along streamlines that
decrease the level of abstraction on each turn.
A strategy for software testing may also be envisioned by moving

outward along the spiral of Figure 5. Unit testing begins at the vertex of the
spiral and concentrates on each unit of the software as implemented in the source
code. Testing progresses by moving outward along the spiral to integration
testing, where the focus is on the design and the construction of the software
architecture. Taking another turn outward on the spiral, we encounter validation
testing, where requirements established as part of software requirement analysis
are validated against the software that has been constructed. Finally, we arrive at
system testing, where the software and other system elements are tested as a
whole. To test computer software, we spiral out along streamlines that broaden
the scope of testing..
SAFE HANDS
Figure 1 Testing Strategy
Considering the process from a procedural point of view, testing within

the context of software engineering is actually a series of three steps that are
implemented sequentially. The steps are shown in Figure 6. Initially, tests focus
on each module individually, ensuring that it functions properly as a unit. Hence,
the name unit testing.
Requirements
High Order Tests
Integration test
Design
Unit
Code test
Testing
”direction”
Figure 2 Software Testing
Unit testing makes heavy use of white box testing techniques, exercising
specific paths in a module’s control structure to ensure complete coverage and
maximum error detection. Next modules must be assembled or integrated to form
the complete software package. Integration testing addresses the issues
associated with the dual problems of verification and program construction.
Black box test case design techniques are the most prevalent during integration,
SAFE HANDS
although a limited amount of white box testing may be used to ensure coverage
of major control paths. After the software has been integrated (constructed), a set
of high-order tests are conducted. Validation criteria (established during
requirements analysis) must be tested.
Validation testing provides the final assurance that software meets all
functional, behavioral, and performance requirements. Black box testing
techniques are used exclusively during validation. Software, once validated, must
be combined with other system elements (e.g. hardware, people, databases).
System testing verifies that all elements mesh properly and that overall system
function/performance is achieved.
5.2Testing Methods
The testing methods are:
 Unit Testing
 Integration Testing
 Validation Testing
 User Acceptance Testing
 System Testing
5.2.1Unit Testing
Unit testing focuses verification effort on the smallest unit of the software
design – the module. Using the detail design description as a guide, important
control paths are tested to uncover errors within the boundary of the module. The
relative complexity of tests and the errors detected as a result is limited by the
constrained scope established for unit testing. The unit test is always white box-
oriented, and the step can be conducted in parallel for multiple modules.
SAFE HANDS
All the modules are tested individually with all possible conditions and the
input values. It was found that the modules are error proof with the existing
conditions and environments.
5.2.2Integration Testing
Integration testing is a systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors associated with
interfacing. The objective is to take unit-tested modules and build a program
structure that has been dictated by design. The entire program is tested as a whole.
5.2.3Validation Testing
At the culmination of integration testing, software is completely assembled

as a package. Validation succeeds when the software function manner that is
reasonably expected by the customer. Software validation is achieved through a
series of black box tests that demonstrates conformity with requirement. Deviation
or errors discovered at this project is corrected prior to completion of the project
with the user by negotiating to establish a method for resolving deficiencies.
5.2.4 User Acceptance Testing
User acceptance of the system is the key factor for the success of any
system. The system under consideration is tested for user acceptance by constantly
keeping in touch with prospective system and user at the time of developing and
making changes whenever required.
SAFE HANDS
5.2.5 System Testing
System testing is actually a series of different tests whose primary purpose

is to fully exercise the computer-based system. Although each test has a different
purpose, all work should verify that all system elements have been properly
integrated and perform allocated functions.
 Recovery Testing: it is a system test that forces the software to fall in a variety
of ways and verifies that recovery is properly performed. In this project, if
ever the server crashes, the clients will be notified and all data will be updated
into the database.
 Security Testing: it attempts to verify that protection mechanisms built into the
system will in fact, protect it from improper penetration. This project was
tested for any kind of flaws in security.
 Stress Testing: it executes the system in a manner that demands resources in
abnormal quantity, frequency, or volume. Many intentional efforts were made
to stop the program’s working with different type of invalid input values. Most
of the error conditions were removed with these testing.
 Performance Testing: it is designed to test the run-time performance of
software within the context of an integrated system. Performance testing
occurs throughout all steps in the testing process. Even at the unit level, the
performance of an individual module may be accessed as a white box tests are
conducted. The project was tested for performance during run-time and many
errors were removed during this testing.
SAFE HANDS
SYSTEM
IMPLEMENTATION
AND
MAINTENANCE
SAFE HANDS
3. SYSTEM IMPLEMENTATION AND MAINTENANCE
1.12Implementation
Implementation is the stage of the project where the theoretical design is turned into a
working system. At this time, the main work load, the greatest upheaval and the major
impact on the existing system shifts to the user department. If the implementation is
not carefully planned and controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from old system
to new system. The new system may be totally new, replacing an existing manual or
automated system or it may be a major modification to an existing system. Proper
implementation is essential to provide a reliable system to meet the organization
requirements. Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.
The implementation stage involves the following tasks.
• Careful planning.
• Investigation of system and constrains.
• Design of methods to achieve change over.
• Training of staff in the changeover phase.
• Evaluation of the changeover method.
The method of implementation and the time scale to be adopted are found out
initially. Next the system is tested properly and the same time users are trained in the
new procedures.
Page | 28
SAFE HANDS
 Implementation Procedures
Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system.
In many organizations some one who will not be operating it, will commission the
software development project. In the initial stage, they doubt about the software but
we have to ensure that the resistance does not built up, as one has to make sure that
the active user must be aware of the benefits of using the system. Thus, their
confidence in the software is built up. Proper guidance is imparted to the user so that
he is comfortable in using the application. Before going ahead and viewing the
system, the user must know that for viewing the result, the server program should be
running. If the server object is not up running on the server, the actual processes won’t
take place.
 Implementation Plan
Implementation includes all those activities that take place to convert from the old
system to the new one. The new system may be totally new, replacing an existing
manual or automated system. Proper implementation is essential, to provide a reliable
system to meet organization requirements. Successful implementation may not
guarantee improvement in the organization, using new the system, but improper
installation will prevent it.
The process of putting the developed system in the actual use is called system
implementation. This includes all those activities that take place to convert from the
old system to the new system. The system can be implemented only after thorough
testing is done and if it is found to be working according to the specifications, the
system personnel check the feasibility of the system.
Page | 29
SAFE HANDS
The implementation stage involves the following tasks.
• Investigation of system and constraints.

• Design of methods to achieve the changeover.
• Training of the staff in the changeover phase.
• Evaluation of the changeover method.
The newly proposed system is implemented after the successful testing of the system.
 Post Implementation Review
The final step of the systems approach recognizes that an implemented solution can
fail to solve the problem for which it was developed. The results of implementing a
solution should be monitored and evaluated. This is called post implementation
review process, since the success of a solution is reviewed after it is implemented.
The focus in this step, i.e. to determine if the implemented solution has indeed helped
the firm and selected business units, to meet their system objectives.
6.2 MAINTENANCE
The maintenance phase of the software cycle is the time in which a Software product
performs useful work. After a system is successfully implemented, it should be
maintained in a proper manner. System maintenance is an important aspect in the
software development life cycle. The need for system maintenance is to make it
adaptable to the changes in the system environment. There may be social, technical
and other environment changes, which affects a system, which is implemented.
Software product enhancement may involve providing new functional capabilities,
improving user displays and mode of interaction, upgrading the performance
characteristics of the system. So only through proper system maintenance procedures,
the system can be adapted to cope up with these changes.
Page | 30
SAFE HANDS
Software maintenance is of course, far more than “ finding mistakes”. We may define
maintenance by describing four activities that are undertaken after a program is
released for use.
The first maintenance activity occurs because it is unreasonable to assume that

software testing will uncover latent errors in a large software system. During the use
of any large program, errors will occur and are reported to the developer.
The process that includes the diagnosis and correction of one or more errors are called
corrective maintenance.
The second activity that contributes to a definition of maintenance occurs because of

the rapid change that is encountered in every aspects of computing. Therefore
adaptive maintenance – an activity that modifies software to properly interface with a
changing environment is necessary.
The third activity that may apply to a definition of maintenance occurs when a
software package is successful. As the software is used, recommendations for new
capabilities, modifications to existing functions, and general enhancements are
received from users. To satisfy requests in this category, perfective maintenance is
performed. This activity accounts for the majority of all efforts expended on software
maintenance.
The fourth maintenance activity occurs when software is changed to improve future
maintainability or reliability, or to provide a better basis for future enhancements.
Often called preventive maintenance, this activity is characterized by reverse
engineering and re-engineering techniques.
Page | 31
SAFE HANDS
SCOPE FOR FUTURE

ENHANCEMENTS
SAFE HANDS
Page | 30
SAFE HANDS
SAFE HANDS
4. SCOPE FOR FUTURE ENHANCEMENTS
One of the main features of the web technology is its extensibility. SAFE HANDS is
a complete system as per the user requirement.
Enhancements means modifying, adding or redeveloping the code to support changes

in the specifications. The application provides better extensibility and flexibility for
future enhancement. The design also allows one to add or remove another module or
even modify the existing one without affecting the operations of the rest of the
modules.
This package is developed in PHP with MySQL as back end, it can be further
upgraded with its improved version which provide even more functionalities for the
system and therefore incorporates all aimed features of the software.
The further enhancements that are suggested for this proposed system are:
 Mail sending option for the administrator to policyholders.
 Extend the system for users outside India.
 Premiums paid should be eligible for tax deduction under Section 80C of the
Income Tax Act, 1961.
Page | 32
SAFE HANDS
CONCLUSION
Page | 33
SAFE HANDS
5. CONCLUSION
We believe that all objectives of this work are well met in a computerized system.
Original data has been fed into the system and error free documents are generated. An
efficient report can be done with this system. We are not demanding that this project
work is without any drawbacks, but we are sure that it is unique in its nature. Almost
all suggestions forwarded in the proposed software have been successfully completed
and the final threshold of application has been crossed weaving through the system
developed. The system has been developed using PHP as front-end and MySQL as
back-end.
Thus, through “SAFE HANDS” individuals can know in depth about the various
insurance categories, such as Life, Vehicle and Health. The main idea for the
development of such a system is to avail some of the insurance services online
thereby minimizing his/her visit to the insurance office. It has been created using best
design and coding techniques known. The system is user friendly and is working with
high degree of certainty. “SAFE HANDS” is developed to spread widely and in
particular to the rural areas and to the socially and economically backward classes
with a view to reaching all insurable persons in the country and providing them
adequate financial cover against death at a reasonable cost.
.
SAFE HANDS
ANNEXURE
SAFE HANDS
9. ANNEURE
9.1 Screen Layout
Page | 33
SAFE HANDS
Page | 34
SAFE HANDS
Page | 35
SAFE HANDS
Page | 36
SAFE HANDS
Page | 37
SAFE HANDS
Page | 38
SAFE HANDS
Page | 39
SAFE HANDS
Page | 40
SAFE HANDS
Page | 41
SAFE HANDS
Page | 42
SAFE HANDS
Page | 43
SAFE HANDS
Page | 44
SAFE HANDS
Page | 45
SAFE HANDS
Page | 46
SAFE HANDS
Page | 47
SAFE HANDS
Page | 48
SAFE HANDS
Page | 49
SAFE HANDS
Page | 50
SAFE HANDS
Page | 51
SAFE HANDS
Page | 52
SAFE HANDS
SAFE HANDS
Page | 34
SAFE HANDS
Page | 35
SAFE HANDS
Page | 36
SAFE HANDS
Page | 37
SAFE HANDS
9.2 Reports
Page | 38
SAFE HANDS
Doctor Details Date

06.10.2008
No Name Address Landline No Location City Pin
1 Meera Meera villa,cochin 2210125 Kolencherry Muvattupuzha 600901
2 Sheeba Brown house 3610125 Maramon Kozhencherry 689549
3 Anu Thazhayil house 671291 Thadiyoor Kumband 600254
4 Asha Ash villa 671293 Pullad Chenganur 691471
5 Sally Shalom villa 324712 Malapuram Kannur 654178
6 Anu Sanu house 2347121 Maramon Kozhencherry 689549
7 Fathima Fathima villa 362191 Karukachal Kottiyam 612987
8 Riaz Riaz villa 230062 Kollam Anchal 698701
9 Bobby James homes 313420 Puthiya road Thamanam 623129
10 Bibi Bibi villa 360012 Janatha road Thodupuzha 600547
Page | 39
SAFE HANDS
User Details Date 06.10.2008
First Last Landline

No Address Occupation Income City District
Name Name No
Thazhayil
1 Anu Manu 2671291 Secretary 15000 Kozhenc Pathanamt
house
Thazhayil S/w
2 Sheeba Sam 2671291 10000 Kozhenc Pathanamt
house engineer
H/w Jerome
3 Anju George George villa 2671290 9000 Kollam
engineer nagar
Civil
4 Riaz Babu Riaz villa 2660461 10000 Anchal Kollam
engineer
5 Sally Sam Sally homes 2671211 Teacher 10000 Kozhenc Pathanamt
Page | 40
SAFE HANDS
LifeInsurance Policy Holders Date 06.10.2008
Make
No Policy First Plan Type Nominee
Policy Name VehicleSum Benefit Payment
No Registration No Of Policy Mode
No
No Name TypeAssured Vehicle
Period Mode
1 2130 Anu Secure child Mathew 25000 Maruthi
10 800 YearlyFull
1 2601 Anu KL-03k1169
plan 4wheeler
-Deluxe Insurance
2 2410 Sheeba KL-03k9979 2wheeler Suzuki 220 Third Party
2 2131 Sheeba Money Abraham 15000 12 Half Yearly
3 2403 Anju guarantee plan
KL-03m1069 4wheeler Ford 5001-Deluxe Third Party
Maruthi 800 Full
4 2404 Riaz KL03k-5295 4wheeler
3 2132 Anju Super invest George 25000 -Deluxe
12 Insurance
Quarterly
assure Full
5 2405 Sally KL04-9011 4wheeler Lancer-1005
Insurance
46 2133
2406 Riaz
Babu Automatic
KL01-5312 Babu4wheeler
30000 CityZx
10 -700 Monthly
Third Party
invest
Market return
5 2134 Sally Maria 10000 5 Monthly
plan
Page | 41
SAFE HANDS
VehicleInsurance Policy Holders Date 06.10.2008
Page | 42
SAFE HANDS
HealthInsurance Policy Holders Date 06.10.2008
Policy Benefit
No First Name Doctors Name Sum Insured Nominee
No Period
1 1008 Anu Meera 25000 Aji 5
2 1009 Sheeba Sheeba 15000 Anu 8
3 1010 Anju Anu 30000 Varun 7
4 1011 Riaz Sally 35000 Raji 10
5 1012 Sally Sanu 20000 Meera 8
Page | 43
SAFE HANDS
Page | 44
SAFE HANDS
Page | 45
SAFE HANDS
Page | 46
SAFE HANDS
Page | 47
SAFE HANDS
Page | 48
SAFE HANDS
Page | 49
SAFE HANDS
Page | 50
SAFE HANDS
Page | 51
SAFE HANDS
Page | 52
SAFE HANDS
Page | 53
SAFE HANDS
Page | 54
SAFE HANDS
Page | 55
SAFE HANDS
Page | 56
SAFE HANDS
Page | 57
SAFE HANDS
Page | 58
SAFE HANDS
Page | 59
SAFE HANDS
REFERENCES
SAFE HANDS
6. REFERENCES
Book/References:
• MySQL in 2 ½ days – Jay Greenspan
• Database System Concepts – Silberschatz, Korth & Sudarshan
• Fundamentals of Software Engineering – Ghezzi, Jazayeri & Mandrioli
• An Integrated Approach To Software Engineering – Pankaj Jalote
Websites:
• http://en.wikipedia.org
• http://www.w3schools.com
• http://www.google.com
• http://www.php.net /docs.php
• http://www.mysql.com
• http://www.developerfusion.co.uk
• http://www.freewebmasterhelp.com
• http://www.sourceforge.net
Page | 66
SAFE HANDS
Page | 67

Safehands - FINALdocs

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Safehands - FINALdocs

Caricato da

Copyright:

Formati disponibili

MAR ATHANASIOS COLLEGE FOR ADVANCED STUDIES

Submitted in partial fulfillment of the requirement for the

Department of Computer Applications

MAR ATHANASIOS COLLEGE FOR ADVANCED STUDIES

Mr. Ajith G.S Mr. Tiji Thomas

Rev. Dr Abraham Mulamoottil

MAR ATHANASIOS COLLEGE FOR ADVANCED STUDIES

Certified that the candidate SHEEBA ABRAHAM THAZHAYIL was examined by

Internal Examiner External Examiner

I, SHEEBA ABRAHAM THAZHAYIL do hereby declare that the project work

SHEEBA ABRAHAM THAZHAYIL

Sheeba Abraham Thazhayil

1.1 Organization Profile

By judicious blend of Business analysis & Management with latest

1.2 About the Project

1.3 Objective of the Project

The main objectives of the system are as follows: -

 To provide, administrator with various services such as to add new plans,

System Analysis is a standard procedure to organize and co-ordinate the various

2.2 Existing System

Limitations of Existing System

 Lack of accuracy of data as the existing system is done manually.

 Includes manual work containing lots of paper of work

 More time consumption.

 Access of information is difficult.

 More storage area needed due to redundancy of data.

2.3 Proposed System

The “SAFE HANDS” is an attempt to improve the existing Insurance process

Characteristics of the proposed System

 Can be easily accessible from a distant place

Benefits of the Proposed System

1.5 Feasibility Study

The initial investigation points to a question whether the project is feasible. A

The result of a feasibility study is a formal proposal. The proposal summarizes

• Statements of the problem.

The feasibility study determines whether the proposed system is flexible or

1.5.1 Economic Feasibility

1.5.2 Technical Feasibility

1.5.3 Behavioral Feasibility

1.6 Project Description

removing policyholders, issuing or canceling loans, premium rate setting as well as

2. SYSTEM REQUIREMENT AND SPECIFICATION

SAFE HANDS involves the following hardware and software requirements

1.7 HARDWARE REQUIREMENTS (Minimum)

WEB SERVER / DATABASE SERVER

PROCESSOR : Pentium IV or greater

HARD DISK DRIVE : 80 GB

KEYBOARD : Standard Keyboard

MOUSE : Standard Scroll Mouse

MONITOR : 17” SVGA Color Monitor.

CD-ROM : CD-RW or DVD-RW

CLIENT WORKSTATIONS / DESKTOPS

HARD DISK DRIVE : 40 GB

KEYBOARD : Standard Keyboard

MOUSE : Standard Scroll Mouse

MONITOR : 17” SVGA Color Monitor.

1.8 SOFTWARE REQUIREMENTS (Minimum)

OPERATING SYSTEM : Linux/Windows XP Professional

OPERATING SYSTEM : Linux/Windows

3.3.1 Operating System

Windows NT is a family of operating systems produced by Microsoft, the first