Docstoc

FNOL_SRS_V1

Document Sample
FNOL_SRS_V1 Powered By Docstoc
					       Software Requirements
                 Specification
                                                    For

FNOL IPhone Application 1.0
                                     Version 1.0 approved


  Prepared by: Abraham Rojo, Hiba Alqaysi, Harsh Upadhyay




                                       November 20, 2011
Software Requirements Specification for FNOL iPhone application                                                                                       Page ii




Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
    1.1      Purpose.......................................................................................................................................... 1
    1.2      Project Scope and Product Features .............................................................................................. 1
    1.3      References ..................................................................................................................................... 1
2. Overall Description ..................................................................................................................1
    2.1      Product Perspective ....................................................................................................................... 1
    2.2      Use Case........................................................................................................................................ 1
    2.3      Operating Environment ................................................................................................................. 3
    2.4      Design and Implementation Constraints ....................................................................................... 3
    2.5      User Documentation ..................................................................................................................... 3
    2.6      Assumptions and Dependencies.................................................................................................... 3
3. System Features .......................................................................................................................4
4. External Interface Requirements ...........................................................................................5
    4.1      User Interfaces .............................................................................................................................. 5
    4.2      Hardware Interfaces ...................................................................................................................... 5
    4.3      Software Interfaces ....................................................................................................................... 5
    4.4      Communications Interfaces........................................................................................................... 5
5. Other Nonfunctional Requirements. ......................................................................................6
    5.1      Performance Requirements ........................................................................................................... 6
Appendix A: Data Dictionary and Data Model.(harsh) .............................................................1
Appendix B: Analysis Models(harsh)...........................................................................................1



Revision History
Name                                 Date                Reason For Changes                                                                  Version
Abraham ,Hiba,                       11/17/11            initial draft                                                                       1.0
Harsh
Hiba                                 11/18/11            Updated external interface requirement                                              2.0
Harsh                                11/19/11            Other functional and data requirement updated                                       3.0
Abraham                              11/20/11            Updated use case                                                                    4.0(final )
1. Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for release 1.0 of the
FNOL. This document is intended to be used by the members of the project team that will
implement and verify the correct functioning of the system. Unless otherwise noted, all
requirements specified here is high priority and committed for release 1.0.

1.2 Project Scope and Product Features
The purpose of this vision document is to collect, analyze and define high-level use needs and features of
the FNOL on the Go IPhone application.




1.3 References

2. Overall Description
2.1 Product Perspective
       With the free FNOL on the Go App for IPhone, iPad® and iPod touch®, a variety of information and
        services—including claims reporting—are just a touch away. So wherever you are, you can connect
        with your auto insurer quickly.

Here are just a few of the things you can do with the FNOL on the Go App for IPhone:

       Find a local agent.
       Report a claim and submit photos of the damage to your vehicle.
       Locate a Service Center.
       Get emergency service, if you have our Roadside Assistance coverage.
       Get safety tips and roadside how-to's.



2.2 Use Case
                                                                                                     Email

                                                     FNOL on the Go iPhone
                                                          Application
                                           iPhone
  Customer
                                                                                                 Mobile carrier
                                                            iPhone camera
                                                                                    Extends


                                                        includes
                                                                                    Extends
                                                                                                   Insurance
Fnol developer   Enterprise App
                                                                                                carrier’s claims
                  FNOL server
                                           Extends                                  Extends       application

                                                                   FNOL on the Go




                                                                                                Emergency call-
                                                                                                 911 receiver




Customer

The customer is an iPhone user, who has an active iPhone that is subscribed to an iTune store and an active
mobile carrier subscription

Customer would freely download the FNOL application from the iTunes store.

Customer will activate the application with the activation code provided by the insurance company

Customer will register the FNOL application with an active email address for the automated
communication from the FNOL app to the customer regarding status of the requests and activation.

FNOL developer

FNOL developer is the member of the application development team who takes care of the application
maintenance and active synch-up of the activation code database with the application that is activated the
insurance company code activations

iPhone

iphone is a use case that includes the FNOL application, also it will provide the operating environment for the
application

FNOL enterprise application sever

FNOL enterprise application server is the use case that supports the application maintenance, , upgrades,
and activation status of the application

iPhone camera
This is the use case that directly integrate with the FNOL application to enable the application to attach the
pictures to the FNOL request

Emergency call

The iPhone calling feature integrates with the FNL application for a single touch emergency call
To 911

Insurance carrier Claims Application

This use case integrates with the FNOL application to FNOL request and sends status from/to the application

email

the email will be send from the FNOL application for the activation status and FNOL application request
status , also any latest feature upgrade information will be sent to the emails registered with the app




2.3 Operating Environment
        OE-1:      Basically the working environment for this app is when accident has occurred and person
                   has to provide the information for example how incident has occur and provide the details
                   and photos of the incident by using their Smartphone (iPhone). The application is also useful
                   while driving by providing free services unrelated to loss event
        .

2.4 Design and Implementation Constraints
        CO-1:      The system’s design, code, and maintenance documentation shall conform to the
                   standard IOS pack.

2.5 User Documentation
        UD-1:      The app will be self-explained and highly user friendly provides an online
                   hierarchical and cross-linked help system in HTML

2.6 Assumptions and Dependencies
           FNOL app will be freely available to all iPhone users via iTunes.
           Activation code will be provided to the customer by their insurance carrier.
           Customers’ needs to provide their basic information when operating app.
           The app will be upgraded by the customers to enable the latest feature and capabilities.
3. System Features
Functional requirements:

   The “FNoL on the Go” application should be listed in iPhone, iPad 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

   The primary insurance carrier information should be repopulated as soon as the user click to initiate
   new loss report

   User should be able to 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 should be 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 claim 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
4. External Interface Requirements
4.1 User Interfaces
    UI-1:     The FNOL application displays shall conform to the iPhone application development UI
              standard
    UI-2:     The system shall provide a help link to the company website where the a highly user-friendly
              demo will ve hoisted along with help documentation
    UI-3:     The application pages shall permit complete navigation and process selection using the
              touch screen.

4.2 Hardware Interfaces
    HI-1:     IPhone.
    HI-1.1:   IPhone will support the application operational environment for the FNOL application to run
              on iOS




4.3 Software Interfaces
    SI-1:        FNOL application
    SI-1.1:      The FNOL shall takes the activation code and the email id entered by the customer and
                 transmits the information to the FNOL application server
    SI-1.2:      The FNOL will application will receive the insurance carrier information from the FNOL
                 application server and pre-populates the information specific to the insurance company.
    SI-1.3:      FNOL application will integrates with IPhone camera application to enable the photo
                 attachment capability to the FNOL request
    SI-1.4:      FNOL application will transmit the FNOL request along with attached photo to the
                 insurance company’s claims application server
    SI-1.5:      FNOL application will receive the acknowledgement from the claims application and
                 display the status upon successful return message from the claims application
    SI-1.6:      FNOL application will save the entered FNOL if a successful real-time connection cannot
                 be made in the event of an accident due to poor signal strength and sends the
                 information to the claims application upon successful connection is made
    SI-1.7:      FNOL application will integrate with iphone calling feature to automatically calls 911
                 when the user opts to call emergency from the FNOL application
    SI-1.8:      FNOL application will receive the signals from the GPS to identify the exact location of
                 the accident while the FNOL is entered

4.4 Communications Interfaces
    CI-1:     The FNOL application will receive the status of the activation and sends an email to the user
              the status of successful activation
    CI-2:     The FNOL application will send the copy of the FNOL request send to the insurance
              company via an email to the customer
    CI-2:     The FNOL application will send the status of the submitted Claims to the email addresses
              provided by the customer
5. Other Non-functional Requirements.
5.1 Performance Requirements
         PE-1:    The app shall support any kind of the IOS package.
         PE-2:    The app should be insurance carrier claims application independent.
         PE-3:    the app should be mobile carrier independent.




Security Requirements:

Local Security:

Local security includes the password protection offered by the Finder, encryption of data provided by
FileVault, BSD access permissions, and access permissions added to applications through use of
Authorization Services (Apple, 2001).

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).

Certificate, Key, and Trust Services:

In iOS, 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 (Apple, 2001).



CFNetwork:

CFNetwork is a high-level API that can be used by applications to create and maintain secure data streams
and to add authentication information to a message. CFNetwork calls underlying security services to set up a
secure connection (Apple, 2001).

Authentication, Identification, and Authorization:
Authentication is the process by which a person or other entity proves that it is who it says it is (Apple, 2001).
Identification, which verifies that the person or entity is the same one you communicated with last time
(Apple, 2001).
Authorization requires first a determination that the authenticated entity has the appropriate permissions—
that is, the right to the specific type of access (such as read, write, or execute) requested—and then the
actual granting of that access (Apple, 2001).



Security Server Daemon:

The iOS security implementation includes a daemon called the Security Server that implements several
security protocols, such as access to keychain items and root certificate trust management (Apple, 2001).

Sandboxing:

To limit the damage in case a program is hijacked, both Mac OS X and iOS provide process sandboxing
(described in “Sandboxing and the Mandatory Access Control Framework”).In iOS, every application is
sandboxed during installation. The application, its preferences, and its data are restricted to a unique location
in the file system and no application can access another application’s preferences or data. In addition, an
application running in iOS can see only its own keychain items. Because every iOS application is sandboxed,
your application’s data and preferences cannot be read or modified by other applications, even if they have
been compromised by an attacker. If your application is compromised, the attacker cannot use it to take
control of the device or to attack other applications (Apple, 2001).
      :

Software Quality Attributes
Availability-1: App will be available 24*7 .
Robustness-1: If the connection between the user and the system is broken. The data enter will be
                saved in the system database and on connecting back the data input will be
                available.
Appendix A: Data Dictionary and Data Model.




Data                                                                        Drop   Radio
Classification   Attribute Name    Data type   Mandatory Optional Prefilled Down   Button   Remarks

Carrier
Information
                                                                                            One time entry
                 Company                                                                    for the primary
                 Activation Code   String      Yes                         No               insurance

                 Company Name      String      Yes                Yes
                 NAIC Code         String      Yes                Yes
Policy Holder
Information
                 First Name        String      Yes
                 Last Name         String      Yes
                 Date Of Birth     Date        Yes
              Last four digit of
              SSN                Numeric   Yes
              Policy Number      String          Yes
Vehicle
Information
              Vehicle Type      String     Yes               Yes   Owned/ Rental
              Vin Number        String     Yes

Loss Event                                                         Collision,
Details       Event Type        String     Yes               Yes   Vandalism
                                                                   GPS
                                                                   automatically
                                                                   locate the event
              Event Location    String     Yes         Yes         location
Data                                                                         Drop   Radio
Classification   Attribute Name     Data type   Mandatory Optional Prefilled Down   Button   Remarks
                 Event Time                                                                  Record the time
                 Stamp              Timestamp             Yes                                of FNOL entry
                 Event
                 Description        String      Yes
                 Event Pictures     Mime                  Yes
Policy Report
Information
                                                                                             to indicate if
                 Report filed                                                                police report was
                 Yes/No             String      Yes                                          filed

Driver
Information
                                                                                             If driver same as
                                                                                             the policy holder
                 Driver same as                                                              then prefill the
                 policy holder      String      Yes                         Yes              rest
                 Driver Name        String      Yes
                 Driver Date of
                 birth              Date        Yes

                 Driver Last four
                 digit of SSN       Numeric     Yes                         Yes
                 Driver's
                 Insurance
                 Carrier            String      Yes
Appendix B: Analysis Models

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:10
posted:4/8/2012
language:English
pages:18