[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-174811-105":53,"doc-detail-174811-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","business-requirements-document-brd-template-table-of-contents-complete","Business Requirements Document (BRD) Template - Table of Contents - Complete","","Business Requirements Document (BRD) Template provides a structured way to document application business requirements in a technology-independent format. It defines the project’s purpose, intended audience, background, and the goals, benefits, stakeholders, dependencies, references, and assumptions that shape the requirement set. The template then organizes requirements scope (in/out), functional requirements with actor profiles, use case diagrams/specifications, functional hierarchy, function definition reports, and business rules. It further covers data requirements including architecture, diagrams, volumes, conversion, retention/archiving, privacy implications, and definition reports, plus non-functional requirements such as security, availability, usability, system help, performance, scalability, and interface requirements. It concludes with a business glossary and sections for updates, revision history, appendices, and approval.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/business-requirements-document-brd-template-table-of-contents-complete/174811/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/business-requirements-document-brd-template-table-of-contents-complete/174811.png","ImageObject",442,249,{"name":88,"@type":89},"Gelato","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/octet-stream","2026-10-25","2026-09-02",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",23,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the main purpose of the BRD template?","Question",{"text":109,"@type":110},"To describe application business requirements completely, accurately, and unambiguously in a technology-independent manner using mostly business terminology.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Which sections define functional requirements in the template?",{"text":114,"@type":110},"Functional requirements are organized around actor profiles, essential use case diagram and specifications, function hierarchy diagram, function definition report, and business rules.",{"name":116,"@type":107,"acceptedAnswer":117},"How does the template handle non-functional requirements?",{"text":118,"@type":110},"Non-functional requirements include security, availability, usability, system help, performance, scalability, and interface requirements, with sub-sections for specific areas like authentication and access controls.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},174811,1791433772,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":142},19241457091524,"https://us-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","\u0013 DOCPROPERTY \"Company\"  \\* MERGEFORMAT \u0014Ministry/Agency Name\u0015\n[Complete file/properties to populate fields on this page and in the document headers]\n\u0013 SUBJECT  \\* MERGEFORMAT \u0014Project Name\u0015\nProject #:\nBusiness Requirements Document (BRD) Template\nPrepared by:\t\u0013 AUTHOR  \\* MERGEFORMAT \u0014Author's Name\u0015\nPrepared for:\nDate Submitted:\t[Date]\nProject Sponsor:\t\u0013 DOCPROPERTY \"Manager\"  \\* MERGEFORMAT \u0014Project Sponsor's Name\u0015\nClient Acceptor:\nProject Manager:\nDocument Number:\t6450-20/Project Number /BRD\nSecurity Classification: Low\nVersion:\t0.1\nLast Updated:\tApril 26, 2013\nCreation Date:\tJune 06, 2006\nTable of Contents\n\u0013 TOC \\o \"1-3\" \\h \\z \\u \u0014\u0013 HYPERLINK \\l \"_Toc361052586\" \u0014Table of Contents\t\u0013 PAGEREF _Toc361052586 \\h \u00142\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052587\" \u00141.\tIntroduction\t\u0013 PAGEREF _Toc361052587 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052588\" \u00141.1.\tDocument Purpose\t\u0013 PAGEREF _Toc361052588 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052589\" \u00141.2.\tIntended Audience\t\u0013 PAGEREF _Toc361052589 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052590\" \u00141.3.\tProject Background\t\u0013 PAGEREF _Toc361052590 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052591\" \u00141.4.\tPurpose of the Business Requirements\t\u0013 PAGEREF _Toc361052591 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052592\" \u00141.5.\tBusiness Goals/Objectives to be achieved\t\u0013 PAGEREF _Toc361052592 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052593\" \u00141.6.\tBenefits/Rationale\t\u0013 PAGEREF _Toc361052593 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052594\" \u00141.7.\tStakeholders\t\u0013 PAGEREF _Toc361052594 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052595\" \u00141.8.\tDependencies on existing systems\t\u0013 PAGEREF _Toc361052595 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052596\" \u00141.9.\tReferences\t\u0013 PAGEREF _Toc361052596 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052597\" \u00141.10.\tAssumptions\t\u0013 PAGEREF _Toc361052597 \\h \u00146\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052598\" \u00142.\tRequirements Scope\t\u0013 PAGEREF _Toc361052598 \\h \u00147\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052599\" \u00142.1.\tIn Scope\t\u0013 PAGEREF _Toc361052599 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052600\" \u00142.2.\tOut of Scope\t\u0013 PAGEREF _Toc361052600 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052601\" \u00143.\tFunctional Requirements\t\u0013 PAGEREF _Toc361052601 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052602\" \u00143.1.\tActor Profiles Specification\t\u0013 PAGEREF _Toc361052602 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052603\" \u00143.2.\tEssential Use Case Diagram\t\u0013 PAGEREF _Toc361052603 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052604\" \u00143.3.\tEssential Use Case Specifications\t\u0013 PAGEREF _Toc361052604 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052605\" \u00143.4.\tFunction Hierarchy Diagram\t\u0013 PAGEREF _Toc361052605 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052606\" \u00143.5.\tFunction Definition Report\t\u0013 PAGEREF _Toc361052606 \\h \u001411\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052607\" \u00143.6.\tBusiness Rules\t\u0013 PAGEREF _Toc361052607 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052608\" \u00144.\tData Requirements\t\u0013 PAGEREF _Toc361052608 \\h \u001413\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052609\" \u00144.1.\tData Architecture\t\u0013 PAGEREF _Toc361052609 \\h \u001413\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052610\" \u00144.1.1.\tDomain Class Diagram\t\u0013 PAGEREF _Toc361052610 \\h \u001413\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052611\" \u00144.1.2.\tEntity Relationship Diagram\t\u0013 PAGEREF _Toc361052611 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052612\" \u00144.2.\tData Volumes\t\u0013 PAGEREF _Toc361052612 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052613\" \u00144.3.\tData Conversion\t\u0013 PAGEREF _Toc361052613 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052614\" \u00144.4.\tData Retention and Archiving\t\u0013 PAGEREF _Toc361052614 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052615\" \u00144.5.\tFOI/Privacy Implications\t\u0013 PAGEREF _Toc361052615 \\h \u001414\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052616\" \u00144.6.\tData Definition Reports\t\u0013 PAGEREF _Toc361052616 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052617\" \u00144.6.1.\tDomain Class Definition Report\t\u0013 PAGEREF _Toc361052617 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052618\" \u00144.6.2.\tEntity Definition Report\t\u0013 PAGEREF _Toc361052618 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052619\" \u00145.\tNon-Functional requirements\t\u0013 PAGEREF _Toc361052619 \\h \u001417\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052620\" \u00145.1.\tSecurity Requirements\t\u0013 PAGEREF _Toc361052620 \\h \u001417\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052621\" \u00145.1.1.\tAuthentication\t\u0013 PAGEREF _Toc361052621 \\h \u001417\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc361052622\" \u00145.1.2.\tAuthorization and Access Controls","cbCaiaDgslcIV4tJ","https://ap.wps.com/l/cbCaiaDgslcIV4tJ","doc",422400,25,"English","# Table of Contents\n# 1. Introduction\n## 1.1. Document Purpose\n## 1.2. Intended Audience\n## 1.3. Project Background\n## 1.4. Purpose of the Business Requirements\n## 1.5. Business Goals/Objectives to be achieved\n## 1.6. Benefits/Rationale\n## 1.7. Stakeholders\n## 1.8. Dependencies on existing systems\n## 1.9. References\n## 1.10. Assumptions\n# 2. Requirements Scope\n## 2.1. In Scope\n## 2.2. Out of Scope\n# 3. Functional Requirements\n## 3.1. Actor Profiles Specification\n## 3.2. Essential Use Case Diagram\n## 3.3. Essential Use Case Specifications\n## 3.4. Function Hierarchy Diagram\n## 3.5. Function Definition Report\n## 3.6. Business Rules\n# 4. Data Requirements\n## 4.1. Data Architecture\n## 4.2. Data Volumes\n## 4.3. Data Conversion\n## 4.4. Data Retention and Archiving\n## 4.5. FOI/Privacy Implications\n## 4.6. Data Definition Reports\n# 5. Non-Functional requirements\n## 5.1. Security Requirements\n## 5.2. Availability Requirements\n## 5.3. Usability Requirements\n## 5.4. System Help Requirements\n## 5.5. Performance Requirements\n## 5.6. Scalability Requirements\n# 6. Interface Requirements\n## 6.1. User Interface Requirements\n## 6.2. System Interface Requirements\n# Business Glossary\n# APMS Update\n# Revision Log\n# Appendices\n# Approval","[{\"question\":\"What is the main purpose of the BRD template?\",\"answer\":\"To describe application business requirements completely, accurately, and unambiguously in a technology-independent manner using mostly business terminology.\"},{\"question\":\"Which sections define functional requirements in the template?\",\"answer\":\"Functional requirements are organized around actor profiles, essential use case diagram and specifications, function hierarchy diagram, function definition report, and business rules.\"},{\"question\":\"How does the template handle non-functional requirements?\",\"answer\":\"Non-functional requirements include security, availability, usability, system help, performance, scalability, and interface requirements, with sub-sections for specific areas like authentication and access controls.\"}]","Business Requirements Document (BRD) Template - Table of Contents - Complete | DOC",1788316675,9]