Line 45: |
Line 45: |
| * User Interface Design Principles | | * User Interface Design Principles |
| * perform Algorithmic Impact Assessment (AIA) to support risk mitigation activities when deploying an automated decision system as per ''Directive on Automated Decision-Making'' | | * perform Algorithmic Impact Assessment (AIA) to support risk mitigation activities when deploying an automated decision system as per ''Directive on Automated Decision-Making'' |
− | * model end‑to‑end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (for example, lean process) | + | <b>How to achieve:</b> |
| + | * Provide the impact level based on the completion of the conceptual AIA |
| + | * Describe how the architecture will address the recommendations coming from the AIA |
| + | * Describe how the architecture meets the directive's requirements for the impact level |
| + | <b>Tools:</b> |
| + | * AIA Results (Conceptual) |
| | | |
| === Architect to be outcome‑driven and strategically aligned to the department and to the Government of Canada === | | === Architect to be outcome‑driven and strategically aligned to the department and to the Government of Canada === |
| * identify which departmental/GC business services, outcomes and strategies will be addressed | | * identify which departmental/GC business services, outcomes and strategies will be addressed |
| + | <b>How to achieve:</b> |
| + | * Outline the GC/Departmental Strategies the architect aligns and/or implements |
| + | * Describe the architecture's contribution to realizing the appropriate outcomes of the strategy |
| + | <b>Artifacts:</b> |
| + | * Drivers |
| + | * Outcomes (intimidate and ultimate) |
| + | * Business services (External) |
| * establish metrics for identified business outcomes throughout the life cycle of an investment | | * establish metrics for identified business outcomes throughout the life cycle of an investment |
| + | <b>How to achieve:</b> |
| + | * What are the metrics used to ensure that the outcomes are being realized |
| + | * What data is required for the metrics and identify how any gaps in the data will be addressed. |
| + | <b>Tools:</b> |
| + | * Value Stream (Measure KPI linked to benefits outcomes and objectives |
| * translate business outcomes and strategy into business capability implications in the [[GC Enterprise Architecture/Business Capability Model| <b>GC Business Capability Model</b>]] to establish a common vocabulary between business, development, and operation | | * translate business outcomes and strategy into business capability implications in the [[GC Enterprise Architecture/Business Capability Model| <b>GC Business Capability Model</b>]] to establish a common vocabulary between business, development, and operation |
| + | <b>How to achieve:</b> |
| + | * Outline the business capabilities involved in achieving each outcome |
| + | <b>Tools:</b> |
| + | * Business Impact Assessment |
| + | * Departmental BCM |
| + | * GC BCM (mapping to D BCM) |
| + | * Value Stream |
| | | |
| === Promote horizontal enablement of the enterprise === | | === Promote horizontal enablement of the enterprise === |
| * identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders | | * identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders |
| + | <b>How to achieve:</b> |
| + | * Summarize the departmental / GC opportunities where the architecture could be reused |
| + | * Summarize departmental/GC architectures that impact or influence the ability of the user having a cohesive experience |
| + | (what are the plans to ensure user has a cohesive experience across these architectures and the ecosystem |
| + | <b>Tools:</b> |
| + | * Business Capability |
| + | * Departmental Value Stream model |
| + | * Projects to Value Stream Script |
| * reuse common business capabilities, processes and enterprise solutions from across government and private sector | | * reuse common business capabilities, processes and enterprise solutions from across government and private sector |
| * publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services | | * publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services |