GCcode/ConceptCase - Revision history

Johanne.jean-baptiste: /* Desired business outcome */

2018-12-06T19:22:01Z

Desired business outcome

Guillaume.charest: /* Root Cause */

2018-11-30T17:33:02Z

Root Cause

Guillaume.charest at 13:24, 24 October 2018

2018-10-24T13:24:03Z

Guillaume.charest: /* Problem or opportunity statement */

2018-10-24T13:21:37Z

Problem or opportunity statement

Guillaume.charest at 13:20, 24 October 2018

2018-10-24T13:20:39Z

Guillaume.charest at 13:18, 24 October 2018

2018-10-24T13:18:52Z

Guillaume.charest: /* Problem or opportunity statement */

2018-10-24T13:08:44Z

Problem or opportunity statement

Johanne.jean-baptiste at 20:41, 22 October 2018

2018-10-22T20:41:46Z

Johanne.jean-baptiste at 20:40, 22 October 2018

2018-10-22T20:40:01Z

Johanne.jean-baptiste at 20:16, 22 October 2018

2018-10-22T20:16:21Z

@@ Line 37: / Line 37: @@
 * help developers share best coding practices
 * Decrease time and cost to build new solutions
-* Reduce costs maintenance cost of source code repositories
+* Reduce overall maintenance costs for source code repositories by eliminating duplication
 * Improve continuous integration (CI/CD) practices
 * Enable teams across the entire government to leverage best practices and tools for the development and reuse of source code in the GC.

@@ Line 23: / Line 23: @@
 == Root Cause ==
-Traditionally, software development is done within departments without a view to reuse the code for other projects, or across departments. Massive online collaboration tools did not exist to easily share source code outside departments and the public.
+Traditionally, software development was done within departments without a view to reuse the code for other projects, or across departments. Massive online collaboration tools did not exist to easily share source code outside departments and the public.
 The current instance of Gitlab, GCcode, has provided departments with a common place to share their custom code and to experiment quickly without the constraints of a department specific version control system.

@@ Line 9: / Line 9: @@
 <code>''Explain the business problem or opportunity that needs to be solved in one sentence.''</code>
-Current development of Government of Canada computer programs and solutions rely on mixed practices and version control systems specific to each department and agency. By providing a common place to develop and share development projects and solutions, there is an opportunity to:
+Current development of Government of Canada computer programs and solutions rely on mixed practices and version control systems specific to each department and agency. By providing a common place to develop and share development projects and solutions, there is an opportunity to reuse the same platform across departments in most cases.
 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.
@@ Line 47: / Line 39: @@
 * Reduce costs maintenance cost of source code repositories
 * Improve continuous integration (CI/CD) practices
 The use of GCcode is aligned with the GC Digital Standards "Work in the open by default" and "Collaborate widely".

@@ Line 12: / Line 12: @@
 * Enable teams across the entire government to leverage best practices and tools for the development and reuse of source code in the GC.
-  * Smaller departments may not have the financial resources to host and maintain such a development environment; by providing a common place for all to work together, we would be generating economies of scale beyond single departments.
+** Smaller departments may not have the financial resources to host and maintain such a development environment; by providing a common place for all to work together, we would be generating economies of scale beyond single departments.
 * Automate and scale CI/CD with automation and leveraging corporate level tools like automated scanning of known security vulnerabilities and legal compliance.
 * Enterprise standard use of open source components (inbound single version of package)

@@ Line 12: / Line 12: @@
 * Enable teams across the entire government to leverage best practices and tools for the development and reuse of source code in the GC.
 * Automate and scale CI/CD with automation and leveraging corporate level tools like automated scanning of known security vulnerabilities and legal compliance.
 * Enterprise standard use of open source components (inbound single version of package)

@@ Line 9: / Line 9: @@
 <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:
 == 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>
@@ Line 37: / Line 49: @@
 == 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>
@@ Line 63: / Line 75: @@
 == 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>

← Older revision		Revision as of 20:41, 22 October 2018
Line 1:		Line 1:
		+	== Context ==
		+	* Proposed initiative: Integration of GCcode within the GCTools suite
		+	* Department: Treasury Board Secretariat
		+	* Assistant Deputy Minister:
		+	* Business owner: Treasury Board Secretariat

	== Problem or opportunity statement ==		== Problem or opportunity statement ==

@@ Line 4: / Line 4: @@
 <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.
+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 state or context ==
@@ Line 12: / Line 12: @@
 </code>
-Each department has at least one source code repository to manage versioning, and manage the software development life cycle. Many departments have several source code repositories. About $2 million is spent by departments on maintenance of source code repositories their associated continuous integration tools. This is based on data from the Application Portfolio Management program's inventory of applications which covers mostly the large departments.
+Each department has at least one source code repository to manage versioning, and the software development life cycle. Many departments have several source code repositories. About $1.5 million is spent annually by departments on maintenance of source code repositories, and their associated continuous integration tools. This is based on data from the Application Portfolio Management program's inventory of applications which covers mostly the large departments. Extrapolating to the whole of the GC, we estimate that at least $2 million is spent annually around the GC on source code repositories.
 == Root Cause ==
-Traditionally, software development is done within departments without a view to reuse the code or solution for other projects or across departments. Tools did not exist to easily share source code outside departments. Over the past few years, several collaboration platforms centered on development have emerged and gained popularity. The GC can leverage one of those platforms.
+Traditionally, software development is done within departments without a view to reuse the code for other projects, or across departments. Massive online collaboration tools did not exist to easily share source code outside departments and the public.
 == Desired business outcome ==
-A common platform to develop and collaborate around source code will
+Over the past few years, several software development collaboration platforms have emerged and gained popularity. A few departments are already leveraging GitHub to co-develop source code with the public at large, using an open source license. Most of the software developed by departments is not for co-creation with the public, and would not be candidates for an open source licence. However, this source code can be shared within the GC. Several departments are already using the GCcode platform (GitLab instance). To make this platform mainstream for all departments it requires continuous funding and support.
 * Decrease time and cost to build new solutions
-* Reduce costs associated with acquisition and maintenance of source code repositories in each department
+* Reduce costs maintenance cost of source code repositories
 * Improve continuous integration (CI/CD) practices
 == Future state ==
@@ Line 30: / Line 36: @@
 Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment''
 </code>
 Source code developers will be able to
@@ Line 46: / Line 54: @@
 IT Security managers will be able to
 * Quickly locate vulnerable software libraries at the departmental level or across departments
-* Automate application security scans to prevent issues
+* Automate application security scans to alert departments and prevent costly emergency responses
 == Next Steps ==

@@ Line 1: / Line 1: @@
 == Problem or opportunity statement ==
 ''Explain the business problem or opportunity that needs to be solved in one sentence.''
 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 state or context ==
-''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:
+Aspects to consider: stakeholders and users, business process, technology employed, information or data used, relevant legislation or policies, strategic alignment''
-•	stakeholders and users
+</code>
 Each department has at least one source code repository to manage versioning, and manage the software development life cycle. Many departments have several source code repositories. About $2 million is spent by departments on maintenance of source code repositories their associated continuous integration tools. This is based on data from the Application Portfolio Management program's inventory of applications which covers mostly the large departments.
@@ Line 31: / Line 26: @@
 == Future state ==
-''Describe the expected future state.
+<code>''Describe the expected future state.
-Aspects to consider:
+Source code developers will be able to
-o	discover tools to help them be more efficient, such as configuration scripts, user interface customizations.
+* discover tools to help them be more efficient, such as configuration scripts, user interface customizations.
-o	collaborate on common solutions
+* collaborate on common solutions
-o	decrease their learning curve for new technologies
+* decrease their learning curve for new technologies
-o	discover solutions which they can reuse to address their clients needs
+* discover solutions which they can reuse to address their clients needs
-o	network and learn from their peers
+* network and learn from their peers
-•	Departments can
+Departments will be able to
-o	Reduce their IT costs by using common version control and CI/CD tools
+* Reduce their IT costs by using common version control and CI/CD tools
-o	Reduce software development costs by reusing solutions for the same business need.
+* Reduce software development costs by reusing solutions for the same business need.
-o	Discover and retain talent
+* Discover and retain talent
-•	IT Security managers can
+IT Security managers will be able to
-o	Quickly locate vulnerable software libraries at the departmental level or across departments
+* Quickly locate vulnerable software libraries at the departmental level or across departments
-o	Automate application security scans to prevent issues
+* Automate application security scans to prevent issues
 == Next Steps ==
-''What are the planned next steps?
+<code>''What are the planned next steps?
 Are there any known time constraints moving forward?''