Line 16: |
Line 16: |
| <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> | + | <b><u>Fulfill the Government of Canada stakeholder's needs</b> |
− | * <I>Understand stakeholders well, conduct stakeholder analysis and create stakeholder mapping for each service being delivered | + | * <I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design |
− | * Ensure stakeholders' needs are clearly identified and captured for each service </I></u>
| + | * Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service |
− | * Ensure accountability for privacy is clear | + | * Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process) |
− | * <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
| |
− | * 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 Business Outcome and Strategic Alignment to the Department and to the Government of Canada </b> | + | <b>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b> |
− | * <I>Establish business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps | + | * Identify which departmental/GC business services, outcomes and strategies will be addressed |
− | * Use tools, such as Value Stream, to ensure business outcomes are achieved through services being delivered</I></u> | + | * Establish metrics for identified business outcomes throughout the lifecycle of an investment |
− | * 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 | + | * Translate business outcomes and strategy into business capability implications in the GC Business Capability Model to establish a common vocabulary between business, development, and operation |
− | * 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> Promote Horizontal Enablement of the Enterprise</b> |
− | <b><u> Horizontal Enablement </b> | + | * Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders |
− | * <i>Use business processes developed to identify common enterprise processes | + | * Reuse common business capabilities and processes from across government and private sector |
− | * Optimize common enterprise processes and maximize its re-use</i></u> | + | * Publish in the open reusable common business capabilities and processes (in the Open Government portal) for others to develop cohesive horizontal enterprise services</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>
| |
− | * 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
| |
− | * 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>
| |
| |} | | |} |
| | | |