Mini Project

Insurance Approval
ACHARYA INSTITUTE OF GRADUATE

STUDIES
(NACC “A” RE-ACCREDITED & AFFILIATED TO BENGALURU
CITY UNNIVERSITY)
Soldevanahalli, Bengaluru – 560107
A mini project report on
INSURANCE APPROVAL
Submitted By
Jacob Laudwin L (P18AJ21S0174)
Srinivasareddy D N (P18AJ21S0192)
Under the Guidance of

Prof. NAGARAJU M L
Assistant professor, Dept of MCA, AIGS
Acharya Institutes of Graduate Studies Page 1

Insurance Approval
Department of Master of Computer

Applications
ACHARYA INSTITUTE OF GRADUATE STUDIES

(NACC “A” Re-Accredited & Affiliated To Bengaluru City University)
Soldevanahalli, Bengaluru - 560107
DEPARTMENT OF MASTER OF COMPUTER

APPLICATIONS
JUNE 2023
CERTIFICATE
This is to certify that the Project entitled
INSURANCE APPROVAL
Submitted in partial fulfilment of the III SEM MCA Mini-Project
is a result of the bonafide work carried out by
Jacob Laudwin L (P18AJ21S0174)
and
Srinivasareddy D N (P18AJ21S192)
During the Academic Year 2022-2023

Dr. Sudha M,
Nagaraju M L,
Assistant Professor, HOD,
Dept. of MCA, Dept. of MCA,

AIGS, AIGS,
Bangalore – 560107 Bengaluru – 560107

Insurance Approval

Insurance Approval
UNDERTAKING
We, Jacob Laudwin L (P18AJ21S0174), Srinivasareddy D N (P18AJ21S0192) hereby

declare that the project report on “INSURANCE APPROVAL” is carried out and completed
successfully by us, and is our original work.
Jacob Laudwin L Srinivasareddy D N

(P18AJ21S0174) (P18AJ21S0192)

Insurance Approval
ACKNOWLEDGMENT
I express my sincere thanks to my internal guide Mr. Nagaraju M L, Assistant Professor,
Department of MCA, Acharya Institute of Graduate Studies for
the valuable suggestions and guidance throughout the project.
I am thankful to our Head of the Department Dr. Sudha M, Department of MCA, Acharya Institute
of Graduate Studies for constant encouragement and support throughout the project.
I would also like to extend my gratitude to our Principal Dr. Gurunath Rao Vaidya, Acharya
Institute of Graduate Studies for constantly evaluating and setting up rules which help the students to
learn, innovate and indulge into a better quality of education.
I extend my thanks to all the faculty members and the Management for their constant support and
upliftment.
Date: Student Name
(USN)
Synopsis

Insurance Approval
The insurance management system is a comprehensive software solution designed to

streamline and automate various processes within insurance companies. It serves as a
centralized platform for managing policy administration, claims processing, underwriting,
and compliance tasks. The system integrates with various data sources, enabling insurers to
efficiently handle customer information, policy details, and claims data.
Key features of the Insurance Management System include policy administration, claims
processing, underwriting, customer relationship management (CRM), billing and accounting,
reporting and analytics, and integration capabilities.
The policy administration module allows insurers to create, update, and manage insurance
policies. It supports policy quoting, rating, issuance, endorsements, and renewals. The claims
processing module automates the handling of insurance claims, tracking and managing
claims, and calculating claim settlements.
2022-23
Insurance Approval
INDEX
Sr. No. Particular Pg. No.
1 Introduction 7
2 System Environment
2.1 Hardware Configuration 8
2.2 Software Configuration 9
3 Problem Specification
3.1 Introduction, Objective and Purpose 10
3.2 System Model 12
3.3 Feasibility Study 16
3.3.1 Economical Feasibility 16
3.3.2 Technical Feasibility 17
3.3.3 Behavioural Feasibility 17
4 Project Analysis and Planning 18
4.1 Implementation Planning 20
5 Risk Identification and Management 21
6 Technology Used For Development 23
7 Database Design 26
8 Implementation 27
9 Testing 34
10 Screenshots 36
11 Future Enhancement 39
12 Conclusion 40
13 References 41
CHAPTER 1

Insurance Approval
INTRODUCTION
The goal of bank loan prediction is to develop an accurate and reliable model that can assist
banks and lenders in making informed decisions regarding loan approvals. By leveraging
historical loan data, along with various borrower attributes and financial indicators, machine
learning models can assess creditworthiness and estimate the probability of loan repayment.
The ultimate aim of bank loan prediction is to assist financial institutions in mitigating risk
and improving the efficiency of their lending processes. By accurately assessing
creditworthiness, banks can streamline loan approval procedures, reduce the likelihood of
defaults, and optimize their loan portfolios. Furthermore, borrowers can benefit from fair and
transparent evaluation processes, ensuring that loans are granted based on merit and their
ability to fulfil repayment obligations.
Bank loan prediction using machine learning is a vital application that leverages advanced
algorithms to analyse historical data and predict the likelihood of loan approval or default.
With the increasing availability of digital data and the need for efficient credit risk
assessment, machine learning models have become a valuable tool for financial institutions.
The use of machine learning in bank loan prediction involves several stages, including data
collection, pre-processing, feature engineering, model selection, training, and evaluation.
Historical loan data, encompassing attributes such as credit scores, income, employment
history, loan amounts, and repayment status, serves as the foundation for training the model.
By analysing this data and extracting meaningful patterns, the model can identify critical
factors that contribute to loan default or successful repayment.
CHAPTER 2

Insurance Approval
SYSTEM ENVIRONMENT
2.1 Software Requirements :
A software requirement is a field within software engineering that deals with

establishing the needs of stakeholders that are to be solved by software. A
software requirements specification (SRS) is a description of a software system to
be developed. Software requirements specifications can help prevent software
project failure.
OPERATING SYSTEM : Windows 7 or above
LANGUAGE : Python
BACKEND : SQLite3
DESIGNING TOOLS : HTML, CSS
APPLICATIONS : PyCharm
WEB BROWSER : Chrome, Firefox, Microsoft Edge

Insurance Approval
2.2 Hardware Requirements
The most common set of requirements defined by any operating system

or software application is the physical computer resources, also known
as hardware, A hardware requirements list is often accompanied by a
hardware compatibility list, especially in case of operating systems. An
HCL lists tested, compatible, and sometimes incompatible hardware
devices for a particular operating system or application. The following
sub-sections discuss the various aspects of hardware requirements.
All computer operating systems are designed for a particular computer
architecture. Most software applications are limited to particular
operating systems running on particular architectures. Although
architecture-independent operating systems and applications exist, most
need to be recompiled to run on a
new architecture.
The power of the central processing unit (CPU) is a fundamental system
requirement for any software. Most software running on x86 architecture
define processing power as the model and the clock speed of the CPU.
Many other features of a CPU that influence its speed and power, like
bus speed, cache, and MIPS are often ignored. This definition of power
is often erroneous, as Marathon and Intel Pentium CPUs at similar clock
speed often have different throughput speeds.
 10GB HDD(min)
 6GB RAM(min)
 Intel I3 or more higher processor
 Keyboard
 Mouse
 Monitor

Insurance Approval
CHAPTER 3
3.1 PROBLEM SPECIFICATION
3.1.1 Introduction, Objectives and purpose

The insurance industry plays a vital role in managing risk and providing financial protection
to individuals and businesses. As the industry continues to evolve, insurance companies are
increasingly turning to advanced technologies to enhance their operations and improve
customer experiences. One such technology is an Insurance Management System (IMS),
which is a comprehensive software solution designed to streamline and automate various
processes involved in insurance operations. An Insurance Management System serves as a
centralized platform that enables insurance companies to efficiently manage policy
administration, claims processing, underwriting, customer management, and other critical
aspects of their business. It integrates multiple functionalities and data sources into a cohesive
system, facilitating seamless communication and data flow across different departments and
stakeholders. The primary objective of an Insurance Management System is to enhance
operational efficiency, reduce manual effort, minimize errors, and improve overall
productivity within the insurance company. By automating routine tasks and leveraging data
analytics capabilities, an IMS empowers insurers to make informed decisions, optimize
resource allocation, and provide timely and accurate services to policyholders. Key features
of an Insurance Management System typically include policy management, claims
management, customer relationship management, document management, billing and
accounting, reporting and analytics, and integration with external systems and data sources.
These features enable insurers to efficiently handle policy issuance and renewals, process
claims efficiently, maintain customer records, generate invoices, track financial transactions,
and extract meaningful insights from the collected data.
Implementing an Insurance Management System can bring numerous benefits to

insurance companies, including improved customer satisfaction through faster and more
accurate service delivery, enhanced risk management through real-time monitoring and
analysis of policy and claims data, reduced operational costs through process automation, and
better compliance with regulatory requirements.

Insurance Approval
3.1.2 Objectives:
Efficient Policy Administration: The IMS aims to streamline and automate policy
administration processes, including policy issuance, underwriting, endorsements,
renewals, and cancellations. It enables insurance companies to handle policy-related
tasks efficiently, ensuring accurate and timely policy management.
Seamless Claims Processing: One of the key objectives of an IMS is to facilitate smooth
claims processing. It automates and simplifies the end-to-end claims lifecycle, from
claims registration to assessment, verification, settlement, and recovery. The IMS helps
improve the speed and accuracy of claims handling, leading to enhanced customer
satisfaction and operational efficiency.
Effective Customer Relationship Management: The IMS focuses on providing a
centralized platform for managing customer information and interactions. It aims to
maintain a comprehensive customer database, enabling insurers to track customer
history, preferences, and communication. This helps insurers deliver personalized
services, respond promptly to customer queries, and build strong customer
relationships.
Accurate Data Management and Analysis: An essential objective of the IMS is to
ensure proper storage, organization, and analysis of insurance-related data. It helps
insurers collect, process, and analyse vast amounts of data, including policy records,
claims history, customer information, and market trends. By leveraging data analytics
techniques, the IMS enables insurers to extract valuable insights, identify patterns,
detect fraud, and make informed business decisions.
Regulatory Compliance: The IMS aims to assist insurance companies in adhering to
regulatory requirements and industry standards. It helps automate compliance-related
tasks, such as generating reports, tracking policy compliance, and ensuring data
privacy and security. Compliance features within the IMS help insurers avoid penalties,
maintain transparency, and operate within legal boundaries.
Enhanced Operational Efficiency: The IMS seeks to improve operational efficiency by
automating routine tasks, reducing manual effort, and minimizing errors. It optimizes
workflow processes, eliminates duplication of efforts, and provides a centralized

Insurance Approval
system for collaboration and communication among different departments. The IMS
enables insurers to streamline operations, save costs, and allocate resources effectively.
3.1.3 Purpose:
The purpose of insurance management is to fulfil several key objectives and serve
various stakeholders in the Insurance industry. Here are some main purposes:
 Automation and Efficiency: Python's extensive libraries and frameworks enable the
automation of various insurance processes, reducing manual effort and increasing
operational efficiency. Python allows for the development of streamlined workflows,
automated data processing, and efficient communication between different components of
the IMS.
 Data Processing and Analysis: Python's robust libraries, such as Pandas and NumPy,
provide powerful tools for data manipulation, processing, and analysis. With Python, an
IMS can handle large volumes of insurance data, extract insights, and perform complex
calculations. Python's integration with machine learning libraries, such as Scikit-learn,
allows for predictive analytics and risk modelling.
 Customization and Flexibility: Python's versatility and readability make it an ideal
choice for building customizable insurance management solutions. Python's object-
oriented programming (OOP) capabilities enable developers to design modular and
scalable systems, allowing for easy customization and adaptation to specific business
needs.
 Integration and Interoperability: Python's extensive support for APIs and its ability to
integrate with various external systems and data sources make it suitable for developing an
IMS with seamless connectivity. Python enables the integration of insurance systems with
external services, such as payment gateways, document management systems, or third-
party data providers.
 Web Development and User Interface: Python web frameworks, such as Django or
Flask, facilitate the development of intuitive user interfaces and web portals for accessing
the IMS. These frameworks provide tools for user authentication, session management,
and secure data transmission, enabling insurance agents, administrators, and customers to
interact with the system efficiently.

Insurance Approval
 Testing and Debugging: Python offers robust testing frameworks, such as PyTest or
UnitTest, which aid in ensuring the reliability and stability of the IMS.
3.2 SYSTEM MODEL
3.2.1 Dataflow Diagram:
A data flow diagram shows the way information flows through a process or system. It
includes data inputs and outputs, data stores, and the various subprocesses the data moves
through. DFDs are built using standardized symbols and notation to describe various entities
and their relationships. A data flow diagram (DFD) is a graphical representation of how data
flows within a system. It is commonly used in software engineering and system analysis to
visualize the flow of data between various processes, data stores, and external entities.

Insurance Approval
3.2.2 Sequence diagram:

A sequence diagram is a type of interaction diagram because it describes how and
in what order a group of objects works together. These diagrams are used by
software developers and business professionals to understand requirements for a
new system or to document an existing process. Sequence diagrams are
sometimes known as event diagrams or event scenarios.

Insurance Approval
3.2.3 E-R DIAGRAM:

An Entity-Relationship (ER) diagram is a visual representation of the entities
(objects), their attributes (properties), and the relationships between entities in a
database. ER diagrams are commonly used in database design to model the structure
and organization of data.

Insurance Approval
3.3 FEASIBALITY STUDY
To demonstrate the feasibility of real-time systems in Python, we implemented real-time

tasks in Python using the C types module in a real-time Linux environment. We compared the
real-time metrics of periodicity and responsiveness in Python and C/C++ languages. The
statistical results always showed promising results in C/C++. While Python could be easily

Insurance Approval
and rapidly implemented in the experimental condition, C/C++ had the disadvantage of being
somewhat complicated and time-consuming concerning its coding and compiling processes.
Lastly, an environment was built using Ether CAT Fieldbus-based servo motors and digital
outputs used in actual industrial sites, and periodicity and synchronicity were measured
through a python-based real-time control system experiment also performed statistical
analysis using Z−score.
As a result, Python was shown to work in a real-time environment, task periodicity was
satisfied, priority-based pre-emption occurred, and the feasibility of Python was researched
on a real-time control system.
The results here can be applied to industrial controllers, robots, and the mobility field
where real-time performance is required, and this method can extend the limits and relax the
constraints of real-time performance with Python, enabling integration with real-time systems
in various fields, such as artificial intelligence (AI), data science, and networking.
For future studies, as shown in RT−AIDE, performance evaluations and research using a
greater variety of real-time metrics will be conducted to improve experiment and analysis
methods, including power consumption, which may be applied only to RT-Pre-empt but also
to several RTOSs, and both non–real-time and real-time types. In addition, we will be
conducting research on intelligent control systems leveraging machine learning and neural
network inference for service and industrial robots
3.3.1 ECONOMIC FEASIBILITY
Economic feasibility determines whether the required software is capable of generating

financial gains for an organization. It involves the cost incurred on the software
development team, estimated cost of hardware and software, cost of performing feasibility
study, and so on. For this, it is essential to consider expenses made on purchases (such as
hardware purchase) and activities required to carry out software development. In addition, it
is necessary to consider the benefits that can be achieved by developing the software.
Software is said to be economically feasible if it focuses on the issues listed below.
• Cost incurred on software development to produce long-term gains for an organization.
• Cost required to conduct full software investigation (such as requirements elicitation and
requirements analysis).

Insurance Approval
• Cost of hardware, software, development team, and training.
3.3.2 TECHNICAL FEASIBILITY
Technical feasibility assesses the current resources (such as hardware and software) and
technology, which are required to accomplish user requirements in the software within the
allocated time and budget. For this, the software development team ascertains whether the
current resources and technology can be upgraded or added in the software to accomplish
specified user requirements. Technical feasibility also performs the following tasks.
• analysis the technical skills and capabilities of the software development team members.
• Determines whether the relevant technology is stable and established.
• Ascertains that the technology chosen for software development has a large number of
users so that they can be consulted when problems arise or improvements are required.
3.3.3 BEHAVIOURAL FEASIBILITY
Behavioural feasibility refers to assessing the acceptance and willingness of users to adopt
and use a proposed system or software. In the case of an Insurance Management System
(IMS), evaluating behavioural feasibility involves understanding the attitudes, preferences,
and behaviour patterns of the system's potential users, including insurance agents,
administrators, and customers. This assessment aims to determine whether the proposed IMS
aligns with the needs and expectations of the users and whether they are likely to embrace
and utilize the system effectively.
CHAPTER 4
PROJECT ANALYSIS AND PLANNING

Project Analysis and Planning is a crucial phase in project management where a
comprehensive evaluation and strategic planning of a project are conducted. It involves
gathering information, assessing feasibility, defining goals and objectives, determining

Insurance Approval
resources, and developing a roadmap for project execution. Here's an overview of the key
steps involved in project analysis and planning:
 Define Project Objectives: Clearly articulate the goals and objectives of the IMS
project. This may include improving operational efficiency, enhancing customer
service, streamlining policy administration, or enabling advanced data analytics.
 Identify Stakeholders: Identify the individuals or groups who will be impacted
by or have an interest in the IMS project. This may include insurance company
executives, IT staff, insurance agents, administrators, underwriters, claims
processors, and customers.
 Gather Requirements: Engage with stakeholders to elicit their needs,
expectations, and pain points related to insurance operations. Conduct interviews,
surveys, or workshops to capture detailed requirements. Identify functional
requirements, such as policy management, claims processing, customer
relationship management, reporting and analytics, and integration with external
systems. Determine non-functional requirements, including system performance,
scalability, security, usability, and regulatory compliance.
 Perform System Analysis: Analyse the current insurance processes and
workflows to identify inefficiencies, bottlenecks, and areas for improvement.
Identify data sources and integration points within the insurance ecosystem, such
as external data providers, payment gateways, or document management systems.
Assess the potential impact of implementing the IMS on existing systems,
infrastructure, and personnel.
 Determine System Components and Functionalities: Based on the requirements
and analysis, define the core components and functionalities of the IMS. This may
include policy administration, claims management, customer relationship
management, document management, reporting and analytics, and integration
capabilities. Prioritize functionalities based on their importance, feasibility, and
alignment with project objectives.
 Evaluate Technology Stack: Determine the appropriate technology stack for
developing the IMS. Consider factors such as scalability, maintainability, security,
and compatibility with existing infrastructure and systems. Evaluate programming

Insurance Approval
languages, frameworks, databases, and third-party libraries or APIs that best suit
the project requirements. For example, Python, Django, PostgreSQL, and data
analytics libraries like Pandas and Scikit-learn.
 Assess Project Constraints and Risks: Identify any constraints or limitations
that may impact the implementation of the IMS. These may include budgetary
constraints, time limitations, resource availability, or regulatory compliance
requirements. Conduct a risk assessment to identify potential risks and develop
strategies to mitigate or manage them. This includes risks related to data security,
system performance, technology compatibility, or user adoption.
 Create Project Plan: Develop a detailed project plan that outlines the tasks,
timelines, and resource allocation for each phase of the IMS project. Include
milestones, deliverables, and dependencies to ensure effective project
management. Define roles and responsibilities for team members and establish
communication channels and reporting mechanisms.
 Obtain Stakeholder Buy-In: Present the project analysis findings and the
proposed IMS solution to key stakeholders. Seek their feedback and obtain their
buy-in and support for the project. Address any concerns or questions raised by
stakeholders and ensure alignment between their expectations and the project
objectives.
4.1 Implementation plan
The implementation plan and timeline shown:
Name of the task Start date End date Duration
Project kick off 2/14/2022 2/15/2022 1

Insurance Approval
initial design 2/16/2022 2/20/2022 4

Research 03/01/2022 03/07/2022 6
Initiating development 03/15/2022 03/20/2022 5
Finalizing design 03/21/2022 03/24/2022 3
Testing functionality 03/29/2022 03/31/2022 2
Implementing the solution 04/01/2022 04/06/2022 4
Initiating integration of modules 04/07/2022 04/12/2022 5
Finalizing
essential 04/13/2022 04/20/2022 7
functionalities
Planning add-on functionalities 04/21/2022 04/26/2022 5
Implementing add-
on functionalities 04/27/2022 04/30/2022 3
testing of the project 05/01/2022 05/06/2022 5
implement improvements and
debugging 05/07/2022 05/10/2022 3
CHAPTER 5
Risk Identification and Management

Risk identification and management is a crucial aspect of project management. It involves
identifying potential risks that could affect project objectives, analysing their likelihood and

Insurance Approval
impact, and implementing strategies to mitigate or manage those risks. Here's an overview of
the key steps involved in risk identification and management:
Risk Identification Brainstorming:
 Engage project team members and stakeholders in brainstorming sessions to identify

potential risks. Consider all aspects of the project, such as scope, resources, schedule,
technology, and external factors.
 Documentation: Document identified risks in a risk register or risk log. Include a
description of each risk, its potential causes, potential impacts, and any initial thoughts on
mitigation strategies.
Risk Analysis:
 Risk Probability and Impact Assessment: Assess the likelihood or probability of each
identified risk occurring and the potential impact it would have on the project objectives.
This analysis helps prioritize risks for further attention.
 Qualitative Analysis: Use subjective scales or qualitative methods (e.g., low, medium,
high) to assess risk probability and impact based on expert judgment or historical data.
 Quantitative Analysis: If sufficient data is available, conduct a quantitative analysis using
techniques such as Monte Carlo simulations or sensitivity analysis to assign numerical
probabilities and impacts to risks.
Risk Response Planning:
 Risk Avoidance: Identify risks that can be completely avoided by taking preventive
actions. Modify the project plan or scope to eliminate the risk altogether.
 Risk Mitigation: Develop strategies to reduce the probability or impact of identified risks.
Implement preventive measures or controls to minimize the likelihood of occurrence or
reduce the severity of the impact.
 Risk Transfer: Transfer the risk to a third party, such as through insurance or outsourcing,
to mitigate the project's potential financial or operational impact.
 Risk Acceptance: Accept certain risks if their impact is deemed acceptable and no further
actions are deemed necessary. Document the decision-making process and ensure
stakeholders are aware of the accepted risks.

Insurance Approval
Risk Monitoring and Control:
 Regular Review: Continuously monitor identified risks throughout the project lifecycle.
Update the risks register and reassess risks as the project progresses and new information
becomes available.
 Trigger Identification: Establish triggers or warning signs that indicate when a risk is
about to occur or has occurred. Define specific actions or contingency plans to be
activated when triggers are observed.
 Risk Response Execution: Implement the planned risk response strategies when
necessary. This may involve activating contingency plans, adjusting project resources or
schedules, or seeking additional approvals or support.
Communication and Documentation:
 Stakeholder Engagement: Keep stakeholders informed about identified risks, their

potential impact, and the strategies in place to manage them. Engage in regular
communication to ensure their awareness and involvement.
 Risk Reporting: Include risk-related updates in project status reports and meetings.
Provide clear and concise information about the status of identified risks, any changes in
risk assessments, and the effectiveness of risk response strategies.
Remember that risk management is an on-going process throughout the project lifecycle.
Regularly reassess risks, monitor the effectiveness of risk response strategies, and make
adjustments as needed. By actively identifying and managing risks, project teams can
minimize potential threats and increase the chances of project success.
CHAPTER 6
TECHNOLOGY USED FOR DEVELOPMENT

Insurance Approval
PYTHON DJANGO FRAMEWORK AND SOFTWARE

ENVIRONMENT
Python:
Python is a high-level, general-purpose programming language. Its design philosophy

emphasizes code readability with the use of significant indentation via the off-side rule.
Python is dynamically typed and garbage-collected. It supports multiple programming
paradigms, including structured (particularly procedural), object-oriented and functional
programming. It is often described as a "batteries included" language due to its
comprehensive standard library.
Guido van Rossum began working on Python in the late 1980s as a successor to the ABC
programming language and first released it in 1991 as Python 0.9.0. Python 2.0 was released
in 2000. Python 3.0, released in 2008, was a major revision not completely backward-
compatible with earlier versions. Python 2.7.18, released in 2020, was the last release of
Python 2.
DJANGO FRAMEWORK:

Insurance Approval
Django is a Python framework that makes it easier to create web sites using Python.
Django takes care of the difficult stuff so that you can concentrate on building your web
applications. Django emphasizes reusability of components, also referred to as DRY (Don't
Repeat Yourself), and comes with ready-to-use features like login system, database
connection and CRUD operations (Create Read Update Delete). Django was invented by
Lawrence Journal-World in 2003, to meet the short deadlines in the newspaper and at the
same time meeting the demands of experienced web developers. Initial release to the public
was in July 2005. Latest version of Django is 4.0.3 (March 2022).
Django follows the MVT design pattern (Model View Template).
 Model - The data you want to present, usually data from a database.
 View - A request handler that returns the relevant template and content - based on the
request from the user.
 Template - A text file (like an HTML file) containing the layout of the web page, with
logic on how to display the data.
SQLite:

Insurance Approval
SQLite is a database engine written in the C programming language. It is not a

standalone app; rather, it is a library that software developers embed in their apps. As such, it
belongs to the family of embedded databases. It is the most widely deployed database engine,
as it is used by several of the top web browsers, operating systems, mobile phones, and
other embedded systems.
Many programming languages have bindings to the SQLite library. It generally

follows PostgreSQL syntax, but does not enforce type checking by default. This means that
one can, for example, insert a string into a column defined as an integer.
D. Richard Hipp designed SQLite in the spring of 2000 while working for General

Dynamics on contract with the United States Navy. Hipp was designing software used for
a damage-control system aboard guided-missile destroyers, which originally used HP-
UX with an IBM Informix database back-end. SQLite began as a TCL extension.
CHAPTER 7

Insurance Approval
DATABASE DESIGN
POLICY HOLDERS
Policyholders in insurance refer to individuals or entities that have purchased an insurance

policy from an insurance company. A policyholder is also commonly known as an insured or
a customer.
EXISTING POLICIES
Existing policies in insurance refer to insurance policies that are currently in effect and have
not yet expired or been cancelled. These are the policies that policyholders have purchased
and are actively covered by.
INSURANCE CATEGORIES
Insurance is a way to manage your risk. When you buy insurance, you purchase protection
against unexpected financial losses. The insurance company pays you or someone you choose
if something bad happens to you. If you have no insurance and an accident happens, you may
be responsible for all related costs.
CHAPTER 8

Insurance Approval
IMPLEMENTATION
def main():
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'insurancemanagement.settings')
try:
from django.core.management import execute_from_command_line
except ImportError as exc:
raise ImportError(
"Couldn't import Django. Are you sure it's installed and "
"available on your PYTHONPATH environment variable? Did you "
"forget to activate a virtual environment?"
) from exc
execute_from_command_line(sys.argv)
if _name_ == '_main_':
main()
import os
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)

BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(_file_)))
TEMPLATE_DIR = os.path.join(BASE_DIR,'templates')
STATIC_DIR=os.path.join(BASE_DIR,'static')
MEDIA_ROOT=os.path.join(BASE_DIR,'static')
# Quick-start development settings - unsuitable for production

# See https://docs.djangoproject.com/en/3.0/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!

Insurance Approval
SECRET_KEY = 'ls@!_(edqp*xy76kvbsst$07at(v^li*2&ew!^$8o(@wa6@a+$'
# SECURITY WARNING: don't run with debug turned on in production!

DEBUG = True
ALLOWED_HOSTS = []
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'widget_tweaks',
'insurance',
'customer',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',

Insurance Approval
ROOT_URLCONF = 'insurancemanagement.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [TEMPLATE_DIR,],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'insurancemanagement.wsgi.application'
# Database
# https://docs.djangoproject.com/en/3.0/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),

Insurance Approval
}
}
# Password validation
# https://docs.djangoproject.com/en/3.0/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/3.0/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True

Insurance Approval
USE_L10N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/3.0/howto/static-files/
STATIC_URL = '/static/'
STATICFILES_DIRS=[
STATIC_DIR,
]
LOGIN_REDIRECT_URL='/afterlogin'
#for contact us give your gmail id and password

EMAIL_BACKEND ='django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_USE_TLS = True
EMAIL_PORT = 587
EMAIL_HOST_USER = 'from@gmail.com' # this email will be used to send emails
EMAIL_HOST_PASSWORD = 'xyz' # host email password required
# now sign in with your host gmail account in your browser
# open following link and turn it ON
# https://myaccount.google.com/lesssecureapps
# otherwise you will get SMTPAuthenticationError at /contactus
# this process is required because google blocks apps authentication by default
EMAIL_RECEIVING_USER = ['to@gmail.com'] # email on which you will receive
messages sent from website
from django.contrib import admin
from django.urls import path
from insurance import views
from django.contrib.auth.views import LogoutView,LoginView
from django.urls import path,include

Insurance Approval
urlpatterns = [
path('admin/', admin.site.urls),
path('customer/',include('customer.urls')),
path('',views.home_view,name=''),
path('logout',
LogoutView.as_view(template_name='insurance/logout.html'),name='logout'),
path('aboutus', views.aboutus_view),
path('contactus', views.contactus_view),
path('afterlogin', views.afterlogin_view,name='afterlogin'),
path('adminlogin',
LoginView.as_view(template_name='insurance/adminlogin.html'),name='adminlogin'),
path('admin-dashboard', views.admin_dashboard_view,name='admin-dashboard'),
path('admin-view-customer', views.admin_view_customer_view,name='admin-view-
customer'),
path('update-customer/<int:pk>', views.update_customer_view,name='update-customer'),
path('delete-customer/<int:pk>', views.delete_customer_view,name='delete-customer'),
path('admin-category', views.admin_category_view,name='admin-category'),
path('admin-view-category', views.admin_view_category_view,name='admin-view-
category'),
path('admin-update-category', views.admin_update_category_view,name='admin-update-
category'),
path('update-category/<int:pk>', views.update_category_view,name='update-category'),
path('admin-add-category', views.admin_add_category_view,name='admin-add-category'),
path('admin-delete-category', views.admin_delete_category_view,name='admin-delete-
category'),

Insurance Approval
path('delete-category/<int:pk>', views.delete_category_view,name='delete-category'),
path('admin-policy', views.admin_policy_view,name='admin-policy'),
path('admin-add-policy', views.admin_add_policy_view,name='admin-add-policy'),
path('admin-view-policy', views.admin_view_policy_view,name='admin-view-policy'),
path('admin-update-policy', views.admin_update_policy_view,name='admin-update-
policy'),
path('update-policy/<int:pk>', views.update_policy_view,name='update-policy'),
path('admin-delete-policy', views.admin_delete_policy_view,name='admin-delete-policy'),
path('delete-policy/<int:pk>', views.delete_policy_view,name='delete-policy'),
path('admin-view-policy-holder', views.admin_view_policy_holder_view,name='admin-
view-policy-holder'),
path('admin-view-approved-policy-holder',
views.admin_view_approved_policy_holder_view,name='admin-view-approved-policy-
holder'),
path('admin-view-disapproved-policy-holder',
views.admin_view_disapproved_policy_holder_view,name='admin-view-disapproved-
policy-holder'),
path('admin-view-waiting-policy-holder',
views.admin_view_waiting_policy_holder_view,name='admin-view-waiting-policy-holder'),
path('approve-request/<int:pk>', views.approve_request_view,name='approve-request'),
path('reject-request/<int:pk>', views.disapprove_request_view,name='reject-request'),
path('admin-question', views.admin_question_view,name='admin-question'),
path('update-question/<int:pk>', views.update_question_view,name='update-question'),
]
CHAPTER 9
TESTING

Insurance Approval
Testing Strategies:
There are two general strategies for testing software. There are follows.
Code Testing:
This examines the logic of the program. To follow this test, cases are developed such that very
path of the program is tested.
Specification Testing:
Specification testing examines the specifications starting what the program should
do and how it should perform under various conditions. Then test cases are developed for
each condition and combinations of conditions and to be submitted for processing.
Stages in the testing process:

Unit Testing:
Individual components are tested to ensure that they operate correctly. Each component is tested
independently without other system components. Ex. Checked for Login and Password with the
table.
Module Testing:
Module is a collection of dependent components such as an object class an abstract data
type or some looser collection of procedures and functions. A module encapsulates related
components so can be tested without other system modules.
Subsystem Testing:
This phase involves testing collection of modules, which have been integrated into
subsystems. Subsystems may be independently designed and implemented. The most
common problems which arise in the large software systems are subsystems interface
mismatches. The subsystem test process should therefore concentrate on the detection of
interface errors by rigorously exercising these interfaces.
System Testing:
The subsystems are integrated to make up the entire system. The testing process is
concerned with finding errors, which result from unanticipated interactions between
subsystems and system components. It is also concerned with validating that the system is
functional and non-functional requirements.
Ex Those all subsystems are integrated and checked for inter-dependency between the subsystems.

Insurance Approval
Acceptance Testing:
This is final stage in testing process before the system is tested for operational use. The
system is tested with data supplied by the system procurer rather than simulated test data.
Acceptance testing may reveal errors and omissions in the systems requirements definitions
because the real data exercises the system in different phase from the test data. Acceptance
testing may also reveal the requirements problems where the system facilities do not really
meet the user’s needs or system performance is unacceptable.
CHAPTER 10
SCREENSHOT

Insurance Approval
Home page:
CUSTOMER LOGIN PAGE:
LOGIN PAGE:

Insurance Approval
HOME PAGE:
CUSTOMER SIGNUP PAGE:

Insurance Approval
Chapter 11
FUTURE ENHANCEMENT

Insurance Approval
In the future, Insurance management systems are likely to undergo several enhancements to
keep up with evolving technology and customer expectations. Here are some potential future
enhancements.
 Integration of artificial intelligence (AI): AI-powered algorithms can be used to

automate various aspects of insurance management, such as underwriting, claims
processing, fraud detection, and customer support. AI can improve efficiency,
accuracy, and speed in decision-making processes.
 Advanced data analytics: Insurance management systems will leverage big data
analytics to gain insights into customer behaviour, risk assessment, and market
trends. Predictive analytics can be used to identify potential risks, prevent fraud,
and personalize insurance offerings.
 Blockchain technology: Blockchain can enhance security and transparency in
insurance processes. It can be utilized for secure data sharing, verification of
policyholders, and smart contracts, automating claims settlement processes.
 Internet of Things (IoT) integration: IoT devices, such as connected cars,
wearables, and smart home devices, can provide real-time data to insurance
management systems. This data can be utilized for risk assessment, personalized
pricing, and proactive risk mitigation.
CHAPTER 12

Insurance Approval
CONCLUSION
insurance approval systems play a crucial role in the efficient operation of insurance
companies. They enable insurers to streamline processes, improve customer service, manage
risks, and maintain regulatory compliance. Over time, these systems have evolved to
incorporate advancements in technology and customer expectations. Insurance approval
systems provide a centralized repository for storing policyholder information, claims data,
underwriting details, and other essential data. This allows for easy access, retrieval, and
analysis of information, leading to faster decision-making and improved operational
efficiency. These systems facilitate policy administration tasks such as policy issuance,
renewal, endorsement, and cancellation. They automate these processes, reducing manual
errors and ensuring accuracy and consistency across policy documentation.
CHAPTER 13
REFERENCES

Insurance Approval
 Book: Software Engineering. Author : A.A. Puntambekar.
 Book : Programming the World Wide Web. Author : Robert W. Sebesta. (Fourth
Edition).
 Python : https://www.w3schools.com/python/
 Django : https://www.javatpoint.com/django-tutorial
 SQLite3 : https://docs.python.org/3/library/sqlite3.html
 HTML : https://www.w3schools.com/html
 CSS : https://www.javatpoint.com/css-tutorial
 Python : https://www.programiz.com/python-programming
 Django : https://www.djangoproject.com/
 SQL : https://www.tutorialspoint.com/sql/index.htm
 PyCharm : https://realpython.com/pycharm-guide/
 Bootstrap : https://django-bootstrap-v5.readthedocs.io/en/latest/

Mini Project

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mini Project

Uploaded by

Copyright:

Available Formats

Insurance Approval

ACHARYA INSTITUTE OF GRADUATE

A mini project report on

Under the Guidance of

Acharya Institutes of Graduate Studies Page 1

Department of Master of Computer

ACHARYA INSTITUTE OF GRADUATE STUDIES

DEPARTMENT OF MASTER OF COMPUTER

During the Academic Year 2022-2023

Dept. of MCA, Dept. of MCA,

Acharya Institutes of Graduate Studies Page 2

Acharya Institutes of Graduate Studies Page 3

We, Jacob Laudwin L (P18AJ21S0174), Srinivasareddy D N (P18AJ21S0192) hereby

Jacob Laudwin L Srinivasareddy D N

Acharya Institutes of Graduate Studies Page 4

I express my sincere thanks to my internal guide Mr. Nagaraju M L, Assistant Professor,

Department of MCA, Acharya Institute of Graduate Studies for

the valuable suggestions and guidance throughout the project.

learn, innovate and indulge into a better quality of education.

Date: Student Name

Acharya Institutes of Graduate Studies Page 5

The insurance management system is a comprehensive software solution designed to

2.1 Hardware Configuration 8

2.2 Software Configuration 9

3.1 Introduction, Objective and Purpose 10

3.2 System Model 12

3.3 Feasibility Study 16

3.3.1 Economical Feasibility 16

3.3.2 Technical Feasibility 17

3.3.3 Behavioural Feasibility 17

4 Project Analysis and Planning 18

4.1 Implementation Planning 20

5 Risk Identification and Management 21

6 Technology Used For Development 23

Acharya Institutes of Graduate Studies Page 7

Acharya Institutes of Graduate Studies Page 8

2.1 Software Requirements :

A software requirement is a field within software engineering that deals with

OPERATING SYSTEM : Windows 7 or above

DESIGNING TOOLS : HTML, CSS

WEB BROWSER : Chrome, Firefox, Microsoft Edge

Acharya Institutes of Graduate Studies Page 9

2.2 Hardware Requirements

The most common set of requirements defined by any operating system

Acharya Institutes of Graduate Studies Page 10

3.1 PROBLEM SPECIFICATION

3.1.1 Introduction, Objectives and purpose

Implementing an Insurance Management System can bring numerous benefits to

Acharya Institutes of Graduate Studies Page 11

Acharya Institutes of Graduate Studies Page 12

Acharya Institutes of Graduate Studies Page 13

3.2 SYSTEM MODEL

3.2.1 Dataflow Diagram:

Acharya Institutes of Graduate Studies Page 14

3.2.2 Sequence diagram:

Acharya Institutes of Graduate Studies Page 15

3.2.3 E-R DIAGRAM:

Acharya Institutes of Graduate Studies Page 16

3.3 FEASIBALITY STUDY

To demonstrate the feasibility of real-time systems in Python, we implemented real-time

Acharya Institutes of Graduate Studies Page 17

3.3.1 ECONOMIC FEASIBILITY