Академический Документы
Профессиональный Документы
Культура Документы
NO
ABSTRACTS
LIST OF TABLES
LIST OF FIGURES
1 INTRODUCTION
2 SYSTEM STUDY
3 SYSTEM CONFIGURATION
7 CONCLUSION
8 APPENDICES
I. Source Code
II. Screenshots
ABSTRACTS
This project aims at providing an online platform where the records of a typical
vehicle insurance company are properly and efficiently managed so as to ensure
improvement in the productivity of operations of the company. The proposed vehicle
insurance policy system is a web-based application that aims to develop a complete and fully
functional independent system to manage records of vehicle insurance companies. It is
developed with the intent of providing such insurance companies an online platform for
accurate processing, organized data handling, and efficient retrieval and storage of records.
LIST OF TABLES
5
LIST OF FIGURES
5
1. INTRODUCTION
This section deals with the concept of system analysis, which is the primary phase of the
software development. The purpose is to identify the new system and establish what the new
system is to accomplish. Moreover, a brief review of requirement determination, report
feasibility analysis and finding are recorded here. System analysis is an important activity
that takes place, when a new system is being built. It is the central intact of the system
development and it includes gathering necessary data and developing a plan to the new
system. It is not an easy task because many people need to be satisfied and many conflicts are
to be resolved. System analysis should be creative and imaginative in producing new
solutions to meet the user requirements.
1.1 Problem Description
The starting point of any system is to understand what the issues are on hand and therefore
what need to be done. In fact the same problem across different organization could be
handled differently depending on various issues like organizational culture and resources
constraints etc. At this stage it was necessary to look at the following.
Problem introduction or problem stating is the starting point of the software development
activity. The objective of this statement is to answer: Exactly what must the system do? The
software project is initiated by the client’s need. This application achieves as the follows:
Insurance Details, Vehicle Details, Customer Details, Payment, and Time Period that are all
maintained by this application.
2. SYSTEM STUDY
Like many other existing system, the current vehicle insurance management procedure is
very traditional involving a lot of paper work and manpower. The current system cannot
ensure effective data processing, so it is very insecure.
Disadvantage
Data is maintained in papers
Customer visits an agent and asks him to insure his vehicle.
The system is very uneconomical, tedious, and time taking.
Retrieval of data is done manually
2.2 Proposed System
The proposed vehicle insurance policy system is a web-based application that aims to
develop a complete and fully functional independent system to manage records of vehicle
insurance companies. The overall project is developed taking into account the importance of
a software application for insurance-related data management, report generation, handling
customer information, etc.
Advantage
Proper management of vehicle insurance details like adds new vehicle details, modify
existing records, delete existing records, etc.
Non-motor insurance details option in insurance category for customers to provide
their details and personal information.
Report generation feature for every data and record entered into the system database.
Use of report generation module to add, modify, and delete records to/from the
database.
Easily access customer’s information from organized database.
2.3 Need for Computerization
The main objective of this project is to manage the details of customer, insurance,
vehicle, vehicle type. This project aims at providing an online platform where the records of
typical vehicle insurance are properly and efficiently managed so as to ensure improvement
in the productivity of operations .It is developed with the intent of providing such insurance
companies an online platform for accurate processing, organized data handling, and efficient
retrieval and storage of records.
The project Vehicle Insurance Management System is to maintain all records of vehicle
insurance such as 2 Wheeler vehicle, 3 wheeler vehicle, heavy vehicle etc, The main
objective of this project is to simple application for insurance companies for managing
customers who buy new vehicles and take insurance for that vehicles. This system is
managing the details of payment, time period, vehicle details, and customer personal details,
insurance specifications are updated to database. In this system admin can add, delete, and
modify, records and search for old records with in short time.
2.4 Data Flow Diagram
Manage vehicle
Logon to details
Admin
system
Manage
insurance details
Manage vehicle
type details
Forgot Check
password credential Manage customer
s details
Manage payment
details
Send Manage
email to modules
user Manage report
2.5 Class Diagram
3. SYSTEM CONFIGURATION
Front-End : ASP.NET
Back end : SQL server
Operating System : Windows 7
IDE : Visual Studio
4. OVERVIEW OF THE SOFTWARE
manage user
Manage registration
Admin
Manage insurance
update profile
user
manage insurance
period
manage payments
5.2 Data Base Design
5.3 E-R Diagram
6. IMPLEMENTATION AND TESTING
Modules
Login Module
Admin and customers can use their respective log in forms to log in to the system
providing user id or security details such as username and password.
Existing Records
All existing records in the system database can be viewed, modified, and deleted by
the admin. Further, records of similar type can be added in respective corners of the system.
This module contains vehicle insurance details that are provided by the user while
purchasing the vehicle. The records here contain information regarding Vehicle details, total
years of insurance, amount paid, etc.
Vehicle Search
Vehicle Report
In this module, a report containing insurance details can be generated in a file and
sent to the customer in printed form.
Setting Module
Basic system settings such as user id (username and password), layout, profiles, etc.
can be changed by the admin.
Software Testing
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub assemblies, assemblies and/or a finished product It is
the process of exercising software with the intent of ensuring that the Software system meets
its requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
Types of Tests:
Testing is the process of trying to discover every conceivable fault or weakness in a
work product. The different type of testing are given below:
Unit Testing:
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application .it is done after the completion of an individual unit before
integration.
This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration. Unit tests ensure that each unique path of a
business process performs accurately to the documented specifications and contains clearly
defined inputs and expected results.
Integration Testing:
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.
Functional Test:
Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centered on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/ Procedures : interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements, key functions, or
special test cases. In addition, systematic coverage pertaining to identify Business process
flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.
System Test:
System testing ensures that the entire integrated software system meets requirements. It tests
a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
White Box Testing:
White Box Testing is a testing in which in which the software tester has knowledge of the
inner workings, structure and language of the software, or at least its purpose. It is purpose. It
is used to test areas that cannot be reached from a black box level.
Black Box Testing:
Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of
tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.
7. CONCLUSION
Effectiveness, efficiency, and reliability are the key aspects that make this web-based vehicle
insurance management system very useful for vehicle showroom business. The proposed
project is very flexible to handle new modules and features as per user requirements in
future. It can also be integrated with other systems such as vehicle tracking system, vehicle
information management system, vehicle registration system, etc.
8. APPENDICES
Source Code
Screenshots