514
edits
Changes
Jump to navigation
Jump to search
Line 34:
Line 34: + Line 40:
Line 41: − + + + + − +
GC Enterprise Architecture/Framework (view source)
Revision as of 15:35, 29 August 2019
, 15:35, 29 August 2019no edit summary
<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>
* 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 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>
<b><u> Focus on the business outcome and Strategic Alignment to the Department and to the GC </b></u>
<b><u> Focus on the business outcome and Strategic Alignment to the Department and to the GC </b></u>
* <u><I>Establish the business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps</u></I>
* <u><I>Establish business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps </I></u>
* Model business processes 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
* Collect business requirements prior to jumping to a solution
* Conduct proper option analysis to make sure all options are considered and the best solution is chosen</u></I>
<b><u> Horizontal Enablement </b></u>
<b><u> Horizontal Enablement </b></u>
* Model business processes using <u><I> departmental chosen standard for business process notation, such as </u></I> Business Process Modeling Notation (BPMN), to identify common enterprise processes
* <i><u>Use the business processes developed to identify common enterprise processes </I></u>
* Encourage and adopt <u><i>a process (for example:</i></u> Test Driven Development (TDD)) to improve the trust between Business and IT
* Encourage and adopt <u><i>a process (for example:</i></u> Test Driven Development (TDD)) to improve the trust between Business and IT
