Archived [2020-03-31] - Directive on Management of Information Technology

Information technology (IT) enables the federal government to effect operations and service transformation. IT matters strategically for increasing government productivity and enhancing government services to the public for the benefit of citizens, businesses, taxpayers and employees.
Date modified: 2019-08-02

Supporting tools



Mandatory procedures:



This directive replaces:

View all inactive instruments
Print-friendly XML

The Directive on Management of Information Technology is no longer in effect. It was replaced by the Directive on Service and Digital and the Policy on Service and Digital on April 1, 2020.

Appendix C - Mandatory Procedures for Enterprise Architecture Assessment

  • C.1These procedures take effect on December 1, 2018.
  • C.2Procedures
    • C.2.1These procedures provide details on the requirements set out in section 6.1.1 of the Directive on Management of Information Technology.
    • C.2.2These procedures will be used by Departmental Enterprise Architecture Review Boards and the Government of Canada Enterprise Architectural Review Board as an assessment framework to review digital initiatives to ensure the GC acts as a single enterprise and to ensure departmental alignment with the Government of Canada digital direction.
    • C.2.3Mandatory procedures are as follows:
      • Business Architecture
        • C.2.3.1Align to the GC Business Capability model
          • C. program services as business capabilities to establish a common vocabulary between business, development, and operation
          • C. capabilities that are common to the GC enterprise and can be shared and reused
          • C. business processes using Business Process Management Notation (BPMN) to identify common enterprise processes
        • C.2.3.2Design for Users First and Deliver with Multidisciplinary Teams
          • C. on the needs of users, using agile, iterative, and user-centred methods
          • C. to both accessibility and official languages requirements
          • C. all skillsets required for delivery, including for requirements, design, development, and operations
          • C. across the entire application lifecycle, from development and testing to deployment and operations
          • C. quality is considered throughout the Software Development Lifecycle
          • C. accountability for privacy is clear
          • C. and adopt Test Driven Development (TDD) to improve the trust between Business and IT
        • C.2.3.3Design Systems to be Measurable and Accountable
          • C. performance expectations for each IT service
          • C. an audit trail available for all transactions to ensure accountability and non repudiation
          • C. business and IT metrics to enable business outcomes
          • C. oversight and lifecycle management to digital investments through governance
      • Information Architecture
        • C.2.3.4Data Collection
          • C. data is collected in a manner that maximizes use and availability of data
          • C. data collected aligns to existing enterprise and international standards
          • C. enterprise or international standards don't exist, develop Standards in the open with key subject matter experts
          • C. collection of data yields high quality data as per data quality guidelines
          • C. data is collected through ethical practices supporting appropriate citizen and business-centric use
          • C. should only be purchased once and should align with international standards
          • C. necessary, ensure collaboration with department/ agency data stewards/ custodians, other levels of government, and Indigenous people
        • C.2.3.5Data Management
          • C. alignment with enterprise and departmental data governance and strategies
          • C. accountability for data roles and responsibilities
          • C. to maximize data use and availability
        • C.2.3.6Data Storage
          • C. data is stored in a secure manner in accordance with the National Cyber Security Strategy, and the Privacy Act
          • C. existing retention and disposition schedules
          • C. data is stored in a way to facilitate easy data discoverability, accessibility, and interoperability
        • C.2.3.7Data Sharing
          • C. should be shared openly by default as per the Directive on Open Government
          • C. government-held data can be combined with data from other sources enabling interoperability and interpretability through for internal and external use
          • C. the collection of redundant data
          • C. existing data where possible
          • C. data sharing and collaboration
      • Application Architecture
        • C.2.3.8Use Open Standards and Solutions by Default
          • C. possible, use open standards and open source software first
          • C. an open source option is not available or does not meet user needs, favour platform-agnostic COTS over proprietary COTS, avoiding technology dependency, allowing for substitutability and interoperability
          • C. a custom-built application is the appropriate option, by default any source code written by the government must be released in an open format via Government of Canada websites and services designated by the Treasury Board of Canada Secretariat
          • C. source code must be released under an appropriate open source software license
          • C. public data to implement Open Data and Open Information initiatives
        • C.2.3.9Maximize Reuse
          • C. and reuse existing solutions, components, and processes
          • C. enterprise and cluster solutions over department-specific solutions
          • C. simplification by minimizing duplication of components and adhering to relevant standards
          • C. the GC EARB about departmental investments and innovations
          • C. code publicly when appropriate, and when not, share within the Government of Canada
        • C.2.3.10Enable Interoperability
          • C. all functionality as services
          • C. microservices built around business capabilities. Scope each service to a single purpose
          • C. each IT service in its own process and have it communicate with other IT services through a well-defined interface, such as an HTTPS-based application programming interface (API) as per Appendix D: Mandatory Procedures for Application Programming Interfaces
          • C. applications in containers
          • C. the GC Digital Exchange Platform for components such as the API Store, Messaging, and the GC Service Bus
      • Technology Architecture
        • C.2.3.11Use Cloud first
          • C. this order of preference: Software as a Service (SaaS) first, then Platform as a Service (PaaS), and lastly Infrastructure as a Service (IaaS)
          • C. this order of preference: Public cloud first, then Hybrid cloud, then Private cloud, and lastly non-cloud (on-premises) solutions
          • C. for cloud mobility and develop an exit strategy to avoid vendor lock-in
        • C.2.3.12Design for Performance, Availability, and Scalability
          • C. for resiliency
          • C. response times meet user needs for availability
          • C. zero-downtime deployments for planned and unplanned maintenance
          • C. distributed architectures, assume failure will happen, handle errors gracefully, and monitor actively
      • Security Architecture and Privacy
        • C.2.3.13Design for Security and Privacy
          • C. security across all architectural layers
          • C. data properly to determine appropriate safeguards
          • C. a privacy impact assessment (PIA) and mitigate all privacy risks when personal information is involved
          • C. user and business needs with proportionate security measures and adequate privacy protections.
Date modified: