Changes

<h2> The Plays </h2> <br>

<h2> The Plays </h2> <br>

<span style="font-size: 1.5em;">[[GC_Business_Enterprise_Architecture | 1. Business Architecture]]</span> <br><br>

<span style="font-size: 1.5em;"> 1. Business Architecture</span> <br><br>

A Business Architecture is where an organization identifies the various services that it suppose to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In terms of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>

A Business Architecture is where an organization identifies the various services that it suppose to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In terms of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>

<b><u>Fulfill the Government of Canada stakeholder's needs</b></u>

<b><u>Fulfill the Government of Canada stakeholder's needs</b></u>

As the provider of service to Canadians, it is important for the GC to understand the stakeholders well. The stakeholders in this case can mean their users, their partners (if any), their suppliers (if any), their program or project manager, their implementor, etc. Once a department identify all your stakeholders, it needs to identify the stakeholders' requirements and figure out how to make it easier for them to use its service, which means it needs to really drill down on the user interface design. This is what digital is all about, to make it easy for the users to consume the GC service.

As the provider of service to Canadians, it is important for the GC to understand the stakeholders well. The stakeholders in this case can mean their users, their partners (if any), their suppliers (if any), their program or project manager, their implementor, etc. Once a department identify all its stakeholders, it needs to identify the stakeholders' requirements and figure out how to make it easier for them to use its service, which means it needs to really drill down on the user interface design. This is what digital is all about, to make it easy for the users to consume the GC service.

While configuring the service, you should also take into account the policy requirements, including accessibilities, gender based+ analysis and official languages.<br><br>

While configuring the service, departments should also take into account the policy requirements, including accessibilities, gender based+ analysis and official languages.<br><br>

* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b></I>

* <b><I>Clearly identify internal and external stakeholders and their needs for each business service including user centric design </b></I>

To understand your stakeholder, it is recommended for program & project manager to conduct stakeholder analysis and create stakeholder mapping for each service being delivered. Users in this case can be Canadians (in terms of service your department provides), employees (if the service also applicable to your employees, or if your employees is the one implementing the service), or others. Partners can mean other departments or organizations that consume your service, provide data to you, or those who are building the system/program with you. Suppliers can be the SaaS companies who provide you with service, vendors, SSC, etc. <br><br>

To understand the stakeholder, it is recommended for program & project manager to conduct stakeholder analysis and create stakeholder mapping for each service being delivered. Users in this case can be Canadians (in terms of service the department provides), employees (if the service also applicable to the departmental employees, or if the employees is the one implementing the service), or others. Partners can mean other departments or organizations that consume the departmental service, provide data to the department, or those who are building the system/program with the department. Suppliers can be the SaaS companies who provide the department with service, vendors, SSC, etc. <br><br>

* <b><I>Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service </b></I>

* <b><I>Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service </b></I>

In identifying your stakeholder, ensure you are being inclusive, include other stakeholder groups.<br><br>

In identifying the stakeholder, department needs to ensure that it is being inclusive, include other stakeholder groups.<br><br>

* <b><I>Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)</b></I>

* <b><I>Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)</b></I>

<span style="font-size: 1.5em;">[[GC_Information_Enterprise_Architecture | 2. Information Architecture]]</span> <br><br>

<span style="font-size: 1.5em;">2. Information Architecture</span> <br><br>

<b>Collect data to address the needs of the stakeholders </b>

<b>Collect data to address the needs of the stakeholders </b>

<span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br>

<span style="font-size: 1.5em;">3. Application Architecture</span> <br><br>

Application Architecture consists of the interaction of applications with each other and with users. It focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>

Application Architecture consists of the interaction of applications with each other and with users. It focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>

<span style="font-size: 1.5em;">[[GC_Technology_Enterprise_Architecture | 4. Technology Architecture]]</span> <br><br>

<span style="font-size: 1.5em;">4. Technology Architecture</span> <br><br>

<b>Use Cloud first</b>

<b>Use Cloud first</b>

<span style="font-size: 1.5em;">[[GC_Security_Enterprise_Architecture | 5. Security and Privacy Architecture]]</span> <br><br>

<span style="font-size: 1.5em;">5. Security and Privacy Architecture</span> <br><br>

<b>Build Security into the Full System Life Cycle, Across All Architectural Layers</b>

<b>Build Security into the Full System Life Cycle, Across All Architectural Layers</b>