Difference between revisions of "GC Enterprise Architecture"
Jana.jessome (talk | contribs) |
|||
| (65 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | < | + | {{OCIO GCEA Header}} |
| + | <multilang> | ||
| + | @en| | ||
| + | == Definition == | ||
| + | Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, and security domains to support strategic outcomes. | ||
| − | + | == Mandate == | |
| − | + | The ''<u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32603 Policy on Service and Digital]</u>'' and supporting instruments serve as an integrated set of rules that articulate how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. Other requirements, including but not limited to, requirements for privacy, official languages and accessibility, also apply to the management of service delivery, information and data, information management and cyber security. Those policies, set out in Section 8, must be applied in conjunction with the Policy on Service and Digital. The Policy on Service and Digital focuses on the client, ensuring proactive consideration at the design stage of key requirements of these functions in the development of operations and services. It establishes an enterprise-wide, integrated approach to governance, planning and management. Overall, the Policy on Service and Digital advances the delivery of services and the effectiveness of government operations through the strategic management of government information and data and leveraging of information technology, supporting the mandate of the Minister for Digital Government in leading the Government of Canada’s digital transition. The management of these functions is guided by a commitment to the guiding principles and best practices of the Government of Canada Digital Standards: design with users; iterate and improve frequently; work in the open by default; use open standards and solutions; address security and privacy risks; build in accessible from the start; empower staff to deliver better services; be good data stewards; design ethical services; collaborate widely. | |
| − | |||
| − | |||
| − | + | Section 4.1.2.3 of the ''Policy on Service and Digital''. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to '''enterprise architecture'''. | |
| − | + | Section 4.1.2.4 of the ''Policy on Service and Digital''. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an '''enterprise architecture''' review board that is mandated to '''define current and target architecture standards''' for the Government of Canada and review departmental proposals for '''alignment'''. | |
| − | + | The Directive on Service and Digital articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. | |
| − | + | Section 4.1.1.1 of the ''<u>[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601 Directive on Service and Digital]</u>''. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental '''architecture''' review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with '''enterprise architectures.''' | |
| − | + | @fr| | |
| − | + | To be translated | |
| − | + | </multilang> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 12:45, 7 September 2021
Definition[edit | edit source]
Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, and security domains to support strategic outcomes.
Mandate[edit | edit source]
The Policy on Service and Digital and supporting instruments serve as an integrated set of rules that articulate how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era. Other requirements, including but not limited to, requirements for privacy, official languages and accessibility, also apply to the management of service delivery, information and data, information management and cyber security. Those policies, set out in Section 8, must be applied in conjunction with the Policy on Service and Digital. The Policy on Service and Digital focuses on the client, ensuring proactive consideration at the design stage of key requirements of these functions in the development of operations and services. It establishes an enterprise-wide, integrated approach to governance, planning and management. Overall, the Policy on Service and Digital advances the delivery of services and the effectiveness of government operations through the strategic management of government information and data and leveraging of information technology, supporting the mandate of the Minister for Digital Government in leading the Government of Canada’s digital transition. The management of these functions is guided by a commitment to the guiding principles and best practices of the Government of Canada Digital Standards: design with users; iterate and improve frequently; work in the open by default; use open standards and solutions; address security and privacy risks; build in accessible from the start; empower staff to deliver better services; be good data stewards; design ethical services; collaborate widely.
Section 4.1.2.3 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Prescribing expectations with regard to enterprise architecture.
Section 4.1.2.4 of the Policy on Service and Digital. The Chief Information Officer (CIO) of Canada is responsible for: Establishing and chairing an enterprise architecture review board that is mandated to define current and target architecture standards for the Government of Canada and review departmental proposals for alignment.
The Directive on Service and Digital articulates how Government of Canada organizations manage service delivery, information and data, information technology, and cyber security in the digital era.
Section 4.1.1.1 of the Directive on Service and Digital. The departmental Chief Information Officer (CIO) is responsible for: Chairing a departmental architecture review board that is mandated to review and approve the architecture of all departmental digital initiatives and ensure their alignment with enterprise architectures.
