514
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: − + Line 17:
Line 17: − + + + + + + − + + + + + + + + + + + + + + Line 62:
Line 80: + + + + + + + + + + + + + + + + + + + + + + + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GC Enterprise Architecture/Playbook (view source)
Revision as of 17:37, 8 January 2020
, 17:37, 8 January 2020no edit summary
<i><h3> This is a <b><u>DRAFT COPY</u></b> of the proposed GC EA Playbook. It is a work IN PROGRESS, and has not undergone any review. </h3></i>
<i><h3> This is a <b><u>DRAFT COPY</u></b> of the proposed GC EA Playbook. It is a work IN PROGRESS, and has not undergone any review. </h3></i>
<h2> INTRODUCTION - How to use the Playbook</h2>
<h2> INTRODUCTION - How to use the Playbook</h2><br>
This EA Playbook is intended to help Enterprise Architects build their departmental Enterprise Architecture.
This EA Playbook is intended to help Enterprise Architects build their departmental Enterprise Architecture.
<h2> The Plays </h2> <br><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;">[[GC_Business_Enterprise_Architecture | 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 the external service. 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.
<b>Fulfill the Government of Canada stakeholder's needs</b>
* Clearly identify internal and external stakeholders and their needs for each business service including user centric design
* Include policy requirement applying to specific stakeholder groups, such as accessibilities, gender based+ analysis, and official languages in the creation of the service
* Model end-to-end business service delivery to provide quality, maximize effectiveness and optimize efficiencies across all channels (e.g lean process)
<span style="font-size: 1.5em;">[[GC_Information_Enterprise_Architecture | 2. Information Architecture]]</span> <br>
<b>Architect to be Outcome Driven and Strategically Aligned to the Department and to the Government of Canada</b>
* Identify which departmental/GC business services, outcomes and strategies will be addressed
* Establish metrics for identified business outcomes throughout the lifecycle of an investment
* 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
<b> Promote Horizontal Enablement of the Enterprise</b>
* Identify opportunities to horizontally enabled business services and provide cohesive experience to stakeholders
* Reuse common business capabilities and processes from across government and private sector
* Publish in the open reusable common business capabilities and processes (in the Open Government portal) for others to develop cohesive horizontal enterprise services
<span style="font-size: 1.5em;">[[GC_Information_Enterprise_Architecture | 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>
* Ensure that combined data does not risk identification or re-identification of sensitive or personal information
* Ensure that combined data does not risk identification or re-identification of sensitive or personal information
** Do you have a risk assessment process or mechanism in place to ensure that combining two or more datasets does not risk compromising the privacy and security of individuals by exposing sensitive or personal information?
** Do you have a risk assessment process or mechanism in place to ensure that combining two or more datasets does not risk compromising the privacy and security of individuals by exposing sensitive or personal information?
<span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br>
<span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br>
<b>Use Open Source Solutions hosted in Public Cloud</b>
* Select existing solutions that can be reused over custom built
* Contribute all improvements back to the communities
* Register Open Source software to the Open Resource Exchange
<br>
<b>Use Software as a Service (SaaS) hosted in Public Cloud</b>
* Choose SaaS that best fit for purpose based on alignment with SaaS capabilities
* Choose a SaaS solution that is extendable
* Configure SaaS and if customization is necessary extend as Open Source modules
<br>
<b>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b>
* Design systems as highly modular and loosely coupled services
* Expose services through APIs
* Make the APIs discoverable to the appropriate stakeholders
<br>
<b>Follow DevSecOps Principles</b>
* Use continuous integration and continuous deployments (CI/CD)
* Ensure automated testing occurs for security and functionality
* Include your stakeholders as part of DevSecOps process
<span style="font-size: 1.5em;">[[GC_Technology_Enterprise_Architecture | 4. Technology Architecture]]</span> <br><br>
<span style="font-size: 1.5em;">[[GC_Technology_Enterprise_Architecture | 4. Technology Architecture]]</span> <br><br>
<span style="font-size: 1.5em;">[[GC_Security_Enterprise_Architecture | 5. Security Architecture]]</span> <br><br>
<b>Use Cloud first</b>
* Adopt the Use of the GC Accelerators to ensure proper Security and Access Controls
* Enforce this order of preference: Software as a Service (SaaS) first, then Platform as a Service (PaaS), and lastly Infrastructure as a Service (IaaS)
* Fulfill Cloud Services through SSC Cloud Brokering Services
* Enforce this order of preference: Public cloud first, then Hybrid cloud, then Private cloud, and lastly non-cloud (on-premises) solutions
* Design for cloud mobility and develop an exit strategy to avoid vendor lock-in
<br>
<b>Design for Performance, Availability, and Scalability</b>
* Ensure response times meet user needs, and critical services are highly available
* Support zero-downtime deployments for planned and unplanned maintenance
* Use distributed architectures, assume failure will happen, handle errors gracefully, and monitor <u><I>performance and behaviour </I></u> actively
* Establish architectures that supports new technology insertion with minimal disruption to existing programs and services
* Control Technical Diversity - design systems based on modern technologies and platforms already in use
<span style="font-size: 1.5em;">[[GC_Security_Enterprise_Architecture | 5. Security and Privacy Architecture]]</span> <br><br>
<b>Build Security into the Full System Life Cycle, Across All Architectural Layers</b>
* Identify and classify risks associated to the service’s business objectives, goals, and strategy
* Design security measures according to business and user needs, risks identified, and security categorization of the information and assets; integrate security across all architectural layers (BIAT)
* Design systems to not be susceptible to common security vulnerabilities; resilient and can be rebuilt quickly in the event of compromise; and fail secure if the system encounters an error or crashes
* Ensure that data received from external parties is profiled and validated prior to its use
<br>
<b>Ensure Secure Access to Systems and Services</b>
* Identify and authenticate individuals, processes and/or devices to an appropriate level of assurance before granting access to information and services
* Constrain service interfaces to authorized entities (users and devices), with clearly defined roles
* Make use of modern password guidance, and prioritizing length over complexity, eliminating expiry, and blacklisting common passwords
<br>
<b>Maintain Secure Operations</b>
* Integrate aggregate outputs from security assessment and authorization activities into security architecture lifecycle processes, to ensure reference artefacts remain relevant and valid
* Design processes to operate and manage services securely, and continuously monitor system events and performance in order to detect, prevent, and respond to attacks
* Establish processes to monitor security advisories, and apply security-related patches and updates to reduce exposure to vulnerabilities. Apply appropriate risk-based mitigations when patches can’t be applied
<br>
<b> Privacy by Design </b>
* Perform a privacy impact assessment (PIA) to support risk mitigation activities when personal information is involved
* Implement security measures to assure the protection of personal information
* Take into consideration the <b>[https://www.ryerson.ca/pbdce/certification/seven-foundational-principles-of-privacy-by-design/ 7 Foundational Privacy Design Principles] </b> when designing services
