Line 103: |
Line 103: |
| | | |
| 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 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. |
− | | + | [[File:Service and Digital information architecture.png|center|thumb|595x595px]] |
− | == ADD image Information architecture ==
| |
| The following layer depicts how services will interoperate through a standard fabric, supported by a set of common API standards specifying protocols and payloads. These services will be published in the API Store to facilitate reuse. APIs will be brokered through an API gateway to manage traffic, ensure version control, and monitor how services are exposed and consumed, either directly, or through a common event broker. Procurement of software as a service (SaaS) offerings will be facilitated through Shared Services Canada’s (SSC’s) Cloud Brokering Service and supported through their managed services. These are services that are available to steward infrastructure that are offered by SSC include database management services, cabling, facility management, transition planning and support, system integration services, and project management, among others. GC business programs and services and their enabling capabilities are built on resources within the application and information landscapes. | | The following layer depicts how services will interoperate through a standard fabric, supported by a set of common API standards specifying protocols and payloads. These services will be published in the API Store to facilitate reuse. APIs will be brokered through an API gateway to manage traffic, ensure version control, and monitor how services are exposed and consumed, either directly, or through a common event broker. Procurement of software as a service (SaaS) offerings will be facilitated through Shared Services Canada’s (SSC’s) Cloud Brokering Service and supported through their managed services. These are services that are available to steward infrastructure that are offered by SSC include database management services, cabling, facility management, transition planning and support, system integration services, and project management, among others. GC business programs and services and their enabling capabilities are built on resources within the application and information landscapes. |
− | | + | [[File:Service and Digital interoperability.png|center|thumb|595x595px]] |
− | == ADD image application architecture and technology architecture ==
| |
| Also highlighted in this layer are automation capabilities such as artificial intelligence and open source solutions listed on an open resource exchange. | | Also highlighted in this layer are automation capabilities such as artificial intelligence and open source solutions listed on an open resource exchange. |
− | | + | [[File:Service and Digital Application architecture and technology architecture.png|center|thumb|595x595px]] |
− | == ADD image application architecture and technology architecture ==
| |
| In the bottom‑most view of the Service and Digital Target Enterprise Architecture, the focus is on the technology infrastructure that acts as the glue to bring everything together: the network. The GC network consists of local area network (LAN), wide area network (WAN), satellite, and internet infrastructure that provides general connectivity for internal government users, as well as secure and networks that support collaboration between the government and scientific communities. These are all connected with network hubs that optimize the performance of the GC network. The core infrastructure includes SSC services that ensure IT continuity (disaster recovery), including performance monitoring and reliability planning. | | In the bottom‑most view of the Service and Digital Target Enterprise Architecture, the focus is on the technology infrastructure that acts as the glue to bring everything together: the network. The GC network consists of local area network (LAN), wide area network (WAN), satellite, and internet infrastructure that provides general connectivity for internal government users, as well as secure and networks that support collaboration between the government and scientific communities. These are all connected with network hubs that optimize the performance of the GC network. The core infrastructure includes SSC services that ensure IT continuity (disaster recovery), including performance monitoring and reliability planning. |
− | | + | [[File:Service and Digital Enterprise Network Conectivity.png|center|thumb|595x595px]] |
− | == Add Image Enterprise Network connectivity ==
| |
| Security is reflected in the Service and Digital Target Enterprise Architecture diagram as a cross‑cutting factor that spans all horizontal layers. The goal is to ensure security at all architectural levels, from design to implementation to operations; and to ensure authentication, authorization, auditing, monitoring, tokenization, and encryption of all data, whether at rest or in motion. | | Security is reflected in the Service and Digital Target Enterprise Architecture diagram as a cross‑cutting factor that spans all horizontal layers. The goal is to ensure security at all architectural levels, from design to implementation to operations; and to ensure authentication, authorization, auditing, monitoring, tokenization, and encryption of all data, whether at rest or in motion. |
− | | + | [[File:Service and Digital security architecture.png|center|thumb|595x595px]] |
− | == ADD image security architecture ==
| |
| | | |
| === Improved outcomes === | | === Improved outcomes === |