Line 88: |
Line 88: |
| <b>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b> | | <b>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b> |
| * Design systems as highly modular and loosely coupled services | | * Design systems as highly modular and loosely coupled services |
− | * Expose services through APIs | + | * Expose services, including existing ones, through APIs |
| * Make the APIs discoverable to the appropriate stakeholders | | * Make the APIs discoverable to the appropriate stakeholders |
| <br> | | <br> |
| | | |
− | <b>Follow DevSecOps Principles</b>
| |
− | * Use continuous integration and continuous deployments (CI/CD)
| |
− | * Ensure automated testing occurs for security and functionality
| |
− | * Include your stakeholders as part of DevSecOps process
| |
| </u></I> | | </u></I> |
| |} | | |} |
Line 119: |
Line 115: |
| * Establish architectures that supports new technology insertion with minimal disruption to existing programs and services | | * Establish architectures that supports new technology insertion with minimal disruption to existing programs and services |
| * Control Technical Diversity - design systems based on modern technologies and platforms already in use. | | * Control Technical Diversity - design systems based on modern technologies and platforms already in use. |
− | | + | <br> |
| + | <b>Follow DevSecOps Principles</b> |
| + | <u><i> |
| + | * Use continuous integration and continuous deployments (CI/CD) |
| + | * Ensure automated testing occurs for security and functionality |
| + | * Include your stakeholders as part of DevSecOps process |
| + | </u></i> |
| |} | | |} |
| | | |