Difference between revisions of "GC Enterprise Architecture"
Jump to navigation
Jump to search
m |
m |
||
| Line 25: | Line 25: | ||
<!-- NAV end --> | <!-- NAV end --> | ||
| + | ==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, security, and privacy domains to support strategic outcomes. | Enterprise Architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization considering and aligning business, information/data, application, technology, security, and privacy domains to support strategic outcomes. | ||
| + | ==Mandate== | ||
The mandate of GC EA, as part of the GC Enterprise Architecture Review Board (EARB), is to refine current architecture standards and to define target architecture standards. | The mandate of GC EA, as part of the GC Enterprise Architecture Review Board (EARB), is to refine current architecture standards and to define target architecture standards. | ||
EA does this by linking business and IT strategy, enabling cooperation between business and IT, and leading the enterprise response to disruption. | EA does this by linking business and IT strategy, enabling cooperation between business and IT, and leading the enterprise response to disruption. | ||
| + | ==B-I-A-T-S+P (GC EA Layers)== | ||
The use of an industry standard framework called TOGAF (The Open Group Architecture Framework) is useful for providing a structured approach to these standards, and it has been adapted using the same building blocks, the '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). The "P" (Privacy) was added as an important component part of Security for Canadian public. | The use of an industry standard framework called TOGAF (The Open Group Architecture Framework) is useful for providing a structured approach to these standards, and it has been adapted using the same building blocks, the '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). The "P" (Privacy) was added as an important component part of Security for Canadian public. | ||
* <u>Business Architecture</u> is the discipline that defines '''[https://gcconnex.gc.ca/file/download/50303099 business capabilities]''' and ensures that design is focused on '''outcomes for users'''. It also ensures systems are designed to be '''measurable and accountable''', and delivered by '''multidisciplinary teams'''. | * <u>Business Architecture</u> is the discipline that defines '''[https://gcconnex.gc.ca/file/download/50303099 business capabilities]''' and ensures that design is focused on '''outcomes for users'''. It also ensures systems are designed to be '''measurable and accountable''', and delivered by '''multidisciplinary teams'''. | ||
| Line 40: | Line 43: | ||
The use of the BIATS+P was codified as a set of GC Architectural Standards in the Directive on Management of Information Technology (Appendix C - Mandatory Procedures for Enterprise Architecture Assessment). These standards are used to evaluate GC initiatives and ensure alignment. | The use of the BIATS+P was codified as a set of GC Architectural Standards in the Directive on Management of Information Technology (Appendix C - Mandatory Procedures for Enterprise Architecture Assessment). These standards are used to evaluate GC initiatives and ensure alignment. | ||
| + | ==Working Groups== | ||
A number of GC Working Groups support the refinement of these standards and influence departments to align with the direction set in the Digital Operations Strategic Plan. | A number of GC Working Groups support the refinement of these standards and influence departments to align with the direction set in the Digital Operations Strategic Plan. | ||
* Supporting '''Business''' architecture, a working group was created based on the mandate from the DMCEPP to refine the [https://gcconnex.gc.ca/file/download/50303099 GC Business Capability Model] (GC BCM), which defines common terminology across the government for discussing business capabilities. | * Supporting '''Business''' architecture, a working group was created based on the mandate from the DMCEPP to refine the [https://gcconnex.gc.ca/file/download/50303099 GC Business Capability Model] (GC BCM), which defines common terminology across the government for discussing business capabilities. | ||
| Line 112: | Line 116: | ||
<!-- FRENCH --> | <!-- FRENCH --> | ||
@fr|__NOTOC__ | @fr|__NOTOC__ | ||
| − | |||
<h1>l'architecture integrée de GC </h1> | <h1>l'architecture integrée de GC </h1> | ||
| − | |||
<!-- NAV --> | <!-- NAV --> | ||
| − | |||
{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center" | {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center" | ||
|- | |- | ||
| Line 133: | Line 134: | ||
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="9%" | '''[[Other_References|<span style="color: Snow">'''les references autres'''</span>]] ''' | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="9%" | '''[[Other_References|<span style="color: Snow">'''les references autres'''</span>]] ''' | ||
| − | |||
|} | |} | ||
| − | |||
<!-- NAV end --> | <!-- NAV end --> | ||
| + | ==Definition== | ||
<br>En tant que membre du Conseil d’examen de l’architecture intégrée (CEAI) du GC, l’architecture intégrée (AI) du GC a le mandat de perfectionner les normes d’architecture actuelles et d’établir les normes d’architecture visées. | <br>En tant que membre du Conseil d’examen de l’architecture intégrée (CEAI) du GC, l’architecture intégrée (AI) du GC a le mandat de perfectionner les normes d’architecture actuelles et d’établir les normes d’architecture visées. | ||
| + | ==Mandat== | ||
'''L’AI est une plan conceptuel qui définit la structure et le fonctionnement d’un organisme en tenant compte et en harmonisant les activités opérationnelles, l’information, les données, les applications, la technologie, la sécurité et la protection des renseignements personnels afin d’appuyer les résultats stratégiques. ''' | '''L’AI est une plan conceptuel qui définit la structure et le fonctionnement d’un organisme en tenant compte et en harmonisant les activités opérationnelles, l’information, les données, les applications, la technologie, la sécurité et la protection des renseignements personnels afin d’appuyer les résultats stratégiques. ''' | ||
Pour y parvenir, l’AI établit le lien entre les activités opérationnelles et la stratégie en matière de TI, permet la collaboration entre les activités opérationnelles et la stratégie en matière de TI et dirige l’intervention ministérielle en cas de perturbation. | Pour y parvenir, l’AI établit le lien entre les activités opérationnelles et la stratégie en matière de TI, permet la collaboration entre les activités opérationnelles et la stratégie en matière de TI et dirige l’intervention ministérielle en cas de perturbation. | ||
| + | ==B-I-A-T-S+P (l'AI GC layers)== | ||
L’utilisation du cadre de normes industrielles appelée le TOGAF (The Open Group Architecture Framework) permet d’offrir une approche structurée relativement à ces normes. Le cadre a question a été élaborée au moyen des mêmes éléments constitutifs, c’est-à-dire le '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). Le « P » (pour protection de la vie privée) a été ajouté à titre de composante de sécurité importante pour la population canadienne. | L’utilisation du cadre de normes industrielles appelée le TOGAF (The Open Group Architecture Framework) permet d’offrir une approche structurée relativement à ces normes. Le cadre a question a été élaborée au moyen des mêmes éléments constitutifs, c’est-à-dire le '''B-I-A-T-S+P''' (Business - Information - Application - Technology - Security + Privacy). Le « P » (pour protection de la vie privée) a été ajouté à titre de composante de sécurité importante pour la population canadienne. | ||
| Line 160: | Line 162: | ||
L’utilisation de la BIATS+P est établi comme ensemble de normes architecturales du GC dans la Directive sur la gestion des technologies de l'information (Annexe C - Procédures obligatoires pour l'évaluation de l'architecture intégrée). Ces normes sont utilisées pour évaluer les initiatives du GC et garantir l’harmonisation. | L’utilisation de la BIATS+P est établi comme ensemble de normes architecturales du GC dans la Directive sur la gestion des technologies de l'information (Annexe C - Procédures obligatoires pour l'évaluation de l'architecture intégrée). Ces normes sont utilisées pour évaluer les initiatives du GC et garantir l’harmonisation. | ||
| + | ==Equipe de travail== | ||
Un certain nombre de groupes de travail du GC soutiennent l’amélioration de ces normes et incitent les ministères à s’harmoniser à l’orientation établie dans le Plan stratégique des opérations numériques. | Un certain nombre de groupes de travail du GC soutiennent l’amélioration de ces normes et incitent les ministères à s’harmoniser à l’orientation établie dans le Plan stratégique des opérations numériques. | ||
| Line 175: | Line 178: | ||
· La communauté de pratique de l’architecture d’entreprise [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msocom 5|[SP5]]] travaille avec les ministères du GC pour continuer à perfectionner le BIATS+P et aider à assurer l’harmonisation. | · La communauté de pratique de l’architecture d’entreprise [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msocom 5|[SP5]]] travaille avec les ministères du GC pour continuer à perfectionner le BIATS+P et aider à assurer l’harmonisation. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<span style="font-size:1.5em;"><b>[[Government_of_Canada_Architectural_Standards | les normes de l'AI]]</b></span> | <span style="font-size:1.5em;"><b>[[Government_of_Canada_Architectural_Standards | les normes de l'AI]]</b></span> | ||
| Line 208: | Line 201: | ||
<span style="font-size:1.5em;"><b>[[Monitoring_Architectural_Implementation |les references autres]]</b></span> | <span style="font-size:1.5em;"><b>[[Monitoring_Architectural_Implementation |les references autres]]</b></span> | ||
: Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors | : Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors | ||
| + | |||
| + | |||
| + | ----[[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msoanchor 1|[SP1]]]Pas trouvé de traduction officielle, j’ai donc traduit ces termes en m’inspirant de la traduction de termes similaires | ||
| + | |||
| + | [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msoanchor 2|[SP2]]]Pas trouvé de traduction officielle, j’ai donc traduit ces termes en m’inspirant de la traduction de termes similaires | ||
| + | |||
| + | [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msoanchor 3|[SP3]]]Pas trouvé de traduction officielle, j’ai donc traduit ces termes en m’inspirant de la traduction de termes similaires | ||
| + | |||
| + | [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msoanchor 4|[SP4]]]Pas trouvé de traduction officielle, j’ai donc traduit ces termes en m’inspirant de la traduction de termes similaires | ||
| + | |||
| + | [[:File:///C:/Users/JCURRAH/AppData/Local/Microsoft/Windows/INetCache/Content.Outlook/14VIGJ05/FINAL-7136434 1-FR.DOCX# msoanchor 5|[SP5]]]Pas trouvé de traduction officielle, j’ai donc traduit ces termes en m’inspirant de la traduction de termes similaires | ||
Revision as of 15:58, 30 September 2019
| Home | EA standards | EARB Endorsements | EA Artifacts | Working Groups | GC EARB | Other References |
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, security, and privacy domains to support strategic outcomes.
Mandate[edit | edit source]
The mandate of GC EA, as part of the GC Enterprise Architecture Review Board (EARB), is to refine current architecture standards and to define target architecture standards.
EA does this by linking business and IT strategy, enabling cooperation between business and IT, and leading the enterprise response to disruption.
B-I-A-T-S+P (GC EA Layers)[edit | edit source]
The use of an industry standard framework called TOGAF (The Open Group Architecture Framework) is useful for providing a structured approach to these standards, and it has been adapted using the same building blocks, the B-I-A-T-S+P (Business - Information - Application - Technology - Security + Privacy). The "P" (Privacy) was added as an important component part of Security for Canadian public.
- Business Architecture is the discipline that defines business capabilities and ensures that design is focused on outcomes for users. It also ensures systems are designed to be measurable and accountable, and delivered by multidisciplinary teams.
- Information Architecture establishes a structure for data collection, management, storage, and sharing (with a focus on open sharing as per the Directive on Open Government).
- Application Architecture emphasises the use of open standards and solutions, ensures reuse is maximized, and focuses on enabling interoperability.
- Technology Architecture is the discipline that defines standards for using Public Cloud hosting (and related models such as Software as a Service), and designing for performance, availability, and scalability.
- Security Architecture is concerned with ensuring security is implemented across all architectural layers, and categorizing data to determine appropriate safeguards.
- Privacy Architecture emphasizes the need to perform a privacy impact assessment (PIA) when personal information is involved, and ensures a balance between user and business needs with proportionate security measures.
The use of the BIATS+P was codified as a set of GC Architectural Standards in the Directive on Management of Information Technology (Appendix C - Mandatory Procedures for Enterprise Architecture Assessment). These standards are used to evaluate GC initiatives and ensure alignment.
Working Groups[edit | edit source]
A number of GC Working Groups support the refinement of these standards and influence departments to align with the direction set in the Digital Operations Strategic Plan.
- Supporting Business architecture, a working group was created based on the mandate from the DMCEPP to refine the GC Business Capability Model (GC BCM), which defines common terminology across the government for discussing business capabilities.
- Supporting Information architecture, another working group called the GC Enterprise Data Community of Practice was created to discuss how to collect, store, share and manage data. An Artificial Intelligence Policy working group also supports the "Information" building block.
- Supporting Application architecture, the Digital Exchange Program working group was created to discuss using APIs (Application Programming Interfaces) for GC use, and publishing them in the GC API store.
- The Cloud Working group was created to support Technology architecture related to Public Cloud infrastructure for Protected B workloads and below.
- In Security architecture, the Sign in Canada & Pan Canadian Trust Framework working group focuses on the Enterprise Digital Identity.
- Privacy architecture is supported by members of the TBS Privacy team, who worked closely with the Office of the Privacy Commissioner on the definition of the Privacy standards.
- The Enterprise Architecture Community of Practice works with departments across the GC to continue refine the BIATS+P and help ensure alignment.
- Creates GC Architectural Standards as per the Directive for Management of IT
- Publishes Past EA Endorsements as tied into the BIATS layers
- Produces Artifacts supporting the Architectural Standards
- Creates EA Working groups - to identify and develop artifacts to bridge the gaps
- Refers to the GC EARB for Governance
- Provides quick references, such as: List of approved Cloud Vendors & approved AI Vendors
|
Need help? Contact us.
|
