System Analysis General Overview

In this brief post I will be covering a general overview of some parts of system analysis. One of the ways that I learn best is by either doing something like it or looking at examples. System

OneQuote Company system analysis: Mission Statement, Functional System Requirements, System-Level Use Cases and System-Level Constraints.

Here we will be looking at a general scenario, this is based of a made up company and keep in mind it is a general overview and many details on the company or process will not be here.

 

OneQuote is an insurance company that covers vehicles, hours, farm and specialty items.OneQuote has a large group of sales members throughout the nation and would like them to be able to gain access to their information system back at the main office. Having mobile access will permit them to have location-specific rates, exceptions, templates that the company uses while they are at the customer’s location. They are known for offering personalized service for three year policies paid at once and their overall low rates. 

Mission Statement

Wether we have worked with a company or have used services of certain companies each one has their mission statement. A mission statement declares the company’s main purpose, goal and their focus. This tends to be the global and longterm goal and most of the time it remains unchanged.

 

OneQuote application is a system for sales representatives to help them assist potential and current customers while maintaining constant communication with central office. The OneQuote application promotes sales representatives to quickly, securely and accurately access templates, location-specific rates, exceptions,  and manage promotional rates. The OneQuote application encourages sales representatives to work efficiency by allowing quick, and simple access to information required for delivering quotes.

Functional Requirements

The functional requirements are things that the system will be able to do, perform. It discussed the behavior of what the system will do when it is used.

  • An agent will be able to use the system to retrieve insurance rates for homes, vehicles, farm animals and specialty items based on geographic region such as zip code or city.
  • An agent will be able to use the system to determine if multiple insurance products can be purchased together for a bundled discount.
  • An agent will be able to create and save an insurance quotes for a client following a template.
  • An agent will be able to retrieve saved quotes for a specific client by name, policy number, or phone number.
  • An agent will be able to query current clients by geographic region.
  • A unique customer number will be generated by the system when a new customer is added to the system.
  • A unique quote number will be generated by the system for each new quote.
  • A unique policy number will be generated by the system when a product is purchased.
  • The system will be accessible without internet connection.
  • The system will be able to upload all quotes to a central server.
  • The system will be able to send quotes through e-mail.

 

System-Level Use Cases

Perhaps this is one of the ways I am able to “see” how the system actually works and how the user will be interacting with it. A use case is an “action” or a single interaction with the system. After a while it can appear to be repetitive and redundant to have a long list of them, but you can decide which ones you want to walk through first. I usually like to start with the main components of what the system is supposed to do. For those familiar with databases you will see that these are familiar. Here are couple of examples.

Create a new quote

  1. Agent selects new quote option on the action bar.
  2. OneQuote application shows fields to be completed out for a client.
  3. Agent enters client’s contact information in the appropriate fields. Agent selects next.
  4. OneQuote application lists insurance options available in client’s geographic region including bundled options.
  5. Agent chooses insurance product.
  6. OneQuote application returns more options specific to the type of product chosen earlier.[2]
  7. Agent enters additional information for that product and selects next.
  8. OneQuote application displays product price for the chosen options.
  9. OneQuote application provides options to send quote to the client by email, or mail.

Client search by geographic region

  1. Agent selects search option on the action bar.
  2. OneQuote application shows a list of search fields.
  3. Agent enters geographic information such as zip code or city in appropriate fields. Agent selects the search button.
  4. OneQuote application displays clients matching search criteria.

Purchase insurance for a current quote

  1. Agent selects search option on the action bar.
  2. OneQuote application displays a list of search fields.
  3. Agent enters client information in appropriate fields. Agent selects next.
  4. OneQuote application lists clients matching searching criteria.
  5. Agent selects the appropriate client.
  6. The application displays a list of quotes for that client.
  7. Agent selects quote customer would like to purchase.
  8. The application displays total product price.
  9. Agent selects the purchase button.
  10. The application displays payment options.
  11. Agent selects payment options and fills in payment information.
  12. The application displays new policy number.

 

System-Level Constraints

To put into simple terms system level constraints are items that the system has to have.

  • The OneQuote application will run on Android version 5 tablets.
  • The OneQuote application must be consistent with recommended development practices[3].
  • The OneQuote application will be able to retrieve information through Wi-Fi and cellular phone networks.
  • Agents will not have permission to delete existing policies, clients, or quotes.
  • The OneQuote application can be viewed in horizontal and vertical orientation.
  • The OneQuote application will use the color theme of the company logo.
  • Every customer record must have the following information: first name, last name, and date of birth.

 

Next time, we’ll briefly look at system categories…

 

 

 

 


[1] zipForm Plus (http://www.ziplogix.com/zipformplus/index.asp)
[2] https://sales.esurance.com/CustomerFlow/CustomerFlowStandard/VehicleInfoPage.aspx
[3] http://developer.android.com/guide/topics/ui/index.html
How To Insure Your Home. (n.d.). Retrieved September 2015, from The Wall Street Journal: http://guides.wsj.com/personal-finance/insurance/how-to-insure-your-home/
Patra, P. K., Sahu, D. P., & Mandal, I. (2010). An Expert System for Diagnosis of Human Diseases. International Journal of Computer Applications, 1(13), 71-73.
User Interface . (n.d.). Retrieved September 2015, from Android Developers: https://developer.android.com/guide/topics/ui/index.htm
What You Need for Car Insurance Quote. (n.d.). Retrieved September 2015, from DMV.org: http://www.dmv.org/insurance/what-you-need-for-a-car-insurance-quote.php