View source for GC Enterprise Architecture/Framework/BusinessGuide


<multilang>
@en|

== Business architecture ==
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.
<br>
=== Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs === 

* <b>Clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service</b>

In order to ensure that a service will be able to meet the users and stakeholders' needs, it needs to understand what needs it is trying to provide service for, who their users and stakeholders are, both internal and external. <br>
Once the needs, the users and stakeholders are defined, then a service provider can proceed to create a stakeholder mapping to further understand the relationship between the service and the users & stakeholders, ie. how a change in one component impacts the other. <br>
From there, the service provider 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 or value mapping). <br>
This exercise can also help define the limitation/scope of the program/policy/service to better manage the expectation of their users/stakeholders.

    <b>How to demonstrate that the project fulfils this framework:</b>
     * summarize the needs and outcome of each key external and internal stakeholders in scope of the architecture
     * demonstrate how the architecture is focused on the needs and outcomes of internal and external stakeholders
    <b>Tools:</b>
     * Business Case
     * Stakeholder (Actors, Roles, Organizational Units) Mapping & Stakeholder requirements 
     * Outcomes
     * business process
     * Value Stream and Value Mapping

* include policy requirement applying to specific users and other stakeholder groups, such as accessibility, gender-based plus analysis, and official languages in the creation of the service
    <b>How to achieve:</b>
     * 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 how architecture supports full spectrum of service design and user experience
    <b>Tools:</b>
     * 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''
    <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)
* 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>
     * 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>
     * Business Impact Assessment
     * Value Stream and Value Mapping

=== 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
    <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
    <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
    <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 ===
* 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
    <b>How to achieve:</b>
     * 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>
     * Projects to value Stream Script
     * Business Capability Heat map
* publish in the open all reusable common business capabilities, processes and enterprise solutions for others to develop and leverage cohesive horizontal enterprise services
    <b>How to achieve:</b>
     * Outline the plan to allow other public sector organizations to reuse the common capability
    <b>Tools:</b>
     * Business Capability Heat Map
     * Projects to Value Stream Script


@fr|


=== Architecture opérationnelle ===
L’architecture opérationnelle est un aspect essentiel à la réussite de la mise en œuvre de l’architecture cible de l’écosystème intégré du GC. La stratégie architecturale préconise une approche pangouvernementale où les TI sont harmonisées avec les services opérationnels et les solutions sont fondées sur des composantes réutilisables mettant en œuvre des capacités opérationnelles afin d’offrir une expérience utilisateur cohérente. Par conséquent, il est essentiel de bien comprendre les services aux entreprises, les besoins des intervenants, les possibilités d’améliorer la cohésion et les possibilités de réutilisation à l’échelle du gouvernement. Par le passé, ces éléments n’étaient pas une priorité. On s’attend à ce que la culture et les pratiques en matière de TI doivent changer pour que l’architecture opérationnelle, en général, et ces éléments soient une priorité.
{| class="wikitable"
|'''Conception entièrement numérique des services pour répondre aux besoins des utilisateurs du gouvernement du Canada et des autres intervenants'''
|
* Identifier clairement les utilisateurs internes et externes et les autres intervenants et leurs besoins dans le cadre de chaque politique, programme et service opérationnel;
* Inclure les exigences de la politique qui s’appliquent à des utilisateurs en particulier et à d’autres groupes d’intervenants, comme l’accessibilité, l’analyse comparative entre les sexes plus et les langues officielles, dans la création du service;
* Effectuer une évaluation de l’incidence algorithmique (EIA) pour appuyer les activités d’atténuation des risques lors du déploiement d’un système décisionnel automatisé conformément à la Directive sur la prise de décisions automatisée;
* Modéliser la prestation de services opérationnels du début à la fin afin d’assurer la qualité, de maximiser l’efficacité et d’optimiser les gains d’efficience dans tous les canaux (p. ex., processus allégé).
|-
|'''Architecte axé sur les résultats et stratégiquement aligné sur le Ministère et le gouvernement du Canada'''
|
* Déterminer les services opérationnels, les résultats et les stratégies du Ministère et du GC qui seront abordés;
* Établir des mesures pour les résultats opérationnels déterminés tout au long du cycle de vie d’un investissement;
* Traduire les résultats opérationnels et la stratégie en répercussions sur les capacités opérationnelles dans le modèle des capacités opérationnelles du GC pour établir un vocabulaire commun entre les organisations, le développement et les opérations.
|-
|'''Promotion de l’habilitation horizontale de l’entreprise'''
|
* Repérer les possibilités de rendre possibles des services opérationnels horizontaux à l’échelle du GC et d’offrir une expérience cohésive aux utilisateurs et aux autres intervenants;
* Réutiliser les capacités opérationnelles, les processus et les solutions d’entreprise communs provenant de l’ensemble du gouvernement et du secteur privé;
* Publier en mode ouvert tous les processus, les capacités et les solutions d’entreprise communs réutilisables pour que les autres puissent élaborer et tirer parti de services d’entreprise horizontaux cohérents.
|}

</multilang>