Product Area – i.e. claims system, pharmacy, etc.

Business Requirements Specification

Project Title – Descriptive summary
CorVel Corporation Business Requirements Specification
July 18, 2011 2

Document Revision History

Date Revision Author Changes Made
Date this Version Who created List all changes made when creating this version
version was number this version
created (i.e. 1.0.0)
Date this Version Who created List all changes made when creating this version
version was number this version
created (i.e. 1.0.0)
CorVel Corporation Business Requirements Specification
July 18, 2011 3

Table of Contents

1 Introduction.........................................................................................................................................3
1.1 Current Process...........................................................................................................................3
1.2 Purpose........................................................................................................................................3
1.3 Scope...........................................................................................................................................3
1.4 Systems Impacted........................................................................................................................3
1.5 Acronyms.....................................................................................................................................3
1.6 Users / Roles................................................................................................................................3
1.7 Stakeholders................................................................................................................................3
1.8 Questions.....................................................................................................................................3
2 Functional Requirements.....................................................................................................................3
2.1 [Title]...........................................................................................................................................3
2.2 [Title]...........................................................................................................................................3
3 Reporting Impacts...............................................................................................................................3
4 Access Control.....................................................................................................................................3
5 Data Conversions.................................................................................................................................3
6 Data Exchange.....................................................................................................................................3
7 Attachments........................................................................................................................................3
8 Documentation Team Section.............................................................................................................3
9 PSG Section..........................................................................................................................................3
10 Stakeholders....................................................................................................................................3
10.1 Account Management Section.....................................................................................................3
10.2 Sales Impact Section....................................................................................................................3
10.3 Implementation Team Section.....................................................................................................3
10.4 Post-Implementation Section......................................................................................................3
10.5 Measurement of Project Success.................................................................................................3
11 End of Document.............................................................................................................................3
CorVel Corporation Business Requirements Specification
July 18, 2011 4

1 Introduction
Brief history of business need, who submitted project, what the project should accomplish

1.1 Current Process

Detailed description of the current process

1.2 Purpose
The intent of the project as it relates to changing the current process

1.3 Scope
What the project will *and* won’t accomplish. Detailed list of proposed changes in the phase of
the project outlined in this document

1.4 Systems Impacted

Select any systems that will be impacted by the project scope
Claims System MedCheck CareMC
Database Hardware/IT Reporting
EDI PeopleSoft Data Warehouse Other [Click here to

enter text]

1.5 Acronyms
List all acronyms referenced in this document, with a full name and definition of each

1.6 Users / Roles

Check each CorVel internal or external role that will be impacted by this development

Role 1 Role 2 Role 3 Role 4

Role 5 Role 6 Role 7 Role 8

1.7 Stakeholders
List the names and the titles of the major business side owners for this project
CorVel Corporation Business Requirements Specification
July 18, 2011 5
1.8 Questions
List any unknowns for the project that need to be addressed by business stakeholders,
developers, or other parties. Include dates for each question, as well as who the question is
from
CorVel Corporation Business Requirements Specification
July 18, 2011 6

2 Functional Requirements
List additional summary of proposed development that weren’t addressed in purpose and scope

2.1 [Title]
List subproject with detail below

2.2 [Title]
List subproject title with detail below. Add additional sub-projects as needed

3 Reporting Impacts
List any reporting elements that are impacted by development proposed in the functional
requirements. i.e., if data changes based on the new development, how will it affect reporting
downstream?

4 Access Control
Who needs access (internal/external) and what type of access needed (read-only, etc)

5 Data Conversions
List any changes in existing data formatting, conversions to new data formats, or changes in the
way data is displayed in the application

6 Data Exchange
List any instance in which data is transferred from one system to another as a result of this
development

7 Attachments
Place link to attachment in SharePoint site and include SharePoint directory list
CorVel Corporation Business Requirements Specification
July 18, 2011 7
8 Documentation Team Section
Determine the documentation and training requirements associated with this project, i.e. if the
user manual will need to be updated, a training guide needs to be created, or if video training is
required

9 PSG Section
Determine the Product Support Group requirements associated with this project, i.e. if the
customer and/or user setup process will need to be updated, if the support of the product will be
impacted in any way, etc.

10 Stakeholders
10.1 Account Management Section

Besides the release call and the release notes, is there anything that should be communicated
directly to account managers in order to better help them do their jobs?

10.2 Sales Impact Section

Besides the release call and the release notes, is there anything that should be communicated
directly to account executives/sales VPs in order to better help them do their jobs?

10.3 Implementation Team Section

What needs to be done for it to “turn on”? Who’s responsible? Technical Needs, Training: How
to use it. – Lead member lets Sales (#10.2) and Account Managers (#10.1) know if affected

10.4 Post-Implementation Section

Are there any follow-up actions once the development code is implemented, PSG setups
complete, and all other bases covered to close out this project? If so, who is responsible for
those actions, and who is responsible for ensuring that those actions are completed?

10.5 Measurement of Project Success

Define how the success of this project will be measured. Are there specific people that will be
analyzing the project? If so, who and how exactly will they determine if the project is meeting
the needs as outlined in the requirements?

11 End of Document