Plan BA Governance

BA Doc/Detail Design Document
Typewriter to Computer
Business Requirement Document Version 1.0
07/07/2017
BA Doc SIGN-OFF
Sign-off is a prerequisite for moving forward on the project. This BRD Document will be baselined to
ensure the delivered system meets the approved business and functional requirements as per the
Configuration Management process. Once approved and signed-off, the requirements are fixed and any
subsequent changes to the project requirements or scope must follow the Configuration Management
process for the project.
BRD Approvals Name / Signature Date Approval Received
Stakeholder:
Stakeholder:
Stakeholder:
Stakeholder:
Stakeholder:
Project / Application
Delivery Manager:
Revision History
Version No. Date Revised By Revision Description

0.1 05/24/2017 Akhilendra P Singh Initial Draft
0.2 05/31/2017 Akhilendra P Singh Updated Based on Comments

Version No. Date Revised By Revision Description

0.3 06/05/2017 Akhilendra P Singh Updated Based on Comments
1.0 06/27/2017 Akhilendra P Singh Approved and baselined
1 Introduction
Company X is currently using Typewriters to perform its daily operations. As a result, processing is very
slow and it takes 5 days to process 1 application. It is very hard to retrieve the processed application if
you need to refer to some old contracts.
Lots of efforts are needed to record and log the processed applications along with higher risk of losing
documents.
1.1 Current Situation and Business Need
Company X is currently using Typewriters to perform its daily operations. As a result, processing is very
slow and it takes 5 days to process 1 application. It is very hard to retrieve the processed application if
you need to refer to some old contracts.
Lots of efforts are needed to record and log the processed applications along with higher risk of losing
documents.
Business Need to automate the process of processing applications, retrieving processed applications and
solution should make it easier to record and log the processing.
1.2 Out of Scope
1. User training
2. Infrastructure changes to support the solution implementation.
3.
1.3 Systems/Departments Impacted:
o Team A
o Team B
2 Challenges/Assumptions
Challenge # Challenge Description Priority
Ude.2.01 Training users to work with new system High
Page 2 of 6 Document1
Challenge # Challenge Description Priority
2.1 Assumptions
1. Training department will update their training manuals for computer usage.
2. Admin team will make necessary changes to support computer installation.
3 High-Level Requirements
High-Level High-Level Requirement Description Associated Priority
Requirement # Challenge #
Ude.3.01 Solution should improve the processing Ude.2.01 High
speed.
Ude.3.02 Solution should automate the process of Ude.2.01 High
templating
Ude.3.03 Solution should make it easier to access Ude.2.01 High
the produced letters.
Ude.3.04 Solution should make it easier to print the Ude.2.01 High
letters
4 Business and Functional Requirements

4.1 Detailed Requirements
4.1.1 Team A
Requirement # Description Priority

Ude.4.1. 01 This is a SAMPLE Requirement for Team A change Medium
Ude.4.1.02 This is a SAMPLE Requirement for Team A change High
Ude.4.1.03 This is a SAMPLE Requirement for Team A change Low
4.1.2 Team B

Ude.4.2. 01 This is a SAMPLE Requirement for Team B change Medium
4.1.3 Additional Miscellaneous Requirements

Manual Processing, Operations
4.1.4 Form
Attach copy of existing forms here.
5 Screen and Report Requirements

5.1 Screen and User Interface Requirements
5.2 Report Requirements
Sample Reports- Do not treat as standard

5.3 Screen and Report Data Elements
Requirement # Data Element Description Priority

Name
6 Non-Functional Requirements
7 Detailed Design & Solution

7.1 This is a SAMPLE Requirement for Team A change.
Description
Add more details about the requirement, if applicable. Sometime it is not based on company’s guidelines.
Solution
In this section talk about changes which will be made in system to accomplish the above-mentioned
requirements.
7.2 This is a SAMPLE Requirement for Team A change.

Description
Add more details about the requirement, if applicable. Sometimes it is not based on company’s
guidelines.
Solution
In this section talk about changes which will be made in system to accomplish the above-mentioned
requirements.
8 Technical Design
8.1 Database Changes
Mention the name of the database/table.
8.2 XML Updates
Mention the name of the xml updates here

9 Open Items
Requirement # Question/Open Item Response
10 Appendix
10.1 Supplemental Documents
Document Title Version Date Released URL

A.

Plan BA Governance

Uploaded by

Copyright:

Available Formats

Plan BA Governance

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Plan BA Governance

Uploaded by

Copyright:

Available Formats

BA Doc/Detail Design Document

Business Requirement Document Version 1.0

BRD Approvals Name / Signature Date Approval Received

Version No. Date Revised By Revision Description

0.2 05/31/2017 Akhilendra P Singh Updated Based on Comments

Version No. Date Revised By Revision Description

1.1 Current Situation and Business Need

1.2 Out of Scope

Challenge # Challenge Description Priority

4 Business and Functional Requirements

Requirement # Description Priority

Requirement # Description Priority

4.1.3 Additional Miscellaneous Requirements

Requirement # Description Priority

Attach copy of existing forms here.

5 Screen and Report Requirements

Requirement # Description Priority

5.2 Report Requirements

Sample Reports- Do not treat as standard

5.3 Screen and Report Data Elements

Requirement # Data Element Description Priority

7 Detailed Design & Solution

7.2 This is a SAMPLE Requirement for Team A change.

8.2 XML Updates

Mention the name of the xml updates here

Requirement # Question/Open Item Response

Document Title Version Date Released URL

You might also like