[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-161754-105":53,"doc-detail-161754-en":126},{"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":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","businessit-requirements-document-introduction-template","Business/IT Requirements Document - Introduction - Template","","Business/IT requirements document template for capturing elicited business needs from key stakeholders in a structured, reviewable format. Defines purpose, objectives, scope, and supporting elements including definitions, risks, assumptions, issues, and dependencies. Describes required process artifacts such as context and process overview diagrams, and outlines how to present high-level “to-be” business requirements and detailed business/IT requirements for functional and non-functional coverage. Supports shared understanding, functional specification preparation, and solution identification for designated approvers.",{"@graph":63,"@context":118},[64,80,101],{"@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":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/businessit-requirements-document-introduction-template/161754/",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/businessit-requirements-document-introduction-template/161754.png","ImageObject",442,249,{"name":88,"@type":89},"Jordan Avery","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-09-20","2026-08-30",true,{"@type":98,"interactionType":99,"userInteractionCount":47},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of a Business/IT Requirements Document?","Question",{"text":108,"@type":109},"It captures business requirements in a structured way based on inputs from key stakeholders, enabling review and sign off by designated approvers. It also provides the basis for functional requirements specification preparation.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What sections should be included to explain requirements completeness and context?",{"text":113,"@type":109},"Include objectives, scope, definitions/acronyms, and also risks, assumptions, issues, and dependencies. Add process context such as a context diagram and a process overview diagram.",{"name":115,"@type":106,"acceptedAnswer":116},"How should the “As Is” and “To Be” requirements be documented?",{"text":117,"@type":109},"Describe the current As Is process at a high level and reference related documents if already documented. Then provide high-level To Be business requirements and detailed business/IT requirements, including functional, process, and non-functional items.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},161754,1788109004,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":47,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":125,"read_time":47},1099523882367,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","BUSINESS/IT\nREQUIREMENTS DOCUMENT\n\u003CProject Name:>\n\u003CProject Reference:>\n\u000fDOCUMENT CONTROL\n\u003CBlue italic text is included to provide guidance to the author and should be deleted before publishing>\nContacts\n\u003CContacts that would be useful to provide for business information>\nDocument Approval\n\u003CEnter details of all stakeholders who will be subject to approval of this document>\nDocument Distribution\n\u003CEnter details of all stakeholders who will be subject to receipt of this document for reference purposes>\nRevision History\n\u003CInitially a document will be numbered 0.1 to 0.9 until it becomes the first issue for approval at which point the document is numbered 1.0. For future updates the document will be numbered using decimals to 1 place until it adopts the next whole number for issue>\nRelated Documents\n\u003CList any significant documents that precede and relate to the project>\n\u003CNot all of the following sections may be applicable to the work being performed. If so, the preference would be to keep the section heading, but make a note such as “This section is not applicable for this process” and provide an explanation for the reasons why>\nTable of Contents\n\u0013 TOC \\o \"1-3\" \\h \\z \\u \u0014\u0013 HYPERLINK \\l \"_Toc359583147\" \u00141\tIntroduction\t\u0013 PAGEREF _Toc359583147 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583148\" \u00142\tProblem/Impact/Successful Outcome\t\u0013 PAGEREF _Toc359583148 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583149\" \u00143\tObjectives\t\u0013 PAGEREF _Toc359583149 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583150\" \u00144\tPurpose Of Document\t\u0013 PAGEREF _Toc359583150 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583151\" \u00145\tScope\t\u0013 PAGEREF _Toc359583151 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583152\" \u00146\tDefinitions, Acronyms and Abbreviations\t\u0013 PAGEREF _Toc359583152 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583153\" \u00147\tRisks\t\u0013 PAGEREF _Toc359583153 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583154\" \u00148\tAssumptions\t\u0013 PAGEREF _Toc359583154 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583155\" \u00149\tIssues\t\u0013 PAGEREF _Toc359583155 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583156\" \u001410\tDependencies\t\u0013 PAGEREF _Toc359583156 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583157\" \u001411\tAs Is Process\t\u0013 PAGEREF _Toc359583157 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583158\" \u001412\tContext Diagram\t\u0013 PAGEREF _Toc359583158 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583159\" \u001413\tProcess Overview Diagram\t\u0013 PAGEREF _Toc359583159 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583160\" \u001414\tHigh Level To Be Business Requirements\t\u0013 PAGEREF _Toc359583160 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583161\" \u001415\tDetailed Business/IT Requirements\t\u0013 PAGEREF _Toc359583161 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583162\" \u001415.1\tFunctional Requirements\t\u0013 PAGEREF _Toc359583162 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583163\" \u001415.2\tProcess Diagram\t\u0013 PAGEREF _Toc359583163 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583164\" \u001415.3\tNon Functional Requirements\t\u0013 PAGEREF _Toc359583164 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583165\" \u001416\tCosts\t\u0013 PAGEREF _Toc359583165 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc359583166\" \u001417\tAppendices\t\u0013 PAGEREF _Toc359583166 \\h \u00143\u0015\u0015\n\u0015\nIntroduction\n\u003CThis should be a high level introduction and background to the Project>\nProblem/Impact/Successful Outcome\nObjectives\n\u003CState the objectives to be met by the business solution. The ID number will take the form of Oxx where xx = a consecutive number per entry>\nPurpose Of Document\nThe Business Requirements Specification details the business requirements as elicited by the business analyst from the key stakeholders. The document presents the requirements in a structured way that facilitates review and sign off by the designated approvers.\nBuilding on the high level scope of the project as defined in the Project Definition Document, the business requirements clearly state in business language what any chosen solution must do.\nThis document captures the business requirements in a structured way, providing the basis for ensuring that the solution delivered meets the requirements.\nIt should:-\nFacilitate a shared understanding for all stakeholders of the business requirements\nBe the key input for the preparation of a functional requirements specification\nFacilitate the identification","cbCail5ZS0YkczyI","https://ap.wps.com/l/cbCail5ZS0YkczyI","docx",87166,13,"English","# Introduction\n# Problem/Impact/Successful Outcome\n# Objectives\n# Purpose Of Document\n# Scope\n# Definitions, Acronyms and Abbreviations\n# Risks\n# Assumptions\n# Issues\n# Dependencies\n# As Is Process\n# Context Diagram\n# Process Overview Diagram\n# High Level To Be Business Requirements\n# Detailed Business/IT Requirements\n## Functional Requirements\n## Process Diagram\n## Non Functional Requirements\n# Costs\n# Appendices","[{\"question\":\"What is the purpose of a Business/IT Requirements Document?\",\"answer\":\"It captures business requirements in a structured way based on inputs from key stakeholders, enabling review and sign off by designated approvers. It also provides the basis for functional requirements specification preparation.\"},{\"question\":\"What sections should be included to explain requirements completeness and context?\",\"answer\":\"Include objectives, scope, definitions/acronyms, and also risks, assumptions, issues, and dependencies. Add process context such as a context diagram and a process overview diagram.\"},{\"question\":\"How should the “As Is” and “To Be” requirements be documented?\",\"answer\":\"Describe the current As Is process at a high level and reference related documents if already documented. Then provide high-level To Be business requirements and detailed business/IT requirements, including functional, process, and non-functional items.\"}]","Business/IT Requirements Document - Introduction - Template | DOCX"]