Brd Templte

Topics: Unified Modeling Language, Use case, Entity-relationship model Pages: 34 (5442 words) Published: May 9, 2013

Ministry/Agency Name

[Complete file/properties to populate fields on this page and in the document headers]

Project Name
Project #:
Business Requirements Document (BRD) Template

Prepared by:Author's Name
Prepared for:
Date Submitted:[Date]

Project Sponsor:Project Sponsor's Name
Client Acceptor:
Project Manager:

Document Number:6450-20/Project Number /BRD
Security Classification: Low

Last Updated:June 06, 2006
Creation Date:June 06, 2006

Table of Contents

Table of Contents2


1.1.Document Purpose4
1.2.Intended Audience4
1.3.Project Background5
1.4.Purpose of the Business Requirements5
1.5.Business Goals/Objectives to be achieved7
1.8.Dependencies on existing systems7

2.Requirements Scope8

2.1.In Scope9
2.2.Out of Scope9

3.Functional Requirements10

3.1.Actor Profiles Specification10
3.2.Essential Use Case Diagram11
3.3.Essential Use Case Specifications12
3.4.Function Hierarchy Diagram13
3.5.Function Definition Report14
3.6.Business Rules14

4.Data Requirements15

4.1.Data Architecture15
4.1.1.Domain Class Diagram16
4.1.2.Entity Relationship Diagram16
4.2.Data Volumes17
4.3.Data Conversion17
4.4.Data Retention and Archiving17
4.5.FOI/Privacy Implications18
4.6.Data Definition Reports19
4.6.1.Domain Class Definition Report19
4.6.2.Entity Definition Report20

5.Non-Functional requirements21

5.1.Security Requirements21
5.1.2.Authorization and Access Controls23
5.2.Availability Requirements23
5.3.Usability Requirements24
5.4.System Help Requirements24
5.5.Performance Requirements25
5.6.Scalability Requirements25
5.6.1.User Scalability26
5.6.2.Application Scalability26

6.Interface Requirements26

6.1.User Interface Requirements26
6.2.System Interface Requirements26

7.Business Glossary26

APMS Update27

Revision Log27




1 Document Purpose

The purpose of this document is to describe business requirements of an Application completely, accurately and unambiguously in Technology-independent manner. All attempts have been made in using mostly business terminology and business language while describing the requirements in this document. Very minimal and commonly understood Technical terminology is used. Use case / Designer approach is used in modeling the business requirements in this document. [Delete the approach that is not applicable.]

2 Intended Audience

The main intended audience for this document are the business owners of the proposed system. This document should be readable by business owners of the proposed system. They must be able to verify that their business requirements have been documented here completely, accurately and unambiguously.

Data Architects, Application Architects and Technical Architects would also find the information in this document useful when they need to design a solution that will address these business requirements.

Since the requirements are documented here in Technology-independent manner, the end-users of the system should be able to comprehend the requirements fairly easily from this document.

Document filling instructions

• This document template contains hidden text. To enable hidden text, under the “Tools | Options | View” tab, make sure that "Hidden Text" is checked. To print the template with hidden text displayed, under the “Tools | Options | Print” tab, make sure...
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Brd Documennt Essay
  • Brd of Erp Essay
  • Brd

Become a StudyMode Member

Sign Up - It's Free