Changes

GC Enterprise Architecture/Framework (view source)

Revision as of 14:03, 20 August 2019

742 bytes added , 14:03, 20 August 2019

no edit summary

Line 36: Line 36:

* Identify capabilities that are common to the GC enterprise and can be shared and reused

* Model business processes using Business Process Management Notation (BPMN) to identify common enterprise processes

−

* Establish the business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps</u~~></I~~>

+

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

−

* Translate the business strategy into business capability implications using the GC Business Capability Model. Use these to guide investments.</u~~></I~~>

+

* Translate the business strategy into business capability implications using the GC Business Capability Model. Use these to guide investments.

Design for Users First and Deliver with Multidisciplinary Teams

Line 45: Line 45:

* 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

* Ensure accountability for privacy is clear

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

Line 68: Line 68:

* 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

+

* 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

* Ensure data is collected through ethical practices supporting appropriate citizen and business-centric use

Line 75: Line 75:

* Where necessary, ensure collaboration with department/agency data stewards/custodians, other levels and jurisdiction of government and indigenous people

* Reduce the collection of redundant data

+

* ''Ensure provisions are in place for Data access when using third-party contracting services. '''(may revise section to Business Arch?)'''''

Data Management

−

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

+

* 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''

* Ensure accountability for data roles and responsibilities

* Design to maximize data use and availability

Line 84: Line 87:

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

+

Data Use

+

* ''Ensure that data is used in an Ethical and Secure manner''

+

* ''Maximize re-usability where appropriate''

+

* ''Ensure that combined data does not risk identification or re-identification of sensitive or personal information''

+

* ''Ensure the data is fit for the use it is employed for in accordance with data quality guidelines''

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 114: Line 122:

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

Line 196: Line 204:

* Implement security measures to assure the protection of personal information

* Take into consideration the [https://www.ryerson.ca/pbdce/certification/seven-foundational-principles-of-privacy-by-design/ 7 Foundational Privacy Design Principles] when designing services.

−

</I~~></u~~>

+

|}

Vivian.nobrega

101

edits