Changes

Line 194: Line 194:  
{| class="wikitable"
 
{| class="wikitable"
 
|'''Design services digitally from end‑to‑end to meet  the Government of Canada users and other stakeholders’ needs'''
 
|'''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
+
|
 
+
* 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
+
* 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''
§  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)
 
  −
§  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'''
 
|'''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
+
|
 
+
* 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
+
* 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
§  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'''
 
|'''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
+
|
 
+
* 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
+
* 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
§  publish in  the open all reusable common business capabilities, processes and enterprise  solutions for others to develop and leverage cohesive horizontal enterprise  services
   
|}
 
|}
   Line 221: Line 217:  
{| class="wikitable"
 
{| class="wikitable"
 
|'''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
 
+
* contribute  to and align with enterprise and international data taxonomy and  classification structures to manage, store, search and retrieve data
§  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'''
 
|'''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
+
|
 
+
* 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 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
§  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'''
 
|'''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
+
|
 
+
* 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  
+
* 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
§  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''
§  notify individuals  of the purpose for collection at the point of collection by including a  privacy notice
+
* 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
§  personal  information should be, wherever possible, collected directly from individuals  but can be from other sources where permitted by the ''Privacy Act''
+
* 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
§  personal  information must be available to facilitate Canadians’ right of access to and  correction of government records
+
* 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
§  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
   
|}
 
|}
   Line 274: Line 256:  
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.
 
{| class="wikitable"
 
{| class="wikitable"
|'''Use  open source solutions hosted in public cloud'''
+
|'''Use  open source solutions'''
|§  select  existing solutions that can be reused over custom built
+
'''hosted in public cloud'''
 
+
|
§  contribute  all improvements back to the communities
+
* 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
+
* register  open source software to the Open Resource Exchange
 
|-
 
|-
|'''Use  software as a service (SaaS) hosted in public cloud'''
+
|'''Use  software as a service (SaaS)'''
|§  choose SaaS  that best fit for purpose based on alignment with SaaS capabilities
+
'''hosted in public cloud'''
 
+
|
§  choose a  SaaS solution that is extendable
+
* 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
+
* configure  SaaS and if customization is necessary extend as open source modules
 
|-
 
|-
 
|'''Design  for Interoperability'''
 
|'''Design  for Interoperability'''
|§  design systems  as highly modular and loosely coupled services
+
|
 
+
* design systems  as highly modular and loosely coupled services
§  expose services,  including existing ones, through APIs
+
* expose services,  including existing ones, through APIs
 
+
* make the  APIs discoverable to the appropriate stakeholders
§  make the  APIs discoverable to the appropriate stakeholders
   
|}
 
|}
   Line 300: Line 281:  
{| class="wikitable"
 
{| class="wikitable"
 
|'''Use  cloud first'''
 
|'''Use  cloud first'''
|§  adopt the  use of the GC Accelerators to ensure proper security and access controls
+
|
 
+
* 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)
+
* 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
§  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
§  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'''
 
|'''Design  for performance, availability and scalability'''
|§  ensure response  times meet user needs, and critical services are highly available
+
|
 
+
* ensure response  times meet user needs, and critical services are highly available
§  support zero‑downtime  deployments for planned and unplanned maintenance
+
* 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
§  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
§  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'''
 
|'''Follow  DevSecOps principles'''
|§  use continuous  integration and continuous deployments
+
|
 
+
* use continuous  integration and continuous deployments
§  ensure automated  testing occurs for security and functionality
+
* 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
§  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
   
|}
 
|}