GC Enterprise Architecture/Framework/BusinessGuide

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.

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

• clearly identify internal and external users and other stakeholders and their needs for each policy, program and business service

   How to achieve:
    * 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
   Tools:
    * Business Case
    * Stakeholder requirements 
    * Outcomes
    * Stakeholders (Actors, Roles, Organizational Units)
    * 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

   How to achieve:
    * 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
   Tools:
    * 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

   How to achieve:
    * 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
   Tools:
    * AIA Results (Conceptual)

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

   How to achieve:
    * Outline the GC/Departmental Strategies the architect aligns and/or implements
    * Describe the architecture's contribution to realizing the appropriate outcomes of the strategy
   Artifacts:
    * Drivers
    * Outcomes (intimidate and ultimate)
    * Business services (External)

• establish metrics for identified business outcomes throughout the life cycle of an investment

   How to achieve:
    * 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.
   Tools:
    * Value Stream (Measure KPI linked to benefits outcomes and objectives

• translate business outcomes and strategy into business capability implications in the GC Business Capability Model to establish a common vocabulary between business, development, and operation

   How to achieve:
    * Outline the business capabilities involved in achieving each outcome
   Tools:
    * 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

   How to achieve:
    * 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)
   Tools:
    * 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

   How to achieve:
    * Describe the plan and approach to standardize the realization of the business capability so it can be reused within the department and GC
   Tools:
    * 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

   How to achieve:
    * Outline the plan to allow other public sector organizations to reuse the common capability
   Tools:
    * Business Capability Heat Map
    * Projects to Value Stream Script