6
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − + + + + + + + + + + + + + − + − + Line 37:
Line 49: − + − + Line 63:
Line 75: − + − +
→Problem or opportunity statement
<code>''Explain the business problem or opportunity that needs to be solved in one sentence.''</code>
<code>''Explain the business problem or opportunity that needs to be solved in one sentence.''</code>
Source code developed by GC workers (software engineering, scientists, researchers,...) to support key programs needs to be available for reuse across departments, and to be scanned for security vulnerabilities.
Current development of Government of Canada computer programs and solutions rely on mixed practices and version control systems, if any. By providing a common place to develop solutions, there is an opportunity to:
- Enable teams across the entire government to leverage best practices
- CI/CD automation, known security vulnerability and legal compliance scanning and reporting automation.
- Enterprise standard use of open source components (inbound single version of package)
- Set enterprise wide policies as well as department specific policies (prohibit or authorize use of AGPL, MIT, etc.) for software inbound.
- Identify duplicate custom code, reuse existing code and create communities around specific projects across departments: meeting room reservation application from department A could be leveraged across the government.
Source code developed by GC employees (software engineering, scientists, researchers,...) to support key programs needs to be available for reuse across departments, and to be scanned for security vulnerabilities.
== Current state or context ==
== Current state or context ==
<code>''Describe the current state in which the problem or opportunity exists. Provide evidence to support the business problem or opportunity.
<code>''Describe the current state in which the problem or opportunity exists. Provide evidence to support the business problem or opportunity.''
Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment''
Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment
</code>
</code>
== Future state ==
== Future state ==
<code>''Describe the expected future state.
<code>''Describe the expected future state.''
Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment''
Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment
</code>
</code>
== Next Steps ==
== Next Steps ==
<code>''What are the planned next steps?
<code>''What are the planned next steps? ''
Are there any known time constraints moving forward?''
Are there any known time constraints moving forward?
</code>
</code>
