Pacific Compensation Insurance Company

<Project Name> Business Revision No.: <N.NN>

Requirements
SYSTEMS AFFECTED: <system name(s)> Date: <MM/DD/YY>

Status: <DRAFT or FINAL> Page 1 of 7

Confidentiality Statement

The information and data contained herein are the proprietary and confidential information and data
of Pacific Compensation Corporation.
 <Project Name> Business Requirements

Document Revision History

Version Change Description Date Author

<N.NN> <MM/DD/YY>

Document Information

File Name Network Directory Path

<fileName>.doc <drive\directory\ or EDC wiki > Project Documentation > <project

name>>

Related Documents

Document # Document Title Location

<relDocNo> <relDocTitle> <drive>:\directory\

References

Document Title Location

<refDocTitle> <drive>:\directory\ or physical location

Contributors

Contributor Name Responsibility

<DRAFT or FINAL> PCIC Confidential Page 2 of 7

 <Project Name> Business Requirements

Approvals

Name Title, Department Signature Date

<Business owner>

<Business analyst for the

business>

<DRAFT or FINAL> PCIC Confidential Page 3 of 7

 <Project Name> Business Requirements

Contents
1.0 Executive Summary ...................................................................................................... 5
2.0 Scope ............................................................................................................................. 5
3.0 Business Case ............................................................................................................... 5
3.1. Problem Statement ............................................................................................................. 5
3.2. Business Drivers ................................................................................................................. 6
4.0 Workflow ........................................................................................................................ 6
5.0 Requirements ................................................................................................................ 6
5.1. General Requirements ........................................................................................................ 6
6.0 Report Requirements .................................................................................................... 6
7.0 System Documentation................................................................................................. 7
8.0 Training Requirements ................................................................................................. 7
9.0 Other Considerations .................................................................................................... 7

<DRAFT or FINAL> PCIC Confidential Page 4 of 7

 <Project Name> Business Requirements

1.0 Executive Summary

<NOTE: Text in angle brackets, like this <text>, is an instruction or placeholder. Delete this text once you
understand the instructions. Replace it with any required text.>

<Present a high level summary of business issues being addressed by this project and the anticipated benefits.
Provide an understanding of risks associated with the project. Include:

 What the project needs to accomplish and why

 By when (especially if there is a compelling reason, such as compliance or new business relationship

 What department needs the project>

2.0 Scope

The scope of <project name> Business Requirements covers <provide a short description of the system,
application, enhancement, Software-as-a-Service (SaaS), Commercial Off-the-Shelf (COTS) software being
specified and its purpose>, including benefits, objectives and goals. Relate the project to corporate goals or
business strategies.>

3.0 Business Case

<Business Case including high-level problem, benefits, objectives and goals. Relate the project to corporate goals
or business strategies.>

3.1. Problem Statement

<Duplicate as necessary>

Problem <Describe the problem; for example, improper resolution of claims issues, inefficiency in
process, compliance requirements.>

Stakeholders <List the primary stakeholders; for example, Claims Examiners, Executives, Customers and
Supervisors.>

Impacts <Describe the impact of the problem; for example, compliance penalties, workflow
problems, customer satisfaction, loss of revenue.>

Success Criteria <List some key factors of a successful solution; for example, ability to provide up-to-date,
accurate claims information.>

<DRAFT or FINAL> PCIC Confidential Page 5 of 7

 <Project Name> Business Requirements

3.2. Business Drivers

<Identify the business drivers for this solution>

4.0 Workflow

<optional>
<As an introduction, briefly summarize what will be addressed in this workflow section. Describe current and
proposed workflows. Include or attach reference workflow diagrams, if available.>

5.0 Requirements

This section describes the general features required for the project or solution.

5.1. General Requirements

Feature Description

<First feature>

<Second feature>

6.0 Report Requirements

<When a project also has a report requirement, identify high-level report description and reference to report
specification (if it exists).>

<DRAFT or FINAL> PCIC Confidential Page 6 of 7

 <Project Name> Business Requirements

7.0 System Documentation

<If applicable, reference system documentation requirements, which may include:

 System Administration and Maintenance Standard Operating Procedure
 Vendor documents
 Training manual
 User’s Guide>

8.0 Training Requirements

<List necessary training related to implementation of this system for business users, developers, system
administrators and help desk representatives. Include sandbox training environment needs. List the types of
training records that are required. Discuss training plan and schedule.>

9.0 Other Considerations

<Provide additional information not covered in other sections of the document.>

<DRAFT or FINAL> PCIC Confidential Page 7 of 7