Changes

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 reuse 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 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 reuse 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 a primary focus.

=== Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs ===

=== Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs ===

In order to ensure that the service will be able to meet the users and stakeholders' needs, a policy, a program or a business service (we can refer to this as "the entity") needs to know who their targeted users are (internal and external) as well as who the stakeholders are. Once these users and stakeholders are defined, then the entity can proceed to create a stakeholder mapping to further understand the relationship between the service / the program / the policy and the users / stakeholders, how it impacts one another. From there, the entity can conduct need analysis of its users and stakeholder to develop a program, a policy or a service that meets their needs (this practice may also be known as stakeholder requirements). This exercise can also help define the limitation/scope of the program/policy/service to better manage the expectation of their users/stakeholders.

In order to ensure that the service will be able to meet the users and stakeholders' needs, a policy, a program or a business service (we can refer to this as "the entity") needs to know who their targeted users are (internal and external) as well as who the stakeholders are. Once these users and stakeholders are defined, then the entity can proceed to create a stakeholder mapping to further understand the relationship between the service / the program / the policy and the users / stakeholders, how it impacts one another. From there, the entity can conduct need analysis of its users and stakeholder to develop a program, a policy or a service that meets their needs (this practice may also be known as stakeholder requirements). This exercise can also help define the limitation/scope of the program/policy/service to better manage the expectation of their users/stakeholders.