Essay: Unified Claim Handling Process (UCHP) proposal

Chapter 1
INTRODUCTION
1.1 Project Description
UCHP is an abbreviation of Unified Claim Handling Process. The aim with UCHP is to support the claim process with a centrally installed system. The reason for this is that the old system structure no longer accommodates the need for change and upgrades. Changes over the years have resulted in a diverse and unspecified claim process. UCHP is the response to a system with a huge need for change.
The new system will have a centralized coverage handling process with a direct communication between the dealer and the factory. This will replace the old structure where claims were controlled in batches. With UCHP a claim will be validated in real time speeding up the customer communication and decreasing lead times. The result is a better information flow with higher quality.
Another goal is to collect all relevant information in a single system using the same environment. One point of interaction also minimizes the need for double work and online data ensures up to date information. Every aspect of the claim, including among others; coverage, parts, economy and campaigns will gradually be included in the system.
UCHP is a system used for handling claims in a unified way in all markets. The purpose of UCHP is to secure that the customers are handled in the same way in all markets as well as increase the efficiency of the warranty process.
Objectives of the UCHP:
UCHP is a system used for handling claims in a unified way in all markets.The purpose of UCHP is to secure that the customers are handled in the same way in all markets as well as increase the efficiency of the warranty process.
Scope:
‘ Provides direct connection between dealer and factory.
‘ In the new system, all the data from claimer will be validated in real time so that result provides a better information flow with higher quality.
‘ Here we can maintain less servers with better quality compare to previous. Here in the new system all relevant data is collected in single windows.
1.2 Company Profile
Nanoclair is an IT Services company specializing in providing dedicated software solutions to corporations all over the globe. Our core competencies are in leveraging our deep technical, management and process skills to tailor and execute customized software development strategies for global corporations of any size.
We are leaders in the field of Software development, and are at the forefront of revolutions and innovations creating benefits at large. Our mission is to drive the world towards a simpler, better and more evolved tomorrow. We are specialist in leveraging the best quality software services and developed solutions with many leading software technologies.
Nanoclair has been built on the foundation of human principles and values. We measure the true worth and effectiveness of technology based on whether it produces the highest quality of results effectively, consistently and in the most efficient manner possible. We strive towards total involvement in our work at all times, since mistakes and errors are a result of distraction. We view problems as challenges that require innovation and a shift in perspective, and are not just situations in need of rectification or correction. We believe that life has a deeper purpose and it is our constant endeavor to make life better and more meaningful.
Quality – Incorporate an organizational culture that encourages continuous improvement of the Quality management system and individual commitment to quality standards.
Efficiency – Plan efficiently to identify and execute the best solutions for our Customers.
Training and Development
Transparency – Believe in being transparent in all our operations to ensure highest level of integrity in what we deliver.
In times of changing technology, the importance of training cannot be overemphasized. Both technical and soft skills training are part of the year long human resource development program at Nanoclair.
An integral approach to channelizing the potential of human resources include systematic planning for training and development.
Quick delivery: We understand your business pressures and complex business problems, and deliver innovative solutions saving time and money.
Improved web presence: Our team develops effective web solutions driven by client business strategy. This generates high web presence and sustained ROI.
Professional team: We have a highly professional and committed team, with ‘client first’ attitude, delivering high quality web solutions.
Cost Effective: Our solutions come at highly competitive rates and are proven to be very cost effective.
Chapter 2
LITERATURE SURVEY
2.1 Existing And Proposed System
Existing System:
‘ It was a major drawback in the older system. This new feature makes claims faster as compared to previous batch process.
‘ It requires more servers to maintain software.
‘ With much software handling the claims is not easy task.
‘ If any server fails means, the customer has to wait long time to claim.
Proposed System:
‘ UCHP provides a direct connection between dealer and factory which was a major drawback in the older system. This new feature makes claims faster as compared to previous batch process.
‘ In the new system, all the data from claimer will be validated in real time so that result provides a better information flow with higher quality.
‘ The purpose of UCHP is to secure that the customers are handled in the same way in all markets as well as increase the efficiency of the warranty process. Here in the new system all relevant data is collected in single windows.
‘ This project useful to you in such a way that you will be learning all cutting edge tools and technologies in a real time environment. And throughout your internship you will be learning all the things mentioned in the first point.
2.2 Feasibility Study
The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are
‘ Economical feasibility
‘ Technical feasibility
Economical feasibility
This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.
Technical feasibility
This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. This will lead to high demands being placed on the client.The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.
The technical issue usually raised during the feasibility stage of the investigation includes the following:
‘ Does the necessary technology exist to do what is suggested’? Do the proposed equipment’s have the technical capacity to hold the data required to use the new system.
‘ Will the proposed system provide adequate response to inquiries, regardless of the number or location of users’? Can the system be upgraded if developed’? Are there technical guarantees of accuracy, reliability, ease of access and data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.
2.3 Tools and Technologies Used
JSP
Java server page is a textual document that describes how to create a response object from a request object for a given protocol. The processing of the jsp may involve creating and using other object.
A JSP page defines a jsp page implementation class that implements the semantics of the jsp page. This class implements the javax.servlet.Servlet interface. At request time a request intended for the jsp page is delivered to the jsp page implementation object for processing. HTTP is the default protocol for requests and responses. Additional request/response protocols may be supported by jsp containers. The default request and response objects are of type HttpServletRequest and HttpServletResponse respectively.
Java Server Pages (JSP) is a Java technology that allows software developers to dynamically generate HTML, XML or other types of documents in response to a Web client request. The technology allows Java code and certain pre-defined actions to be embedded into static content. “Java Server Pages” is a technology released by Sun.
Why JSP?
Java Server Pages (JSP) is a technology that lets you mix regular, static HTML with dynamically-generated HTML. Many Web pages that are built by CGI programs are mostly static, with the dynamic part limited to a few small locations. But most CGI variations, including servlets, make you generate the entire page via your program, even though most of it is always the same. JSP lets us create the two parts separately. The JSP syntax adds additional XML-like tags, called JSP actions, to be used to invoke built-in functionality. Additionally, the technology allows for the creation of JSP tag libraries that act as extensions to the standard HTML or XML tags. Tag libraries provide a platform independent way of extending the capabilities of a Web server.
JSP Syntax
A Java Server Page may be broken down into the following pieces:
‘ static data such as HTML,
‘ JSP directives such as the include directive,
‘ JSP scripting elements and variables,
‘ JSP actions,
‘ custom tags
JSP Directives
‘ JSP directives control how the JSP compiler generates the servlet. The following directives are available:
‘ include ‘ The include directive informs the JSP compiler to include a complete file into the current file. It is as if the contents of the included file were pasted directly into the original file. This functionality is similar to the one provided by the C preprocessor. Included files generally have the extension “jspf” (for JSP Fragment):
Example : <%@ include file=".jspf” %>
‘ page ‘ The page directive tag holds the instructions used by the translation stage of the JSP lifecycle. The instructions affect the various properties associated with the whole JSP page. You can use page directive multiple times in a JSP page. The page directive used on any part of the JSP page is automatically applied to the entire translation unit.
‘ Syntax : <%@page attributes %>
‘ There are several options to the page directive.
‘ Example for import : <%@ page import="java.util.*" %>
‘ Example for contentType : <%@ page contentType="text/html" %>
‘ Example for isErrorPage : <%@ page isErrorPage=false %>
‘ Only the “import” page directive can be used multiple times in the same JSP.
Scripting Tags
JSP Scripting tags, also called as JSP Scripting elements, allow you to add a script code into the Java code of a JSP page generated by the JSP translator. There are 3 types of scripting tags:
‘ Scriptlet Tag
‘ Declarative Tag
‘ Expression Tag
Scriptlet Tag allows to write the script code or the java code for implementing the jspService method functionality.
Syntax : <% Script code (allows multiple statements) %>
Declarative Tag allows you to write the script code that you need to provide in the generated Servlet Class, outside the jspService() method.
Syntax : <%! Script code (allows multiple statements) %>
Expression Tag allows you to write a Java expression, which is then resolved and the resultant value is displayed.
Syntax : <%= Script code (allows multiple statements) %>
JSP Actions
JSP actions are XML tags that invoke built-in web server functionality. The following actions are provided:
‘ jsp:include
‘ jsp:forward
‘ jsp:param
‘ jsp:useBean
‘ jsp:setProperty
‘ jsp:getProperty
‘ jsp:plugin
action tag allows a static or dynamic resource such as HTML or JSP page , specified by a URL, to be included in the current JSP while processing a request.
tag forwards a JSP request to another resource, which can be either static or dynamic.
tag allows us to pass a name and value pair as parameter to a dynamic resource, while including it in a JSP page or forwarding a request from a JSP page to another JSP page.
action tag is used to instantiate a java bean, or to locate an existing bean instance and assign it to a variable name.
action tag sets the value of a property in a bean, using the bean’s setter methods.
action tag gets the value of a property in a bean, using the bean’s setter methods and writes the value to a current JspWriter.
action tag provides easy support for including a Java Applet or a bean in the client Web Browse, using built-in or downloaded Java plug-in.
JBOSS Web Server
WildFly, formerly known as JBoss AS, or simply JBoss, is an application server authored by JBoss, now developed by Red Hat. WildFly is written in Java, and implements the Java Platform, Enterprise Edition (Java EE) specification. It runs on multiple platforms.
WildFly is free and open-source software, subject to the requirements of the GNU Lesser General Public License (LGPL), version 2.1.
The renaming to WildFly was done to reduce confusion. The renaming only affects the JBoss Application Server project. The JBoss Community or the Red Hat JBoss product line (with JBoss Enterprise Application Platform) all retain their names.
Product features
‘ Clustering
‘ Deployment API
‘ Distributed caching (using Infinispan, a standalone project)
‘ Distributed deployment
‘ Enterprise JavaBeans versions 3 and 2.1
‘ Failover (including Web and EJB sessions)
‘ Hibernate integration (for persistence programming; Java Persistence API or JPA)
‘ Java Authentication and Authorization Service (JAAS)
‘ Java EE Connector Architecture (JCA) integration
‘ Java Management Extensions
‘ Java Message Service (JMS) integration
‘ Java Naming and Directory Interface (JNDI)
‘ Java Transaction API (JTA)
‘ Java Authorization Contract for Containers (JACC) integration
‘ JavaMail
‘ Java Server Faces 1.2 (Mojarra)
‘ Java Server Pages (JSP) / Java Servlet 2.1/2.5 (Tomcat).
Generating HTML
A traditional application domain of the JSP technology is HTML content. The JSP specification supports well this use through a syntax that is friendly to HTML and XML although it is not HTML specific for instance, HTML comments are treated no differently than other HTML content. The JSP Standard Tag Library has specific support for HTML though some specific custom actions.
HTML stands for Hyper Text Markup Language, which is an application of Standard Generalized Markup Language (SGML). It is simple language used to define and describe the layout of a Web page. HTML also supports Multimedia and document links. HTML consists of special codes which when embedded in text, adds formatting. The special characters, which separate HTML from ordinary text, are the left and right brackets(<>). These brackets contain instructions known as TAGS that are not case sensitive. The usage of HTML is in designing the Web pages.
MySQL
The MySQL database has become the world’s most popular open source database because of its consistent fast performance, high reliability and ease of use. It’s used in more than 10 million installations ranging from large corporations to specialized embedded applications on every continent in the world.
Features of MySQL
‘ MySQL is a database management system.
‘ MySQL is a relational database management system.
‘ MySQL software is Open Source.
‘ MySQL Database Server is very fast, reliable, and easy to use.
‘ MySQL Server works in client/server or embedded systems.
Mysql Connector File
MySQL provides connectivity for client applications developed in the Java programming language via a JDBC driver, which is called MySQL Connector/J.
MySQL Connector/J is a JDBC-3.0 Type 4 driver, which means that is pure Java, implements version 3.0 of the JDBC specification, and communicates directly with the MySQL server using the MySQL protocol.
com.mysql.jdbc.Driver is the class that implements java.sql.Driver. Within Windows 2000, Windows XP and Windows Server 2003, set the environment variable through the System control panel.
The various MysqlDataSource classes support the following parameters
‘ User
‘ Password
‘ Server Name
‘ Database Name
‘ Port
2.4 Hardware and Software Requirements
HARDWARE REQUIREMENTS:
‘ System : Pentium IV 2.4 GHz and Above
‘ Hard Disk : 40 GB
‘ Monitor : 15 VGA color
‘ RAM : 2 GB
‘ OS : Windows.
SOFTWARE REQUIREMENTS:
‘ Front End : JSP 2.0, HTML, CS, JQuery.
‘ Back End :Springs 3, Hibernate 3.2
‘ DB :My SQL 5.1
‘ Server :JBOSS 7
‘ Coding Environment : Eclipse Juno
Chapter 3
SOFTWARE REQUIREMENTS SPECIFICATION
3.1 Users
Role of SRS
Software requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended. Hence the need for the requirement phase arose. The software project is initiated by the client’s needs. The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document.
Software Requirement Specification is the medium through which the client and the user needs are accurately specified. It forms the basis of software development.
Aim
The reason for this is that the old system structure no longer accommodates the need for change and upgrades. Changes over the years have resulted in a diverse and unspecified claim process. UCHP is the response to a system with a huge need for change. The aim with UCHP is to support the claim process with a centrally installed system.
Purpose
The software requirement specification document is specifically designed for the UCHP (Unified Claim Handling Process).
Scope
UCHP is to collect all relevant information in a single system using the same environment. One point of interaction also minimizes the need for double work and online data ensures up to date information. Every aspect of the claim, including among others; coverage, parts, economy and campaigns will gradually be included in the system.
UCHP is a system used for handling claims in a unified way in all markets. The purpose of UCHP is to secure that the customers are handled in the same way in all markets as well as increase the efficiency of the warranty process.
Advantages of UCHP:
‘ Provides direct connection between dealer and factory:
It can be done how means if a person wants to apply claim for his vehicle, he doesn’t need to go for showroom where he purchased. He can move directly to the manufacture company. In this situation he saves lot of time and immediately solution he can get through his claim.
‘ Better Quality assurance:
In the new system, all the data from claimer will be validated in real time so that result provides a better information flow with higher quality.
‘ Easily maintain the system hardware and software infrastructures:
Here we can maintain less servers with better quality compare to previous. Here in the new system all relevant data is collected in single windows.
3.2 Functional Requirements
Functional requirements are the statements of services that the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.
Functional requirements describe the functionality or system services. Functional requirements depend on the type of software, expected users and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do but functional system requirements should describe the system services in detail.
Some of the functionalities of UCHP are given below:
‘ The Claimer can easily view the repair history.
‘ The Claimer can easily view the technical data.
‘ The Claimer can view the coverage and campaign.
‘ The Claimer can get the details of printable versions.
CLAIM
Using the New Claim Job ‘ Header Tab Window:
Registration:
UCHP provides a registration form for entering new claim jobs. Since UCHP is an online system, a validation of the claim job will be performed when saving the claim job. The claim job creator will have immediate response whether the claim job is entered in a correct format or not. A successful registration of a claim job will end up with a saved claim job in status Validated. In order to get evaluated, the claim job needs to be released.
Create New Claim Job
Entering a new claim job consists of creating a repair header and a claim job. When the claim job is created, more claim jobs can be created for the same repair header.
Add Members:
In this module manufacturer, vehicle show room vendor and claimer are members to the system by eligible criteria.
Approve Benefits:
In this system we can save lot of time by applying the claim and get soon the claim recover.
3.2 Functional Requirements
Non-Functional requirements as the name suggests, are those requirements that are not directly concerned with the specific functions delivered by the system. They may relate to the emergent system properties such as reliability, response time and the store occupancy. Many non-functional requirements relate to the system as a whole rather than to individual functional requirement may degrade the system. Failure meet a non-functional system requirement may take whole.
Performance Requirements:
‘ It must be able to perform in adverse conditions like high/low temperature etc.
‘ Uninterrupted interrupted connections
‘ High data transfer rate
Safety Requirements:
‘ Scheduled backup after updating the application
‘ Validation of inputs
‘ Modem and Server must be safe kept in physical aspects, say in a cabin
Security Requirements:
‘ Login authentication
‘ Scheduled backup
‘ Login authentication for database operators
Software Quality Attributes:
‘ Correctness
‘ Flexibility
‘ Maintainability
‘ Usability
‘ Testability
Chapter 4
SYSTEM DESIGN
4.1 System Perspective
System model is usually a guideline system for solving a problem, with specific components such as phases, tasks, methods, techniques and tools.
The V model is a modified version of the Waterfall method. As opposed to the waterfall model, this one was not designed in a linear axis; instead the stages turn back upwards after the coding phase is done so that it makes a V shape and hence the name V Model. Testing of the product is planned in parallel with a corresponding phase of development.
Advantages of V Model:
‘ Simple and easy to use.
‘ Testing activities like planning, test designing happens well before coding.
‘ This saves a lot of time. Hence higher chance of success over the waterfall model.
‘ Proactive defect tracking that is defects are found at early stage.
‘ Avoids the downward flow of the defects.
‘ Works well for small projects where requirements are easily understood.
Disadvantages of V Model:
‘ Very rigid and least flexible.
‘ Software is developed during the implementation phase, so no early prototypes (Dummy) of the software’s are produced.
‘ If any changes happen in midway, then the test documents along with requirement documents has to be updated.
UCHP is a WebSphere based Java application. It is run on UNIX with a DB2/Mainframe database. Communication with a number of other systems is done via client and user administration is handled. UCHP is accessed via the Dealer Workshop Portal or via an http address.
‘
‘
‘
‘
‘
‘
‘
‘
‘
‘
‘
UCHP system structure
Chapter 5
DETAILED SEDIGN
5.1 Database Designs
Database designing is all about designing the tables with required fields, data type and proper relationship between them. Database schema describes the physical structure of the database. That is, it gives details of all the tables that form the database of the application.
Database Design:
Database designing is all about designing the tables with required fields, data type and proper relationship between them.
Database Schema
Database schema describes the physical structure of the database. That is, it gives details of all the tables that form the database of the application.
1. VCLAIM TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
VCLAIM_ID NUMBER(15) PRIMARY KEY
REPAIR_ORDER_DATE DATE
REPAIR_DATE DATE
2. VDEALER TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
VDEALER _ID NUMBER(15) PRIMARY KEY
BS_POSITION VARCHAR2(30) UNIQUE
FIRST_NAME VARCHAR2(30)
LAST_NAME VARCHAR2(30)
DOB VARCHAR2(30)
ADDRESS_ID NUMBER(15) FOREIGN KEY TO VADDRESS TABLE(ADDRESS_ID)
VCLAIM_ID NUMBER(30) FOREIGN KEY TO VCLAIM TABLE
(VCLAIM_ID)
3. VCLINT TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
VCLIENT_ID NUMBER(15) PRIMARY KEY
FIRST_NAME VARCHAR2(30)
LAST_NAME VARCHAR2(30)
DOB DATE
ZIP_CODE NUMBER(12)
VEHICLE_PURCHASE_DATE DATE
CLAIM_DATE DATE
VDEALER _ID NUMBER(12) FOREIGN KEY TO VDEALER TABLE
(VDEALER _ID)
ADDRESS_ID NUMBER(15) FOREIGN KEY TO ADDRESS TABLE
(VDEALER _ID)
4. VCOUNTRY TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
COUNTRY_ID NUMBER(30) PRIMARY KEY
COUNTRY VARCHAR2(30)
CONTINENT_ID VARCHAR2(30) FOREIGN KEY TO VCONTINENT TABLE
(CONTINENT _ID)
5. VADDRESS TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
ADDRESS_ID NUMBER(15) PRIMARY KEY
ADDRESS LINE 1 VARCHAR2(30)
ADDRESS LINE 2 VARCHAR2(30)
CITY NUMBER(15) FOREIGN KEY TO CITY TABLE
(CITY _ID)
STATE VARCHAR2(30) FOREIGN KEY TO STATE TABLE
(STATE _ID)
COUNTRY VARCHAR2(30) FOREIGN KEY TO COUNTRY TABLE
(COUNTRY _ID)
CONTINENT VARCHAR2(30) FOREIGN KEY TO CONTINENT TABLE
(CONTINENT _ID)
ZIP_CODE NUMBER(12)
6. VVECHICLE_INFO
COLUMN NAME DATATYPE CONSTRAINT RELATION
VVECHICLE_INFO_ID NUMBER(15) PRIMARY KEY
MODEL VARCHAR2(30) UNIQUE
VDOM DATE NOTNULL
VTYPE VARCHAR2(30) UNIQUE
VSERIES VARCHAR2(30)
VEOCN_MAX VARCHAR2(30)
VREGNUM NUMBER(18) UNIQUE
VMAX_MILAGE VARCHAR2(30)
7. VSERVICE_INFO
COLUMN NAME DATATYPE CONSTRAINT RELATION
VSERVICE_INFO_INFO_ID NUMBER(15) PRIMARY KEY
MODEL VARCHAR2(30) UNIQUE
VDOM DATE NOTNULL
VTYPE VARCHAR2(30) UNIQUE
VSERIES VARCHAR2(30)
VEOCN_MAX VARCHAR2(30)
VREGNUM NUMBER(18) UNIQUE
VMAX_MILAGE VARCHAR2(30)
VCLAIM_ID NUMBER(10) FOREIGN KEY TO VCLAIM TABLE (VCLAIM_ID)
8. VLABOUR
COLUMN NAME DATATYPE CONSTRAINT RELATION
VLABOUR_ID NUMBER(15) PRIMARY KEY
LABOUR_FIRST_NAME VARCHAR2(30)
LABOUR_LAST_NAME VARCHAR2(30)
LABOUR_DOB DATE
LABOUR_ROLE VARCHAR2(30)
ADDRESS VARCHAR2(30)
CITY VARCHAR2(30)
STATE VARCHAR2(30)
COUNTRY VARCHAR2(30)
CONTINENT VARCHAR2(30)
ZIP_CODE NUMBER(12)
9. VCONTINENT TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
CONTINENT_ID NUMBER(30) PRIMARY KEY
CONTINENT VARCHAR2(30)
10. BVSTATE TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
STATE_ID NUMBER(30) PRIMARY KEY
STATE VARCHAR2(30)
COUNTRY_ID NUMBER(30) FOREIGN KEY TO VCOUNTRY TABLE
(COUNTRY_ID)
11. VCITY TABLE
COLUMN NAME DATATYPE CONSTRAINT RELATION
CITY_ID NUMBER(30) PRIMARY KEY
CITY VARCHAR2(30)
STATE_ID NUMBER(30) FOREIGN KEY TO VSTATE TABLE
(STATE_ID)
Chapter 6
IMPLEMENTATION
6.1 System Implementation
Implementation is the stage of the project where the theoretical design is turned into a working system. At this stage 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 planned and controlled, it can cause uncertainty. Implementation includes all the 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 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 process of putting the developed system in actual use is called system implementation. 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. The most crucial stage is achieving a new successful system and giving confidence on the new system for the user that it will work efficiently and effectively. It involves careful planning, investigation of the current system and its constraints on implementation, design of methods to achieve the changeover. The more complex the system being implemented, the more involved will be the system analysis and the design effort required just for implementation. The system implementation has three main aspects. They are education and training, system testing and changeover.
The implementation stage involves following tasks.
‘ Careful planning.
‘ 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.
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 someone who will not be operating it, will commission the software development project. The people unaware that software is meant to make their job easier. In the initial stage, they doubt about the software but we have to ensure that the resistance does not build up as one has to make sure that
‘ The active user must be aware of the benefits of using the system
‘ 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 in the server. If the server object is not up running on the server, the actual processes won’t take place.
System Installation
In order to install Stash Oversight Structure all the pre-requisite software’s should be installed onto the system.
The system should have the following Licensed Software’s:
‘ Eclipse Juno
‘ DB2
‘ Installing JBOSS Server.
System 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 adaptable to the changes in the system environment. There may be social, technical and other environmental changes, which affects a system, which is being implemented. Software product enhancements 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.
6.2 Screen Shots
Using the New Claim Job ‘ Header Tab Window:
Explanation:
Function bar
‘ Use the Select claim job type drop down list to choose the type of claim job you are about to create. The different claim job types are: Vehicle warranty claim job, Parts claim job, Campaign claim job, Service claim job, Technical goodwill claim job, Specification deviation claim job and Commercial goodwill claim job.
‘ When you are ready specifying claim job header information, click the New claim job button in order to open the claim job tab.
‘ You need to select claim job type in the drop down list before clicking the New claim job button.
Repair header information area
‘ The repair header information area is used to enter information about the repair. The section consists of five fields: Importer, Dealer, Repair order no., Repair date and Force header information. Each field is described below.
‘ Importer ‘ The number of the repairing importer, e.g. ‘1320’ for Volvo Trucks & Bus Ltd. Mandatory.
‘ Dealer ‘ The number of the repairing dealer. Mandatory.
‘ Repair order no. ‘ The repair order number is used for identifying the repair order document (in case of any fault or missing information).
‘ Repair date ‘ The date for the repair causing the claim. The format is local and given clicking the information icon . Mandatory.
‘ Force header information ‘ Indicates that less (a limited number of) checks will be performed during validation. Using the Force header information flag will lead to a manually evaluated claim job.
Vehicle information area:
‘ The vehicle identification section of the page is used to identify the vehicle that the claim job concerns. The section consists of six fields: No vehicle, Reg.no., Series ‘ Chassis, VIN, Mileage (km) and Operating hours. Each field is described below.
‘ No vehicle ‘ Indicates that the repair header is not linked to a vehicle.
‘ Reg. no. ‘ The registration number of the vehicle. Mandatory*.
‘ Series ‘ Chassis ‘ The chassis ID of the vehicle. It is unique and consists of chassis number
‘ Series + chassis number. Mandatory*.
‘ VIN ‘ Vehicle Identification Number. Mandatory*.
‘ * Either Reg. no., Series ‘ Chassis or VIN is mandatory. One of these fields is used to identify the vehicle.
‘ Mileage (km) ‘ Distance driven in kilometres at the time for the repair. Mandatory**.
‘ Operating hours ‘ Number of hours a vehicle has been in operation at the time for the repair. Mandatory**.
‘ ** Either mileage or operating hours should be given.
Using the New Claim Job ‘ Claim Job Tab Window:
The New claim job ‘ Claim job tab window consists of a function bar, vertical tabs representing the Header and the associating claim jobs, a Repair header information summary and five horizontal tabs: Claim job information, Labour, Material, Other cost and Remarks.
Function bar
When you have registered or edited the wanted information use the Save claim job button to save the claim job. All information under the different tabs will be saved. When saving a validation will be performed..
Use the Release claim job button to release a claim job. The claim job can only be released in status Validated. Use the release function in order to get the claim job evaluated..
In order to delete a claim job use the Delete claim job button.
You can select a claim job type in the Select claim job type drop down list and click the New claim job button in order to create another claim job. An additional vertical tab will appear in the left part of the page.
Header tab and associating claim jobs:
The vertical tabs are used to reach the header information and associating claim jobs for the same repair header. Using the vertical tabs will reload the page and it is therefore important to save changed information before.
Repair header information
The repair header information contains a summary of the repair and vehicle information. The fields are: Importer, Dealer, Reference no., Repair order no., Repair date, Registration date, Series-Chassis, Mileage and Age. Each field is described below.
Importer ‘ The number of the repairing importer, e.g. ‘1320’ for Trucks & Bus Ltd.
Dealer ‘ The number of the repairing dealer.
Reference no. ‘ The reference number identifies the claim job repair header. It is unique together with importer and dealer.
Repair order no. ‘ The repair order number is used for identifying the repair order document (in case of any fault or missing information).
Repair date ‘ The date for the repair causing the claim job.
Registration date ‘ The date for the claim job registration.
Series ‘ Chassis ‘ The chassis ID of the vehicle. It is unique and consists of chassis number series and chassis number.
Mileage (km) ‘ Distance driven in kilometres at the time for the repair.
Age ‘ Specifies the age of the vehicle in month.
From this area it is also possible to use four links: View repair history, View technical data View coverage, View campaign.
View repair history Lists previous claim jobs for the specified vehicle.
View technical data Links you to the VVS system in VTBOS to view technical data for the specified vehicle.
View coverage Lists the coverage for the specified vehicle.
View campaign Lists outstanding campaigns for the specified vehicle.
Note! The list does not include programs or policies operated on a customer complaint basis.
View printable version Opens a printable version of the claim job.
.1.2. Claim job information tab:
Information area
The information area varies depending on claim job type. It looks like in Figure 5 for all claim job types except campaign claim jobs and parts claim jobs, where some additional fields exist. All variants are described below.
Vehicle warranty claim job, Service claim job, Technical goodwill claim job and Specification deviation claim job ‘ The information area consists of: Status, Type, Scenario code, Force claim job, MI name and Follow up code. Each field is described below.
Status ‘ A claim job can have different statuses during its life period in UCHP. For existing statuses. This field is not filled until claim job is saved for the first time.
Type ‘ The claim jobs are categorised in different claim job types. For existing types. It is possible to change claim job type.
Scenario code ‘ Information about check scenario used during the validation. This field is not filled until saved for the first time.
Force claim job ‘ Indicates that less (a limited number of) checks will be performed during validation.
Follow up code ‘ A claim job can be marked with a follow up code. The follow up code groups claim jobs with a common type of problem. It indicates that there is something concerning this claim job to follow up. Set during manual evaluation, if applicable.
MI name ‘ The name of the material instruction attached to the claim job. A material instruction describes what to do with the claim job material. Set after evaluation.
6.1.3 Parts claim jobs
Beside the common fields, parts claim jobs have three additional fields: Part fitted date, Part mileage and Part age. These fields are described below.
Part fitted date ‘ The date the part was taken in use, fitted in the vehicle. Mandatory.
Part mileage ‘ Distance driven with the part in use, i.e. from fitted date to time of repair.
Mandatory.
Part age ‘ Part age in month, from part fitted date to repairing date.
6.1.4 Campaign claim jobs ‘
Beside the common fields, campaign claim jobs have two additional fields: SCC code and SCC description. The fields are described below.
SCC code ‘ Special Commitment Code. Campaign identification code. It is possible to browse for a SCC code, using the browse button . Mandatory.
The browse SCC code window consists of a list with all outstanding campaigns for a selected vehicle.
The SCC codes are listed by Code and Description. They are sorted by Code in ascending order. By clicking a row in the list you will choose the SCC code you want to use. This will close the window and the chosen SCC code and its description will be inserted in the referring page.
SCC description ‘ Description of the SCC code. Fetched by the system during save or from the browse window.
6.1.5 Summary area:
The summary area gives an economical summary of the claim job. It consists of: Labour Net summary, Labour Hours summary, Material Net summary, Other cost Net summary and Grand total.
‘ Labour Net summary ‘ sum of labour net costs.
‘ Labour Hours summary ‘ sum of all labour hours.
‘ Material Net summary ‘ sum of all material net costs.
‘ Other cost Net summary ‘ sum of all other costs.
‘ Grand total ‘ total sum of all net costs.
Labour tab
The labour tab lets you create rows for included labour. Each row consists of nine fields: Main, VST, Operation, Description, Quantity, Hours, Cost/hour, Net and Delete. Each field is described below.
Main ‘ Describes the main work carried out during the repair.
VST ‘ Indication that the operation is a Volvo Standard Time operation.
Operation ‘ The number of the included operation.
Description ‘ Description of the operation number.
Quantity ‘ Number of operations.
Hours ‘ If VST is checked this field will be filled during save. If VST is unchecked the hour field needs to be filled with the time for the operation.
Cost/hour ‘ Cost per hour to perform the operation.
Net ‘ Net cost of the operation
Delete ‘ Used to delete the row. When deleting, the row will be marked as disabled and deleted next time saving.
Material tab
The material tab consists of the causal part area and the included material area.
Other cost tab
The other cost tab lets you create rows for other costs. Each row consists of three fields: Cost, Description and Delete. Each field is described below.
Cost ‘ Other cost.
Description ‘ Description for other cost.
Delete ‘ Used to delete the row. When deleting, the row will be marked as disabled and deleted next time saving.
Rows can be dynamically added to the other cost list. Use the Add row button in order to create a new, empty row to use.
Remarks tab
The remarks tab includes Remarks four fields: Complaint, Cause, Correction and Comment. Each field is described below.
Complaint ‘ Describe the problem as the customer or driver has described it.
Cause ‘ Describe what has caused the problem on the basis of the mechanic’s analysis.
Correction ‘ Describe what has been done to solve the problem.
Comment ‘ Any other comments about the claim job.
Chapter 7
SOFTWARE TESTING
7.1 Test plan
This document is a Test Plan for the Members Welfare Association System produced by Quality Assurance. It describes the testing strategy and approach to testing QA will use to validate the quality of this product prior to release. It also contains various resources required for the project. The focus of the Members Welfare Association System is to support those new features that will allow easier development, deployment and maintenance of solutions built upon the Members Welfare Association System.
Those features include:
‘ UCHP aims to give faster reply to customers and showroom vendors. To provide web based proposed solution.
‘ Using this system members can apply to claim easily.
This release of the Members Welfare Association System will also include legacy bug fixing, and redesigning or including missing functionality from previous release
The following implementations were made:
Hardware implementation
In order to develop UCHP application UCHP logon needs to be installed on the web server.
Software implementation
UCHP logon needs to be installed with necessary standard business objects available on web.
User interface implementation
In order to run the application user system must contain browser with additional plug-in and UCHP GUI interface.
Software capabilities:
‘ Windows XP Operating System/Windows 7 Operating System.
‘ Microsoft Visual Studio 2008, Oracle 10g
Test Tools
Manual Testing performed for member welfare association system these following features are tested
Features to Be Tested:
‘ Validating the data.
Features Not To Be Tested
‘ Alphabetic input
‘ Date should be entered proper in format
Approach:
The module has been tested manually, the module has undergone following testing
‘ Unit testing
‘ Functionality testing
Test Deliverables
‘ Test case document.
‘ Test Plan document.
Personnel Dependencies
The test team requires experience testers to develop, perform and validate tests. The test team will also need the following resources available: Application developers and Payroll Clerks.
Software Dependencies
The source code must be unit tested and provided within the scheduled time outlined in the Project Schedule.
Hardware Dependencies
The Mainframe, 10 PCs (with specified hardware/software) as well as the LAN environment need to be available during normal working hours. Any downtime will affect the test schedule.
Test Data & Database
Test data (member information) & database should also be made available to the testers for use during testing.
Risks & Schedule
The schedule for each phase is very aggressive and could affect testing. A slip in the schedule in one of the other phases could result in a subsequent slip in the test phase. Close project management is crucial to meeting the forecasted completion date.
Management
Management support is required so when the project falls behind, the test schedule does not get squeezed to make up for the delay. Management can reduce the risk of delays by supporting the test team throughout the testing phase and assigning people to this project with the required skills set.
Personnel
Due to the aggressive schedule, it is very important to have experienced testers on this project. Unexpected turnovers can impact the schedule. If attrition does happen, all efforts must be made to replace the experienced individual.
Requirements
The test plan and test schedule are based on the current Requirements Document. Any changes to the requirements could affect the test schedule and will need to be approved by the CCB.
5.2 Test cases
Test Cases and Results
CLAIM MODULE
SL no. Test condition Expected result Actual result Result
1 The New Claim Job ‘ New Job Window. Accepting the claim details of a person Information Accepted Pass
2 Claim Job Information tab Accepting the new claim job, if it is one or more claims New Claim job accepted Pass
3 Parts claim job Here we can apply claim for vehicle parts also. Different parts of the vehicle information accepted Pass
4 Campaign Claim Job Insurance information claims Accepted Properly
Pass
5 Summary Area Here labors information, material information, cost every thing working properly. Verified Pass
Chapter 8
CONCLUSION
This project report brought out the development of a Unified Claim Handling Process (UCHP). This system helps to claimer and shopkeeper in obtaining the information related to their respective benefits. After implementing this UCHP, it has been revitalized to next level.
The project titled as ‘UCHP’ is a web based application. This software provides function of making on window accessibility. This software is developed with scalability in mind.
Additional modules can be easily added when necessary. The software is developed with modular approach. All modules in the system have been tested with valid data and invalid data and everything work successfully. Thus the system has fulfilled all the objectives identified and is able to replace the existing system.
‘ Shop Keepers is approved benefits of the member claimed.
‘ Member Can view all his account details.
‘ It is help full for Inspector for investigating the vehicle information.
Finally, the report work is open to suggestion and modification by the experts.
Chapter 9
FUTURE ENHANCEMENTS
‘ This project can be developed for all the type of vehicles.
‘ We can make claim agencies in all urban areas. It will helpful for recovering the claims easily.
‘ Now it is in JAVA / J2EE Platform. In future we have to develop in different languages using android application.
Appendix A BIBLIOGRAPHY
References
‘ Rick Greenwald, Robert Stackowiak& Jonathan Stern: Oracle Essentials-Oracle Database2, Oreilly.
‘ RamezElmasri and Shamkant B. Navathe: Fundamentals of Database Systems
‘ Complete Reference J2EE and JAVA. By TATA McGraw-Hill.
‘ Investigated MVC docs(Motor Vehicle Cases) examples.
Websites
‘
‘ http://www.volvo.com
‘ http://en.wikipedia.org/wiki/j2ee.
‘ http://www.codeproject.com
‘ http://www.w3school.com
Appendix B:
User Manual