This document outlines the business requirements for a project including non-functional requirements. It provides details on the purpose, audience, assumptions and associated documents. The business requirements section lists over 20 specific requirements categorized by ID and priority. Non-functional requirements cover areas such as data center needs, business continuity, and compliance. Attachments and references are included, and the document requires approval from those who authored, reviewed, and approved the requirements.

1. Business Requirements
Project Name: [Insert Project Name here.]
Project Number: [Insert Project Number here.]
Project Manager: [Insert Project Manager Name here.]
Document Version History
Version Revision Date Author Change Description
[v0.01] [08/15/2012] [Replace this text with
the name of the
Document Owner.]
[First draft created.]
[v0.02] [09/30/2012] [Replace this text with
the name of the Change
Owner.]
[Describe the changes made in this version.]
• [Change 1]
• [Change 2]
• [Change n]

2. [Project Name] Business Requirements
Table of Contents
1.INTRODUCTION................................................................................................................................................... 2
1.1 Document Purpose..................................................................................................................................2
1.2 Audience................................................................................................................................................... 2
1.3 Assumptions............................................................................................................................................. 2
1.4 Associated Documents...........................................................................................................................2
1.5 Definitions................................................................................................................................................. 2
2.BUSINESS REQUIREMENTS...............................................................................................................................3
2.1 Non-Functional Requirements..................................................................................................................4
3.ATTACHMENTS................................................................................................................................................... 4
4.REFERENCES...................................................................................................................................................... 4
5APPROVALS......................................................................................................................................................... 6
Gilead Sciences, Inc. – Internal Use Only Page 1

3. [Project Name] Business Requirements
1. INTRODUCTION
1.1 Document Purpose
The purpose of the Business Requirements document is to:
 Detail the expected business requirements
 Provide a list of specific requirements that can be used for vendor selection
1.2 Audience
The audience for this document will be the project team. Additional audiences may include the project
Steering Committee or vendors. The tables in this document may be pasted into an RFP to provide
details on Gilead’s required functionality.
1.3 Assumptions
This document assumes that the reader is familiar with general project management principles and has
a copy of the Gilead IT Project System methodology (GPS).
1.4 Associated Documents
This document should be used in concurrence with the Gilead Project System (GPS).
1.5 Definitions
The reader should reference ITD-0289, Lexicon of Computer Terminology, for a complete list of
definitions used through-out this document, and other definitions and abbreviations used in the
document are as follows:
Term Definition
PMM Project Management Methodology
PLC Project Life Cycle
GPS Gilead Project System
Gilead Sciences, Inc. – Internal Use Only Page 2

4. [Project Name] Business Requirements
2. BUSINESS REQUIREMENTS
These are the specific requirements that tie directly to the need of the business. Describe all of the business requirements using the table
below. Each business requirement should have a unique id. Areas/Functions and processes should be added on as needed basis.
Req ID Req Type/Area
Business
Function/
Process
Requirement Description
Priority
(High/
Medium
/Low)
Vendor
Fit
Issues/
Assumptions
System
Impacted
Architecture
Impact
FR.1 Enter the
requirement type
category to
which the
requirement
belongs, i.e.
Oracle, OBIEE
Localization,
Data Interface,
User Interface,
etc.
A category based
on the specific
project used for the
purpose of
categorizing and
organizing the
requirements, i.e.
specific module:
Order to Cash,
Procure to Pay,
etc..
Include a description of the
requirement, including country
specific requirements; user
interface requirements which may
include data entry screens, reports
or web pages, etc.
Fully met,
Partially
met or
Not met
List any issues or
assumptions regarding this
specific requirement
List the system
impacted by this
requirement or
N/A for no
impact.
List whether the
requirement is
Critical,
Important or
Ancillary to the
architecture, or
N/A for no
impact to the
architecture
FR.2 Add additional requirements as
needed
FR.3
FR.4
FR.5
Gilead Sciences, Inc. – Internal Use Only Page 3

5. [Project Name] Business Requirements
2.1 Non-Functional Requirements
Non-functional requirements could include hardware or purchased components; data center requirements, storage and retention
requirements, Business Continuity & Recovery requirements, Legal/Regulatory Compliance, etc.
Req ID Type Requirement Description
Priority
(High/
Medium/
Low)
Vendor
Fit
Issues/
Assumptions
System
Impacted
Architecture
Impact
NFR.1 i.e. Data Center,
Business
Continuity &
Recovery, etc.
Complete description of the requirement,
including necessary technical requirements for
operating system, etc.
If for Legal/Regulatory compliance-related, list
requirements to meet GxP, SOX, etc.
Fully met,
Partially
met or
Not met
List any issues or
assumptions regarding this
specific requirement
List the system
impacted by this
requirement or
N/A for no
impact.
List whether the
requirement is
Critical,
Important or
Ancillary to the
architecture, or
N/A for no
impact to the
architecture
NFR.2 Add additional requirements as needed
NFR.3
NFR.4
NFR.5
3. ATTACHMENTS
# Attachment Description
A [Include support materials or visuals for the requirements, such as screen prints, mock-ups, or prototypes in support of the requirement presented.]
B
C
4. REFERENCES
Ref # ID Reference Description Location Owner
4.1 ITD-0289 Lexicon of Computer Terminology
4.2 [Include appropriate reference documents that help clarify or expand upon
requirements as needed.]
[Provide a description of where
the reference item is located…]
[…and who owns or is
currently retaining the
reference item.]
Gilead Sciences, Inc. – Internal Use Only Page 4

6. [Project Name] Business Requirements
Gilead Sciences, Inc. – Internal Use Only Page 5

7. [Project Name] Business Requirements
Business Requirements
5 APPROVALS
Prepared By:
The “Prepared By” signature indicates the individual(s) who authored this document:
Name Title/Role Approval
Documentation
[Insert email approvals as
embedded objects or location
where approval is stored]
Reviewed By:
The “Reviewed By” signature indicates the individual(s) who reviewed this document for content and
clarity, and to the best of their knowledge, this document satisfactorily achieves the purpose and
scope defined herein:
Name Title/Role Approval
Documentation
[Insert email approvals as
embedded objects or location
where approval is stored]
Approved By:
The “Approved By” signature indicates the individual(s) who approved this document for content and
clarity and to the best of their knowledge, the document satisfactorily reflects the detail required to
achieve the defined project goals and objectives:
Name Title/Role Approval
Documentation
i.e. Project Sponsor [Insert email approvals as
embedded objects or location
where approval is stored]
GPS Methodology
Gilead Sciences, Inc.
For Internal Use Only
Business Requirements
Template Revised:
10/01/2012
Gilead Sciences, Inc. – Internal Use Only Page 6