Line 23: |
Line 23: |
| Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole-of-government approach where IT is aligned to business services and solutions are based on re-useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for re-use across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements, in particular, a primary focus. | | Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole-of-government approach where IT is aligned to business services and solutions are based on re-useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for re-use across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements, in particular, a primary focus. |
| | | |
− | === Fulfill the Government of Canada users and other stakeholder's needs === | + | === <s>Fulfill</s> Design services digitally from end-to-end to meet the Government of Canada users and other stakeholder's needs === |
| * Clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service | | * Clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service |
| * Include policy requirement applying to specific users and other stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service | | * Include policy requirement applying to specific users and other stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service |
Line 41: |
Line 41: |
| Information architecture best practices and principles remain consistent but their focus must accommodate the needs of a business service and business capability orientation. In particular, in order to share information across Government, information architecture must address the higher standards needed in terms of the awareness of the information handling needs of each piece of data – its source, quality, and associated policy obligations. <u>The collection, use and management of personal information requires adherence to the principles and requirements of GC privacy legislation and its related policies.</u> | | Information architecture best practices and principles remain consistent but their focus must accommodate the needs of a business service and business capability orientation. In particular, in order to share information across Government, information architecture must address the higher standards needed in terms of the awareness of the information handling needs of each piece of data – its source, quality, and associated policy obligations. <u>The collection, use and management of personal information requires adherence to the principles and requirements of GC privacy legislation and its related policies.</u> |
| | | |
− | === Collect data to address the needs of the users and other stakeholders <u>where permissible legislation</u> === | + | === Collect data to address the needs of the users and other stakeholders <u>where permissible by legislation</u> === |
| * Assess data requirements based on users and other stakeholder needs | | * Assess data requirements based on users and other stakeholder needs |
| * Collect only the minimum set of data needed to support a policy, program, or service | | * Collect only the minimum set of data needed to support a policy, program, or service |
Line 47: |
Line 47: |
| * Ensure data collected, including from third party sources, are of high quality | | * Ensure data collected, including from third party sources, are of high quality |
| | | |
− | === Manage data strategically and responsibly === | + | === Manage <u>and re-use</u> data strategically and responsibly === |
| * Define and establish clear roles, responsibilities, and accountabilities for data management | | * Define and establish clear roles, responsibilities, and accountabilities for data management |
| * Identify and document the lineage of data assets | | * Identify and document the lineage of data assets |