514
edits
Changes
Jump to navigation
Jump to search
Line 33:
Line 33: − + − + + − + − + − + − + − + − + − + + − + − + + − * Identify capabilities that are common to the GC enterprise and can be shared and reused+ − + + + − − <b>Design for Users First and Deliver with Multidisciplinary Teams</b> − * Focus on the needs of users, using agile, iterative, and user-centred methods − * Conform to both accessibility and official languages requirements − * Include all skillsets required for delivery, including for requirements, design, development, and operations − * Work across the entire application lifecycle, from development and testing to deployment and operations − * Ensure quality <u><i>and security</i></u> is <u><i>underpinning</i></u> the Software Development Lifecycle − * <I><u>Total Cost Of Ownership (TCO) should include the cost for design, construction, operation, and maintenance of a system. For example Training, Support, Disaster Recovery, and Retirement Cost</I></u> − − − <b>Design Systems to be Measurable and Accountable</b> − * Publish performance expectations for each business service and supporting application and technology service(s) − * Make an audit trail available for all transactions to ensure accountability and non-repudiation − * Establish business and IT metrics to enable business outcomes − * Apply oversight and lifecycle management to digital investments through governance − * <u><I>Complete an Algorithmic Impact Assessment (AIA) for systems automating decisions as per the [https://tbs-sct.gc.ca/pol/doc-eng.aspx?id=32592 Directive on Automated Decision-Making].</u></I> Line 137:
Line 126: + + + + + + + + + + + + + + + + + + Line 145:
Line 152: + Line 152:
Line 160: +
GC Enterprise Architecture/Framework (view source)
Revision as of 20:59, 29 August 2019
, 20:59, 29 August 2019no edit summary
<span style="font-size: 1.5em;">[[GC_Business_Enterprise_Architecture | 1. Business Architecture]]</span> <br><br>
<span style="font-size: 1.5em;">[[GC_Business_Enterprise_Architecture | 1. Business Architecture]]</span> <br><br>
<b><u> Fulfillment to the needs of the stakeholders to the Government of Canada </b></u>
<b><u>Fulfillment to the needs of the stakeholders to the Government of Canada </b></u>
* <I><u>Understand your stakeholders well, conduct stakeholder analysis and create stakeholder mapping</I></u>
* <I><u>Understand stakeholders well, conduct stakeholder analysis and create stakeholder mapping for each service being delivered
* Ensure stakeholders' needs are clearly identified and captured for each service</I></u>
* Ensure accountability for privacy is clear
* Ensure accountability for privacy is clear
* <u><I> Ensure that gender diversity and inclusion is considered as part of an intersectional approach to designing for users. Consult the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices and best practices for gender inclusive language. (Would note here that there are likely other examples of best practices that could be included such as positive space exemplars, but nothing else is springing to mind at the moment!) </I></u>
* <u><I>Ensure gender diversity and inclusion are considered as part of an intersectional approach to designing the service. Consult the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices and best practices for gender inclusive language </I></u>
* <u><I>Adopt a client-centric view of business delivery through customer journey maps and end-to-end service decomposition (internal (GC) and external (public)) </I></u>
* <u><I>Adopt a client-centric view of business delivery of service through customer journey maps and end-to-end service decomposition (internal (GC) and external (public)) </I></u>
<b><u> Focus on the business outcome and Strategic Alignment to the Department and to the GC </b></u>
<b><u> Focus on Business Outcome and Strategic Alignment to the Department and to the Government of Canada </b></u>
* <u><I>Establish business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps </I></u>
* <u><I>Establish business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps
* Model <I><u> the operation flow in a business process modeling, using </u></I> departmental chosen standard for business process notation, such as </u></I> Business Process Modeling Notation (BPMN), <I><u> to understand the business process well and find optimization in the process first
* Use tools, such as Value Stream, to ensure business outcomes are achieved through services being delivered</I></u>
* Collect business requirements prior to jumping to a solution
* Model <I><u> operation flow for each service being delivered in a business process modeling tool, using departmental chosen standard for business process notation, such as </u></I> Business Process Modeling Notation (BPMN), <I><u> and find optimization in the business process first
* Conduct proper option analysis to make sure all options are considered and the best solution is chosen</u></I>
* Ensure business requirements collection are completed prior to considering options
* Conduct option analysis from a business lens and ensure all options are considered prior to select the best solution to achieve business outcomes </u></I>
<b><u> Horizontal Enablement </b></u>
<b><u> Horizontal Enablement </b></u>
* <i><u>Use the business processes developed to identify common enterprise processes </I></u>
* <i><u>Use business processes developed to identify common enterprise processes
* Encourage and adopt <u><i>a process (for example:</i></u> Test Driven Development (TDD)) to improve the trust between Business and IT
* Optimize common enterprise processes and maximize its re-use</I></u>
* Encourage and use <u><i>a process (for example:</i></u> Test Driven Development (TDD)) to improve the trust between Business and IT
<b>Align to the [https://gcconnex.gc.ca/file/view/50303099/gcbcm-gcmca-v2-visualmodel-20190617-en-pdf?language=en GC Business Capability model]</b>
<b>Align to the [https://gcconnex.gc.ca/file/view/50303099/gcbcm-gcmca-v2-visualmodel-20190617-en-pdf?language=en GC Business Capability model]</b>
* Define program services as business capabilities to establish a common vocabulary between business, development, and operation
* Define program services as business capabilities to establish a common vocabulary between business, development, and operation
* <u><I>Translate business strategy into business capability implications using the GC Business Capability Model
* <u><I>Translate the business strategy into business capability implications using the GC Business Capability Model. Use these to guide investments.</u></I>
* Use the GC Business Capability Model as a baseline and refine the capabilities to deeper levels that are applicable to the departmental use
* Identify frequently used business capabilities to identify area of focus in resource and skills requirement (Resource Management) for the department as well as to guide investments
* Identify common business capabilities that can be leveraged by the GC enterprise and share it with the community for possible collaboration through a working group
|}
|}
* <I><u>Ensure valid license and legal requirements are met for use of Open Source items</u></I>
* <I><u>Ensure valid license and legal requirements are met for use of Open Source items</u></I>
* Expose public data to implement Open Data and Open Information initiatives
* Expose public data to implement Open Data and Open Information initiatives
<b>Design for Users First and Deliver with Multidisciplinary Teams</b>
* Focus on the needs of users, using agile, iterative, and user-centred methods
* Conform to both accessibility and official languages requirements
* Include all skillsets required for delivery, including for requirements, design, development, and operations
* Work across the entire application lifecycle, from development and testing to deployment and operations
* Ensure quality <u><i>and security</i></u> is <u><i>underpinning</i></u> the Software Development Lifecycle
* <I><u>Total Cost Of Ownership (TCO) should include the cost for design, construction, operation, and maintenance of a system. For example Training, Support, Disaster Recovery, and Retirement Cost</I></u>
<b>Design Systems to be Measurable and Accountable</b>
* Publish performance expectations for each business service and supporting application and technology service(s)
* Make an audit trail available for all transactions to ensure accountability and non-repudiation
* Establish business and IT metrics to enable business outcomes
* Apply oversight and lifecycle management to digital investments through governance
* <u><I>Complete an Algorithmic Impact Assessment (AIA) for systems automating decisions as per the [https://tbs-sct.gc.ca/pol/doc-eng.aspx?id=32592 Directive on Automated Decision-Making].</u></I>
<b>Maximize Reuse</b>
<b>Maximize Reuse</b>
* Inform the GC EARB about departmental investments and innovations
* Inform the GC EARB about departmental investments and innovations
* 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
<b>Enable Interoperability</b>
<b>Enable Interoperability</b>
* Run applications in containers
* Run applications in containers
* Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as [https://api.canada.ca/en/homepage#all-apis the API Store], Messaging, and the GC Service Bus
* Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as [https://api.canada.ca/en/homepage#all-apis the API Store], Messaging, and the GC Service Bus
<I><u><b>Develop with Security in mind</b>
<I><u><b>Develop with Security in mind</b>
