Beruflich Dokumente
Kultur Dokumente
Template
for
Version #.#
Project Name:
Project Identifier:
Executive Sponsor:
IT Project Manager:
IT Relationship Manager:
Business Requirements QC
Manager:
Date Submitted:
Change History
Version
Date Revised By Requested By Change Description
No.
Page 2 of 17
< Project name goes here >
CONTENTS
1 INTRODUCTION.......................................................................................................5
1.1 Background............................................................................................................................. 5
1.1.1 Current Situation / Business Need...............................................................................5
1.1.2 Project Objectives........................................................................................................ 5
1.2 Scope....................................................................................................................................... 5
1.2.1 Out Of Scope................................................................................................................ 5
1.3 Desired Outcomes.................................................................................................................. 5
1.4 Stakeholders and End Users................................................................................................. 5
1.5 Dependencies......................................................................................................................... 6
1.6 Risks / Issues.......................................................................................................................... 6
1.7 Assumptions........................................................................................................................... 6
2 CURRENT STATE.....................................................................................................7
2.1 Description.............................................................................................................................. 7
2.1.1 Business Processes..................................................................................................... 7
2.1.2 Systems....................................................................................................................... 7
2.1.3 People / Organization................................................................................................... 7
2.1.4 Other............................................................................................................................ 8
2.2 Challenges and Opportunities............................................................................................... 8
2.2.1 Challenges................................................................................................................... 8
2.2.2 Opportunities................................................................................................................ 8
2.3 Information Transfers............................................................................................................. 8
3 PROPOSED STATE..................................................................................................9
3.1 Proposed Vision..................................................................................................................... 9
3.2 Benefits................................................................................................................................... 9
3.3 Proposed Business Processes............................................................................................. 9
3.4 Business Requirement Descriptions....................................................................................9
3.5 Systems................................................................................................................................. 10
3.6 Information Transfers........................................................................................................... 10
3.7 Minimum / Recommended Performance Considerations.................................................10
3.8 People / Organization........................................................................................................... 10
3.9 Optional Features................................................................................................................. 10
3.10 Impacts on Other Business Areas....................................................................................10
3.11 Future Considerations....................................................................................................... 10
4 BUSINESS REQUIREMENTS................................................................................12
Page 3 of 17
< Project name goes here >
5 IMPLEMENTATION CONSIDERATIONS...............................................................15
5.1 Critical Dates......................................................................................................................... 15
5.2 Constraints and Dependencies...........................................................................................15
5.3 Disaster Recovery Considerations.....................................................................................15
5.4 Security Requirements......................................................................................................... 15
5.5 Statutory and Regulatory Requirements............................................................................15
5.6 Training.................................................................................................................................. 16
6 ADDITIONAL INFORMATION................................................................................17
6.1 Reference Material................................................................................................................ 17
6.2 Glossary of Terms................................................................................................................... 17
Page 4 of 17
< Project name goes here >
1 INTRODUCTION
1.1 Background
In a few paragraphs, introduce the project and why we are doing it.
Provide a background and description of project, including factual information on the current situation and
business need. What is the impact of this problem on the business? Is there anything depending on this
project?
1.2 Scope
Describe the boundaries of the business process. Detail what is included (deliverables, product areas,
etc.) within the scope of this BRD bullet points are OK.
1.5 Dependencies
List dependencies that have been identified and are being actively managed. These could be
dependencies on other projects, resources, people or business areas/functions.
Page 5 of 17
< Project name goes here >
The following dependencies have been identified and are being actively managed:
The following project risks have been identified and will need to be managed to ensure the project is
successfully launched on schedule:
1.7 Assumptions
Clearly detail all assumption in relation to this BRD. For example:
This BRD assumes that ABC will continue to be the external provider of service XYZ.
Assumption #1
Assumption #2
Assumption #3
Assumption #n
Page 6 of 17
< Project name goes here >
2 CURRENT STATE
The Current State section of the BRD provides factual information describing how the business currently
operates, and any problems or enhancements that will be addressed by the project.
NOTE: If you do not include this section in the BRD you are required to provide the information in a
separate document that is signed off by the business.
2.1 Description
2.1.1 Business Processes
Provide diagrams of the current business processes. Include details such as activities being undertaken,
who undertakes the activities and systems and tools used. Swimlane process maps (see below) may be
useful. Written explanation may also be required.
2.1.2 Systems
Outline the systems involved in the current business processes. Include system names and the specifics
of their involvement with this project. Systems can also be indicated on the process maps. Context
Diagrams may be used as well.
Detail the people involved in the current business process and organizational structure if relevant
include details such as team names and roles, if known, and their involvement within the current
processes. This may be covered by the process map(s) in Section 2.1.1 above. For example:
Operators within the Admin Processing Team are required to manually manipulate reports on a
daily basis, which takes between 1 and 2 hours.
2.1.4 Other
Provide other detailed information relating to the Current State not covered in the preceding sections. For
example:
Page 7 of 17
< Project name goes here >
The physical location of the system may need to be changed as the lease on the current floor
expires at the end of 2006 and may not be renewed.
2.2.1 Challenges
Clearly detail the business challenges with the Current State and their impacts on the business. The
requirements detailed in later sections of the BRD will refer back to the challenges you are trying to
resolve. Challenges can be related to things that are broken, a need for improvement, a compliance
need, etc.
2.2.2 Opportunities
Clearly detail the business opportunities this project will address. The requirements detailed in later
sections of the BRD will refer back to these opportunities.
Page 8 of 17
< Project name goes here >
3 PROPOSED STATE
This section of the BRD provides a description of the proposed business state. In addition to describing
the proposed state, you should indicate which aspects represent a change from the current situation.
NOTE: If you do not include this section in the BRD you are required to provide the information in a
separate document that is signed off by the business.
3.2 Benefits
List the intended benefits of the Proposed State, and which specific Challenges and Opportunities from
Sections 2.2.1 and 2.2.2 that they resolve.
NOTE: The process groupings or requirement functions identified in this section will specifically drive the
requirements decomposition, with those results being captured in Section 4.
Page 9 of 17
< Project name goes here >
3.5 Systems
Outline the systems involved in the future business processes. Include system names and their
particulars involvement with this initiative. Systems employed can also be indicated on the process maps
in Section 3.2 above.
NOTE: In this section you are discussing the system requirements from a business perspective, rather
than detailing the IS solution.
NOTE: This may be covered by the Proposed Business Processes map in Section 3.2 above.
Once Phase 1 of the XYZ project has been launched successfully, implementation of a report
module may provide added value to the business. This report module is OUT OF SCOPE for
Phase 1.
Page 10 of 17
< Project name goes here >
IT SIO Sponsor:
Business Requirements
QC Manager:
Page 11 of 17
< Project name goes here >
4 BUSINESS REQUIREMENTS
Use the following outline to provide details of the business requirements for the Proposed State. This
section of the BRD should provide the detail on the features of the Proposed State and list the planned
outcomes.
Section 2 (Current State) and Section 3 (Proposed State) of this BRD should be completed in sufficient
detail to provide the feature groupings that will drive the outline of this business requirements section.
Section 3.2 should specifically list these high level requirement or feature categories. In the example
below, 2.0 Obtain Customer Information represents one individual Requirement or feature grouping /
family.
Where appropriate include tables, diagrams and screen prints to outline business requirements
necessary to deliver proposed state.
Use the following format to detail each requirement repeat the format for each requirement grouping.
Requirement Number
Requirement Title
Process or Context Diagram
Summary Process Narrative
Triggering Event(s) and Pre-Conditions
Outcome(s) and Post-Conditions
Alternatives Considered
Design Considerations / Notes
Issues / Assumptions / Risks
Requirements List
Page 12 of 17
< Project name goes here >
Process Diagram
CUSTOMER
other
customer & other driver detail known CUSTOMER
driver detail info
Obtain
Customer garaging
VEHICLE
CAMPAIGN solicitation / Information address
response
channel
vehicle detail
Customer information will be verified (or entered if it is a new customer with no Customer ID or if
the customer does not know their Customer ID). The agent will record information about all
drivers who are to be insured, including the relationship between the drivers.
Alternatives Considered
Through IVR/Not through IVR
Customer ID available/Not available
Resident of more than one state
Design Considerations/Notes
Want ability for reps to re-request CBUS with additional information without doing a manual
workaround
Score and reason codes cannot be altered (security)
Page 13 of 17
< Project name goes here >
Want ability to capture ANI and link to policy/quote without adding as alternate number
Ability to capture all phone numbers, but only display the number most commonly used
Requirements List
2.1 The system shall be capable of determining a customer exists using on the telephone
number that the customer dialed from.
2.2 The system shall be capable of determining if a customer exists based on the
customers last name and zip code.
2.3 The system shall be capable of allowing the agent to record the reason for a call.
2.4 The system shall be capable of recording the response channel as phone when a
customer calls in to speak to an agent.
2.5 The system shall be capable of allowing the agent to record the solicitation channel.
2.6 The system shall be capable of allowing the agent to record new customer detail.
2.7 The system shall be capable of allowing the agent to update existing customer
information if it has changed.
2.8 The system shall be capable of recording the details of the agent transferring a call and
the details of the agent or department to whom the call was transferred.
2.9 The system shall be capable of allowing the agent to record other driver information for
as many drivers as the customer wishes to insure in the household.
2.10 The system shall be capable of allowing the agent to record the relationship between
the head of the household and other drivers.
2.11 The system shall be capable of recording the customers home address as the default
risk address for the vehicles.
Page 14 of 17
< Project name goes here >
5 IMPLEMENTATION CONSIDERATIONS
5.1 Critical Dates
List any Critical Dates that must be met to ensure the project is a success. For example:
Using the Standards for the System Development Life Cycle form, review the Overview, Requirements,
Functional Design and Business Continuity Planning tabs. Each of these sections contains important
considerations for the Business Requirements phase. Ensure that the requirements address the issues
listed that are relevant to your project.
The Standards for the System Development Life Cycle form is available by navigating to:
Teams => Operational Risk Management => Information Security => Forms => Standards for the
System Development Life Cycle
http://intranet.axa-financial.com/Teams/RiskMgmt/Info_Security_Library.html#forms
Some of the important issues addressed there include security forum reviews, data transfer in and out of
the enterprise, third party contractual relationships, risk assessment, key project roles for security,
information classification, disaster recovery, integration with standard access control systems, defining
user profiles for role based access control, etc. See the form for further details.
All solutions are affected in some way by federal, state and or local regulations. The key is determining
which regulations apply to the Proposed State solution, and what must be done to ensure both immediate
and sustained compliance. Some examples of regulations that may apply include:
Page 15 of 17
< Project name goes here >
It is critical that requirements that pertain to regulatory compliance are clearly identified. This will help
ensure that future decision-makers do not inappropriately nullify a compliance requirement due to an
imperfect understanding of the intent and consequences.
5.6 Training
Identify any training needs for using the new / modified tools or processes. Describe the expected
approach for training including who will provide the training, the type of training to be provided, when
training needs to occur (timing), the location of training, etc.
Page 16 of 17
< Project name goes here >
6 Additional Information
6.1 Reference Material
Identify any documents that are referenced in the BRD, and where they may be located.
The following phrases, acronyms and abbreviations are used throughout this document:
Term Definition
Enter phrase, acronym, or Enter the definition here
abbreviation here
Page 17 of 17