Changes

GC Enterprise Architecture/Framework (view source)

Revision as of 11:55, 10 September 2019

83 bytes added , 11:55, 10 September 2019

m

Add not around formatting for changes to standard

Line 23: Line 23:

<h3> This is a draft copy of the proposed updates to the GC EA standards </h3>

+

Changes from the [[Government of Canada Architectural Standards|previous version]] are marked as ''italic and underlined''

Line 33: Line 35:

[[GC_Business_Enterprise_Architecture | 1. Business Architecture]]

−

Fulfillment to the needs of the stakeholders to the Government of Canada </b~~></u~~>

+

Fulfillment to the needs of the stakeholders to the Government of Canada

* Understand stakeholders well, conduct stakeholder analysis and create stakeholder mapping for each service being delivered

* Ensure stakeholders' needs are clearly identified and captured for each service

Line 41: Line 43: −

Focus on Business Outcome and Strategic Alignment to the Department and to the Government of Canada </b~~></u~~>

+

Focus on Business Outcome and Strategic Alignment to the Department and to the Government of Canada

* Establish business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps

* Use tools, such as Value Stream, to ensure business outcomes are achieved through services being delivered

Line 49: Line 51: −

Horizontal Enablement </b~~></u~~>

+

Horizontal Enablement

* Use business processes developed to identify common enterprise processes

−

* Optimize common enterprise processes and maximize its re-use

+

* Optimize common enterprise processes and maximize its re-use

* Encourage and use a process (for example: Test Driven Development (TDD)) to improve the trust between Business and IT

Line 73: Line 75:

* Ensure data is collected in a manner that maximizes use and availability of data

* Ensure data collected aligns to existing enterprise and international standards

−

* Ensure that gender diversity and inclusion is considered according to the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices. The government is moving toward defaulting to gender, sex by exception, and adding a third gender option in a respectful and inclusive manner. This involves making changes in the front end (collection) and the back end (coding, display). For collecting information, the recommended approach is to offer the options “male”, “female” or the third option of “another gender”. If there is a need for more specificity and the capacity for analysis, add a write in option labelled “Please Specify”. </I~~></u~~>

+

* Ensure that gender diversity and inclusion is considered according to the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices. The government is moving toward defaulting to gender, sex by exception, and adding a third gender option in a respectful and inclusive manner. This involves making changes in the front end (collection) and the back end (coding, display). For collecting information, the recommended approach is to offer the options “male”, “female” or the third option of “another gender”. If there is a need for more specificity and the capacity for analysis, add a write in option labelled “Please Specify”.

* Where enterprise or international standards don't exist, develop Standards in the open with key subject matter experts and consultation with Enterprise Data Community of Practice.

* Ensure collection of data yields high quality data as per data quality guidelines

Line 83: Line 85:

Data Management

−

* Demonstrate alignment with enterprise and departmental data governance, architecture, strategies, and reference models</I~~></u~~>

+

* Demonstrate alignment with enterprise and departmental data governance, architecture, strategies, and reference models

* Where appropriate align data to existing common vocabulary

* Ensure metadata is captured and defined to maximize discovery and availability

Line 92: Line 94:

Data Storage

−

* Only handle data which is essential to your service. Do not store all data that you capture unless absolutely necessary</i~~></u~~>

+

* Only handle data which is essential to your service. Do not store all data that you capture unless absolutely necessary

−

* Ensure data is stored in a secure manner in accordance with CSE approved cryptographic algorithms and protocols and legislation such as</I~~></u~~> the Privacy Act

+

* Ensure data is stored in a secure manner in accordance with CSE approved cryptographic algorithms and protocols and legislation such as the Privacy Act

* Retain data for the minimum time necessary. Follow existing retention and disposition schedules

* Ensure data is stored in a way to facilitate easy data discoverability, accessibility and interoperability

Line 104: Line 106:

Data Sharing

−

* Data should be shared openly by default as per the Directive on Open Government while taking into consideration existing laws and regulations related to the safeguarding of data, while permitting free and open access</I~~></u~~>

+

* Data should be shared openly by default as per the Directive on Open Government while taking into consideration existing laws and regulations related to the safeguarding of data, while permitting free and open access

* Ensure government-held data can be combined with data from other sources enabling interoperability and interpretability through for internal and external use

* Reduce existing data where possible

* Encourage data sharing and collaboration

−

* Validate or transform all external input before processing</I~~></u~~>

+

* Validate or transform all external input before processing

|}

Line 134: Line 136:

* Work across the entire application lifecycle, from development and testing to deployment and operations

* Ensure quality and security is underpinning the Software Development Lifecycle

−

* Total Cost Of Ownership (TCO) should include the cost for design, construction, operation, and maintenance of a system. For example Training, Support, Disaster Recovery, and Retirement Cost</I~~></u~~>

+

* Total Cost Of Ownership (TCO) should include the cost for design, construction, operation, and maintenance of a system. For example Training, Support, Disaster Recovery, and Retirement Cost

Line 142: Line 144:

* Establish business and IT metrics to enable business outcomes

* Apply oversight and lifecycle management to digital investments through governance

−

* Complete an Algorithmic Impact Assessment (AIA) for systems automating decisions as per the [https://tbs-sct.gc.ca/pol/doc-eng.aspx?id=32592 Directive on Automated Decision-Making].</u~~></I~~>

+

* Complete an Algorithmic Impact Assessment (AIA) for systems automating decisions as per the [https://tbs-sct.gc.ca/pol/doc-eng.aspx?id=32592 Directive on Automated Decision-Making].

Maximize Reuse

−

* Reduce integration Complexity - design systems to be highly modular and loosely coupled to be able to reuse components. </I~~></u~~>

+

* Reduce integration Complexity - design systems to be highly modular and loosely coupled to be able to reuse components.

* Leverage and reuse existing solutions, components, and processes

* Select enterprise and cluster solutions over department-specific solutions

Nick.schonning

2,055

edits

Changes

GC Enterprise Architecture/Framework (view source)

Revision as of 11:55, 10 September 2019

Navigation menu

Search