Changes

Application Architecture consists of the interaction of applications with each other and with users. It focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability.

Application Architecture consists of the interaction of applications with each other and with users. It focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability.

==Use Open Standards and Solutions by Default==

==Key Messages==

The [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=15249#appC Directive on Management of Information Technology] and [https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html Digital Standards] states that where possible, open source software be used first, The primary driving factors for this are:

* Protocol and measures will be put in place to ensure that the workplace is equipped to properly support returning personnel and making sure the space is safe.

* [Require specific details of how workplace is responding to:]

# Supporting the Local Economy and Communities

# Lowering initial and long term Cost of Solutions

** sanitizer availability and ordering;

** reducing chairs in boardrooms for meetings;

** kitchen protocols; and

** marking floor spaces, among others.

* Staff returning to the workplace will not be automatically tested for COVID-19. However, any DT member who is experiencing COVID-19 symptoms is encouraged to get tested, following the advice of their provincial and territorial health authorities

* '''Where possible, use open source standards, and open source software first'''

* Should a staff member feel ill and be experiencing symptoms of COVID-19, they are asked to inform their supervisor, go/stay home, and contact local public health authorities. This will be supported by management across the DT.

** While OSS is not a silver bullet several common misconceptions are used as arguments against Open Source software:

* Each supervisor, including myself, will be responsible for ensuring that staff are abiding by physical distancing requirements and PPE and PHM guidance within the workplace.

*** A misconception with security is that with the code out of the eyes of the public that it prevents successful attacks and lowers liability, however in reality Security Best practices state that 'System security should not depend on the secrecy of the implementation or its components', and as Open Source development relies n hardening (or improving the security) of code it is often equal or more secure then proprietary solutions.

* Upon your return, you will notice that all Defence Establishments have been - or are being - marked with one-way pathways and staircases, and elevators only to be used by individuals with limited mobility.

*** A misconception with support is that a support contract or license some how ensures that the proprietary system will receive improvements and patches, but in reality there is no obligation for a vendor to do so, while Open Source software survives by having a vibrant and helpful support community. Average resolution of issues are solved faster then in proprietary software by the very nature of crowd sourcing reducing the barrier of communication with a single entity or individual.

* Hand sanitizer will be available at each entrance/exit and will be replenished when possible given the high demand for the product. More importantly, staff are encouraged to frequently wash their hands with soap and water for at least twenty seconds, as this is the most effective way to sanitize hands.

 

* Direction on how cubicles can and should be occupied to maintain distancing has been received and you may notice some differences in how to access and use communal spaces. For example, you will see that washrooms, for the most part, will be single occupancy.

* '''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'''

* As a Defence Team member, you are encouraged to continue to talk to your supervisor if there is a periodic or ongoing requirement for you to work from home due to COVID-19 related reasons (i.e. child care, elder care, symptoms, etc.).

** Vendor lock is a real concern in the Development of Applications, and when propietary COTS applications are selected it increases the difficulty of ever moving to a new system, and any integration or interoperability functions.

* '''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'''

** It is important to reduce the duplication of effort that has occurred due to segmented mandates, and increase collaboration and sharing across Departments and Agencies. Crown Corporations, Provincial and Municipal Governments as well as the Public at large who can benefit from new and innovative products and services based off of creations from the Government.

** 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]

** 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'''

** 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].

* '''Expose public data to implement Open Data and Open Information initiatives'''

** Scientific Innovation can occur from exposing Data to interested members of the activists, researchers, students and the public at large.  

** Define Metadata for your application early in both English and French to support your release to https://open.canada.ca/en/open-data

** Development following the [https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/government-canada-standards-apis.html Government of Canada Standards on APIs] can allow rapid uptake into Open Data feeds.

==Maximize Reuse==

==Maximize Reuse==