Running head: FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab
ab ab ab ab ab ab 1
Milestone Three: System Requirements
IT 510 – Advanced Info Technology
SNHU
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 2
URCovered, Inc., one of the largest major auto insurance companies in
North America, is on the way to develop a mobile application to improve customer
service in the area of claim management which will be an extension of the current web
based claim management system. The development of this mobile application project
needs a system requirements model which includes a requirements model, a data process
model, a data flow diagram, a data dictionary, an object model, and a use case diagram.
Requirements Modeling
Information is collected by using various fact-finding techniques, such as
interviews, surveys, feedbacks from the customers, observation, analysis of the existing
system, etc. to create system requirements checklist.
Outputs
• The mobile application must be the extension, not a replacement of the current
process.
• The system must have the options for two-way communication (voice calls and
chat) so that the customers and case managers can directly communicate through
the app.
• The application must be compatible with key platforms.
• The system must alert the customers to new information.
Inputs
• Security IDs and levels must be the same as already exist in the web application.
• Same user IDs and passwords as web application will be used to access the
mobile application.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 3
• Each customer input must include client ID, name, address, age, sex, contact
information, insurance ID, vehicle information, etc. to proceed further for any
claim management.
• The mobile application will integrate with the current database of the claim
management system.
Processes
• The system must record the information in the existing database of the claim
management system.
• The system must provide the information or status of a claim in the same
manner that a case manager would.
• The system must have the case manager’s online business card with an option to
immediately dial the case manager from the mobile application.
• The system must update the customers for any change in the status of a claim.
Performance
• The system must support at least 25 customers simultaneously.
• Response time must not exceed 4 seconds.
• The system must be operational 24 x 7 and 365 days a year.
Controls
• The system must provide access to all the services of the application to the
customers after providing login information.
• The SSN and other information of the customers must be secured properly.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 4
• The login information of the customers must be encrypted.
• The status of a claim to the customers must only be provided by the case
managers.
Data Process Model
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 5
Login
Information
Input
Success
Claim Management
System Database
Case Manager
Claim
Processing
Status to Customer
Decision
Log out/ End
Failure
Figure 1: A data process model for the mobile application.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 6
Data Flow Diagram
0
CLAIM
MANAGEMENT
SYSTEM
0
CLAIM
MANAGEMENT
SYSTEM
CUSTOMER
CASE MANAGER
BANK
CAR REPAIR SHOP
CLAIM
CLAIM PROCESSING
COMPLETED STATUS
DECISIONPENDING STATUS
FEEDBACK
BANK PROCESSING
PAYMENT AS THE CLAIM
Figure 2: Context diagram DFD for claim management system of the mobile application
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 7
Data Dictionary
Data Elements
Data
Element
Name
Data
Type &
Length
Description
Required
(Y/N)
Acceptable Values
CUSTOMER
ID
Integer
Primary Key, Unique
identifier
Y
System generated
FIRST
NAME
Character
(20)
Customer’s First Name
Y
Must start with A –
Z. No numbers
allowed to start.
LAST
NAME
Character
(20)
Customer’s Last Name
Y
Must start with A –
Z. No numbers
allowed to start.
DOB
Date
Customer’s date of
birth
N
Cannot be a date in
future.
PHONE
Integer
Customer’s phone
number
N
Various formats
(xxx)-xxx-xxxx
EMAIL
Character
(50)
Customer’s email
address
N
Must have “@”
symbol. Alphanumeric
ADDRESS
Character
(100)
Customer’s address
Y
Alphanumeric. Must
be valid USA address
SSN
9N
Customer’s Social
Security Number
Y
Any nine-digit number
VEHICLE
Character
(50)
Customer’s vehicle
type, make and model
Y
Alphanumeric
DATE
Date
The date of record
entry
Y
System generated
today’s date.
ACTIVE
Boolean
1 for Active (Yes)
0 for Inactive (No)
Y
0 or 1
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 8
Data Flows
Data Flow
Name
Description
Origin
Destination
CLAIM
Insurance claim
by customer
CUSTOMER entity
CLAIM
MANAGEMENT
SYSTEM process
CLAIM
PROCESSING
Claim on
processing by case
manager
CLAIM
MANAGEMENT
SYSTEM process
CASE MANAGER
entity
PENDING
STATUS
Status to customer
about the claim.
CLAIM
MANAGEMENT
SYSTEM process
CUSTOMER entity
DECISION
Decision made by
case manager
about the claim
CASE MANAGER
entity
CLAIM
MANAGEMENT
SYSTEM process
COMPLETED
STATUS
Completed status
of the claim to
the customer
CLAIM
MANAGEMENT
SYSTEM process
CUSTOMER entity
FEEDBACK
Feedback by the
customer about
overall system
CUSTOMER entity
CLAIM
MANAGEMENT
SYSTEM process
BANK
PROCESSING
Bank processing
for payment as
the claim
BANK entity
CLAIM
MANAGEMENT
SYSTEM process
PAYMENT AS
THE CLAIM
Payment to the
car repair shop as
the claim
CLAIM
MANAGEMENT
SYSTEM process
CAR REPAIR
SHOP entity
Processes
Process Name
Description
Process
Number
Process Description
CLAIM
MANAGEMENT
SYSTEM
A process
to manage
auto
0
Input data flows: CLAIM,
DECISION, FEEDBACK, BANK
PROCESSING.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 9
insurance
claim
Output data flows: PENDING
STATUS, CLAIM PROCESSING,
COMPLETED STATUS,
PAYMENT AS THE CLAIM
Entities
Entity Name
Description
Input Data Flows
Output Data
Flows
CUSTOMER
Auto insurance
customer
PENDING STATUS,
COMPLETED STATUS
CLAIM,
FEEDBACK
CASE
MANAGER
Case manager of the
auto insurance company
CLAIM PROCESSING
DECISION
BANK
For banking services
of the auto insurance
company
---
BANK
PROCESSING
CAR
REPAIR
SHOP
For maintenance of
the insured vehicles
PAYMENT AS THE
CLAIM
---
Object Modeling
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 10
Figure 3: Diagrams showing three objects, CUSTOMER, CASE MANAGER, and
VEHICLE with their attributes and methods for the mobile application of the claim
management system.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 11
Use Case Diagram
Analyze
Information
Claims
insurance Investigates
information
Checks
Update Decision
Makes Payment
Update
Update
Notifies
Asks for
detail
Provides
expenses
Customer
Car Repair
Shop
Case Manager
Figure 4: Use case diagram showing claim management system for the mobile
application.
FINAL PROJECT MILESTONE THREE: SYSTEM REQUIREMENTS ab ab ab ab ab ab ab ab a ab 12
References
IT 510 Module two case study. (n.d.). Southern New Hampshire University, Manchester
NH
Tilley, S., & Rosenblatt, H. (2016). Systems analysis and design (11th ed.). Boston,
MA: Cengage Learning.
