Line 30: |
Line 30: |
| This will in turn enable the service to be far-reaching and more inclusive to all its users. | | This will in turn enable the service to be far-reaching and more inclusive to all its users. |
| | | |
− | <b>How to achieve:</b> | + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Outline what policies constrain the architecture | | * Outline what policies constrain the architecture |
| * Outline positive and negative impact the policy has on the architecture to meet the needs of the stakeholder | | * Outline positive and negative impact the policy has on the architecture to meet the needs of the stakeholder |
Line 42: |
Line 42: |
| The use of this type of system must closely follow the Directive on Automated Decision-Making. | | The use of this type of system must closely follow the Directive on Automated Decision-Making. |
| | | |
− | <b>How to achieve:</b> | + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Provide the impact level based on the completion of the conceptual AIA | | * 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 will address the recommendations coming from the AIA |
Line 57: |
Line 57: |
| Then go through different possible scenarios to ensure the service is still being delivered correctly, effectively and efficiently.</br> | | Then go through different possible scenarios to ensure the service is still being delivered correctly, effectively and efficiently.</br> |
| | | |
− | <b>How to achieve:</b> | + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Summarize the delivery of value to customer across the architecture’s business ecosystem and the contribution of each stakeholder to the value | | * Summarize the delivery of value to customer across the architecture’s business ecosystem and the contribution of each stakeholder to the value |
| <b>Tools:</b> | | <b>Tools:</b> |
Line 71: |
Line 71: |
| The service can affect the mandate directly/indirectly, however, one needs to justify the needs of the service in relation to the actual mandate of the department. | | The service can affect the mandate directly/indirectly, however, one needs to justify the needs of the service in relation to the actual mandate of the department. |
| | | |
− | <b>How to achieve:</b>
| + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Outline the GC/Departmental Strategies the architect aligns and/or implements | | * Outline the GC/Departmental Strategies the architect aligns and/or implements |
| * Describe the architecture's contribution to realizing the appropriate outcomes of the strategy | | * Describe the architecture's contribution to realizing the appropriate outcomes of the strategy |
Line 85: |
Line 85: |
| This is an important step to ensure that we can prioritize the effort correctly to identify and build the right service that is of high priority with the budget assigned.</br> | | This is an important step to ensure that we can prioritize the effort correctly to identify and build the right service that is of high priority with the budget assigned.</br> |
| | | |
− | <b>How to achieve:</b> | + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * What are the metrics used to ensure that the outcomes are being realized | | * 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. | | * What data is required for the metrics and identify how any gaps in the data will be addressed. |
Line 97: |
Line 97: |
| Having an open communication between the various teams also helps in getting the right solution that closely match the business requirement.</br> | | Having an open communication between the various teams also helps in getting the right solution that closely match the business requirement.</br> |
| | | |
− | <b>How to achieve:</b> | + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Outline the business capabilities involved in achieving each outcome | | * Outline the business capabilities involved in achieving each outcome |
| <b>Tools:</b> | | <b>Tools:</b> |
Line 108: |
Line 108: |
| * <b>identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders</b> | | * <b>identify opportunities to enable business services horizontally across the GC enterprise and to provide cohesive experience to users and other stakeholders</b> |
| | | |
− | <b>How to achieve:</b> | + | In creating any service, we always need to go back to think about the users/stakeholders. Put ourselves in the users'/stakeholders' shoes. If we are at the receiving end of the service, what kind of experience do we get when we are trying to get the service. Does the user need to know where to get related services, or can we provide them with a seamless service, a cohesive service ? How do we provide a good experience to the users / stakeholders ? </br> |
| + | We need to start thinking more of an enterprise level, starting at the departmental level first. How can we enable this service across the department ? Is there any opportunity to reuse what we have in other areas of the department ? What do we need to do to leverage this process ? </br> |
| + | We need to plug in to community of practices, network of expertise or other working groups in order to exchange information, understand the various obstacles experienced by others, get lessons learned from others' experiences, share lessons learned, learn from others how they overcome similar obstacles in their work, share your solutions to others. </br> |
| + | |
| + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Summarize the departmental / GC opportunities where the architecture could be reused | | * 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 | | * Summarize departmental/GC architectures that impact or influence the ability of the user having a cohesive experience |
Line 118: |
Line 122: |
| </br> | | </br> |
| * <b>reuse common business capabilities, processes and enterprise solutions from across government and private sector</b> | | * <b>reuse common business capabilities, processes and enterprise solutions from across government and private sector</b> |
− | <b>How to achieve:</b> | + | |
| + | |
| + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Describe the plan and approach to standardize the realization of the business capability so it can be reused within the department and GC | | * Describe the plan and approach to standardize the realization of the business capability so it can be reused within the department and GC |
| <b>Tools:</b> | | <b>Tools:</b> |
Line 125: |
Line 131: |
| </br> | | </br> |
| * <b>publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services</b> | | * <b>publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services</b> |
− | <b>How to achieve:</b> | + | |
| + | |
| + | <b>How to demonstrate that the project fulfils this framework:</b> |
| * Outline the plan to allow other public sector organizations to reuse the common capability | | * Outline the plan to allow other public sector organizations to reuse the common capability |
| <b>Tools:</b> | | <b>Tools:</b> |