Changes

Jump to navigation Jump to search

GC Service & Digital Target Enterprise Architecture (view source)

Revision as of 13:24, 22 December 2020

13,740 bytes added ,  13:24, 22 December 2020
→‎Realization practices and principles
Line 186: Line 186:     
The Government of Canada Enterprise Architecture Framework defined below presents the evaluation criteria being used by GC Enterprise Architecture Review Board to align solutions to the Service and Digital Target Enterprise Architecture. In the interest of effective communication to the architecture community of practice, the material has been organized based on the architectural domains business, information, application, technology, and security.
 
The Government of Canada Enterprise Architecture Framework defined below presents the evaluation criteria being used by GC Enterprise Architecture Review Board to align solutions to the Service and Digital Target Enterprise Architecture. In the interest of effective communication to the architecture community of practice, the material has been organized based on the architectural domains business, information, application, technology, and security.
 +
 +
=== Enterprise architecture framework ===
 +
The enterprise architecture framework is the criteria used by the Government of Canada enterprise architecture review board and departmental architecture review boards when reviewing digital initiatives to ensure their alignment with enterprise architectures across business, information, application, technology and security domains to support strategic outcomes.
 +
 +
==== Business architecture ====
 +
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.
 +
{| class="wikitable"
 +
|'''Design services digitally from end‑to‑end to meet  the Government of Canada users and other stakeholders’ needs'''
 +
|§  clearly identify internal and external users  and other stakeholders and their needs for each policy, program and business  service
 +
 +
§  include policy requirement applying to  specific users and other stakeholder groups, such as accessibility, gender-based  plus analysis, and official languages in the creation of the service
 +
 +
§  perform Algorithmic Impact Assessment (AIA)  to support risk mitigation activities when deploying an automated decision  system as per ''Directive on Automated Decision-Making''
 +
 +
§  model end‑to‑end business service delivery to  provide quality, maximize effectiveness and optimize efficiencies across all  channels (for example, lean process)
 +
|-
 +
|'''Architect  to be outcome‑driven and strategically aligned to the department and to the  Government of Canada'''
 +
|§  identify  which departmental/GC business services, outcomes and strategies will be  addressed
 +
 +
§  establish  metrics for identified business outcomes throughout the life cycle of an  investment
 +
 +
§  translate  business outcomes and strategy into business capability implications in the  GC Business Capability Model to establish a common vocabulary between  business, development, and operation
 +
|-
 +
|'''Promote  horizontal enablement of the enterprise'''
 +
|§  identify  opportunities to enable business services horizontally across the GC  enterprise and to provide cohesive experience to users and other stakeholders
 +
 +
§  reuse common  business capabilities, processes and enterprise solutions from across  government and private sector
 +
 +
§  publish in  the open all reusable common business capabilities, processes and enterprise  solutions for others to develop and leverage cohesive horizontal enterprise  services
 +
|}
 +
 +
==== Information architecture ====
 +
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.
 +
{| class="wikitable"
 +
|'''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
 +
 +
§  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
 +
 +
§  ensure data  collected, including from third-party sources, are of high quality
 +
|-
 +
|'''Manage  and reuse data strategically and responsibly'''
 +
|§  define and  establish clear roles, responsibilities, and accountabilities for data  management
 +
 +
§  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
 +
 +
§  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
 +
|-
 +
|'''Use and share data openly in an ethical and  secure manner'''
 +
|§  share data  openly by default as per the ''Directive on Open Government and Digital  Standards'', while respecting security and privacy requirements; data  shared should adhere to existing enterprise and international standards,  including on data quality and ethics
 +
 +
§  ensure data  formatting aligns to existing enterprise and international standards on  interoperability; where none exist, develop data standards in the open with  key subject matter experts
 +
 +
§  ensure that  combined data does not risk identification or re‑identification of sensitive  or personal information
 +
|-
 +
|'''Design  with privacy in mind for the collection, use and management of personal  Information'''
 +
|§  ensure alignment  with guidance from appropriate institutional ATIP Office with respect to  interpretation and application of the ''Privacy  Act'' and related policy instruments
 +
 +
§  assess initiatives  to determine if personal information will be collected, used, disclosed,  retained, shared, and disposed
 +
 +
§  only collect  personal information if it directly relates to the operation of the programs  or activities
 +
 +
§  notify individuals  of the purpose for collection at the point of collection by including a  privacy notice
 +
 +
§  personal  information should be, wherever possible, collected directly from individuals  but can be from other sources where permitted by the ''Privacy Act''
 +
 +
§  personal  information must be available to facilitate Canadians’ right of access to and  correction of government records
 +
 +
§  design  access controls into all processes and across all architectural layers from  the earliest stages of design to limit the use and disclosure of personal  information
 +
 +
§  design  processes so personal information remains accurate, up‑to‑date and as  complete as possible, and can be corrected if required
 +
 +
§  de‑identification  techniques should be considered prior to sharing personal information
 +
 +
§  in collaboration  with appropriate institutional ATIP Office, determine if a Privacy Impact  Assessment (PIA) is required to identify and mitigate privacy risks for new  or substantially modified programs that impact the privacy of individuals
 +
 +
§  establish  procedures to identify and address privacy breaches so they can be reported  quickly and responded to efficiently to appropriate institutional ATIP Office
 +
|}
 +
 +
==== Application architecture ====
 +
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.
 +
{| class="wikitable"
 +
|'''Use  open source solutions hosted in public cloud'''
 +
|§  select  existing solutions that can be reused over custom built
 +
 +
§  contribute  all improvements back to the communities
 +
 +
§  register  open source software to the Open Resource Exchange
 +
|-
 +
|'''Use  software as a service (SaaS) hosted in public cloud'''
 +
|§  choose SaaS  that best fit for purpose based on alignment with SaaS capabilities
 +
 +
§  choose a  SaaS solution that is extendable
 +
 +
§  configure  SaaS and if customization is necessary extend as open source modules
 +
|-
 +
|'''Design  for Interoperability'''
 +
|§  design systems  as highly modular and loosely coupled services
 +
 +
§  expose services,  including existing ones, through APIs
 +
 +
§  make the  APIs discoverable to the appropriate stakeholders
 +
|}
 +
 +
==== Technology architecture ====
 +
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.
 +
{| class="wikitable"
 +
|'''Use  cloud first'''
 +
|§  adopt the  use of the GC Accelerators to ensure proper security and access controls
 +
 +
§  enforce this  order of preference: software as a service  (SaaS) first, then platform as a service (PaaS), and lastly infrastructure as  a service (IaaS)
 +
 +
§  fulfill cloud  services through SSC Cloud‑Brokering Services
 +
 +
§  enforce this  order of preference: public cloud first, then hybrid cloud, then private  cloud, and lastly non‑cloud (on‑premises) solutions
 +
 +
§  design for  cloud mobility and develop an exit strategy to avoid vendor lock‑in
 +
|-
 +
|'''Design  for performance, availability and scalability'''
 +
|§  ensure response  times meet user needs, and critical services are highly available
 +
 +
§  support zero‑downtime  deployments for planned and unplanned maintenance
 +
 +
§  use  distributed architectures, assume failure will happen, handle errors  gracefully, and monitor performance and behaviour actively
 +
 +
§  establish  architectures that supports new technology insertion with minimal disruption  to existing programs and services
 +
 +
§  control technical  diversity; design systems based on modern technologies and platforms already  in use
 +
|-
 +
|'''Follow  DevSecOps principles'''
 +
|§  use continuous  integration and continuous deployments
 +
 +
§  ensure automated  testing occurs for security and functionality
 +
 +
§  include your  users and other stakeholders as part of the DevSecOps process, which refers  to the concept of making software security a core part of the overall  software delivery process
 +
|}
 +
 +
==== Security architecture ====
 +
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.
 +
{| class="wikitable"
 +
|'''Build  security into the system life cycle across all architectural layers'''
 +
|
 +
* identify  and categorize information based on the degree of injury that could be  expected to result from a compromise of its confidentiality, integrity and  availability
 +
* implement  a continuous security approach, in alignment with Centre for Cyber Security’s  IT Security Risk Management Framework; perform threat modelling to minimize  the attack surface by limiting services exposed and information exchanged to  the minimum necessary
 +
* apply  proportionate security measures that address business and user needs while  adequately protecting data at rest and data in transit
 +
* design  systems to be resilient and available in order to support service continuity
 +
|-
 +
|'''Ensure  secure access to systems and services'''
 +
|
 +
* identify  and authenticate individuals, processes or devices to an appropriate level of  assurance, based on clearly defined roles, before granting access to  information and services; leverage enterprise services such as Government of Canada  trusted digital identity solutions that are supported by the Pan‑Canadian  Trust Framework
 +
* constrain  service interfaces to authorized entities (users and devices), with clearly  defined roles; segment and separate information based on sensitivity of information,  in alignment with ITSG‑22 and ITSG‑38. Management interfaces may require  increased levels of protection
 +
* implement  HTTPS for secure web connections and Domain-based Message Authentication,  Reporting and Conformance (DMARC) for enhanced email security
 +
* establish  secure interconnections between systems through secure APIs or leveraging  centrally managed hybrid IT connectivity services
 +
|-
 +
|'''Maintain  secure operations'''
 +
|
 +
* establish  processes to maintain visibility of assets and ensure the prompt application  of security‑related patches and updates in order to reduce exposure to  vulnerabilities, in accordance with GC ''Patch Management Guidance''
 +
* enable event  logging, in accordance with GC ''Event Logging Guidance'', and perform  monitoring of systems and services in order to detect, prevent, and respond  to attacks
 +
* establish an incident management plan in  alignment with the GC Cyber Security Event Management Plan (GC CSEMP) and  report incidents to the Canadian Centre for Cyber Security
 +
|}
Retrieved from "https://wiki.gccollab.ca/Special:MobileDiff/36773"

Navigation menu

GCwiki