[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-256811-105":53,"doc-detail-256811-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","ops-enterprise-architecture-artefacts-appendix-b-corporate-enterprise-architecture-review-requirements-guidebook-version-17","OPS Enterprise Architecture Artefacts - Appendix B - Corporate Enterprise Architecture Review Requirements Guidebook - Version 1.7","","Appendix B of the Government of Ontario IT Standard (GO-ITS) No. 56 sets out approved requirements for conducting a Corporate Enterprise Architecture Review within OPS. It defines what enterprise architecture artefact types must be prepared and reviewed across multiple layers, from contextual and conceptual models to logical and physical artefacts. The guidebook includes detailed coverage of resource, program, service, information and semantic models, governance, business scenarios, functional requirements, application design, deployment, and database inventory, with navigation to supporting artefact templates and internal-access guidance.",{"@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/ops-enterprise-architecture-artefacts-appendix-b-corporate-enterprise-architecture-review-requirements-guidebook-version-17/256811/",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/ops-enterprise-architecture-artefacts-appendix-b-corporate-enterprise-architecture-review-requirements-guidebook-version-17/256811.png","ImageObject",442,249,{"name":88,"@type":89},"Riley West","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-11-01","2026-09-13",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",24,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of OPS Enterprise Architecture Artefacts Appendix B?","Question",{"text":109,"@type":110},"It provides the requirements guidebook for a Corporate Enterprise Architecture Review under GO-ITS OPS, specifying what artefacts must be addressed across architecture layers.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Which architecture layers and artefact categories are covered?",{"text":114,"@type":110},"The guidebook structures requirements into Contextual, Conceptual, Logical, and Physical rows, including models and specifications such as data models, governance, business scenarios, functional requirements, and application/deployment artefacts.",{"name":116,"@type":107,"acceptedAnswer":117},"Are the included hyperlinks accessible outside the OPS intranet?",{"text":118,"@type":110},"Hyperlinks intended for OPS intranet artefact templates and examples may not work externally; external accessibility is handled by separate template files referenced in other appendices.","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},256811,1791731206,{"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},1099523885074,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Government of Ontario IT Standard (GO-ITS)  \nNumber 56  \nOPS Enterprise Architecture Artefacts  \nAppendix B – Corporate Enterprise Architecture Review Requirements Guidebook  \nVersion 1.7  \nStatus: Approved  \nNote:  \n􀁸 This appendix contains hyperlinks that are intended for use on the OPS intranet only. In particular, hyperlinks that point to artefact templates and examples will not work outside the OPS intranet.  \n􀁸 However, for external accessibility, the artefact templates have been included as separate files in Appendix D – Artefact Template Files.  \n􀁸 See Appendix C – Corporate Enterprise Architecture Artefact Template Information for more information and instructions on how to access the included template files.  \nTable of Contents  \nRow 1: Contextual........................................................................... 5  \nResource Type ................................................................................ 5  \nLine of Business Profile..................................................................... 7  \nProgram ......................................................................................... 8  \nService .......................................................................................... 9  \nProgram Profile .............................................................................. 10  \nLocation Type ................................................................................ 11  \nGeographic Area Type ..................................................................... 12  \nParty Type ..................................................................................... 13  \nRole Type ...................................................................................... 13  \nTarget Group Type ......................................................................... 14  \nEvent Type .................................................................................... 15  \nCycle Type..................................................................................... 16  \nNeed............................................................................................. 17  \nGoal ............................................................................................. 17  \nMandate ........................................................................................ 18  \nTarget Group / Needs Cross Reference .............................................. 19  \nRow 2: Conceptual ........................................................................ 21  \nInformation Model ..........................................................................21  \nConceptual Data Model....................................................................22  \nConceptual Data Model (Acquired Solution) .......................................24  \nInterface Data Requirements Document ............................................25  \nSemantic Model..............................................................................26  \nFact and Dimension Matrix ..............................................................29  \nService Life Cycle ...........................................................................31  \nBusiness Function Model..................................................................32  \nService Integration Accountability Model ...........................................34  \nService Profile ................................................................................36  \nBusiness Process Model ...................................................................38  \nSOA Service Specification ................................................................40  \nBusiness Network Model ..................................................................41  \nGovernance Model ..........................................................................42  \nOrganization Chart .........................................................................44  \nBusiness Scenario............................","cbCaihIdmEtj3Pu7","https://ap.wps.com/l/cbCaihIdmEtj3Pu7","pdf",1004854,94,"English","# Contextual\n## Resource Type\n## Line of Business Profile\n## Program\n## Service\n## Program Profile\n## Location Type\n## Geographic Area Type\n## Party Type\n## Role Type\n## Target Group Type\n## Event Type\n## Cycle Type\n## Need\n## Goal\n## Mandate\n## Target Group / Needs Cross Reference\n# Conceptual\n## Information Model\n## Conceptual Data Model\n## Interface Data Requirements Document\n## Semantic Model\n## Fact and Dimension Matrix\n## Service Life Cycle\n## Business Function Model\n## Governance Model\n## Organization Chart\n## Business Scenario\n## State Transition Diagram\n## Service Objectives\n# Logical\n## Logical Data Model\n## System Functional Requirements\n## System Architecture Document\n## Logical Application Design Document\n## Solution Pattern Match\n## Logical Application Deployment Model\n## Supplementary Specification\n# Physical\n## Physical Data Model\n## Database Inventory\n## Physical Dimensional Model\n## Physical Application Design Document","[{\"question\":\"What is the purpose of OPS Enterprise Architecture Artefacts Appendix B?\",\"answer\":\"It provides the requirements guidebook for a Corporate Enterprise Architecture Review under GO-ITS OPS, specifying what artefacts must be addressed across architecture layers.\"},{\"question\":\"Which architecture layers and artefact categories are covered?\",\"answer\":\"The guidebook structures requirements into Contextual, Conceptual, Logical, and Physical rows, including models and specifications such as data models, governance, business scenarios, functional requirements, and application/deployment artefacts.\"},{\"question\":\"Are the included hyperlinks accessible outside the OPS intranet?\",\"answer\":\"Hyperlinks intended for OPS intranet artefact templates and examples may not work externally; external accessibility is handled by separate template files referenced in other appendices.\"}]","OPS Enterprise Architecture Artefacts - Appendix B - Corporate Enterprise Architecture Review Requirements Guidebook - Version 1.7 | PDF",1789307728,33]