513
edits
Changes
Jump to navigation
Jump to search
mLine 6:
Line 6: − + Line 24:
Line 24: − + Line 45:
Line 45: + + − <b>How to achieve:</b> − * Summarize how the architecture meets the data needs of the users and other key stakeholders including: − * How does the data asset contribute to outcomes/needs of the user and other stakeholders − * Gaps in the existing data assets to meet the needs of the users and other stakeholders and how the architecture addresses these gaps − * Gaps in data collection and analysis and how the architecture is addressing it so that ESDC can ensure that we are serving the members of our society − * Alignment to the data foundation of the ESDC information/data architecture practice − * Alignment to the theoretical foundation of the ESDC information/data architecture practice − − <b>Tools:</b> − * For Data Foundation – Implement: − * Data Catalogue − * Benefits Knowledge hub − * Data Lake (growth) − * Data Science and Machine Platform − * Stakeholder Requirements − * Solution Requirements − − <b>How to achieve:</b> − * Summarize how the architecture aligns to “collect with a purpose” including: − * What is necessary (as opposed to what is sufficient) to meet the stakeholder need − * Supporting Performance Information Profiles (PIPs) used to assess a progress towards target and broader objectives − <b>Tools:</b> − * Value Stream (Value Item and Value Proposition – Context on What we measure) − * KPI Linked to benefits outcomes and objectives − − <b>How to achieve:</b> − * Summarize reusability of the architecture’s data assets given: − * Context of data assets and user and stakeholder needs − * Data quality and fit for purpose − * Privacy and Security Regulatory Framework − <b>Tools:</b> − * Legislative / Regulations − − <b>How to achieve:</b> − * Summarize how the architecture meets the data quality requirements of third-party sources: − * Data quality meets fit for purpose − * Data quality dimensions including: − * Relevance, − * Timeliness − * Consistency, − * Reliability, − * Interpretability, − * Usability − * Data quality mechanism − <b>Tools:</b> − * Data Foundation – Implement (Leverage the standard definition) − * Data Catalogue − * Benefits Knowledge hub − * Data Lake (growth) − * Data Science and Machine Platform − <b>How to achieve:</b> − * Summarize how the architecture assists in defining key data management roles and their responsibilities to ensure data is correct, consistent, and complete including: − * Identifies the data steward responsibilities; − * Identifies the data consumer responsibilities, and; − * Identifies the data custodian responsibilities. − <b>Tools:</b> − * Stakeholders − * Business Process Model − * Functional Requirements − * Business Glossary − − <b>How to achieve:</b> − * Summarize how the architecture’s data assets demonstrate alignment with department's data governance and strategy including: − * Alignment to the data foundation of the ESDC information/data architecture practice − * Alignment to the theoretical foundation of the ESDC information/data architecture practice − <b>Tools:</b> − * Target state (solution data elements) − * Data Foundation – Implement (Leverage the standard definition) − * Data Catalogue − * Benefits Knowledge hub − * Data Lake (growth) − * Data Science and Machine Platform − * Theoretical Foundation − * EDRM (Conceptual and Logical) − * Business Glossary − * Departmental Data Strategy − − <b>How to achieve:</b> − * Summarize for each key data assets: − * Retention and disposition schedules − * Disposition process − <b>Tools:</b> − * Target state (solution data elements) − * Non Functional Requirements − * IM Best Practices and Standards − − <b>How to achieve:</b> − * Summarize how the architecture enables interoperability, reuse and sharing to the greatest extent possible within and across departments − * Summarize how the architecture avoids data duplication − <b>Tools:</b> − * Target State − * Data Foundation – Implement (Leverage the standard definition) − * Data Catalogue − * Benefits Knowledge hub − * Data Lake (growth) − − <b>How to achieve:</b> − * Summarize the alignment to departmental/GC: − * Data taxonomy structure − * Data classification structure − <b>Tools:</b> − * Data Foundation – Implement (Leverage the standard definition) − * Data Catalogue − * Theoretical Foundation − * EDRM (Conceptual and Logical) − * Business Glossary Line 185:
Line 81: + + Line 209:
Line 107: + + Line 231:
Line 131: + +
GC Enterprise Architecture/Framework (view source)
Revision as of 12:14, 24 February 2021
, 12:14, 24 February 2021no edit summary
Version: 1.34
Version: 1.34
February 16, 2021
February 24, 2021
Office of the Chief Information Officer of Canada, Treasury Board of Canada Secretariat, Government of Canada
Office of the Chief Information Officer of Canada, Treasury Board of Canada Secretariat, Government of Canada
== Business architecture ==
== Business architecture ==
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b>
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b></br></br>
Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus.
Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus.
== Information architecture ==
== Information architecture ==
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b></br></br>
Information architecture includes both structured and unstructured data. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data and information as the collection, use, sharing (disclosure), and management of personal information must respect the requirements of the ''Privacy Act'' and its related policies.
Information architecture includes both structured and unstructured data. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data and information as the collection, use, sharing (disclosure), and management of personal information must respect the requirements of the ''Privacy Act'' and its related policies.
=== Collect data to address the needs of the users and other stakeholders ===
=== Collect data to address the needs of the users and other stakeholders ===
* assess data requirements‑based program objectives, as well users, business and stakeholder needs
* assess data requirements‑based program objectives, as well users, business and stakeholder needs
* collect only the minimum set of data needed to support a policy, program, or service
* collect only the minimum set of data needed to support a policy, program, or service
* reuse existing data assets where permissible and only acquire new data if required
* reuse existing data assets where permissible and only acquire new data if required
* ensure data collected, including from third-party sources, are of high quality
* ensure data collected, including from third-party sources, are of high quality
=== Manage and reuse data strategically and responsibly ===
=== Manage and reuse data strategically and responsibly ===
* define and establish clear roles, responsibilities, and accountabilities for data management
* define and establish clear roles, responsibilities, and accountabilities for data management
* identify and document the lineage of data assets
* identify and document the lineage of data assets
* define retention and disposition schedules in accordance with business value as well as applicable privacy and security policy and legislation
* define retention and disposition schedules in accordance with business value as well as applicable privacy and security policy and legislation
* ensure data are managed to enable interoperability, reuse and sharing to the greatest extent possible within and across departments in government to avoid duplication and maximize utility, while respecting security and privacy requirements
* ensure data are managed to enable interoperability, reuse and sharing to the greatest extent possible within and across departments in government to avoid duplication and maximize utility, while respecting security and privacy requirements
* contribute to and align with enterprise and international data taxonomy and classification structures to manage, store, search and retrieve data
* contribute to and align with enterprise and international data taxonomy and classification structures to manage, store, search and retrieve data
=== Use and share data openly in an ethical and secure manner ===
=== Use and share data openly in an ethical and secure manner ===
== Application architecture ==
== Application architecture ==
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide click here for Application Architecture guide] </i></b></br></br>
Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that oriented around business services and based on re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases.
Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that oriented around business services and based on re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases.
== Technology architecture ==
== Technology architecture ==
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/TechnologyGuide click here for Technology Architecture guide] </i></b></br></br>
Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages.
Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages.
== Security architecture ==
== Security architecture ==
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/SecurityGuide click here for Security Architecture guide] </i></b></br></br>
The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed.
The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed.
