Difference between revisions of "GC Enterprise Architecture/Standards"
Jump to navigation
Jump to search
(* Update to ID new changes.) |
(Add OSS Playbook Link) |
||
Line 94: | Line 94: | ||
<span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br> | <span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br> | ||
− | <b>Use Open Standards and Solutions by Default</b> | + | <b>Use Open Standards and Solutions by Default</b> |
* Where possible, use open source standards, and open source software first | * Where possible, use open source standards, and open source software first | ||
+ | ** For Guidance, please consult the [[GoC Open Source Playbook|Open Source Playbook]] | ||
* If an open source option is not available or does not meet user needs, favour platform-agnostic COTS over proprietary COTS, avoiding technology dependency, allowing for substitutability and interoperability | * If an open source option is not available or does not meet user needs, favour platform-agnostic COTS over proprietary COTS, avoiding technology dependency, allowing for substitutability and interoperability | ||
* If a custom-built application is the appropriate option, by default any source code written by the government must be released in an open format via Government of Canada website and services designated by the Treasury Board of Canada Secretariat | * If a custom-built application is the appropriate option, by default any source code written by the government must be released in an open format via Government of Canada website and services designated by the Treasury Board of Canada Secretariat | ||
Line 114: | Line 115: | ||
* Run applications in containers | * Run applications in containers | ||
* Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as the API Store, Messaging, and the GC Service Bus | * Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as the API Store, Messaging, and the GC Service Bus | ||
+ | |- | ||
+ | | | ||
|} | |} | ||
Revision as of 10:07, 9 August 2019
Home | EA standards | EARB Endorsements | EA Artifacts | Working Groups | GC EARB | Other References |
This page is a work in progress. We welcome your feedback. Please use the discussion page for suggestions and comments. When the page is approved and finalized, we will send it for translation. |
The GC Enterprise Architecture standard is part of the Directive on Management of Information Technology. It is listed as Appendix C - Mandatory Procedures for Enterprise Architecture Assessment in the Directive.
1. Business Architecture
Design for Users First and Deliver with Multidisciplinary Teams
Design Systems to be Measurable and Accountable
|
Data Collection
Data Management
Data Storage
Data Sharing
|
Use Open Standards and Solutions by Default
Maximize Reuse
Enable Interoperability
|
Use Cloud first
Design for Performance, Availability, and Scalability
|
5. Security Architecture and Privacy Design for Security and Privacy
|
Need help? Contact us.
|