101
edits
Changes
GC Enterprise Architecture/Standards/Application Architecture (view source)
Revision as of 13:05, 23 August 2019
, 13:05, 23 August 2019→Maximize Reuse
** Major benefits can occur not just from publishing the Software, but in developing Guidance the quality of software increases, while publishing Lessons Learned, White Papers and any other technical documentation can assist others in the future by providing templates and baselines.
** Major benefits can occur not just from publishing the Software, but in developing Guidance the quality of software increases, while publishing Lessons Learned, White Papers and any other technical documentation can assist others in the future by providing templates and baselines.
** For assistance in how to do this, you can view the[https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md TBS Guidance on Open Source Publishing]
** For assistance in how to do this, you can view the[https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md TBS Guidance on Open Source Publishing]
** Setting up shared teams for common problems where Developers from multiple departments can produce better solutions. Virtual Teams using open tools can enable rapid development in absence of collocation.
* '''All open source code must be released under an appropriate open source software license'''
* '''All open source code must be released under an appropriate open source software license'''
** It is important to ensure that the License chosen for OSS protects the rights of Government of Canada and Public Servants while enabling the use and re-use of software. Guidance can be found [https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md#select-open-source-software-licence here].
** It is important to ensure that the License chosen for OSS protects the rights of Government of Canada and Public Servants while enabling the use and re-use of software. Guidance can be found [https://github.com/canada-ca/open-source-logiciel-libre/blob/master/en/guides/publishing-open-source-code.md#select-open-source-software-licence here].
** SaaS, PaaS and IaaS solutions can leverage sharing of configurations when no code is involved such as the GC Accelerators ([https://github.com/canada-ca/accelerators_accelerateurs-azure AWS], [https://github.com/canada-ca/accelerators_accelerateurs-aws Amazon])
** SaaS, PaaS and IaaS solutions can leverage sharing of configurations when no code is involved such as the GC Accelerators ([https://github.com/canada-ca/accelerators_accelerateurs-azure AWS], [https://github.com/canada-ca/accelerators_accelerateurs-aws Amazon])
** Opening up Communication with other Departments to identify if they've already developed a solution can enable further reuse.
** Opening up Communication with other Departments to identify if they've already developed a solution can enable further reuse.
* Select enterprise and cluster solutions over department-specific solutions
* '''Select enterprise and cluster solutions over department-specific solutions'''
* Achieve simplification by minimizing duplication of components and adhering to relevant standards
** Focus on solutions that enable sharing with other Departments, do not focus just on individual mandates.
* Inform the GC EARB about departmental investments and innovations
** Costs can be setup to be shared across multiple departments, agencies etc...
* '''Achieve simplification by minimizing duplication of components and adhering to relevant standards'''
** Focus on Separation of Concern by the development of Microservices, and use and reuse of APIs.
** Consume APIs from the [https://api.canada.ca/en/homepage Government of Canada API Store] if it exists, if it does not add it to the API store.
** Follow the [https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/government-canada-standards-apis.html Government of Canada Standards on APIs]
* '''Inform the GC EARB about departmental investments and innovations'''
** Communicate with the GC-EARB Team early and frequently, sharing innovations and lessons learned so we can assistance in broadcasting them to others.
* Share code publicly when appropriate, and when not, share within the Government of Canada
* Share code publicly when appropriate, and when not, share within the Government of Canada