Revision Sheet
Business Process Definition and Requirements for FNoL On the Go
Page i
Revision Sheet
BUSINESS PROCESS DEFINITION
AND
REQUIREMENTS
First Notice of Loss on the Go
(NP20114)
Team # 4 Gannon university _ Requirement engineering
Abraham Rojo,
Harsh Upadhyay,
Hiba Al-Qaysi)
Business Process Definition and Requirements for FNoL On the Go
Page ii
Revision Sheet
Revision Sheet
Release No.
Rev. 1
Date
09/22/2011
Revision Description
Business Process Definition and Requirements Initial Draft
Business Process Definition and Requirements for FNoL On the Go
Page iii
RECOMMENDED POINT OF CONTACT FOR THIS DOCUMENT: Functional Lead within program
area
The Point of Contact for the Document coordinates and insures that the document is completed. This
individual as well as others in the program areas may also contribute in a collaborative fashion as is
often necessary in systems development projects.
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
______ The document is accepted.
______ The document is accepted pending the changes noted.
______ The document is not accepted.
We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based
on our authority and judgment, the continued operation of this system is authorized.
_______________________________
NAME
Project Manager
_____________________
DATE
_______________________________
NAME
Program Area/Sponsor Representative
_____________________
DATE
_______________________________
NAME
Program Area/Sponsor Director
_____________________
DATE
_______________________________
NAME
OCIO Point of Contact
_____________________
DATE
Business Process Definition and Requirements for FNOL On the Go
Page iv
BUSINESS PROCESS DEFINITION AND REQUIREMENTS
TABLE OF CONTENTS
Page #
1.0
BUSINESS OBJECTIVES FOR PROCESS ................................................................................. 1
2.0
Business Requirements ................................................................................................................... 1
2.1 Process Flows (To_Be)...........................................................................................................................1
2.2 New Process Requirements ...................................................................................................................4
Remote Transport Security: .......................................................................................................................................... 8
Certificate, Key, and Trust Services: ............................................................................................................................ 8
2.3 Business Impact .....................................................................................................................................8
2.3.1 Metrics to Measure Business Impact.................................................................................................................... 8
2.3.1.2 Responsibility of Metrics Collection & Analysis .............................................................................................. 9
2.3.1.3 Business / System Metrics Communication Plan .............................................................................................. 9
2.3.2 Business Dependencies ........................................................................................................................................ 9
2.3.3 Business Risks...................................................................................................................................................... 9
2.4 Technology Impact ................................................................................................................................9
2.4.1 Technology Dependencies ................................................................................................................................... 9
2.4.2 Technology Risks ................................................................................................................................................. 9
3.0
Assumptions .................................................................................................................................... 9
4.0
ISSUES ............................................................................................................................................ 9
5.0
Project Success Criteria .................................................................................................................. 9
Business Process Definition and Requirements for FNOL on the Go
1.0
BUSINESS OBJECTIVES FOR PROCESS
The objective of this project is to design, develop, test and market a highly available, flexible and userfriendly mobile application that can record "First Notice of a Loss event using iPhone, iPad, Android or
Blackberry. The NAIC accredited national and regional auto insurers should be able to subscribe to this
service by enabling the usage agreement for their policyholders. The product "FNoL on the Go" will
capture the basic information needed for any NAIC accredited insurers to record a "loss event"
appropriately and respond to the policyholder with the follow-up details in real-time..
This application is free for all to download, but only those users with a valid activation code can activate
the app to record a loss event . This activation code will be provided by their respective insurance carriers.
The company provides unique activation code to the carriers upon a paid subscription to the service.
2.0
BUSINESS REQUIREMENTS
2.1 Process Flows (To_Be)
This project has two processes in scope.
The first process is to install the FNoL on the Go application on the Mobile Phone or on the tablet. The
application is freely available to download and install however the application has to be activated with the
unique insurance career activation code provided by the Insurance Company to Enable the “FNoL on the
Go” to establish the real time interface with respective insurance carrier.
After activating the FNoL on the go , entering the current active policy details and insured information is
strongly recommended and will ease the effort of entering this information while entering an FNOL
Install FNoL on the Go application installation
Business Process Definition and Requirements for FNoL On the Go
Page 1
FNoL entering process is illustrated in the process flow given below. The device owners’ insurance
carrier information is prefilled for the activated primary carrier. Policy details and Insurance holder
details are also prefilled if they are already entered and saved.
Business Process Definition and Requirements for FNoL On the Go
Page 2
Record a First Notice of Loss
Loss event
Occurrence
Initiate an FNOL
Policy details
Insured information,
Location,
Timestamp are
repopulated
Yes
Other vehicle
involved
Collision
No
No
Yes
Enter
Accident details
Other vehicle details
Third party insurance details
Police report details
Enter
Property damage details,
Police report details
Enter
Vandalism details
Police report details
FNOL – First Notice Of Loss
Submit FNOL
entry
Claim number
displayed with
additional details
and saved for
future refernce
Business Process Definition and Requirements for FNoL On the Go
Page 3
2.2 New Process Requirements
Business Requirements
FNoL on the Go - Application specific requirement
 The “FNoL on the Go” application should be listed in iPhone, iPad and Android app store and
from internet
 A unique activation code will be provided to the subscribing insurance carriers
 FNoL should be activated by the mobile device owner by entering the activation code given to the
policy holders by the Insurance carrier
 The Insurance company name and NAIC code should be saved and be prefilled in new FNOL
based the activation code entered
 New FNoL can be entered with new additional insurance provider’s activation code if necessary
(Example rental car having a different insurance other than the drivers primary auto insurance)
 The FNoL app should identify the event entered location using GPS and pre-fill the same
 The FNoL app should record the timestamp of the FNoL entry and should note it as the event
occurred time by default
 The user should be able to overwrite the default event time prefilled if necessary
 User should be able to enter the policy details and policy holder details upon activation at their
discretion
FNoL Entry process specific requirement
 The primary insurance carrier information is repopulated as soon as the user click to initiate new
loss report
 User could select or opt out the pre-populated insurance carrier information
 If opt out the user will be asked to enter a new activation code and the carrier information will be
populated based on the activation code entered.
 The location of the incident is captured using the GPS and populated with a time stamp , which
can be over written by user if needed
 User will be asked to enter the identity information, policy details and the vehicle
information(refer data requirements for the details)
 Upon submission a cliam number will be provided by user’s insurance carrier for future
references with contact information
 The request and response will be saved in the application for future references and reports
System Requirements
Anderiod :
Windows XP (32-bit), Vista (32- or 64-bit), or Windows 7 (32- or 64-bit)
Mac OS X 10.5.8 or later (x86 only)
Linux (tested on Ubuntu Linux, Lucid Lynx)
GNU C Library (glibc) 2.7 or later is required.
On Ubuntu Linux, version 8.04 or later is required.
64-bit distributions must be capable of running 32-bit applications. For information about how to
add support for 32-bit applications,
Business Process Definition and Requirements for FNoL On the Go
Page 4
Eclipse IDE
Eclipse 3.5 (Galileo) or greater
Note: Eclipse 3.4 (Ganymede) is no longer supported with the latest version of ADT.
Eclipse JDT plugin (included in most Eclipse IDE packages)
If you need to install or update Eclipse, you can download it
from http://www.eclipse.org/downloads/.
Several types of Eclipse packages are available for each platform. For developing Android
applications, we recommend that you install one of these packages:
Eclipse IDE for Java Developers
Eclipse Classic (versions 3.5.1 and higher)
Eclipse IDE for Java EE Developers
JDK 5 or JDK 6 (JRE alone is not sufficient)
Android Development Tools plugin (recommended)
Not compatible with Gnu Compiler for Java (gcj)
Other development environments or IDEs
JDK 5 or JDK 6 (JRE alone is not sufficient)
Apache Ant 1.8 or later
Not compatible with Gnu Compiler for Java (gcj)
Iphone : Mac OS X Lion System Requirements
In order to install application Mac OS X 10.7 will be need:
Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor 2GB of RAM
Mac OS X 10.6.6 or later with the Mac App Store installed at least 4GB of additional disk space
to accommodate the download, but more is obviously recommended
To develop for the iPhone you will need an Intel-based Mac running Leopard (OS X 10.5.3 or
later).
If you have a solid grounding in Cocoa development (Apple’s Objective-C framework) with the
xCode development on the Mac platform, developing iPhone Apps should be a breeze
Everything you need to build an iPhone App is contained in the huge iPhone App SDK. Like
everything else on the Mac, installing it as my first Mac App was a bit of a challenge. I had never
heard of .dmg files, let alone used one, to download and install Mac apps. With the help of
this Images explanation, that challenge was soon overcome.
Tablets: Control4® MyHome – iPad
Control4 MyHome app for iPad—iOS 3.2 or
later and Control4 OS 1.7.4 or later (OS 1.7.4 or
1.8.2 require a software patch)
Business Process Definition and Requirements for FNoL On the Go
Page 5
Licenses
Single device license (C4-MyHome). For one
(1) supported device only. Supports Control4
OS 1.7.4 or later.
Site license (C4-MyHome-Site or
C4-MyHome-Site-Trial). For multiple (up to 50) supported devices in the system.
Reporting Requirements
The application should provide a dashboard report of all the claims entered via this app from a specific
phone for a specific insurance carrier
Data Requirements
Data
Classification
Attribute
Name
Data
type
Mandatory
Optional
Prefilled
Drop
down
Radio
Button
Remarks
Carrier
Information
Company
Activation
Code
Company
Name
NAIC
Code
String
Yes
String
Yes
Yes
String
Yes
Yes
String
Yes
String
Yes
Date
Yes
Numeri
c
Yes
No
One time entry
for the primary
insurance
Yes
Owned/ Rental
Policy Holder
Information
First
Name
Last
Name
Date Of
Birth
Last four
digit of
SSN
Policy
Number
String
Yes
Vehicle
Information
Vehicle
Type
Vin
Number
String
Yes
String
Yes
Business Process Definition and Requirements for FNoL On the Go
Page 6
Loss Event
Details
Event
Type
Event
Location
Event
Time
Stamp
Event
Descriptio
n
Event
Pictures
String
Yes
String
Yes
Timest
amp
String
Yes
Yes
Collision,
Vandalism
GPS
automatically
locate the
event location
ecord the time
of FNOL entry
Yes
Yes
Mime
Yes
Police Report
Information
Report
filed
Yes/No
Yes
to indicate if
police report
was filed
String
Yes
If driver is
same as the
policy holder
then prefill the
rest
String
Yes
Date
Yes
Numeri
c
Yes
String
Yes
String
Driver
Information
Driver
same as
policy
holder
Driver
Name
Driver
Date of
birth
Driver
Last four
digit of
SSN
Driver's
Insurance
Carrier
Yes
Yes
Security Requirements
Business Process Definition and Requirements for FNoL On the Go
Page 7
Remote Transport Security:
Many of the security APIs provided by Mac OS X and iOS are useful in this regard, including the secure
networking APIs (Secure Transport, CFNetwork, and URL Loading System), and Certificate, Key, and
Trust Services (Apple, 2001).
Android security features are followed for the android application
Certificate, Key, and Trust Services:
Additional functions are provided to:
1. • Use a private key to generate a digital signature for a block of data.
2. • Use a public key to verify a signature.
3. • Use a public key to encrypt a block of data.
4. • Use a private key to decrypt a block of data
Refer http://code.google.com/p/fnol-on-the-go/wiki/SecurityRequirements for more details
Personnel Requirements
TBD
Name
Organization
Role
Organization
Role
Support Requirements
TBD
Name
2.3 Business Impact
2.3.1 Metrics to Measure Business Impact
.2.3.1.1 Measurable Business Metrics to be Used
Business Process Definition and Requirements for FNoL On the Go
Page 8
2.3.1.2 Responsibility of Metrics Collection & Analysis
2.3.1.3 Business / System Metrics Communication Plan
2.3.2 Business Dependencies
2.3.3 Business Risks
2.4 Technology Impact
2.4.1 Technology Dependencies
2.4.2 Technology Risks
3.0
ASSUMPTIONS
4.0
ISSUES
5.0
PROJECT SUCCESS CRITERIA
Initial launch planned in March 2012 with National Insurance for their PA Auto Insurance policy holders.
Business Process Definition and Requirements for FNoL On the Go
Page 9